Hi list, has anyone else experienced puppet clients that die when the network goes down for an extended period of time ? OS rhel 5 puppet clients / master 0.25.1 clients are left in a state where ~# service puppet status puppetd dead but pid file exists ~# service puppet restart Stopping puppet: [FAILED] Starting puppet: [ OK ] Obviously the stopping part fails because the puppet process has dies previously. Regards, Nathan -- 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.
Does your logs say anything about puppetd dieing during the network outage? On 7 apr, 07:09, Nat <qwerty....@gmail.com> wrote:> Hi list, > > has anyone else experienced puppet clients that die when the network goes > down for an extended period of time ? > > OS rhel 5 > puppet clients / master 0.25.1 > > clients are left in a state where > ~# service puppet status > puppetd dead but pid file exists > ~# service puppet restart > Stopping puppet: [FAILED] > Starting puppet: [ OK ] > > Obviously the stopping part fails because the puppet process has dies > previously. > > Regards, > > Nathan-- 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.
Nat wrote:> has anyone else experienced puppet clients that die when the network goes > down for an extended period of time ?That happens here as well. We even have a script to monitor last_run times of all puppet clients to detect this. It seems that a puppet master not answering for some time can cause that, but this doesn''t seem to be the only cause. k -- 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''ve seen excessive memory usage in some clients due to odd variants - the Linux OOM killer usually kicks in at some point. Check ''dmesg'' to make sure it wasn''t this. Also - are you catching core dumps on your box incidentally? And as Tore mentions - anything in the logs? Of course the obvious thing to note is that 0.25.4 is the latest revision - with 0.25.5 coming (or out - haven''t been paying attention). That would make 0.25.1 older and potentially more prone to bugs that have since been fixed. You would probably want to upgrade one of your boxes and prove that it still occurs. What kind of network outage are we talking here? On Apr 7, 6:09 am, Nat <qwerty....@gmail.com> wrote:> Hi list, > > has anyone else experienced puppet clients that die when the network goes > down for an extended period of time ? > > OS rhel 5 > puppet clients / master 0.25.1 > > clients are left in a state where > ~# service puppet status > puppetd dead but pid file exists > ~# service puppet restart > Stopping puppet: [FAILED] > Starting puppet: [ OK ] > > Obviously the stopping part fails because the puppet process has dies > previously. > > Regards, > > Nathan-- 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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> I''ve seen excessive memory usage in some clients due to odd variants - > the Linux OOM killer usually kicks in at some point. Check ''dmesg'' to > make sure it wasn''t this. > > Also - are you catching core dumps on your box incidentally? And as > Tore mentions - anything in the logs? > > Of course the obvious thing to note is that 0.25.4 is the latest > revision - with 0.25.5 coming (or out - haven''t been paying > attention). That would make 0.25.1 older and potentially more prone to > bugs that have since been fixed. You would probably want to upgrade > one of your boxes and prove that it still occurs. > > What kind of network outage are we talking here?yes, most of the dying problems have been fixed up to 0.25.4 and some of the memory problems (recursive file directories) will be fixed in 0.25.5. cheers pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAku8OlgACgkQbwltcAfKi3+5MQCdHwpMmzl127mFoXZdHkn8tyOG Ov8An3Q92FW1GBHt/qJVxypBxaWkyy24 =wZGU -----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.