Re: Re: Re: Chef 12.4.1 client for Windows 2012r2

(sent via wrong address, resending)

Hello,

The alternative workaround is to run Chef-client as a scheduled task which
will not have the same startup dependencies as starting it as a service.
The chef-client cookbook supports this method[1].

There’s arguments to be made for both methods, but scheduled task is more
resilient than windows_service to the startup issues, and I’d recommend it
to anyone experiencing those issues.

[1]
https://github.com/opscode-cookbooks/chef-client/blob/master/recipes/task.rb

On Mon, Aug 31, 2015 at 10:18 AM, Julian Varanini jvaranini@hotmail.com
wrote:

Thanks Gregory,

I forgot to mention these are AWS instances. I going to try other
windows 2012r2 instances and see if the behavior changes.

Thanks again,

Julian

Sent from my iPhone

On Aug 31, 2015, at 10:12 AM, Gregory K. Ruiz-Ade gkra@unnerving.org
wrote:

We’ve run into this issue as well on our Windows 2012R2 hosts. In our
cases, it seems that setting startup to Automatic (Delayed) does indeed fix
the startup problem, but from the documentation for chef_service_manager
I’m not sure how to do this automatically, or if it would require some
mangling via windows_service in a recipe.

We haven’t noticed this issue on other non-2012R2 Windows hosts.

Thanks,

Gregory


Gregory K. Ruiz-Ade gkra@unnerving.org
https://keybase.io/gkra

On Aug 31, 2015, at 9:04 AM, Julian Varanini jvaranini@hotmail.com
wrote:

We are having an issue with the

12.4.1 chef client for windows 2012 R2 (12.4.0 fails as well). No matter
if

we install the service via the msi or the chef_service_manager command the

chef service will not start on its own and reports to windows that it has

timed out. I have read online that if you set it to Automatic delayed
that

this fixes the issue however that has not worked for us. I have also
added DNS and wmi as dependencies. I can start it

manually and it runs as it should but it will not start on its own. Any
help is appreciated.

Thanks

Julian


Galen Emery — Automation Engineer

425.341.3619 – galen@chef.io my: Linkedin
https://www.linkedin.com/in/gemery
Twitter
http://www.twitter.com/galen_emery

CHEF

TM


https://t.yesware.com/tl/fa4d128b44f15b1f6d3a08e3c3ba836326ce28ca/7963335485c64b73a77697a84b5671ed/ae649db7c07210ea32a5b85e88a4c254?ytl=http%3A%2F%2Fwww.getchef.com%2F

Blog
https://t.yesware.com/tl/fa4d128b44f15b1f6d3a08e3c3ba836326ce28ca/7963335485c64b73a77697a84b5671ed/7f97fd5d54b095e69ab2db7730a19361?ytl=http%3A%2F%2Fwww.getchef.com%2Fblog%2F
Facebook
https://t.yesware.com/tl/fa4d128b44f15b1f6d3a08e3c3ba836326ce28ca/7963335485c64b73a77697a84b5671ed/79b4a7dcc9a3776f42f0c230394779a0?ytl=https%3A%2F%2Fwww.facebook.com%2Fgetchefdotcom
Twitter https://twitter.com/chef Youtube
https://t.yesware.com/tl/fa4d128b44f15b1f6d3a08e3c3ba836326ce28ca/7963335485c64b73a77697a84b5671ed/8e5448001e916bf0317a4e59de1ba7a2?ytl=https%3A%2F%2Fwww.youtube.com%2Fgetchef

Hi Galen,

Good idea, it’s something I was considering but was not sure if it’s generally accepted as I’ve been out of chef for about 1.5 years. I’ll try this method as well.

Thanks

Julian

Sent from my iPhone

On Aug 31, 2015, at 10:25 AM, Galen Emery galen@getchef.com wrote:

(sent via wrong address, resending)

Hello,

The alternative workaround is to run Chef-client as a scheduled task which will not have the same startup dependencies as starting it as a service. The chef-client cookbook supports this method[1].

There’s arguments to be made for both methods, but scheduled task is more resilient than windows_service to the startup issues, and I’d recommend it to anyone experiencing those issues.

[1] https://github.com/opscode-cookbooks/chef-client/blob/master/recipes/task.rb

On Mon, Aug 31, 2015 at 10:18 AM, Julian Varanini jvaranini@hotmail.com wrote:
Thanks Gregory,

I forgot to mention these are AWS instances. I going to try other windows 2012r2 instances and see if the behavior changes.

Thanks again,

Julian

Sent from my iPhone

On Aug 31, 2015, at 10:12 AM, Gregory K. Ruiz-Ade gkra@unnerving.org wrote:

We’ve run into this issue as well on our Windows 2012R2 hosts. In our cases, it seems that setting startup to Automatic (Delayed) does indeed fix the startup problem, but from the documentation for chef_service_manager I’m not sure how to do this automatically, or if it would require some mangling via windows_service in a recipe.

We haven’t noticed this issue on other non-2012R2 Windows hosts.

Thanks,

Gregory


Gregory K. Ruiz-Ade gkra@unnerving.org
https://keybase.io/gkra

On Aug 31, 2015, at 9:04 AM, Julian Varanini jvaranini@hotmail.com wrote:

We are having an issue with the
12.4.1 chef client for windows 2012 R2 (12.4.0 fails as well). No matter if
we install the service via the msi or the chef_service_manager command the
chef service will not start on its own and reports to windows that it has
timed out. I have read online that if you set it to Automatic delayed that
this fixes the issue however that has not worked for us. I have also added DNS and wmi as dependencies. I can start it
manually and it runs as it should but it will not start on its own. Any help is appreciated.

Thanks

Julian


Galen Emery — Automation Engineer
425.341.3619 – galen@chef.io my: Linkedin Twitter
CHEF
TM
CHEF.IO

Blog Facebook Twitter Youtube