-
Notifications
You must be signed in to change notification settings - Fork 210
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 12 on RHEL7: chef-server-ctl reconfigure hangs when configuring embedded rabbitmq #62
Comments
This issue is caused by enterprise cookbook included in chef-server 12.0.1 (/opt/opscode/embedded/cookbooks/enterprise). From the log:
Within |
Opened an issue in enterprise cookbook: chef-cookbooks/enterprise-chef-common#26 |
This should be fixed in 12.0.3. |
its not fixed in chef-server-core-12.0.5-1.el6.x86_64.rpm |
Just got this same error trying to install chef-server-core-12.1.2-1.el7.x86_64.rpm inside a centos 7 docker container. For repeatability, Dockerfile is just: FROM centos
|
Sorry issue with Centos7, ignore the above comment: moby/moby#13297 |
Just got the same error on chef-server-core-12.3.0-1.el6.x86_64.rpm |
Got this same error with both 12.4.1 and 12.4.0 on Ubuntu 14.04. |
Same error for 12.6.0-1 on Ubuntu 16.04 |
Same error Chef Server 12.5.0-1 on Ubuntu 14.04. |
Reopened this as a number of people are seeing the same symptoms still. |
If these are occurring in Docker images, this is a known limitation - let's open a new issue for that so that we can track if this issue is occurring on supported configurations, or only under Docker. That being said, if you are seeing this on Docker, there is a workaround that you can try. Chef Server users runit - and if we tell it to run as a full init system, it takes care of this issue. To do this, manually fork the runsv-start that's embedded with chef-server. This will permit the runit-enabled services to start successfuly. If you're looking to reconfigure Chef Server after the container is up: Dockerfile: ADD /path/to/chef-server-startup.sh /chef-server-startup.sh
CMD ["bash", "/chef-server-startup.sh"] chef-server-startup.sh: #!/bin/bash
export PATH=/opt/opscode/bin:/opt/opscode/bin/embedded:$PATH
# Start this so that chef-server-ctl sv-related commands can
# interact with its services via runsv
/opt/opscode/embedded/bin/runsvdir-start &
chef-server-ctl reconfigure
# Something useful that also keeps the container running...
tail -f /var/log/opscode/nginx/access.log It's similar if you want to reconfigure in the Docker image build and start Chef Server in the running container. In this case, your container build will need to do the same thing: Dockerfile: ADD chef-server-setup.sh /chef-server-setup.sh
RUN /bin/bash /chef-server-setup.sh
ADD /path/to/chef-server-startup.sh /chef-server-startup.sh
CMD ["bash", "/chef-server-startup.sh"] chef-server-setup.sh: /opt/opscode/embedded/bin/runsvdir-start &
chef-server-ctl reconfigure
chef-server-startup.sh
```bash
#!/bin/bash
export PATH=/opt/opscode/bin:/opt/opscode/bin/embedded:$PATH
/opt/opscode/embedded/bin/runsvdir-start &
chef-server-ctl start
# Output current state of things for sanity's sake
chef-server-ctl status
# Something useful that also keeps the container running...
tail -f /var/log/opscode/nginx/access.log |
I'm not on Docker. Using Ubuntu14.04 on regular AWS EC2 VM. |
I am running it on a VM using Vagrant/VirtualBox. I believe my case was caused by the VM running low on memory. I bumped it from the default 2 Gb to 4 Gb and it I haven't had any issues since. |
Hi Everyone, Sorry you've had trouble getting chef-server installed. The originally reported issue is likely fixed (we build and test full installs of chef-server on RHEL 7 with every commit). I don't doubt, however, that many of you have seen similar looking error messages. I'm going to close this out, but if you are still seeing something similar, please open a new bug report with:
|
FYI, Got the same ERROR when trying to install chef-server-core-12.13 on EC2 micro instance with RHEL7.3, 1 CPU and 1 GB RAM and later Re-installed on EC2 Medium sized with 2 CPU and 4GB RAM which worked perfectly without any trouble |
I have tried this on docker, but still its not working. can some one please help me on this. export PATH=/opt/opscode/bin:/opt/opscode/bin/embedded:$PATH Start this so that chef-server-ctl sv-related commands caninteract with its services via runsv/opt/opscode/embedded/bin/runsvdir-start & |
Version
chef-server-core-12.0.1-1.x86_64.rpm
Downloaded from https://web-dl.packagecloud.io/chef/stable/packages/el/6/chef-server-core-12.0.1-1.x86_64.rpm
Environment
RHEL 7.0 x86_64
Summary
When I tried to install and configure a chef-server 12 on RHEL7, I got stuck when executing chef-server-ctl. I know current chef-server 12 does not officially support RHEL7. But since it is opensource, maybe we can find a workaround way here.
Recreate Procedure
Log and symptom
The process stuck at above forever. I tried to wait for hours, but not progress. I need to interrupt it by CTRL+C. And it reports as:
It will wait for a while on
execute[/opt/opscode/bin/private-chef-ctl start rabbitmq] action run
, and then failed.Similar Issue
Failures on RHEL 7 chef-cookbooks/runit#74 (comment)
However, it is using 11.x chef server
Chef Server runit install fails on CentOS 7 chef#1955
It was also using chef server 11.x. And from the output log, it fails to locate /etc/init folder, which does not fit the symptom here.
The text was updated successfully, but these errors were encountered: