-
Notifications
You must be signed in to change notification settings - Fork 197
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
Failures on RHEL 7 #74
Comments
Sorry about the formatting... |
So... I tried forcing "rabbitmq-server" into action:
BTW:
and
Still fails at trying to start "rabbitmq" |
Ran: yum install glibc-static rpmdevtools No change... |
looks to me like it IS running: rabbitmq 2818 1 0 15:04 ? 00:00:04 /usr/lib64/erlang/erts-5.10.4/bin/beam -W w -K true -A30 -P 1048576 -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.1.5/sbin/../ebin -noshell -noinput -s rabbit boot -sname rabbit@chefent -boot start_sasl -kernel inet_default_connect_options [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false -rabbit error_logger {file,"/var/log/rabbitmq/[email protected]"} -rabbit sasl_error_logger {file,"/var/log/rabbitmq/[email protected]"} -rabbit enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir "/usr/lib/rabbitmq/lib/rabbitmq_server-3.1.5/sbin/../plugins" -rabbit plugins_expand_dir "/var/lib/rabbitmq/mnesia/rabbit@chefent-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit@chefent" |
I give for now... I will back the system down to 6.5 or 6.6. |
I am having the exact same set of issues trying to install Jenkins on Centos 7 using the Ops code Jenkins cookbook with the 'war' option (which uses runit to run the war). Similarly The ops-code chef server cookbook, though it appears to use its own runit cookbook, has a detailed post on the same problem Chef Server runit install fails on CentOS 7 #1955. The short of it being that from 6.x to 7 Centos switched from using upstart to systemd as its service manager. So it seems that the solution is to update the runit cookbook configure runit to use systemd on Cento >= 7. |
Dang it...!!! I would have never thought to check for that, I guess because it appeared to be alive (??? have to look back at my notes). Thanks though, for the feedback. It will be a little while before I try it again being that I could afford more time since I was being pressed for a working solution. |
While we do need to get systemd support added to this cookbook so runit can work properly on CentOS/RHEL 7, this is being addressed in the Chef Server's cookbooks under this PR. |
Since the PR referenced (chef-cookbooks/enterprise-chef-common#25) above is merged has this issue been resolved? |
@slyness No I do not think that this issue is resolved. The enterprise-chef-common PR is specific to enterprise-chef which does not use the runit cookbook (but does much the same thing). The runit cookbook itself appears to still broken vis-a-vis Centos 7. I am still unable to install Jenkins on Centos 7 via the jenkins cookbook due to this issue, and I imagine the original reporter is still unable to install RabbitMQ for the same reason. |
Just tried install chef on CentOS7 and ran into the same issue. Has there been any progress on this ? |
I have this issue on Ubuntu 14.04. |
has anyone been able to get passed this point? seem to have this issue in clean centos 7.0 install in Docker, but looks like it might be working correctly if install directly on Host. |
I am experiencing a similar issue. The chef 'artifactory' cookbook depends upon this 'runit' cookbook and I get this error -
Is there a workaround/fix? |
@mmukherjee -- I just went through a similar exercise. Are you running Chef 11? If so, Chef 11 defaults assume CentOS is still using sysvinit. I got around the issue by changing the service provider:
|
Stuck with rabbitmq failing....
Before I get into the details, a couple of things I needed to do on a fresh Centos 7 install:
Just hangs right here....
The text was updated successfully, but these errors were encountered: