Issue #1273 has been updated by Nigel Kersten.

Status changed from Needs Decision to Duplicate

Closing in favor of #7273 where we overhaul the restart signals.
----------------------------------------
Bug #1273: puppetd ignores SIGHUP during catalog run
https://projects.puppetlabs.com/issues/1273

Author: Ask Hansen
Status: Duplicate
Priority: Normal
Assignee: Nigel Kersten
Category: agent
Target version: 
Affected Puppet version: 0.25.4
Keywords: 
Branch: 


It doesn't seem to be possible to restart puppetd from within puppetd.

<pre>
   remote_file { "/etc/puppet.conf":
        source => "puppet/puppet.conf",
        mode   => 444,
        notify => Service[[puppet]],
   }

   service { "puppet":
        ensure => true,
        hasrestart => true,
        restart => "kill -HUP @/var/run/puppet/puppetd.pid@",
        hasstatus => true,
   }
</pre>

Gives me

<pre>
May 31 17:06:50 diesel puppetdr27733: 
(//Node[diesel]/dbserver/baseclass/centos/Remote_file[/etc/puppet.conf]/File[/etc/puppet.conf]/source)
 replacing from source puppet:///dist/puppet/puppet.conf with contents 
{md5}b71014d9e6b6b189591a2ea7bd4b1cf3
May 31 17:06:50 diesel puppetdr27825: Could not create PID file: 
/var/run/puppet/puppetd.pid
May 31 17:06:50 diesel puppetdr27733: 
(//Node[diesel]/dbserver/baseclass/centos/Service[puppet]/ensure) ensure 
changed 'stopped' to 'running'
May 31 17:06:50 diesel puppetdr27733: 
(//Node[diesel]/dbserver/baseclass/centos/Service[puppet]) Triggering 'refresh' 
from 1 dependencies
</pre>

but puppetd doesn't actually restart.

I get the same result without the "restart" service parameter.

See also ticket #793.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to