Bug 1272520
| Summary: | myproxy-server cannot create pidfile | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Matyas Selmeci <mselmeci> | ||||
| Component: | myproxy | Assignee: | Steve Traylen <steve.traylen> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | epel7 | CC: | andrew.elwell, jbasney, mattias.ellert, steve.traylen | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | myproxy-6.1.15-2.fc23 myproxy-6.1.15-2.fc22 myproxy-6.1.15-2.fc21 myproxy-6.1.15-2.el5 myproxy-6.1.15-2.el7 myproxy-6.1.15-2.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-01 02:31:13 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: | |||||||
| Attachments: |
|
||||||
The /var/run/myproxy-server is created by tmpfiles.d $ cat /usr/lib/tmpfiles.d/myproxy-server.conf D /var/run/myproxy-server 0710 myproxy root - What's the recommended fix, then? Run "systemd-tmpfiles myproxy-server.conf" in the %post script for myproxy-server? Or put Requires=systemd-tmpfiles-setup After=systemd-tmpfiles-setup in the service file? Or something else? myproxy-6.1.15-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-fd2fb0355c myproxy-6.1.15-2.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-91efe6bbae myproxy-6.1.15-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-1d5c0ccdce myproxy-6.1.15-2.el5 has been submitted as an update to Fedora EPEL 5. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-40ef4e3c14 myproxy-6.1.15-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-2d4b6bd9bb myproxy-6.1.15-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update myproxy' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-1d5c0ccdce myproxy-6.1.15-2.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update myproxy' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-91efe6bbae myproxy-6.1.15-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update myproxy' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-2d4b6bd9bb myproxy-6.1.15-2.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'yum --enablerepo=epel-testing update myproxy' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7a79236ad7 myproxy-6.1.15-2.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'yum --enablerepo=epel-testing update myproxy' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-40ef4e3c14 myproxy-6.1.15-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'yum --enablerepo=epel-testing update myproxy' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-fd2fb0355c myproxy-6.1.15-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. myproxy-6.1.15-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. myproxy-6.1.15-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. myproxy-6.1.15-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. myproxy-6.1.15-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. myproxy-6.1.15-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 1083749 [details] ExecStartPre line for myproxy-server.service to create /var/run/myproxy-server owned by myproxy:myproxy Description of problem: "systemctl start myproxy-server" hangs on startup; the logs show this error: "Cannot open or create pidfile /var/run/myproxy-server/myproxy.pid" Examining the filesystem shows that "/var/run/myproxy-server" does not exist. When I created the directory and made it owned by myproxy:myproxy, the problem went away. Version-Release number of selected component (if applicable): 6.1.15-1.el7 How reproducible: Always Steps to Reproduce: 1. Install myproxy-server 2. systemctl enable myproxy-server Actual results: Service times out waiting for the pidfile to be created. Expected results: Service starts successfully. Additional info: The SysV init script for myproxy-server used to create the directory on startup, but the SystemD service file does not do that. myproxy-server runs as the user myproxy, so I can't change it to write its pidfile into /var/run/myproxy.pid (for example), since it doesn't have the privileges. I will attach a patch for the service file that fixes the problem.