> On Feb 4, 2009, at 6:49 PM, Steven Nemetz wrote:
>
> > All my puppet clients were running ok.
> > Then 2 things happened yesterday:
> > 1) I had puppet upgrade facter to 1.5.3 everywhere. Most were
> > running 1.3.8 prior.
> > 2) We had network problem, causing one of our datacenters to
> > go offline
> >
> > The network problems have been fixed and was not related to the
> > systems I'm having trouble with. Was a different data center.
> >
> > I found about a dozen systems where puppet was still running but not
> > talking to the master and puppetrun gave no error triggering them,
> > but they did nothing.
> > Restarting puppet on most of these systems fixed the problem. But I
> > still have 4 CentOS 4 systems that will load, but not process the
> > config or request one from the master.
> >
> > Startup messages in debug mode are:
> >
> > debug: Creating default schedules
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/certs/admin4006.sfo.proofpoint.com.pem]:
> > Autorequiring File[/var/lib/puppet/ssl/certs]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/
> > lib/puppet/state]: Autorequiring File[/var/lib/puppet]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/
> > lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/etc/
> > puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/
> > lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/
> > certs]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/private_keys]: Autorequiring
File[/var/lib/puppet/ssl]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/csr_admin4006.sfo.proofpoint.com.pem]: Autorequiring
> > File[/var/lib/puppet/ssl]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/private_keys/admin4006.sfo.proofpoint.com.pem]:
> > Autorequiring File[/var/lib/puppet/ssl/private_keys]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/
> > var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/
> > state]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/public_keys/admin4006.sfo.proofpoint.com.pem]:
> > Autorequiring File[/var/lib/puppet/ssl/public_keys]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/
> > lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/
> > etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/
> > var/log/puppet/http.log]: Autorequiring File[/var/log/puppet]
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/
> > var/lib/puppet/state/state.yaml]: Changing mode
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/
> > var/lib/puppet/state/state.yaml]: 1 change(s)
> > debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/
> > var/lib/puppet/state/state.yaml]/mode: mode changed '640' to '660'
> > debug: Finishing transaction -605596728 with 1 changes
> > info: Starting handler for Runner
> > info: Starting server for Puppet version 0.24.4
> > info: Listening on port 8139
> > notice: Starting Puppet client version 0.24.4
> > debug: Loaded state in 0.00 seconds
> > It then just sits there. All 4 systems behave the same. They are
> > spread across 2 data centers, but all talk to the same puppet
master.
> > I've also noticed that these are very slow at exiting puppet.
> >
> > Anyone have any ideas what could have happened to these 4 systems?
>
> Might you have a fact that's broken, or something similar? That's
> been the cause of 99% of the startup hangs I've seen.
>
> --
> It isn't necessary to have relatives in Kansas City in order to be
> unhappy. -- Groucho Marx
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
The only facts that have changed are the ones that facter 1.5.3
installed.
Facter will run from the command line.
Only thing I've noticed since installing 1.5.3 is that if run as root
facter returns all data with no errors, but if not run as root facter
appears to return all data but it also returns an error on many systems.
I've only seen 1 error per system, but 2 different errors (depending on
which system)
Errors are:
/usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:72: command
not found:
/usr/lib/ruby/site_ruby/1.8/facter/util/ip.rb:145: command not
found:
This includes systems that are working. So I'm not sure if it could be
related or not.
Steven
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
