Puppetmaster is filling up /var/log/messages even though logdir is set to /var/puppet/log/ and masterlog = /var/puppet/log/puppetmaster.log. There is however no file /var/puppet/log/puppetmaster.log These are the messages being filled in /var/log/messages: Apr 30 17:41:44 server puppetmasterd[97213]: Compiled catalog for client in 0.19 seconds Apr 30 17:42:24 server puppetmasterd[97213]: Compiled catalog for client in 0.19 seconds Apr 30 17:42:39 server puppetmasterd[97213]: Compiled catalog for client in 0.13 seconds Apr 30 17:43:01 server puppetmasterd[97213]: Compiled catalog for client in 0.21 seconds Apr 30 17:43:19 server puppetmasterd[97213]: Compiled catalog for client in 0.31 seconds Apr 30 17:43:33 server puppetmasterd[97213]: Compiled catalog for client in 0.22 seconds Apr 30 17:43:39 server puppetmasterd[97213]: Compiled catalog for client in 0.29 seconds Apr 30 17:43:41 server puppetmasterd[97213]: Compiled catalog for client in 0.19 seconds Apr 30 17:43:42 server puppetmasterd[97213]: Compiled catalog for client in 0.15 seconds Apr 30 17:43:55 server puppetmasterd[97213]: Compiled catalog for client in 0.18 seconds The names of the hosts have been changed to protect the innocent. Puppetmaster is version 24.8 and running on FreeBSD 7.2. -- 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.
Peter Meier
2010-Apr-30 19:04 UTC
Re: [Puppet Users] Puppetmaster filing up /var/log/messages
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> The names of the hosts have been changed to protect the innocent. > > Puppetmaster is version 24.8 and running on FreeBSD 7.2.can you check how your puppetmaster is started? sometimes init script add additional cli parameters which overwrite what the config says. otherwise: can you try and start the puppetmaster with --debug --verbose and see if tells something? cheers pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvbKZ8ACgkQbwltcAfKi3/ikQCff1nJ1taWOoeORYb1T2k0T440 2LgAoKf0pU6APiODSxeEKlBqMM8ddDZc =yNHp -----END PGP SIGNATURE----- -- 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 can''t find anywhere where the configs are overridden. I was able to fix the issue by starting puppetmaster with the command: puppetmasterd -l /var/puppet/log/puppetmaster.log but it still concerns me that the config file is not read, even if I point to it directly, by starting it with: puppetmasterd /usr/local/etc/puppet/puppet.conf However, if I open it in debug mode, it says: [root@server /usr/local/etc/rc.d]# puppetmasterd --no-daemonize -- debug --verbose /usr/local/etc/puppet/puppet.conf info: Starting server for Puppet version 0.24.8 debug: Creating default schedules debug: Failed to load library ''ldap'' for feature ''ldap'' debug: Failed to load library ''shadow'' for feature ''libshadow'' debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/serial]: Autorequiring File[/usr/local/etc/ puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[main]/ File[/var/puppet/log]: Autorequiring File[/var/puppet] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/usr/ local/etc/puppet/ssl/certs] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/public_keys]: Autorequiring File[/usr/ local/etc/puppet/ssl] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/certs/server.pem]: Autorequiring File[/ usr/local/etc/puppet/ssl/certs] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/requests]: Autorequiring File[/usr/local/ etc/puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/private]: Autorequiring File[/usr/local/ etc/puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring File[/usr/ local/etc/puppet/ssl/ca/private] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca]: Autorequiring File[/usr/local/etc/puppet/ ssl] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[main]/ File[/usr/local/etc/puppet/ssl]: Autorequiring File[/usr/local/etc/ puppet] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/private]: Autorequiring File[/usr/local/ etc/puppet/ssl] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/signed]: Autorequiring File[/usr/local/etc/ puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/private_keys/server.pem]: Autorequiring File[/usr/local/etc/puppet/ssl/private_keys] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/public_keys/server.pem]: Autorequiring File[/usr/local/etc/puppet/ssl/public_keys] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/usr/local/ etc/puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/ca_crt.pem]: Autorequiring File[/usr/local/ etc/puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[main]/ File[/var/puppet/state]: Autorequiring File[/var/puppet] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[main]/ File[/var/puppet/lib]: Autorequiring File[/var/puppet] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/private_keys]: Autorequiring File[/usr/ local/etc/puppet/ssl] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring File[/usr/local/ etc/puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/inventory.txt]: Autorequiring File[/usr/ local/etc/puppet/ssl/ca] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ssl]/ File[/usr/local/etc/puppet/ssl/certs]: Autorequiring File[/usr/local/ etc/puppet/ssl] debug: /Settings[/usr/local/etc/puppet/puppet.conf]/Settings[ca]/File[/ usr/local/etc/puppet/ssl/ca/ca_crl.pem]: Autorequiring File[/usr/local/ etc/puppet/ssl/ca] debug: Finishing transaction 337156560 with 0 changes So it appears that it is still not reading the line: masterlog = /var/puppet/log/puppetmaster.log On Apr 30, 3:04 pm, Peter Meier <peter.me...@immerda.ch> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > The names of the hosts have been changed to protect the innocent. > > > Puppetmaster is version 24.8 and running on FreeBSD 7.2. > > can you check how your puppetmaster is started? sometimes init script > add additional cli parameters which overwrite what the config says. > > otherwise: can you try and start the puppetmaster with --debug --verbose > and see if tells something? > > cheers pete > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ > > iEYEARECAAYFAkvbKZ8ACgkQbwltcAfKi3/ikQCff1nJ1taWOoeORYb1T2k0T440 > 2LgAoKf0pU6APiODSxeEKlBqMM8ddDZc > =yNHp > -----END PGP SIGNATURE----- > > -- > 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 athttp://groups.google.com/group/puppet-users?hl=en.-- 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.
Nigel Kersten
2010-May-03 14:52 UTC
Re: [Puppet Users] Puppetmaster filing up /var/log/messages
On Fri, Apr 30, 2010 at 9:47 AM, JoE <joehillen@gmail.com> wrote:> Puppetmaster is filling up /var/log/messages even though logdir is set > to /var/puppet/log/ and masterlog = /var/puppet/log/puppetmaster.log. > There is however no file /var/puppet/log/puppetmaster.log >What is logdest set to? It sounds like logdest is set to syslog and you don''t have a syslog destination set up?> > These are the messages being filled in /var/log/messages: > Apr 30 17:41:44 server puppetmasterd[97213]: Compiled catalog for > client in 0.19 seconds > Apr 30 17:42:24 server puppetmasterd[97213]: Compiled catalog for > client in 0.19 seconds > Apr 30 17:42:39 server puppetmasterd[97213]: Compiled catalog for > client in 0.13 seconds > Apr 30 17:43:01 server puppetmasterd[97213]: Compiled catalog for > client in 0.21 seconds > Apr 30 17:43:19 server puppetmasterd[97213]: Compiled catalog for > client in 0.31 seconds > Apr 30 17:43:33 server puppetmasterd[97213]: Compiled catalog for > client in 0.22 seconds > Apr 30 17:43:39 server puppetmasterd[97213]: Compiled catalog for > client in 0.29 seconds > Apr 30 17:43:41 server puppetmasterd[97213]: Compiled catalog for > client in 0.19 seconds > Apr 30 17:43:42 server puppetmasterd[97213]: Compiled catalog for > client in 0.15 seconds > Apr 30 17:43:55 server puppetmasterd[97213]: Compiled catalog for > client in 0.18 seconds > > The names of the hosts have been changed to protect the innocent. > > Puppetmaster is version 24.8 and running on FreeBSD 7.2. > > -- > 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. > >-- nigel -- 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.
Peter Meier
2010-May-03 15:48 UTC
Re: [Puppet Users] Re: Puppetmaster filing up /var/log/messages
> However, if I open it in debug mode, it says: > [root@server /usr/local/etc/rc.d]# puppetmasterd --no-daemonize -- > debug --verbose /usr/local/etc/puppet/puppet.confshouldn''t you use: # puppetmasterd --no-daemonize --debug --verbose --config /usr/local/etc/puppet/puppet.conf ? cheers pete -- 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.