Bug #3169
closedsegfault in mod_status
Description
i updated to Mint 21 and thereby to lighttpd/1.4.63 (ssl).
today i requested /server-status and this very frequently resulted in a segfault of mod_status.
Due to the Mint upgrade i can't tell whether mod_status segfaulted earlier, but from my experience i'd say it didn't.
i'll attach the relevant part from the journal.
The issue may be related to long paths or paths with unusual characters (interpunctation etc.) which were delivered by a cgi script.
I believe this results in a "File" column entry of s.th. like "cgi_script_path ( file_path )" which might be too long. just guessing here.
Files
Updated by gstrauss over 2 years ago
14:40:19 kernel: lighttpd[67059]: segfault at 40 ip 00007f1eb75d1afa sp 00007ffdb86d40a0 error 4 in mod_status.so[7f1eb75d0000+3000]
I do not have a Mint environment, or a Mint build of lighttpd with debug symbols, so while this identifies mod_status, it will take more effort to identify the issue.
If you can frequently reproduce the issue, please attach to the lighttpd process using gdb (gdb -p <pid>), trigger a crash, and then get a stack trace (at the gdb> prompt type: bt full). Alternatively, if you have configured Mint to save core dumps, you can use gdb to get a stack trace from the core dump.
What was the version of lighttpd you were running before upgrading to Mint 21?
Updated by gstrauss over 2 years ago
Depending on your configuration, #3152 may be a similar bug, and was fixed in lighttpd 1.4.65.
Updated by Kio over 2 years ago
i ran lighttpd for a while with gdb attached, but during this time i failed to trigger the error.
i only experienced numerous broken pipes in mod_openssl in connection_state_machine() but i assume this is normal. also my lighttpd is compiled without symbols and thus bt's are less informative.
as for the previous version i don't know. :-(
i'll give it a second try tomorrow.
Updated by gstrauss over 2 years ago
Can you share the package info about lighttpd?apt-cache show lighttpd
You might also run (I think): debuginfo-install lighttpd to get debug symbols.
Updated by Kio over 2 years ago
i installed version 1.4.66 from source and run it in gdb.
as my homepage has little traffic i used wget locally to download some directories and requested the status page frequently during this time.
i could not trigger the error again, so it may no longer be present in 1.4.66.
the ticket can be closed. if it occurs again i can probably reopen it.
thanks,
Kio !
Updated by gstrauss over 2 years ago
- Status changed from Need Feedback to Missing Feedback
Thanks for the update.
I'll mark the issue as Missing Feedback since it could not be reproduced (yet)
If the issue occurs again for you, please try to get a stack trace and post here.
(You won't be able to re-open the issue, but if you post here, I'll see it)
Updated by gstrauss over 1 year ago
- Status changed from Missing Feedback to Fixed
Believed fixed in lighttpd 1.4.65 or lighttpd 1.4.66
Also available in: Atom