Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1478278
Summary: | Error messages about invalid argument during start. | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Frank Büttner <bugzilla> |
Component: | varnish | Assignee: | Ingvar Hagelund <ingvar> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | ingvar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | varnish-4.0.5-3.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-03-03 15:23:40 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
Frank Büttner
2017-08-04 07:51:03 UTC
This is a simple race between the varnish daemons and systemd. systemd is not patient enough waiting for the daemon to open its pidfile, and gives up. Workaround: Add ExecStartPost=/bin/sleep 0.5 to the varnish*.service files and it should work. I'll try to figure out how to deal with this most correctly. Ingvar Reproduced with newer versions of varnish (5.1.3) on epel7. Seems this is not a problem with newer versions of systemd. Fedora 25 and 26 does not have this problem. So this means that this is a problem with systemd, not with varnish. I'll leave it with the workaround, and add that to the next update of varnish for epel7. Ingvar Hi Ingvar, I have try it, and it will solve it. FEDORA-EPEL-2022-18ac3af1c8 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-18ac3af1c8 FEDORA-EPEL-2022-18ac3af1c8 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-18ac3af1c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-18ac3af1c8 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |