Bug 974041
Summary: | [virt-sandbox-service] Fail to start nginx service in a container | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alex Jia <ajia> |
Component: | libvirt-sandbox | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 20 | CC: | berrange, bperkins, dwalsh, dyuan, gsun, mzhan, virt-maint, weizhan, zpeng |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-29 12:00:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alex Jia
2013-06-13 10:41:45 UTC
[root@dell-op790-03 libvirt-sandbox]# rpm -q nginx nginx-1.2.5-1.fc18.x86_64 (In reply to Alex Jia from comment #0) > Additional info: [root@dell-op790-03 libvirt-sandbox]# virt-sandbox-service connect test.example.org sh-4.2# journalctl -xn -- Logs begin at Thu 2013-06-13 17:07:49 CST, end at Thu 2013-06-13 17:07:49 CST. -- Jun 13 17:07:49 test.example.org systemd-journal[11]: Allowing runtime journal files to grow to 1.0M. Jun 13 17:07:49 test.example.org systemd-journal[11]: Journal started Jun 13 17:07:49 test.example.org systemd-tmpfiles[10]: Failed to create device node /dev/lp0: Operation not permitted Jun 13 17:07:49 test.example.org systemd-tmpfiles[10]: Failed to create device node /dev/lp1: Operation not permitted Jun 13 17:07:49 test.example.org systemd-tmpfiles[10]: Failed to create device node /dev/lp2: Operation not permitted Jun 13 17:07:49 test.example.org systemd-tmpfiles[10]: Failed to create device node /dev/lp3: Operation not permitted Jun 13 17:07:49 test.example.org nginx[12]: nginx: [emerg] open() "/etc/nginx/nginx.test.example.org.conf" failed (2: No such file or directory) Jun 13 17:07:49 test.example.org nginx[12]: nginx: configuration file /etc/nginx/nginx.test.example.org.conf test failed Daniel, need we to create /etc/nginx/nginx.test.example.org.conf? Does it work if you use the -C (--copy) command to copy this content off of /etc/nginx directory? (In reply to Daniel Walsh from comment #3) > Does it work if you use the -C (--copy) command to copy this content off of > /etc/nginx directory? Daniel, the nginx.test.example.org.conf file doesn't exist under the /etc/nginx in the container, so I can't use -C option to copy it, but the nginx.conf exists, maybe you mean I need to copy it into /etc/nginx then rename it to nginx.test.example.org.conf in the container, however, the nginx.conf is a empty file without any content, it's also my first question, whether we need to manually configure nginx.conf or nginx.test.example.org.conf in the container? thanks. [root@dell-op790-03 ~]# ll /var/lib/libvirt/filesystems/test.example.org/etc/nginx/ total 4 drwxr-xr-x. 2 root root 4096 Jun 13 16:44 conf.d -rw-r--r--. 1 root root 0 Jun 13 16:44 fastcgi.conf -rw-r--r--. 1 root root 0 Jun 13 16:44 fastcgi.conf.default -rw-r--r--. 1 root root 0 Jun 13 16:44 fastcgi_params -rw-r--r--. 1 root root 0 Jun 13 16:44 fastcgi_params.default -rw-r--r--. 1 root root 0 Jun 13 16:44 koi-utf -rw-r--r--. 1 root root 0 Jun 13 16:44 koi-win -rw-r--r--. 1 root root 0 Jun 13 16:44 mime.types -rw-r--r--. 1 root root 0 Jun 13 16:44 mime.types.default -rw-r--r--. 1 root root 0 Jun 13 16:44 nginx.conf -rw-r--r--. 1 root root 0 Jun 13 16:44 nginx.conf.default -rw-r--r--. 1 root root 0 Jun 13 16:44 scgi_params -rw-r--r--. 1 root root 0 Jun 13 16:44 scgi_params.default -rw-r--r--. 1 root root 0 Jun 13 16:44 uwsgi_params -rw-r--r--. 1 root root 0 Jun 13 16:44 uwsgi_params.default -rw-r--r--. 1 root root 0 Jun 13 16:44 win-utf Yes you would need to configure the service within the container just like you would need to configure it if it was on the host. This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20 This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |