Re: Uplading file via Lighttpd - system hangs
Hello guys, I have noticed today that I have another problem possibly related to this issue. I am running lighttpd+php-cgi in a jail on a 7.0-STABLE system as of Thu Aug 21 10:59:02 CEST 2008. The problem seems to be that lighttpd stops serving the pages, however I haven't had time to dig into this any more closer, but I have found out that there's a lot of connections to the lighty when it seems to be dead. May be it does not close the connections properly?? The only common thing here is that that this jail is serving a page where a lot of image uploading happens. On Mon, 22 Sep 2008 19:04:41 +0200, Mel [EMAIL PROTECTED] wrote: On Monday 22 September 2008 18:11:05 Yury Michurin wrote: Well, I'm working now on creating memory dump. and send it forward for more knowledgeable people, however, as you might notice, different people, with different hardware, and even different version 7.0 and 7.1, have the same problem. Even if lighttpd / php / some script / whatever misbehaves, system should not be halted by such userland proccess. I don't think it's halted, I think it's cluttered by invalid syscalls. Secondly, any userland process can make the system unresponsive, by bad coding. Just write /tmp and /var/tmp full. It's not so hard. I don't think that's the case here though. Any of you guys logging netstat -m output every 500ms? Maybe you can see mbufs being drained just before the system stops servicing syscalls. -- S pozdravom / Best regards Daniel Geržo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uplading file via Lighttpd - system hangs
If you check top command, do you see lighttpd using 99% CPU ? Also does both php and static content hang ? If you have these symptoms the problem is the same. I use strace and found that lighttpd doesn't accept more connections when this thing happens. Hello guys, I have noticed today that I have another problem possibly related to this issue. I am running lighttpd+php-cgi in a jail on a 7.0-STABLE system as of Thu Aug 21 10:59:02 CEST 2008. The problem seems to be that lighttpd stops serving the pages, however I haven't had time to dig into this any more closer, but I have found out that there's a lot of connections to the lighty when it seems to be dead. May be it does not close the connections properly?? The only common thing here is that that this jail is serving a page where a lot of image uploading happens. On Mon, 22 Sep 2008 19:04:41 +0200, Mel [EMAIL PROTECTED] wrote: On Monday 22 September 2008 18:11:05 Yury Michurin wrote: Well, I'm working now on creating memory dump. and send it forward for more knowledgeable people, however, as you might notice, different people, with different hardware, and even different version 7.0 and 7.1, have the same problem. Even if lighttpd / php / some script / whatever misbehaves, system should not be halted by such userland proccess. I don't think it's halted, I think it's cluttered by invalid syscalls. Secondly, any userland process can make the system unresponsive, by bad coding. Just write /tmp and /var/tmp full. It's not so hard. I don't think that's the case here though. Any of you guys logging netstat -m output every 500ms? Maybe you can see mbufs being drained just before the system stops servicing syscalls. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uplading file via Lighttpd - system hangs
On Monday 22 September 2008 05:46:37 Chris wrote: It looks like the freebsd-sendfile is broken. I had the same problems the last days and now I know the source of the problem. Have a look on this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=125592 Yeah, I looked into this, but I do not see why this has anything to do with sendfile in FreeBSD. When you upload a file, you (the server) don't *send* anything, you *read*, so sendfile(2) shouldn't even come into play. Why this magically starts working when changing the write backend, is a mystery, but most likely the answer lies in PHP. If you can, use a different upload script for testing, one that is not done via PHP, but plain CGI. There should be some available on the net. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uplading file via Lighttpd - system hangs
It looks like the freebsd-sendfile is broken. I had the same problems the last days and now I know the source of the problem. Have a look on this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=125592 Yeah, I looked into this, but I do not see why this has anything to do with sendfile in FreeBSD. When you upload a file, you (the server) don't *send* anything, you *read*, so sendfile(2) shouldn't even come into play. Why this magically starts working when changing the write backend, is a mystery, but most likely the answer lies in PHP. If you can, use a different upload script for testing, one that is not done via PHP, but plain CGI. There should be some available on the net. -- Mel im in a serious doubt that a write() family function could have possibly stop something from responding when login is still accepting read() buffer please dont tell me that a userland process can possibly halt everything unless there is a serious harware malfunction. i think this particular case needs solid debugging and investigation. nash ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uplading file via Lighttpd - system hangs
Well, I'm working now on creating memory dump. and send it forward for more knowledgeable people, however, as you might notice, different people, with different hardware, and even different version 7.0 and 7.1, have the same problem. Even if lighttpd / php / some script / whatever misbehaves, system should not be halted by such userland proccess. Regards, Yury. On Mon, Sep 22, 2008 at 6:33 PM, Nash Nipples [EMAIL PROTECTED]wrote: It looks like the freebsd-sendfile is broken. I had the same problems the last days and now I know the source of the problem. Have a look on this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=125592 Yeah, I looked into this, but I do not see why this has anything to do with sendfile in FreeBSD. When you upload a file, you (the server) don't *send* anything, you *read*, so sendfile(2) shouldn't even come into play. Why this magically starts working when changing the write backend, is a mystery, but most likely the answer lies in PHP. If you can, use a different upload script for testing, one that is not done via PHP, but plain CGI. There should be some available on the net. -- Mel im in a serious doubt that a write() family function could have possibly stop something from responding when login is still accepting read() buffer please dont tell me that a userland process can possibly halt everything unless there is a serious harware malfunction. i think this particular case needs solid debugging and investigation. nash ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Uplading file via Lighttpd - system hangs
On Monday 22 September 2008 18:11:05 Yury Michurin wrote: Well, I'm working now on creating memory dump. and send it forward for more knowledgeable people, however, as you might notice, different people, with different hardware, and even different version 7.0 and 7.1, have the same problem. Even if lighttpd / php / some script / whatever misbehaves, system should not be halted by such userland proccess. I don't think it's halted, I think it's cluttered by invalid syscalls. Secondly, any userland process can make the system unresponsive, by bad coding. Just write /tmp and /var/tmp full. It's not so hard. I don't think that's the case here though. Any of you guys logging netstat -m output every 500ms? Maybe you can see mbufs being drained just before the system stops servicing syscalls. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Uplading file via Lighttpd - system hangs
It looks like the freebsd-sendfile is broken. I had the same problems the last days and now I know the source of the problem. Have a look on this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=125592 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Uplading file via Lighttpd - system hangs
Hello, When trying uploading a file to a PHP script over lighttpd, the system just hangs. no output to the console, no panic, just hangs. I can still enter username/password to the login prompt from the keyboard, but then nothing happens. top that was running just freezes and stop refreshing. If i change #server.network-backend = freebsd-sendfile server.network-backend = write (Seen it here: http://trac.lighttpd.net/trac/ticket/1602 ) everything seems to be ok... How can I debug that issue further? I have no crash dump, nothing at the logs. I've got at the kernel: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN I'm currently running: FreeBSD sigma 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #7: Sat Sep 20 17:43:02 IDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/sigma i386 lighttpd-1.4.19_2 thanks in advance, Yury. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
