Ticket #1554 (closed defect: invalid)
lighttpd [1.4.18] RSTs TCP connections if mysql dies, and ceases to work
| Reported by: | hugo | Owned by: | jan |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | core | Version: | 1.4.18 |
| Severity: | blocker | Keywords: | |
| Cc: | Blocked By: | ||
| Need User Feedback: | no | Blocking: |
Description
FreeBSD 7.0-RC1 amd64 lighttpd-1.4.18_1
My MySQL server is crashing regularly with a bus error. While it restarts on it's own, all my webservers running lighttpd will cease to work properly.
A tcpdump analysis shows that lighty is just RSTing connections. FastCGI (php) doesn't work, /server-status doesn't work, and getting a bogus file (in the hopes of getting a 404) doesn't work either (so it isn't just fastcgi going down).
I do not have a ktrace and/or packet capture of this chain of events at hand, but will gladly provide one the next time this happens.
p.s: This is happening on a moderately loaded site (2500 queries/sec to mysql), the volume of connections/s to mysql must be a factor in lighty going nuts while mysql doesn't come back.
p.p.s: In very rare ocasions, one or two webservers in the farm will still be functioning after mysql crashing, but the majority just RST connections. I believe this is a mere coincidence, but here's the info anyway.

