similar to: Service wouldn't restart/refresh

Hi folks, The question I have is regarding to Service resource on Red Hat systems. I have the following: service { [ "anacron", "atd" ]: ensure => stopped, enable => false, hasrestart => true, hasstatus => true, } It runs fine, disabling the service while the system is up. Debugging it, I noticed that it run the following: debug:

Hi, I have this in my sshdconfig module''s init.pp but the service is not getting restarted even though at first connect the file sshd_config is getting modified with the Banner entry. Can someone please help? class sshdconfig { file { "/etc/ssh/sshd_config": path => "/etc/ssh/sshd_config", owner => root,

Hello, I''m trying to do this: service { monit: ensure => running, enable => true, hasrestart => true, if ($operatingsystem == ''centos'') { hasstatus => true, }, require => Package[''monit''], subscribe => File[''monit.conf''], } And it doesn''t work in

Hi, Thanks for the help. I do see these services coming back up if I reboot the system. They are brought down again when puppet run for the first time. Besides, I have never seen Puppet calling chkconfig service off even in the first run, when the services were in a up state after the system installation. I wonder if I missed something. Any other idea? thanks, -fred On Mon, Aug 29, 2011 at

I hope I haven''t dug myself into a corner here... How can I make sure that /some/file.xml is created BEFORE the jboss-tfel0 service is started? I can''t use before => in the file{} in the jboss class because it doesn''t exist there. define create_jboss_inst($inst, $version, $naming_port) { .... service { "jboss-$inst": require

Ok, what am I doing wrong here? I''m including splunkforwarder::app_server and it''s all working except that it appears that splunkforwarder::common isn''t including splunkforwarder::enabled... class splunkforwarder::enabled { service { ''splunkforwarder'': ensure => running, enable => true,

Hi everyone, I''m learning Puppet and I want to configure ssh server with different port on different nodes. Puppet v2.7.1 I have created module ssh: content of modules/ssh/manifests/install.pp class ssh::install { package { "ssh": ensure => present, } } content of modules/ssh/manifests/service.pp class ssh::service { service { "ssh": ensure =>

I''m getting this and it isn''t applying my apache module. Is it because of these warnings? notice: Starting Puppet client version 2.7.5 /usr/local/rvm/gems/ruby-1.9.2-p290/gems/puppet-2.7.5/lib/puppet/ provider/service/freebsd.rb:8: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.2-p290/gems/puppet-2.7.5/lib/puppet/ provider/service/freebsd.rb:9:

I''m having a difficult time with a dependency issue. Basically, I want to be able to call a defined type, but it''s not working out so far. I have my manifests setup like this: init.pp: class foo { .... } bar.pp: class foo::bar { include foo package{ "test": ensure => running, notify =>

I''ve written and deployed a simple Linux SSH module. But I need to modify to include support for FreeBSD and AIX. On top of that, I need to include some conditionals in there that (for example) if (/etc/file1 contains string abc) ; then install sshd-config-x & ssh-config-x elsif (/etc/file1 contains string xyz); then install sshd_config-y & ssh_config-y else install

For my nagios::nrpe class, I have the following service: service {"nagios-nrpe-server": ensure => running, enable => true, require => Package["nagios-nrpe-server"], hasrestart => true, restart => "/etc/init.d/nagios-nrpe-server restart", subscribe =>

Hello ! I''m trying to implement a Nagios solution based on David Schmitt''s Complete Config. But I the following error when running puppetd -t - v : notice: Starting catalog run err: //Node[monitoring]/nagios::target/Nagios::Host[]/File[/conf.d/ _host.cfg]/ensure: change from absent to present failed: Could not set present on ensure: No such file or directory - /conf.d/

Hi, I have a centOS with puppet-server : puppet-server-0.24.0-2.el5 First of I have to say that ever since I installed puppet-server-0.24, I''m unabble to run the puppetmasterd with de flag -d, the programs goes always to daemon mode, with no debug output. Second issue is related with debian clients with puppet-0.20.1-1, that when I have a service subscribed to a file returns always the

First off, new to puppet here, but so far it''s been exceptionally easy to install and get running. I''ve got it on a handful of solaris 10/x86 zones, and it''s working well. I had one gotcha that I ran into, which turned out to be a combination of a sun bug and and just some slight weirdness. I was trying to get the stock solaris snmpd service running (net-snmp 5, by

Hi, For those of you running puppet as non root and are using puppet to manage itself via service, exec or want to use the moo puppet command I have found a fix and submitted a pull request to fix this problem in puppet core. This problem is only unique to non root installations. See http://projects.puppetlabs.com/issues/23053 Example usage in puppet. # Due to this bug we cannot

I''ve seen a couple of instances where a service resource has failed with an error because it''s been evaluated before its corresponding package is installed. I can fix this by adding an explicit require to the service resource, or by just running puppet again, but I thought that there would be an implicit or automatic require from a service object to the associate service

I''m troubled with a node-definition not able to resolve a class: Could not find class rhnsd::common at /etc/puppet/manifests/nodes.pp: 8 on node X Content of manifest/site.pp: import "nodes.pp" [...] The layout of modules/rhnsd/ is: |-- files | `-- up2date-rhn |-- manifests | |-- client.pp | |-- common.pp | |-- init.pp | `-- rhn.pp A `cat'' from each

I''m having an issue with Puma, it fails when it tries to restart itself. When this happens it kills all the Puma processes, resulting in nginx delivering a 502 Bad Gateway to our users. I''m able to start, stop & restart it with my /etc/init.d/puma script (it runs /usr/local/bin/run-puma), it just has issues when it restarts itself. The puma.log file doesn''t

Due to the service name not matching the actual process name, puppet thinks that ovirt-mongrel-rails is never running and tries to start it everytime the installer runs, this adds the hasstatus option to use a service status check rather than puppet's process grep method. --- installer/modules/ovirt/manifests/ovirt.pp | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git

Hi all, I''m trying to setup a puppet installation on FreeBSD. So far I have only one puppetmaster and one puppetclient, both with 0.24.4 from FreeBSD ports. On the master I''ve defined a couple of classes including this: class apache22 { package { apache22: ensure => installed, source => "http://x.x.x.x/packages/apache-2.2.9_5.tbz", provider =>