I've got a host here where I am trying to ensure that syslog-ng is
running, and not surprisingly that syslog is NOT running.
My manifest has...
class syslog_ng {
package { "syslog-ng":
name => "syslog-ng",
ensure => installed;
}
service { "syslog":
ensure => stopped,
enable => false;
}
service { "syslog-ng" :
ensure => running,
enable => true,
subscribe => [
Package["syslog-ng"],
File["/etc/syslog-ng/syslog-ng.conf"]
];
}
....
The following is appearing in the message log...
Oct 15 10:10:01 gumby puppetd[3788]: Starting catalog run
Oct 15 10:10:02 gumby syslog-ng[3675]: Termination requested via
signal, terminating;
Oct 15 10:10:02 gumby syslog-ng[3675]: syslog-ng shutting down; version='2.1.4'
Oct 15 10:10:03 gumby syslog-ng[4091]: syslog-ng starting up; version='2.1.4'
Oct 15 10:10:03 gumby puppetd[3788]:
(//Node[test_node]/syslog_ng/Service[syslog-ng]/ensure) ensure changed
'stopped' to 'running'
It seems to me like there might be a bug here. Puppet appears to think
the syslog-ng and syslog service are the same thing and stops
syslog-ng instead of syslog.
If I change the name of the syslog service, like this...
service { "XXXsyslog":
ensure => stopped,
enable => false;
}
then puppet does NOT stop syslog-ng. Is it doing a regex search on the
first part of the service name or something and stopping when it gets
a match?
Doug.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
