Hi All, I have a strange problem with running puppet as a daemon. I set it up in config to wake up every 15 min and looks like it every time spawns httpd process that becomes zombie, so after some time I see a long list of zombies, like this: root 12427 0.1 0.9 39624 37408 ? Ss Dec20 4:12 /usr/bin/ruby /usr/sbin/puppetd . . . root 23654 0.0 0.0 0 0 ? Z 15:14 0:00 \_ [httpd] <defunct> root 30482 0.0 0.0 0 0 ? Z 15:29 0:00 \_ [httpd] <defunct> root 5389 0.0 0.0 0 0 ? Z 15:44 0:00 \_ [httpd] <defunct> root 12636 0.0 0.0 0 0 ? Z 15:59 0:00 \_ [httpd] <defunct> root 21618 0.0 0.0 0 0 ? Z 16:15 0:00 \_ [httpd] <defunct> root 28044 0.0 0.0 0 0 ? Z 16:30 0:00 \_ [httpd] <defunct> root 2363 0.0 0.0 0 0 ? Z 16:45 0:00 \_ [httpd] <defunct> root 9547 0.0 0.0 0 0 ? Z 17:00 0:00 \_ [httpd] <defunct> root 17770 0.0 0.0 0 0 ? Z 17:15 0:00 \_ [httpd] <defunct> root 24466 0.0 0.0 0 0 ? Z 17:30 0:00 \_ [httpd] <defunct> root 31275 0.0 0.0 0 0 ? Z 17:46 0:00 \_ [httpd] <defunct> root 6199 0.0 0.0 0 0 ? Z 18:01 0:00 \_ [httpd] <defunct> root 14349 0.0 0.0 0 0 ? Z 18:16 0:00 \_ [httpd] <defunct> root 21148 0.0 0.0 0 0 ? Z 18:31 0:00 \_ [httpd] <defunct> When I kill puppetd all zombies die as well. I set it on about 60 servers, and see the same picture on all of them :( I don''t have any idea about why this happen, does someone have any idea? Thanks in advance -- Paul Johnson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On Mon, Dec 22, 2008 at 08:18:25AM +0200, Paul Johnson wrote:> Hi All, > > I have a strange problem with running puppet as a daemon. I set it up in > config to wake up every 15 min and looks like it every time spawns httpd > process that becomes zombie, so after some time I see a long list of > zombies, like this:We''ll need to see your configs to be able to help here. -Robin -- They say: "The first AIs will be built by the military as weapons." And I''m thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
whats the last line you see in your puppet logfiles? I would guess its an exec or similar.... Ohad On 12/22/08, Paul Johnson <gentoo.server@gmail.com> wrote:> Hi All, > > I have a strange problem with running puppet as a daemon. I set it up in > config to wake up every 15 min and looks like it every time spawns httpd > process that becomes zombie, so after some time I see a long list of > zombies, like this: > > root 12427 0.1 0.9 39624 37408 ? Ss Dec20 4:12 /usr/bin/ruby > /usr/sbin/puppetd > . > . > . > root 23654 0.0 0.0 0 0 ? Z 15:14 0:00 \_ [httpd] > <defunct> > root 30482 0.0 0.0 0 0 ? Z 15:29 0:00 \_ [httpd] > <defunct> > root 5389 0.0 0.0 0 0 ? Z 15:44 0:00 \_ [httpd] > <defunct> > root 12636 0.0 0.0 0 0 ? Z 15:59 0:00 \_ [httpd] > <defunct> > root 21618 0.0 0.0 0 0 ? Z 16:15 0:00 \_ [httpd] > <defunct> > root 28044 0.0 0.0 0 0 ? Z 16:30 0:00 \_ [httpd] > <defunct> > root 2363 0.0 0.0 0 0 ? Z 16:45 0:00 \_ [httpd] > <defunct> > root 9547 0.0 0.0 0 0 ? Z 17:00 0:00 \_ [httpd] > <defunct> > root 17770 0.0 0.0 0 0 ? Z 17:15 0:00 \_ [httpd] > <defunct> > root 24466 0.0 0.0 0 0 ? Z 17:30 0:00 \_ [httpd] > <defunct> > root 31275 0.0 0.0 0 0 ? Z 17:46 0:00 \_ [httpd] > <defunct> > root 6199 0.0 0.0 0 0 ? Z 18:01 0:00 \_ [httpd] > <defunct> > root 14349 0.0 0.0 0 0 ? Z 18:16 0:00 \_ [httpd] > <defunct> > root 21148 0.0 0.0 0 0 ? Z 18:31 0:00 \_ [httpd] > <defunct> > > When I kill puppetd all zombies die as well. I set it on about 60 servers, > and see the same picture on all of them :( > I don''t have any idea about why this happen, does someone have any idea? > > Thanks in advance > -- > Paul Johnson > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Thanks for replies, here is the info. Actually there is not much in configs, I tried it with minimal manifest and the issue still persists. manifest: ====================================================node default { $server = "puppetmaster.local" #------------------------------------------------------------------------------------ # distribute puppetd and auth configs to all managed nodes file { ''/etc/puppet/puppet.conf'': source => "puppet://$server/files/puppet.conf"; ''/etc/puppet/puppetd.conf'': source => "puppet://$server/files/puppet.conf"; ''/etc/puppet/namespaceauth.conf'': source => "puppet://$server/files/namespaceauth.conf"; } #------------------------------------------------------------------------------------ # define default filebucket on puppetmaster server filebucket { "main": server => $server } File { backup => ''main'' } } ==================================================== puppetd.conf (the same as puppet.conf) on target server: ====================================================[main] # Where Puppet stores dynamic and growing data. # The default value is ''/var/puppet''. vardir = /var/lib/puppet # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is ''$vardir/run''. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is ''$confdir/ssl''. ssldir = $vardir/ssl [puppetd] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is ''$confdir/classes.txt''. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is ''$confdir/localconfig''. localconfig = $vardir/localconfig # mster server server = puppetmaster.local # interval runinterval = 900 # should we send reports back to puppetmaster server? report = true # should we listen for incoming connections? Allowd hosts are in file listen = true # we want all facts to be synced from master factsync = true ==================================================== As to the logs, it creates only one log file during first run: /var/log/puppet/http.log and nothing writes to it since then, so it remains empty. Puppetd performs all operations I add to manifest and doesn''t report any error or warning and the only problem is it produces those strange zombies... Target OS is Centos, tried versions 3,4 and 5 - the issue is on all of them. I have few instances of puppet running on Gentoo (installed from portages) and there is no such problem. Please let me know if I should provide any additional info. Thanks -- Paul Johnson 2008/12/22 Ohad Levy <ohadlevy@gmail.com>> > whats the last line you see in your puppet logfiles? > > I would guess its an exec or similar.... > > Ohad > > On 12/22/08, Paul Johnson <gentoo.server@gmail.com> wrote: > > Hi All, > > > > I have a strange problem with running puppet as a daemon. I set it up in > > config to wake up every 15 min and looks like it every time spawns httpd > > process that becomes zombie, so after some time I see a long list of > > zombies, like this: > > > > root 12427 0.1 0.9 39624 37408 ? Ss Dec20 4:12 > /usr/bin/ruby > > /usr/sbin/puppetd > > . > > . > > . > > root 23654 0.0 0.0 0 0 ? Z 15:14 0:00 \_ > [httpd] > > <defunct> > > root 30482 0.0 0.0 0 0 ? Z 15:29 0:00 \_ > [httpd] > > <defunct> > > root 5389 0.0 0.0 0 0 ? Z 15:44 0:00 \_ > [httpd] > > <defunct> > > root 12636 0.0 0.0 0 0 ? Z 15:59 0:00 \_ > [httpd] > > <defunct> > > root 21618 0.0 0.0 0 0 ? Z 16:15 0:00 \_ > [httpd] > > <defunct> > > root 28044 0.0 0.0 0 0 ? Z 16:30 0:00 \_ > [httpd] > > <defunct> > > root 2363 0.0 0.0 0 0 ? Z 16:45 0:00 \_ > [httpd] > > <defunct> > > root 9547 0.0 0.0 0 0 ? Z 17:00 0:00 \_ > [httpd] > > <defunct> > > root 17770 0.0 0.0 0 0 ? Z 17:15 0:00 \_ > [httpd] > > <defunct> > > root 24466 0.0 0.0 0 0 ? Z 17:30 0:00 \_ > [httpd] > > <defunct> > > root 31275 0.0 0.0 0 0 ? Z 17:46 0:00 \_ > [httpd] > > <defunct> > > root 6199 0.0 0.0 0 0 ? Z 18:01 0:00 \_ > [httpd] > > <defunct> > > root 14349 0.0 0.0 0 0 ? Z 18:16 0:00 \_ > [httpd] > > <defunct> > > root 21148 0.0 0.0 0 0 ? Z 18:31 0:00 \_ > [httpd] > > <defunct> > > > > When I kill puppetd all zombies die as well. I set it on about 60 > servers, > > and see the same picture on all of them :( > > I don''t have any idea about why this happen, does someone have any idea? > > > > Thanks in advance > > -- > > Paul Johnson > > > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
What version of Puppet are you using? --Paul On Tue, Dec 23, 2008 at 11:59 PM, Paul Johnson <gentoo.server@gmail.com> wrote:> Thanks for replies, here is the info. Actually there is not much in configs, > I tried it with minimal manifest and the issue still persists. > > manifest: > ====================================================> node default { > > $server = "puppetmaster.local" > > #------------------------------------------------------------------------------------ > # distribute puppetd and auth configs to all managed nodes > file { > ''/etc/puppet/puppet.conf'': source => > "puppet://$server/files/puppet.conf"; > ''/etc/puppet/puppetd.conf'': source => > "puppet://$server/files/puppet.conf"; > ''/etc/puppet/namespaceauth.conf'': source => > "puppet://$server/files/namespaceauth.conf"; > } > > #------------------------------------------------------------------------------------ > # define default filebucket on puppetmaster server > filebucket { "main": server => $server } > File { backup => ''main'' } > } > ====================================================> > puppetd.conf (the same as puppet.conf) on target server: > > ====================================================> [main] > > # Where Puppet stores dynamic and growing data. > # The default value is ''/var/puppet''. > vardir = /var/lib/puppet > > # The Puppet log directory. > # The default value is ''$vardir/log''. > logdir = /var/log/puppet > > # Where Puppet PID files are kept. > # The default value is ''$vardir/run''. > rundir = /var/run/puppet > > # Where SSL certificates are kept. > # The default value is ''$confdir/ssl''. > ssldir = $vardir/ssl > > [puppetd] > # The file in which puppetd stores a list of the classes > # associated with the retrieved configuratiion. Can be loaded in > # the separate ``puppet`` executable using the ``--loadclasses`` > # option. > # The default value is ''$confdir/classes.txt''. > classfile = $vardir/classes.txt > > # Where puppetd caches the local configuration. An > # extension indicating the cache format is added automatically. > # The default value is ''$confdir/localconfig''. > localconfig = $vardir/localconfig > > # mster server > server = puppetmaster.local > > # interval > runinterval = 900 > > # should we send reports back to puppetmaster server? > report = true > > # should we listen for incoming connections? Allowd hosts are in file > listen = true > > # we want all facts to be synced from master > factsync = true > ====================================================> > As to the logs, it creates only one log file during first run: > /var/log/puppet/http.log and nothing writes to it since then, so it remains > empty. > > Puppetd performs all operations I add to manifest and doesn''t report any > error or warning and the only problem is it produces those strange > zombies... > Target OS is Centos, tried versions 3,4 and 5 - the issue is on all of them. > I have few instances of puppet running on Gentoo (installed from portages) > and there is no such problem. > > Please let me know if I should provide any additional info. > > Thanks > -- > Paul Johnson > > 2008/12/22 Ohad Levy <ohadlevy@gmail.com> >> >> whats the last line you see in your puppet logfiles? >> >> I would guess its an exec or similar.... >> >> Ohad >> >> On 12/22/08, Paul Johnson <gentoo.server@gmail.com> wrote: >> > Hi All, >> > >> > I have a strange problem with running puppet as a daemon. I set it up in >> > config to wake up every 15 min and looks like it every time spawns httpd >> > process that becomes zombie, so after some time I see a long list of >> > zombies, like this: >> > >> > root 12427 0.1 0.9 39624 37408 ? Ss Dec20 4:12 >> > /usr/bin/ruby >> > /usr/sbin/puppetd >> > . >> > . >> > . >> > root 23654 0.0 0.0 0 0 ? Z 15:14 0:00 \_ >> > [httpd] >> > <defunct> >> > root 30482 0.0 0.0 0 0 ? Z 15:29 0:00 \_ >> > [httpd] >> > <defunct> >> > root 5389 0.0 0.0 0 0 ? Z 15:44 0:00 \_ >> > [httpd] >> > <defunct> >> > root 12636 0.0 0.0 0 0 ? Z 15:59 0:00 \_ >> > [httpd] >> > <defunct> >> > root 21618 0.0 0.0 0 0 ? Z 16:15 0:00 \_ >> > [httpd] >> > <defunct> >> > root 28044 0.0 0.0 0 0 ? Z 16:30 0:00 \_ >> > [httpd] >> > <defunct> >> > root 2363 0.0 0.0 0 0 ? Z 16:45 0:00 \_ >> > [httpd] >> > <defunct> >> > root 9547 0.0 0.0 0 0 ? Z 17:00 0:00 \_ >> > [httpd] >> > <defunct> >> > root 17770 0.0 0.0 0 0 ? Z 17:15 0:00 \_ >> > [httpd] >> > <defunct> >> > root 24466 0.0 0.0 0 0 ? Z 17:30 0:00 \_ >> > [httpd] >> > <defunct> >> > root 31275 0.0 0.0 0 0 ? Z 17:46 0:00 \_ >> > [httpd] >> > <defunct> >> > root 6199 0.0 0.0 0 0 ? Z 18:01 0:00 \_ >> > [httpd] >> > <defunct> >> > root 14349 0.0 0.0 0 0 ? Z 18:16 0:00 \_ >> > [httpd] >> > <defunct> >> > root 21148 0.0 0.0 0 0 ? Z 18:31 0:00 \_ >> > [httpd] >> > <defunct> >> > >> > When I kill puppetd all zombies die as well. I set it on about 60 >> > servers, >> > and see the same picture on all of them :( >> > I don''t have any idea about why this happen, does someone have any idea? >> > >> > Thanks in advance >> > -- >> > Paul Johnson >> > >> > > >> > >> >> > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
it''s 0.24.5, but after upgrading to the latest stable 0.24.7 the issue still persists. Thanks -- Paul Johnson 2008/12/29 Paul Lathrop <paul.lathrop@gmail.com>> > What version of Puppet are you using? > > --Paul > > On Tue, Dec 23, 2008 at 11:59 PM, Paul Johnson <gentoo.server@gmail.com> > wrote: > > Thanks for replies, here is the info. Actually there is not much in > configs, > > I tried it with minimal manifest and the issue still persists. > > > > manifest: > > ====================================================> > node default { > > > > $server = "puppetmaster.local" > > > > > #------------------------------------------------------------------------------------ > > # distribute puppetd and auth configs to all managed nodes > > file { > > ''/etc/puppet/puppet.conf'': source => > > "puppet://$server/files/puppet.conf"; > > ''/etc/puppet/puppetd.conf'': source => > > "puppet://$server/files/puppet.conf"; > > ''/etc/puppet/namespaceauth.conf'': source => > > "puppet://$server/files/namespaceauth.conf"; > > } > > > > > #------------------------------------------------------------------------------------ > > # define default filebucket on puppetmaster server > > filebucket { "main": server => $server } > > File { backup => ''main'' } > > } > > ====================================================> > > > puppetd.conf (the same as puppet.conf) on target server: > > > > ====================================================> > [main] > > > > # Where Puppet stores dynamic and growing data. > > # The default value is ''/var/puppet''. > > vardir = /var/lib/puppet > > > > # The Puppet log directory. > > # The default value is ''$vardir/log''. > > logdir = /var/log/puppet > > > > # Where Puppet PID files are kept. > > # The default value is ''$vardir/run''. > > rundir = /var/run/puppet > > > > # Where SSL certificates are kept. > > # The default value is ''$confdir/ssl''. > > ssldir = $vardir/ssl > > > > [puppetd] > > # The file in which puppetd stores a list of the classes > > # associated with the retrieved configuratiion. Can be loaded in > > # the separate ``puppet`` executable using the ``--loadclasses`` > > # option. > > # The default value is ''$confdir/classes.txt''. > > classfile = $vardir/classes.txt > > > > # Where puppetd caches the local configuration. An > > # extension indicating the cache format is added automatically. > > # The default value is ''$confdir/localconfig''. > > localconfig = $vardir/localconfig > > > > # mster server > > server = puppetmaster.local > > > > # interval > > runinterval = 900 > > > > # should we send reports back to puppetmaster server? > > report = true > > > > # should we listen for incoming connections? Allowd hosts are in > file > > listen = true > > > > # we want all facts to be synced from master > > factsync = true > > ====================================================> > > > As to the logs, it creates only one log file during first run: > > /var/log/puppet/http.log and nothing writes to it since then, so it > remains > > empty. > > > > Puppetd performs all operations I add to manifest and doesn''t report any > > error or warning and the only problem is it produces those strange > > zombies... > > Target OS is Centos, tried versions 3,4 and 5 - the issue is on all of > them. > > I have few instances of puppet running on Gentoo (installed from > portages) > > and there is no such problem. > > > > Please let me know if I should provide any additional info. > > > > Thanks > > -- > > Paul Johnson > > > > 2008/12/22 Ohad Levy <ohadlevy@gmail.com> > >> > >> whats the last line you see in your puppet logfiles? > >> > >> I would guess its an exec or similar.... > >> > >> Ohad > >> > >> On 12/22/08, Paul Johnson <gentoo.server@gmail.com> wrote: > >> > Hi All, > >> > > >> > I have a strange problem with running puppet as a daemon. I set it up > in > >> > config to wake up every 15 min and looks like it every time spawns > httpd > >> > process that becomes zombie, so after some time I see a long list of > >> > zombies, like this: > >> > > >> > root 12427 0.1 0.9 39624 37408 ? Ss Dec20 4:12 > >> > /usr/bin/ruby > >> > /usr/sbin/puppetd > >> > . > >> > . > >> > . > >> > root 23654 0.0 0.0 0 0 ? Z 15:14 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 30482 0.0 0.0 0 0 ? Z 15:29 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 5389 0.0 0.0 0 0 ? Z 15:44 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 12636 0.0 0.0 0 0 ? Z 15:59 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 21618 0.0 0.0 0 0 ? Z 16:15 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 28044 0.0 0.0 0 0 ? Z 16:30 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 2363 0.0 0.0 0 0 ? Z 16:45 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 9547 0.0 0.0 0 0 ? Z 17:00 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 17770 0.0 0.0 0 0 ? Z 17:15 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 24466 0.0 0.0 0 0 ? Z 17:30 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 31275 0.0 0.0 0 0 ? Z 17:46 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 6199 0.0 0.0 0 0 ? Z 18:01 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 14349 0.0 0.0 0 0 ? Z 18:16 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > root 21148 0.0 0.0 0 0 ? Z 18:31 0:00 \_ > >> > [httpd] > >> > <defunct> > >> > > >> > When I kill puppetd all zombies die as well. I set it on about 60 > >> > servers, > >> > and see the same picture on all of them :( > >> > I don''t have any idea about why this happen, does someone have any > idea? > >> > > >> > Thanks in advance > >> > -- > >> > Paul Johnson > >> > > >> > > > >> > > >> > >> > > > > > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
The problem has been solved by myself :) It was caused by one of my custom facts that run apache binary and didn''t close the process properly. My bad. Thanks to all for answers and help! Thanks -- Paul Johnson 2008/12/29 Paul Johnson <gentoo.server@gmail.com>> it''s 0.24.5, but after upgrading to the latest stable 0.24.7 the issue > still persists. > > Thanks > -- > Paul Johnson > > 2008/12/29 Paul Lathrop <paul.lathrop@gmail.com> > > >> What version of Puppet are you using? >> >> --Paul >> >> On Tue, Dec 23, 2008 at 11:59 PM, Paul Johnson <gentoo.server@gmail.com> >> wrote: >> > Thanks for replies, here is the info. Actually there is not much in >> configs, >> > I tried it with minimal manifest and the issue still persists. >> > >> > manifest: >> > ====================================================>> > node default { >> > >> > $server = "puppetmaster.local" >> > >> > >> #------------------------------------------------------------------------------------ >> > # distribute puppetd and auth configs to all managed nodes >> > file { >> > ''/etc/puppet/puppet.conf'': source => >> > "puppet://$server/files/puppet.conf"; >> > ''/etc/puppet/puppetd.conf'': source => >> > "puppet://$server/files/puppet.conf"; >> > ''/etc/puppet/namespaceauth.conf'': source => >> > "puppet://$server/files/namespaceauth.conf"; >> > } >> > >> > >> #------------------------------------------------------------------------------------ >> > # define default filebucket on puppetmaster server >> > filebucket { "main": server => $server } >> > File { backup => ''main'' } >> > } >> > ====================================================>> > >> > puppetd.conf (the same as puppet.conf) on target server: >> > >> > ====================================================>> > [main] >> > >> > # Where Puppet stores dynamic and growing data. >> > # The default value is ''/var/puppet''. >> > vardir = /var/lib/puppet >> > >> > # The Puppet log directory. >> > # The default value is ''$vardir/log''. >> > logdir = /var/log/puppet >> > >> > # Where Puppet PID files are kept. >> > # The default value is ''$vardir/run''. >> > rundir = /var/run/puppet >> > >> > # Where SSL certificates are kept. >> > # The default value is ''$confdir/ssl''. >> > ssldir = $vardir/ssl >> > >> > [puppetd] >> > # The file in which puppetd stores a list of the classes >> > # associated with the retrieved configuratiion. Can be loaded in >> > # the separate ``puppet`` executable using the ``--loadclasses`` >> > # option. >> > # The default value is ''$confdir/classes.txt''. >> > classfile = $vardir/classes.txt >> > >> > # Where puppetd caches the local configuration. An >> > # extension indicating the cache format is added automatically. >> > # The default value is ''$confdir/localconfig''. >> > localconfig = $vardir/localconfig >> > >> > # mster server >> > server = puppetmaster.local >> > >> > # interval >> > runinterval = 900 >> > >> > # should we send reports back to puppetmaster server? >> > report = true >> > >> > # should we listen for incoming connections? Allowd hosts are in >> file >> > listen = true >> > >> > # we want all facts to be synced from master >> > factsync = true >> > ====================================================>> > >> > As to the logs, it creates only one log file during first run: >> > /var/log/puppet/http.log and nothing writes to it since then, so it >> remains >> > empty. >> > >> > Puppetd performs all operations I add to manifest and doesn''t report any >> > error or warning and the only problem is it produces those strange >> > zombies... >> > Target OS is Centos, tried versions 3,4 and 5 - the issue is on all of >> them. >> > I have few instances of puppet running on Gentoo (installed from >> portages) >> > and there is no such problem. >> > >> > Please let me know if I should provide any additional info. >> > >> > Thanks >> > -- >> > Paul Johnson >> > >> > 2008/12/22 Ohad Levy <ohadlevy@gmail.com> >> >> >> >> whats the last line you see in your puppet logfiles? >> >> >> >> I would guess its an exec or similar.... >> >> >> >> Ohad >> >> >> >> On 12/22/08, Paul Johnson <gentoo.server@gmail.com> wrote: >> >> > Hi All, >> >> > >> >> > I have a strange problem with running puppet as a daemon. I set it up >> in >> >> > config to wake up every 15 min and looks like it every time spawns >> httpd >> >> > process that becomes zombie, so after some time I see a long list of >> >> > zombies, like this: >> >> > >> >> > root 12427 0.1 0.9 39624 37408 ? Ss Dec20 4:12 >> >> > /usr/bin/ruby >> >> > /usr/sbin/puppetd >> >> > . >> >> > . >> >> > . >> >> > root 23654 0.0 0.0 0 0 ? Z 15:14 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 30482 0.0 0.0 0 0 ? Z 15:29 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 5389 0.0 0.0 0 0 ? Z 15:44 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 12636 0.0 0.0 0 0 ? Z 15:59 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 21618 0.0 0.0 0 0 ? Z 16:15 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 28044 0.0 0.0 0 0 ? Z 16:30 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 2363 0.0 0.0 0 0 ? Z 16:45 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 9547 0.0 0.0 0 0 ? Z 17:00 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 17770 0.0 0.0 0 0 ? Z 17:15 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 24466 0.0 0.0 0 0 ? Z 17:30 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 31275 0.0 0.0 0 0 ? Z 17:46 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 6199 0.0 0.0 0 0 ? Z 18:01 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 14349 0.0 0.0 0 0 ? Z 18:16 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > root 21148 0.0 0.0 0 0 ? Z 18:31 0:00 \_ >> >> > [httpd] >> >> > <defunct> >> >> > >> >> > When I kill puppetd all zombies die as well. I set it on about 60 >> >> > servers, >> >> > and see the same picture on all of them :( >> >> > I don''t have any idea about why this happen, does someone have any >> idea? >> >> > >> >> > Thanks in advance >> >> > -- >> >> > Paul Johnson >> >> > >> >> > > >> >> > >> >> >> >> >> > >> > >> > > >> > >> >> >> >> >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---