You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chef-server-ctl (and any other -ctl programs) should unset or override the SVDIR environment variable.
I customize the environment variable SVDIR on all my cheffed servers, which broke chef-server-ctl:
$ chef-server-ctl status
fail: bookshelf: unable to change to service directory: file does not exist
fail: nginx: unable to change to service directory: file does not exist
fail: oc_bifrost: unable to change to service directory: file does not exist
fail: oc_id: unable to change to service directory: file does not exist
fail: opscode-erchef: unable to change to service directory: file does not exist
fail: opscode-expander: unable to change to service directory: file does not exist
fail: opscode-expander-reindexer: unable to change to service directory: file does not exist
fail: opscode-pushy-server: unable to change to service directory: file does not exist
fail: opscode-reporting: unable to change to service directory: file does not exist
fail: opscode-solr4: unable to change to service directory: file does not exist
fail: postgresql: unable to change to service directory: file does not exist
fail: rabbitmq: unable to change to service directory: file does not exist
fail: redis_lb: unable to change to service directory: file does not exist
It also breaks reconfigure as well. :-(
The text was updated successfully, but these errors were encountered:
Thanks for filing this bug. Unsetting SVDIR at the start of chef-server-ctl definitely seems like the best course of action here. We should probably do that in omnibus-ctl directly if possible.
chef-server-ctl
(and any other-ctl
programs) should unset or override theSVDIR
environment variable.I customize the environment variable
SVDIR
on all my cheffed servers, which brokechef-server-ctl
:It also breaks
reconfigure
as well. :-(The text was updated successfully, but these errors were encountered: