Oh, sorry, actually there is no error. The puppetmaster is not running yet. I just wanted to check out a little bit what the log would like like. However, I found that strange that if puppet can't connect to the puppetmaster, there is no complaint (in a log) about it...
On 28 January 2011 12:50, Felix Frank <felix.fr...@alumni.tu-berlin.de>wrote: > On 01/28/2011 11:54 AM, Romain Pelisse wrote: > > Well, this was my assumption. I did so, but no messages end up in > > /var/log/puppet/ (as configured in the puppet.conf), which I find weird > > because my puppet is currently unable to connect to the puppetmaster ! > > So it should fill the log with a failure every half an hour... > > If the error hits you before a connection is made, the puppet master > wouldn't notice there is anything to log. > > In such circumstances, I prefer launching an undaemonized master on a > different port and connecting to that from the client's commandline. > > What's the error reported by the client? > > Regards, > Felix > -- Romain PELISSE, *"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett* http://belaran.eu/wordpress/belaran -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
