Bug 1530548
Summary: | Update to lighttpd 1.4.48 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | David Anderson <fedora-packaging2> |
Component: | lighttpd | Assignee: | Gwyn Ciesla <gwync> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | gwync, matthias, rhbugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | lighttpd-1.4.48-1.el7 lighttpd-1.4.47-1.el6 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-01-18 23:32:45 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
David Anderson
2018-01-03 10:28:37 UTC
I've got an update coming for epel7, but 1.4.48 doesn't like EL-6's older autotools. I'm working on it. lighttpd-1.4.48-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5ac9ee4e7f lighttpd-1.4.48-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5ac9ee4e7f I'm fairly sure that this bug - with a trivial patch - is the cause of the segfault-ing that I'm seeing: https://redmine.lighttpd.net/issues/2822 (having strace-d my lighttpd process and watched it crash a few times, the last request is always one like the one in that bug report). Any chance that you could add that patch to the current lighttpd build on EL6, if getting 1.4.48 to build isn't an easy problem to fix? It would appear that: A. That patch is already in 1.4.46. B. I can get 1.4.46 to build on EL-6. Update incoming, please test. lighttpd-1.4.46-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-30b25ee0c6 OK - I will install this on Monday (the affected server is live, so Saturday evening is not a great time... though it currently segfaults, it is automatically restarted, so I'll stick with the known problem until Monday!). Though - the 1.4.47 and 1.4.48 changelogs indicate that 1.4.46 introduces 3 regressions (https://www.lighttpd.net/2017/11/11/1.4.48/ , https://www.lighttpd.net/2017/11/11/1.4.48/) - any chance of pulling in the patches for those? Unless I'm misreading this, as-is, I'll certainly be hit by this (patched in 1.4.47) regression if I try 1.4.46: https://redmine.lighttpd.net/issues/2830 I didn't get the other 2 bug numbers, just 2830. I can certainly try. :) This is the other bug that the changelog marks as a regression in 1.4.46: https://redmine.lighttpd.net/issues/2835 The other bug isn't indicated in the changelog, but a quick hunt reveals that it's this one (the patch is in the last-but-one post) https://redmine.lighttpd.net/boards/2/topics/7686 Though... you don't say whether 1.4.47 itself will already compile on EL6? (You mentioned that 1.4.48 is giving trouble). 1.4.47 wouldn't last I tried, but since learning what I learned in trying to build 1.4.48, it does. Update incoming with a patch for 2835. lighttpd-1.4.47-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-30b25ee0c6 Thank you. I've installed this now, and will let you know how it goes. I've not had time to investigate why, but after updating, I could only visit SSL websites. HTTP ones gave connection errors. Rolling back fixed it. Nothing in the logs. netstat indicated it was listening on the same ports/IPs. I will have to try it again later when I have more time and see what else I can find. I've got it up and running now. For reasons I don't understand (nothing in the changelog stands out), I had to uncomment the server.bind option in my lighttpd.conf (with value "0.0.0.0").... whereas, uncommenting that on 1.4.45 resulted in an error that port 80 was already in use. I think lighttpd has changed how it deals with listening on both IPv4 and IPv6 simultaneously - it doesn't seem to be a packaging problem. And I have no idea how common my (heavily customised) config file would be. I can confirm that with 1.4.47, the segfaults that I was getting with 1.4.45 no longer occur. Fantastic, thank for your help! I have been hit by this bug/regression, which might hit quite a few people. There is a patch available (the alternative is to re-write your configuration file). I think the patch is in 1.4.48, but clearly isn't in 1.4.47 (which I am running): https://redmine.lighttpd.net/issues/2830 This duplicate says that it was fixed in 1.4.47 - https://redmine.lighttpd.net/issues/2831 . (But as I say, I'm having the problem described; and the work-around in #2830 works for me). The patch for 2831 doesn't apply to 1.4.47, and I'm having difficulty finding where it should go. lighttpd-1.4.48-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. lighttpd-1.4.47-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |