I''ve got a bit of an odd one here that''s pretty much stumped
me.
Recently, puppet was upgraded on a Fedora 10 system to 0.24.7. After I made
sure that puppetmaster was also upgraded to 0.24.7, I found that puppetd
appeared to start up fine, but never actually did anything.
More troubleshooting with various debug options revealed that if I specified
--onetime to puppetd, it performed a normal run as expected. If, however, I
start it up as normal - exactly the same, except without onetime - the client
just hangs.
The client claims to have started up normally:
Feb 24 21:26:13 garibaldi-2950 puppetd[21029]: Starting Puppet client version
0.24.7
And puppetmaster sees the request, and claims to have sent the catalog off:
Feb 24 21:26:17 lorien puppetmasterd[18506]: Compiled catalog for
garibaldi-2950.wpi.edu in 1.04 seconds
After that, though, the client never declares "Starting catalog run".
Pointing strace at the client shows that it''s a select() loop, which
implies
to me that it''s waiting around for something to do, rather than locked
up or
crashed.
I tried wiping out the contents of /var/lib/puppet and restarting, and once
puppetd got the new signed cert, it did exactly the same thing.
The puppetmaster in question is server about a dozen other clients, including
at least one other 0.24.7 client on Fedora 8, so I''m assuming that
it''s not a
puppetmaster side problem.
I do have SELinux enabled, but there aren''t any denial messages logged,
and
also tried it with SELinux set to permissive, and nothing changed.
Anyone have any suggestions for anything else for me to try?
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
try added --debug --trace to your puppetd runs... that should give you some more indications Ohad On Wed, Feb 25, 2009 at 10:45 AM, Frank Sweetser <fs@wpi.edu> wrote:> > > I''ve got a bit of an odd one here that''s pretty much stumped me. > > Recently, puppet was upgraded on a Fedora 10 system to 0.24.7. After I > made > sure that puppetmaster was also upgraded to 0.24.7, I found that puppetd > appeared to start up fine, but never actually did anything. > > More troubleshooting with various debug options revealed that if I > specified > --onetime to puppetd, it performed a normal run as expected. If, however, > I > start it up as normal - exactly the same, except without onetime - the > client > just hangs. > > The client claims to have started up normally: > > Feb 24 21:26:13 garibaldi-2950 puppetd[21029]: Starting Puppet client > version > 0.24.7 > > And puppetmaster sees the request, and claims to have sent the catalog off: > > Feb 24 21:26:17 lorien puppetmasterd[18506]: Compiled catalog for > garibaldi-2950.wpi.edu in 1.04 seconds > > After that, though, the client never declares "Starting catalog run". > Pointing strace at the client shows that it''s a select() loop, which > implies > to me that it''s waiting around for something to do, rather than locked up > or > crashed. > > I tried wiping out the contents of /var/lib/puppet and restarting, and once > puppetd got the new signed cert, it did exactly the same thing. > > The puppetmaster in question is server about a dozen other clients, > including > at least one other 0.24.7 client on Fedora 8, so I''m assuming that it''s not > a > puppetmaster side problem. > > I do have SELinux enabled, but there aren''t any denial messages logged, and > also tried it with SELinux set to permissive, and nothing changed. > > Anyone have any suggestions for anything else for me to try? > > -- > Frank Sweetser fs at wpi.edu | For every problem, there is a solution > that > WPI Senior Network Engineer | is simple, elegant, and wrong. - HL > Mencken > GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Ohad Levy wrote:> try added --debug --trace to your puppetd runs... that should give you > some more indicationsI''ve done that, and compared it to traces from working clients, and the two are identical right up to the point where the broken client just stops. Here''s the last few lines of the broken client: Feb 24 22:11:30 garibaldi-2950 puppetd[29448]: Reopening log files Feb 24 22:11:30 garibaldi-2950 puppetd[29448]: Starting Puppet client version 0.24.7 Feb 24 22:11:30 garibaldi-2950 puppetd[29448]: Loaded state in 0.00 seconds Feb 24 22:11:32 garibaldi-2950 puppetd[29448]: Retrieved facts in 2.75 seconds Feb 24 22:11:32 garibaldi-2950 puppetd[29448]: Retrieving catalog Feb 24 22:11:32 garibaldi-2950 puppetd[29448]: Calling puppetmaster.getconfig Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Retrieved catalog in 1.70 seconds Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Type::Service::ProviderDebian: file /usr/sbin/update-rc.d does not exist Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Network::Client::File: defining fileserver.describe Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Network::Client::File: defining fileserver.list Feb 24 22:11:34 garibaldi-2950 puppetd[29448]: Puppet::Network::Client::File: defining fileserver.retrieve After that, it just sits there. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
> More troubleshooting with various debug options revealed that if I specified > --onetime to puppetd, it performed a normal run as expected. If, however, I > start it up as normal - exactly the same, except without onetime - the client > just hangs.Just as a followup to anyone who hits the same problem, it turns out that I was running into http://projects.reductivelabs.com/issues/1963 Once I fixed that, everything else started working fine. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---