chef-client may not restart post-logrotation

[aespinosa]

We use #1034 because of https://github.com/chef/chef/issues/4578 . Unfortunately, a restart may fail:

[2018-04-01T06:35:22-04:00] FATAL: Chef is already running pid 43711
[2018-04-01T06:35:22-04:00] WARN: Chef RFC 062 (https://github.com/chef/chef-rfc/blob/master/rfc062-exit-status.md) defines the exit codes that should be used with Chef.  Chef::Application::ExitCode defines valid exit codes In a future release, non-standard exit codes will be redefined as GENERIC_FAILURE unless `exit_status` is set to `:disabled` in your client.rb. (CHEF-2) at /opt/chef/embedded/lib/ruby/gems/2.3.0/gems/chef-12.19.36/bin/chef-client:26:in `<top (required)>'.
Please see https://docs.chef.io/deprecations_exit_code.html for further details and information on how to correct this problem.

This leaves us having no chef-runs silently.

[aespinosa]

Update: while this is unsolved, operators will have to check chef every monday (weeklyi logrotation time) if some chef-clients died in the cluster.