lighty labs

Today

18:59 Lighttpd Bug #3058: rare spontaneous segfaults

See the one-line patch at the tip of lighttpd git master.
I understand that you need to keep parts of your configura... gstrauss

18:10 Lighttpd Bug #3058: rare spontaneous segfaults

lighttpd should not use 100% CPU unless lighttpd is really busy doing productive work or unless you have a custom mod... gstrauss

16:36 Lighttpd Bug #3058: rare spontaneous segfaults

Among the changes in lighttpd 1.4.56 are improvements to @mod_proxy@. If your lighttpd instance crashes again, pleas... gstrauss

16:25 Lighttpd Bug #3058: rare spontaneous segfaults

BTW, it is not surprising that lighttpd 1.4.56 crashed for you since #3048 was fixed in lighttpd 1.4.57. When you tr... gstrauss

17:02 Lighttpd Revision 471ab4dd: [core] fix 100% CPU spin if traffic limit hit

(thx Dirk) (reported on FreeBSD)
HTTP/1.1 requests might end up spinning if traffic limits are configured
(connect... gstrauss

17:01 Lighttpd Revision fcbfc083: [core] check more carefully after SSL_WANT_WRITE

con->is_readable and con->is_writable might be set to -1 by TLS modules
which encounter SSL_WANT_READ or SSL_WANT_WRI... gstrauss

2021-01-18

21:04 Lighttpd Bug #3058: rare spontaneous segfaults

> Do you want me to list all packages?
Not at this time. I am asking questions that will hopefully lead you in th... gstrauss

19:57 Lighttpd Bug #3058: rare spontaneous segfaults

> I disabled various parts of the configuration - the origin seemed to be Nextcloud.
Which parts? Did you try dis... gstrauss

19:53 Lighttpd Bug #3058: rare spontaneous segfaults

> Both: it crashes with segfault -> lighttpd-angel restarts the process -> it is almost immediately going 100% for so... gstrauss

19:20 Lighttpd Bug #3058: rare spontaneous segfaults

mgottinger: you titled this post "rare spontaneous segfaults". Are you seeing lighttpd crash? Or are you seeing lig... gstrauss