Comments (6)
Closing this out since we've released a version that solves it as much as we can on an old chef client. New clients will handle this much better as @lamont-granquist mentioned
from chef_client_updater.
This is already less noisy in current chef-client versions:
Unpacking chef (13.1.31-1) ...
Setting up chef (13.1.31-1) ...
Thank you for installing Chef!
Transferring files to <kill-ubuntu-1604>
Starting Chef Client, version 13.1.31
Creating a new client identity for kill-ubuntu-1604 using the validator key.
resolving cookbooks for run list: ["test::kill"]
Synchronizing Cookbooks:
- test (1.0.0)
- chef_client_updater (3.0.1)
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 1 resources
Recipe: test::kill
* chef_client_updater[Install latest Chef] action update
* chef_gem[mixlib-install] action install
- install version >= 3.3.1 of package mixlib-install
- moving all files under /opt/chef to /opt/chef.upgrade[2017-07-15T02:24:50+00:00] WARN: Chef client is running forked with a supervisor. Sending TERM to parent process!
[2017-07-15T02:24:50+00:00] WARN: Chef client is running forked with a supervisor. Sending TERM to parent process!
[2017-07-15T02:24:50+00:00] FATAL: SIGTERM received, stopping
[2017-07-15T02:24:50+00:00] FATAL: SIGTERM received, stopping
[2017-07-15T02:24:50+00:00] WARN: New chef-client installed. Forcing chef exit!
[2017-07-15T02:24:50+00:00] WARN: New chef-client installed. Forcing chef exit!
Running handlers:
[2017-07-15T02:24:50+00:00] ERROR: Running exception handlers
[2017-07-15T02:24:50+00:00] ERROR: Running exception handlers
Running handlers complete
[2017-07-15T02:24:50+00:00] ERROR: Exception handlers complete
[2017-07-15T02:24:50+00:00] ERROR: Exception handlers complete
Chef Client failed. 1 resources updated in 14 seconds
[2017-07-15T02:24:50+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
[2017-07-15T02:24:50+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
[2017-07-15T02:24:50+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2017-07-15T02:24:50+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2017-07-15T02:24:50+00:00] ERROR: exit
[2017-07-15T02:24:50+00:00] ERROR: exit
from chef_client_updater.
And yet another example of the duplicated logger lines in chef 13 we still need to track down...
from chef_client_updater.
@lamont-granquist I didn't think about testing that on Chef Client 13.X. Thanks for the information.
One other question (before I can make sure this is good): what gets reported to automate and exception handlers? Are they told a failure occurred?
from chef_client_updater.
I assume based on ERROR: Running exception handlers
that it gets reported to automate, I have no idea how it shows up in that UI.
from chef_client_updater.
@mhedgpeth I've updated the cookbook to slightly improve the log output. Now you will see the message that the upgrade has completed before you see the warning that the kill/exec is going to happen. Previously the exec/kill was within the converge and happened before the logging fired. This might make it a bit more apparent what's going on, even in the older chef-client releases.
from chef_client_updater.
Related Issues (20)
- No checksum validation of handle.zip
- The PowerShell to reschedule the upgrade does not work (Windows) HOT 2
- "cannot load such file -- highline" after upgraded. HOT 8
- Direct Download - Unable to contain self signed certificate
- Require Chef Infra Client 12.5+
- Remove support for ChefDK
- Move the upgrade logic outside of Chef
- Chef client update fails on windows 7 citrix VDIs
- Cookbook removes scheduled task HOT 5
- Chef upgrade failing in windows10 version 2004 and later
- Cookbook hangs when upgrading on Solaris HOT 1
- Assumes `C:\opscode` exists HOT 1
- Calls mixlib-install even when `download_url_override` is set HOT 1
- Create Tag 3.12 HOT 4
- Deprecation warning for `unified_mode` HOT 2
- Latest release contains mac underscore files HOT 3
- The exec_command value cannot be overridden HOT 1
- Provide basic authentication when using download_url_override?
- Restart chef-client.service after upgrade
- product_name does not allow 'cinc' HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chef_client_updater.