Using puppet to manage puppet upgrades to the agent has been an interesting
dilemma that sometimes has issues. OpenTable came out with this module:
https://forge.puppetlabs.com/opentable/puppetversion to help handle
upgrades. On Windows they set a scheduled task to manage the upgrade just
after the
Any idea?
On Saturday, May 10, 2014 12:22:46 PM UTC+2, cko wrote:
>
> After the puppet run the agent service is basically stopped.
>
> Although when i run "sc queryex puppet" the output is "STOP_PENDING" (not
> stopped but not running either).
>
> So i have to run "taskkill /f /pid 1234" and then
After the puppet run the agent service is basically stopped.
Although when i run "sc queryex puppet" the output is "STOP_PENDING" (not
stopped but not running either).
So i have to run "taskkill /f /pid 1234" and then start the service again.
On Friday, May 9, 2014 9:45:35 PM UTC+2, Rob Reyno
This error is somewhat of a misnomer: "The requested service has already
been started."
When you say it gets stuck, what do you mean exactly?
On Fri, May 9, 2014 at 8:08 AM, cko wrote:
> Hi,
>
> I'm using puppet to manage the puppet agent (package, config, service) in
> my Windows Server 2003
Hi,
I'm using puppet to manage the puppet agent (package, config, service) in
my Windows Server 2003 boxes.
Whenever I update the package, the puppet agent service gets stuck (STOP
PENDING).
The report returns:
*Fri May 09 12:13:51 +0200 2014
/Stage[main]/puppet_agent::Windows::Service/Serv
