puppet-server-0.24.8-1.el5.1 not writing logs

9 views
Skip to first unread message

Arnau Bria

unread,
Jun 9, 2009, 6:37:28 AM6/9/09
to puppet...@googlegroups.com
Hi all,

I've just updated my server to puppet-server-0.24.8-1.el5.1 (from epel)
and noticed that puppet-server stopped writing in its log:

# tail -f /var/log/puppet/puppetmaster.log
Tue Jun 09 12:28:48 +0200 2009 Puppet (notice): Shutting down
Tue Jun 09 12:28:51 +0200 2009 Puppet (notice): Reopening log files
Tue Jun 09 12:28:51 +0200 2009 Puppet (notice): Starting Puppet server version 0.24.8
Tue Jun 09 12:28:51 +0200 2009 Puppet (notice): Caught TERM; shutting down
Tue Jun 09 12:28:51 +0200 2009 Puppet (notice): Shutting down
Tue Jun 09 12:28:52 +0200 2009 Puppet (notice): Reopening log files
Tue Jun 09 12:28:52 +0200 2009 Puppet (notice): Starting Puppet server version 0.24.8
Tue Jun 09 12:29:55 +0200 2009 Puppet (notice): Caught TERM; shutting down
Tue Jun 09 12:29:55 +0200 2009 Puppet (notice): Shutting down
Tue Jun 09 12:29:56 +0200 2009 Puppet (notice): Reopening log files

I forced several client reconf (updated or not), but it does not write a
line!

Maybe the size of filE? not sure if 25 MB is too much for puppet:
# ls -lsah /var/log/puppet/puppetmaster.log
25M -rw-rw---- 1 puppet puppet 25M Jun 9 12:29 /var/log/puppet/puppetmaster.log

# lsof|grep puppet|grep log
puppetmas 30324 puppet 3w REG 8,6 25543117 208207882 /var/log/puppet/puppetmaster.log
puppetmas 30324 puppet 6u REG 8,6 28702 208207960 /var/log/puppet/masterhttp.log
puppetmas 30324 puppet 7u REG 8,6 28702 208207960 /var/log/puppet/masterhttp.log
puppetmas 30324 puppet 8u REG 8,6 28702 208207960 /var/log/puppet/masterhttp.log

Anyone did notice this behave before? I see nothing in mail archive.

TIA,
Arnau

Arnau Bria

unread,
Jun 9, 2009, 6:45:08 AM6/9/09
to puppet...@googlegroups.com
Hi,

sorry, I forgot my conf:
# cat /etc/sysconfig/puppetmaster
PUPPETMASTER_LOG=/var/log/puppet/puppetmaster.log

# puppetmasterd --genconfig|grep -v "#"|grep log
puppetdlog = /var/log/puppet/puppetd.log
httplog = /var/log/puppet/http.log
logdir = /var/log/puppet
masterlog = /var/log/puppet/puppetmaster.log
masterhttplog = /var/log/puppet/masterhttp.log
railslog = /var/log/puppet/rails.log
reports = rrdgraph,store,log

Cheers,
Arnau

Avi Miller

unread,
Jun 9, 2009, 7:31:19 AM6/9/09
to puppet...@googlegroups.com
Arnau Bria wrote:
> I've just updated my server to puppet-server-0.24.8-1.el5.1 (from epel)
> and noticed that puppet-server stopped writing in its log:

It hasn't stopped writing it's logs, it's stopping working completely.
Upgrade Facter to 1.5.5 and restart Puppet to resolve this issue. It's
caused by two bugs in Facter that cause Puppet to sit in an infinite loop.

Essentially, Facter hangs trying to read /proc/uptime and /proc/
virtual (on my XenU guests). You should try the new Facter 1.5.5
which has the fixes for these to see if that resolves the problem. This
version is available in the EPEL Testing repo for both EL4 and EL5.

I actually had to manually fix all my servers because Puppet had
stopped working. Also, when upgrading Facter, make sure you restart
Puppet (if you're running a daemon), otherwise you can also run into
problems I've discovered.

cYa,
Avi

Arnau Bria

unread,
Jun 9, 2009, 8:47:16 AM6/9/09
to puppet...@googlegroups.com
On Tue, 09 Jun 2009 21:31:19 +1000
Avi Miller wrote:


> Arnau Bria wrote:
> > I've just updated my server to puppet-server-0.24.8-1.el5.1 (from
> > epel) and noticed that puppet-server stopped writing in its log:
>
> It hasn't stopped writing it's logs, it's stopping working
> completely.

Well, my clients could run...

and, most curious, when I tried a massive run (190 hosts) some logs
where written, but not all...

> Upgrade Facter to 1.5.5 and restart Puppet to resolve
> this issue. It's caused by two bugs in Facter that cause Puppet to
> sit in an infinite loop.

thank you, but I'm going to downgrade, I found some other issues with
my current conf when trying to update it:


svn: 'pre-commit' hook failed with error output:
/usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:102:in `handle': private method `split' called for nil:NilClass (NoMethodError)
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:630:in `setdefaults'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:630:in `each'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:630:in `setdefaults'
from /usr/lib/ruby/site_ruby/1.8/puppet.rb:79:in `setdefaults'
from /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:51
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /usr/lib/ruby/site_ruby/1.8/puppet.rb:118
from /usr/bin/puppet:67:in `require'
from /usr/bin/puppet:67
Puppet syntax error in manifests/modules/yaim/manifests/init.pp.

I have only changed one file from pressent to absent, and this error
just appeared.

Must think about update.


[...]
> cYa,
> Avi
Thanks your reply,
Arnau

Reply all
Reply to author
Forward
0 new messages