Hi! When I issue $ puppetmasterd --no-daemonize --verbose I get very neat and clear log to STDIN. But I can''t figure out how to get this log when I start puppetmasterd without --no-daemonize option. Is it possible? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Thu, Jan 27, 2011 at 16:17, Sergey V. Arlashin <arlashin.maillists@gmail.com> wrote:> When I issue > $ puppetmasterd --no-daemonize --verbose > > I get very neat and clear log to STDIN. But I can''t figure out how to get > this log when I start puppetmasterd without --no-daemonize option. Is it > possible?To STDOUT? You can pass ''--logdest console'' to override the default, which is that we log to syslog if you are daemonized, and to the console if not. The effect of ''--verbose'' is independent of where the logs are sent, though, so you will get the same data to whatever log destination is configured. Regards, Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <daniel@puppetlabs.com> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 28 January 2011 11:17, Sergey V. Arlashin <arlashin.maillists@gmail.com>wrote:> Hi! > When I issue > $ puppetmasterd --no-daemonize --verbose > > I get very neat and clear log to STDIN. But I can''t figure out how to get > this log when I start puppetmasterd without --no-daemonize option. Is it > possible? >You can log to a file with logdest - but doesn''t buffer correctly. Watch https://projects.puppetlabs.com/issues/4139 John -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On this topic, I was searching earlier how to add the --verbose to the puppet.conf, so that when puppet is running as a service the log in /var/log/puppet are more verbosy... On 28 January 2011 01:43, John Warburton <jwarburton@gmail.com> wrote:> On 28 January 2011 11:17, Sergey V. Arlashin <arlashin.maillists@gmail.com > > wrote: > >> Hi! >> When I issue >> $ puppetmasterd --no-daemonize --verbose >> >> I get very neat and clear log to STDIN. But I can''t figure out how to get >> this log when I start puppetmasterd without --no-daemonize option. Is it >> possible? >> > > You can log to a file with logdest - but doesn''t buffer correctly. Watch > https://projects.puppetlabs.com/issues/4139 > > John > > -- > 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I think you can just add "verbose=true" in the master section of /etc/puppet/puppet.conf On Jan 27, 2011, at 5:14 PM, Romain Pelisse wrote:> On this topic, I was searching earlier how to add the --verbose to the puppet.conf, so that when puppet is running as a service the log in /var/log/puppet are more verbosy... > > On 28 January 2011 01:43, John Warburton <jwarburton@gmail.com> wrote: > On 28 January 2011 11:17, Sergey V. Arlashin <arlashin.maillists@gmail.com> wrote: > Hi! > When I issue > $ puppetmasterd --no-daemonize --verbose > > I get very neat and clear log to STDIN. But I can''t figure out how to get this log when I start puppetmasterd without --no-daemonize option. Is it possible? > > You can log to a file with logdest - but doesn''t buffer correctly. Watch https://projects.puppetlabs.com/issues/4139-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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... On 28 January 2011 06:18, Patrick <kc7zzv@gmail.com> wrote:> I think you can just add "verbose=true" in the master section of > /etc/puppet/puppet.conf > > On Jan 27, 2011, at 5:14 PM, Romain Pelisse wrote: > > On this topic, I was searching earlier how to add the --verbose to the > puppet.conf, so that when puppet is running as a service the log in > /var/log/puppet are more verbosy... > > On 28 January 2011 01:43, John Warburton <jwarburton@gmail.com> wrote: > >> On 28 January 2011 11:17, Sergey V. Arlashin < >> arlashin.maillists@gmail.com> wrote: >> >>> Hi! >>> When I issue >>> $ puppetmasterd --no-daemonize --verbose >>> >>> I get very neat and clear log to STDIN. But I can''t figure out how to get >>> this log when I start puppetmasterd without --no-daemonize option. Is it >>> possible? >>> >> >> You can log to a file with logdest - but doesn''t buffer correctly. Watch >> https://projects.puppetlabs.com/issues/4139 >> > -- > 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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 -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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.frank@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/28/2011 02:07 PM, Romain Pelisse wrote:> 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...I don''t comprehend at all. Which process do you expect to log an error each half hour? If the master is not running, it is only logical that the client cannot connect and that the master (not running) cannot log an error. I guess I''m misunderstanding this. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''m not making myself very clear also :) (as you are also in Berlin, you can realize my first question was rather late in the night ;) ) I do apologize. Here is an hopefully enlightening snippet: $ grep -e ''server'' /etc/puppet/puppet.conf server = puppetmaster $ ping puppetmaster (host down) # service puppet start ... So at this point the puppet client will not be able to connect, throwing something like that if run with --no-daemonize and --verbose : err: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Now, I was expecting to find those messages inside the /var/log/puppet/ folder, as I expected the clients to "check on" the master every 30 minutes... But, I''m starting to think I''m getting this wrong ? Maybe the puppetmaster is "pushing" to puppets every 30 minutes ? On 28 January 2011 14:18, Felix Frank <ff@mpexnet.de> wrote:> On 01/28/2011 02:07 PM, Romain Pelisse wrote: > > 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... > > I don''t comprehend at all. Which process do you expect to log an error > each half hour? > > If the master is not running, it is only logical that the client cannot > connect and that the master (not running) cannot log an error. > > I guess I''m misunderstanding this. >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 01/28/2011 02:36 PM, Romain Pelisse wrote:> I''m not making myself very clear also :) (as you are also in Berlin, > you can realize my first question was rather late in the night ;) ) > > I do apologize. Here is an hopefully enlightening snippet: > > $ grep -e ''server'' /etc/puppet/puppet.conf > server = puppetmaster > $ ping puppetmaster > (host down) > # service puppet start > ... > > So at this point the puppet client will not be able to connect, throwing > something like that if run with --no-daemonize and --verbose : > > err: Could not retrieve catalog from remote server: getaddrinfo: Name or > service not known > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > Now, I was expecting to find those messages inside the /var/log/puppet/ > folder, as I expected the clients to "check on" the master every 30 > minutes... But, I''m starting to think I''m getting this wrong ? Maybe the > puppetmaster is "pushing" to puppets every 30 minutes ?No, the clients are supposed to pull. What client version is this? I''ve seen 0.24.5 clients crash when the master went down, and seen 0.25.5 clients end up in a (apparent) sort of deadlock. No further logging in either scenario. I haven''t tried 2.6 yet. You''re right, though. The expected result would be a client log entry every half hour. Cheers, Felix -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
No, the clients are supposed to pull. What client version is this? I''ve seen 0.24.5 clients crash when the master went down, and seen 0.25.5 clients end up in a (apparent) sort of deadlock. No further logging in either scenario. I haven''t tried 2.6 yet. 0.25.5, lastest available for Fedora (well, actually I''m running with CentOS with RPM from Fedora) # puppetd --version 0.25.5 You''re right, though. The expected result would be a client log entry every half hour. Ok, this is confirmation is actually really helpful (I now know something is wrong and I know my premise not). -- 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 -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Ok, I found why : messages are going to /var/log/messages, not the /var/log/puppet folders... On 28 January 2011 14:52, Romain Pelisse <belaran@gmail.com> wrote:> No, the clients are supposed to pull. > > What client version is this? I''ve seen 0.24.5 clients crash when the > master went down, and seen 0.25.5 clients end up in a (apparent) sort of > deadlock. No further logging in either scenario. > > I haven''t tried 2.6 yet. > > 0.25.5, lastest available for Fedora (well, actually I''m running with > CentOS with RPM from Fedora) > # puppetd --version > 0.25.5 You''re right, though. The expected result would be a client log > entry > every half hour. > > > Ok, this is confirmation is actually really helpful (I now know > something is wrong and I know my premise not). > > -- > 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 > > > -- > 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 >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jan 28, 2011 7:56 AM, "Romain Pelisse" <belaran@gmail.com> wrote:> > Ok, I found why : messages are going to /var/log/messages, not the/var/log/puppet folders... Oh, good. Y''all found the reason. Pupput pretty uniformly defaults our logs to the console in interactive runs, and syslog if we daemonize. You can change that, including the syslog facility, or to use a file, on the command line or equivalently (because all options work that way) in the config files. Regards, Daniel -- Puppet Labs Developer –http://puppetlabs.com Daniel Pittman <daniel@puppetlabs.com> Contact me via gtalk, email, or phone: +1 (877) 575-9775 Sent from a mobile device. Please forgive me if this is briefer than usual. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.