One thing that does strike me as odd: if I run 'puppet agent --test'
repeatedly I don't see multiple versions of this app. The duplication only
happens when puppet runs via crond.
In any event - I'm trying 'hasstatus => false' to see if this makes any
difference.
On Tuesday, February 4, 2014
I'm getting suspicious that there is filesystem corruption. This may be
confusing the service control.
On Tuesday, February 4, 2014 12:11:13 PM UTC-8, Jose Luis Ledesma wrote:
>
> Also try removing the subscribe parameter from the service, and check if
> the restart works properly.
>
> Regards,
Also try removing the subscribe parameter from the service, and check if
the restart works properly.
Regards,
El 04/02/2014 21:09, "José Luis Ledesma"
escribió:
> Have you tried setting hasstatus => true in the service definition?
>
> Could you provide a puppet agent -t --debug from the node?
>
Have you tried setting hasstatus => true in the service definition?
Could you provide a puppet agent -t --debug from the node?
Regards,
El 04/02/2014 20:55, "JonY" escribió:
> I have an issue where puppet keeps starting additional instances of a
> process even though it's already running. The '
I have an issue where puppet keeps starting additional instances of a
process even though it's already running. The 'control script' in question
does have a 'status' command but I'm thinking that I'm not properly telling
puppet that the process is ok.
>From the site:
The init script’s status co
