Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chef-server-ctl reconfigure fails if procps is already running #2323

Closed
oleg-z opened this issue Oct 29, 2014 · 7 comments
Closed

chef-server-ctl reconfigure fails if procps is already running #2323

oleg-z opened this issue Oct 29, 2014 · 7 comments

Comments

@oleg-z
Copy link

oleg-z commented Oct 29, 2014

Version:

chef server 12 rc5

Environment:

Ubuntu 14.10 x64

Scenario:

install chef server package

Steps to Reproduce:

chef-server-ctl reconfigure

Problem:

/etc/init.d/procps start exits with code 1 if it's running

Log:

==> env-manager-cibuild1: ================================================================================�[0m
==> env-manager-cibuild1: �[31mError executing action `start` on resource 'service[procps]'�[0m
==> env-manager-cibuild1: ================================================================================�[0m
==> env-manager-cibuild1: 
==> env-manager-cibuild1: �[0m
==> env-manager-cibuild1: Mixlib::ShellOut::ShellCommandFailed�[0m
==> env-manager-cibuild1: ------------------------------------�[0m
==> env-manager-cibuild1: Expected process to exit with [0], but received '1'
==> env-manager-cibuild1: ---- Begin output of /etc/init.d/procps start ----
==> env-manager-cibuild1: STDOUT: 
==> env-manager-cibuild1: STDERR: start: Job is already running: procps
==> env-manager-cibuild1: ---- End output of /etc/init.d/procps start ----
==> env-manager-cibuild1: Ran /etc/init.d/procps start returned 1�[0m
==> env-manager-cibuild1: 
==> env-manager-cibuild1: �[0m
==> env-manager-cibuild1: Resource Declaration:�[0m
==> env-manager-cibuild1: ---------------------�[0m
==> env-manager-cibuild1: # In /opt/opscode/embedded/cookbooks/private-chef/recipes/postgresql.rb
==> env-manager-cibuild1: 
==> env-manager-cibuild1:  68:   service "procps" do
==> env-manager-cibuild1:  69:     action :nothing
==> env-manager-cibuild1:  70:   end
==> env-manager-cibuild1:  71: 
==> env-manager-cibuild1: �[0m
==> env-manager-cibuild1: 
==> env-manager-cibuild1: �[0m
==> env-manager-cibuild1: Compiled Resource:�[0m
==> env-manager-cibuild1: ------------------�[0m
==> env-manager-cibuild1: # Declared in /opt/opscode/embedded/cookbooks/private-chef/recipes/postgresql.rb:68:in `from_file'
==> env-manager-cibuild1: 
==> env-manager-cibuild1: service("procps") do
==> env-manager-cibuild1:   action [:nothing]
==> env-manager-cibuild1:   supports {:restart=>false, :reload=>false, :status=>false}
==> env-manager-cibuild1:   retries 0
==> env-manager-cibuild1:   retry_delay 2
==> env-manager-cibuild1:   guard_interpreter :default
==> env-manager-cibuild1:   service_name "procps"
==> env-manager-cibuild1:   pattern "procps"
==> env-manager-cibuild1:   cookbook_name :"private-chef"
==> env-manager-cibuild1:   recipe_name "postgresql"
==> env-manager-cibuild1: end
==> env-manager-cibuild1: �[0m
@stevendanna
Copy link
Contributor

I imagine this is due to a change in the procps init script. AFAIK, procps typically isn't a service but just a small shell script that runs sysctl -f on some config files in etc.

@lamont-granquist
Copy link
Contributor

Looks like a bug in Ubuntu 14.10:

https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1332362

@lamont-granquist
Copy link
Contributor

technically this is also a bug in chef-server so would need to be opened against https://github.com/opscode/chef-server, this is only the repo for the client code.

@lamont-granquist
Copy link
Contributor

same result trying to use upstart:

# start procps
start: Job is already running: procps

@oleg-z
Copy link
Author

oleg-z commented Oct 31, 2014

I didn't realize this repo isn't place for chef server issues. Should I reopen it against chef-server?

@btm
Copy link
Contributor

btm commented Oct 31, 2014

@oleg-z it's okay. yes, please open an issue over at https://github.com/opscode/chef-server/issues. Once you do link to it from here in case someone else ends up here and close this issue please.

@mmzyk
Copy link

mmzyk commented Nov 3, 2014

Closing this out in favor of the issue opened over on the server repo. Thanks @oleg-z

@mmzyk mmzyk closed this as completed Nov 3, 2014
@chef chef locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants