I have a hardening config that shuts down these two services (among others): "readahead_later": enable => "false", ensure => "stopped"; "readahead_early": enable => "false", ensure => "stopped"; The problem is only one shuts down and gets removed from the chkconfig list. In this case, readahead_early gets shut down and removed, but readahead_later does not. Any thoughts? How do I troubleshoot this problem? There is nothing in the logs to indicate a problem. Cheers, Jeff --~--~---------~--~----~------------~-------~--~----~ 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 May 22, 2:55 pm, Jeff <joesi...@gmail.com> wrote:> I have a hardening config that shuts down these two services (among > others): > > "readahead_later": > enable => "false", > ensure => "stopped"; > > "readahead_early": > enable => "false", > ensure => "stopped"; > > The problem is only one shuts down and gets removed from the chkconfig > list. In this case, readahead_early gets shut down and removed, but > readahead_later does not. Any thoughts? How do I troubleshoot this > problem? There is nothing in the logs to indicate a problem. >The plot sickens... The configuration above didn''t work (and, by the way, that''s in a service {} ) but this DID work: exec{''readahead_later stop'': command => "service readahead_later stop", } exec{''readahead_later del'': command => "chkconfig --del readahead_later", } I suppose I could change the config. It would be nice if I could get my verbotten services in an array and loop through it. Is that possible? Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
James Turnbull
2008-May-22 19:14 UTC
[Puppet Users] Re: Shutting down services in RHEL 5.0
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeff wrote:> I have a hardening config that shuts down these two services (among > others): > > "readahead_later": > enable => "false", > ensure => "stopped"; > > "readahead_early": > enable => "false", > ensure => "stopped"; > > The problem is only one shuts down and gets removed from the chkconfig > list. In this case, readahead_early gets shut down and removed, but > readahead_later does not. Any thoughts? How do I troubleshoot this > problem? There is nothing in the logs to indicate a problem.Jeff We recently changed the service provider on Red Hat-based systems to use /sbin/service and chkconfig more appropriately. These commits are in the current 0.24.x tree and should be available in 0.24.5. This may be relevant to your problem. I think the relevant ticket is #1196. Regards James Turnbull - -- James Turnbull (james@lovedthanlost.net) Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFINcYJ9hTGvAxC30ARAnsQAKCfbQySM3x0J671RlzxeNTSWtg6vgCglcJj sjIOimKGQD7R20KZcUydcnI=QWWq -----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 -~----------~----~----~----~------~----~------~--~---
David Lutterkort
2008-May-22 21:29 UTC
[Puppet Users] Re: Shutting down services in RHEL 5.0
On Thu, 2008-05-22 at 12:04 -0700, Jeff wrote:> On May 22, 2:55 pm, Jeff <joesi...@gmail.com> wrote: > > I have a hardening config that shuts down these two services (among > > others): > > > > "readahead_later": > > enable => "false", > > ensure => "stopped"; > > > > "readahead_early": > > enable => "false", > > ensure => "stopped"; > > > > The problem is only one shuts down and gets removed from the chkconfig > > list. In this case, readahead_early gets shut down and removed, but > > readahead_later does not. Any thoughts? How do I troubleshoot this > > problem? There is nothing in the logs to indicate a problem. > > > > The plot sickens...What version of puppet are you using for this ?> The configuration above didn''t work (and, by the way, that''s in a > service {} ) but this DID work: > > exec{''readahead_later stop'': > command => "service readahead_later stop", > } > > exec{''readahead_later del'': > command => "chkconfig --del readahead_later", > }That''s what 0.24.4 and earlier used to do. Now it will essentially run service readahead_later stop chkconfig readahead_later off The readahead_* services aren''t real ''services'', i.e., there''s no daemon running for them, they just cause a bunch of disk reads to happen. I wonder if any of that confuses puppet. David --~--~---------~--~----~------------~-------~--~----~ 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 May 22, 3:14 pm, James Turnbull <ja...@lovedthanlost.net> wrote:> Jeff wrote: > > I have a hardening config that shuts down these two services (among > > others): > > > "readahead_later": > > enable => "false", > > ensure => "stopped"; > > > "readahead_early": > > enable => "false", > > ensure => "stopped"; > > > The problem is only one shuts down and gets removed from the chkconfig > > list. In this case, readahead_early gets shut down and removed, but > > readahead_later does not. Any thoughts? How do I troubleshoot this > > problem? There is nothing in the logs to indicate a problem. > > Jeff > > We recently changed the service provider on Red Hat-based systems to use > /sbin/service and chkconfig more appropriately. These commits are in > the current 0.24.x tree and should be available in 0.24.5. This may be > relevant to your problem. > > I think the relevant ticket is #1196. >James: Thanks. I wish I could solve this with the execs I posted above. Some services shut down with this: service{ "readahead_early": enable => "false", ensure => "stopped"; } And some shutdown with this: exec{''readahead_later stop'': command => "service readahead_later stop", } exec{''readahead_later del'': command => "chkconfig --del readahead_later", } Unfortunately, I can''t seem to make them all shut down using just one method. The exec method fails for some services even though I can go to a server on which it failed and issue those commands successfully at the command line. I''m off work today but I''ll examine the issue again on Tuesday. Can you provide me with debugging strategies? TIA, Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Jeff wrote:> > > James: Thanks. I wish I could solve this with the execs I posted > above. Some services shut down with this: > > service{ "readahead_early": > enable => "false", > ensure => "stopped"; > } > > And some shutdown with this: > exec{''readahead_later stop'': > command => "service readahead_later stop", > } > > exec{''readahead_later del'': > command => "chkconfig --del readahead_later", > } > > Unfortunately, I can''t seem to make them all shut down using just one > method. The exec method fails for some services even though I can go > to a server on which it failed and issue those commands successfully > at the command line.Please supply --debug output of the puppet run not working to stop and disable this service. Does the service name match in ps -ef|grep $name? If not, does the init script support the status command? if it does, simply use the hasstatus parameter to specify it. This will cause puppet to call ''service $name status'' to query the ensure state, either running or stopped. Are you able to verify that enable => false is *not* disabling readahead_early? (i.e. `chkconfig --list readahead_early`)> > I''m off work today but I''ll examine the issue again on Tuesday. Can > you provide me with debugging strategies? > > TIA, > Jeff >Regards, AJ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
James Turnbull
2008-May-23 14:19 UTC
[Puppet Users] Re: Shutting down services in RHEL 5.0
Jeff wrote:> > > On May 22, 3:14 pm, James Turnbull <ja...@lovedthanlost.net> wrote: >> Jeff wrote: >>> I have a hardening config that shuts down these two services (among >>> others): >>> "readahead_later": >>> enable => "false", >>> ensure => "stopped"; >>> "readahead_early": >>> enable => "false", >>> ensure => "stopped"; >>> The problem is only one shuts down and gets removed from the chkconfig >>> list. In this case, readahead_early gets shut down and removed, but >>> readahead_later does not. Any thoughts? How do I troubleshoot this >>> problem? There is nothing in the logs to indicate a problem. >> Jeff >> >> We recently changed the service provider on Red Hat-based systems to use >> /sbin/service and chkconfig more appropriately. These commits are in >> the current 0.24.x tree and should be available in 0.24.5. This may be >> relevant to your problem. >> >> I think the relevant ticket is #1196. >> > > James: Thanks. I wish I could solve this with the execs I posted > above. Some services shut down with this: > > service{ "readahead_early": > enable => "false", > ensure => "stopped"; > } > > And some shutdown with this: > exec{''readahead_later stop'': > command => "service readahead_later stop", > } > > exec{''readahead_later del'': > command => "chkconfig --del readahead_later", > } > > Unfortunately, I can''t seem to make them all shut down using just one > method. The exec method fails for some services even though I can go > to a server on which it failed and issue those commands successfully > at the command line. > > I''m off work today but I''ll examine the issue again on Tuesday. Can > you provide me with debugging strategies?Traces and debugs of the issue are always helpful. Regards James Turnbull -- James Turnbull (james@lovedthanlost.net) Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/)