Giter Club home page Giter Club logo

Comments (6)

username-is-already-taken2 avatar username-is-already-taken2 commented on July 19, 2024 1

Hi @tas50 I tried the kill action method on another box and that worked fine. My thought is that maybe you should consider changing the default action to kill? (rather than exec)
In Exec mode the chef-client is hung and won't run again until terminated or the system is rebooted. In windows the chef-client installation creates a schedule tasks which will terminate a long running process after 3days.
image

That would be a long time to wait, just my 5p worth :)

from chef_client_updater.

username-is-already-taken2 avatar username-is-already-taken2 commented on July 19, 2024

As I have a couple of machines in Azure (same template and version of Chef I thought I would enable debug within the client.rb.

Might be significate but there was a couple of extra lines, going to sleep and the run of ohai.

[2017-06-27T16:02:52+00:00] INFO: powershell_script[name] ran successfully
[2017-06-27T16:02:52+00:00] WARN: Replacing ourselves with the new version of Chef to continue the run.
[2017-06-27T16:02:58+00:00] DEBUG: Sleeping for 0 seconds
[2017-06-27T16:02:58+00:00] DEBUG: Running Ohai with the following configuration: {}
[2017-06-27T16:02:58+00:00] WARN: Chef client 5032 is running, will wait for it to finish and then run.

Hope that helps

from chef_client_updater.

tas50 avatar tas50 commented on July 19, 2024

@username-is-already-taken2 If you set the post install action to kill this will probably resolve itself. The old client hasn't been killed and the new client won't run if the pid file for the previous client is still active.

from chef_client_updater.

username-is-already-taken2 avatar username-is-already-taken2 commented on July 19, 2024

After a reboot, re-running the chef-client removed the file that was kicking around.

from chef_client_updater.

tas50 avatar tas50 commented on July 19, 2024

A reboot would achieve the same end result of killing the old process. If you use kill as the post install action this will probably work as expected without a reboot. I'll close this out. Feel free to open it back up if you give that a try and it doesn't work.

from chef_client_updater.

lamont-granquist avatar lamont-granquist commented on July 19, 2024

we might want to document this in the README, i also saw this happen a bunch but never got around to tracking it down...

from chef_client_updater.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.