-----Original Message----- From: Jeff Rush [mailto:jrush@taupro.com]
Yes, there is a timeout value buried in ZServer. Go look in the file /usr/share/zope/ZServer/HTTPServer.py, class zhttp_channel. There is a class variable 'zombie_timeout', set to 100 minutes. Also look in /usr/share/zope/ZServer/medusa/http_server.py for 'zombie' code, *both* in the http_channel class and status_handler class. In the medua/http_server.py class, that timeout is *** 30 minutes ***.
Well, I tweaked the values to 120 minutes, but it still won't work. This time, it timed out after about 40 minutes. Apache showed the following: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /artists/boj/dibugg/add_mp3. Reason: Error reading from remote server And Zope printed the following to the console: 2000-03-11T00:09:50 ERROR(200) ZServer uncaptured python exception, closing channel <zhttp_channel connected 212.71.72.22:20245 at 116c50 channel#: 1575 requests:1> (exceptions.AttributeError:data [/opt/zope-mp3/ZServer/medusa/asyncore.py|poll|59] [/opt/zope-mp3/ZServer/medusa/asyncore.py|handle_read_event|291] [/opt/zope-mp3/ZServer/medusa/asynchat.py|handle_read|103] [/opt/zope-mp3/ZServer/medusa/http_server.py|collect_incoming_data|439] [/opt/zope-mp3/ZServer/medusa/http_server.py|collect_incoming_data|143] [/opt/zope-mp3/ZServer/HTTPServer.py|collect_incoming_data|300]) And I logged everything with a HTTP proxy on my machine. Junkbuster put out this: junkbstr: accept connection ... scan: POST /artists/boj/zoff/add_mp3 HTTP/1.0 scan: Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */* scan: Referer: http://mp3.no/artists/boj/zoff/upload crunch! scan: Accept-Language: no scan: Content-Type: multipart/form-data; boundary=---------------------------7d01ae2c904ac scan: Accept-Encoding: gzip, deflate scan: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) default scan: Host: mp3.no scan: Content-Length: 10689875 scan: Proxy-Connection: Keep-Alive crunch! scan: Pragma: no-cache scan: Cookie: dtpref_rows="20"; dtpref_cols="65" crunch! scan: Authorization: Basic Ym9qOmdhZ2E= junkbstr: GPC mp3.no/artists/boj/zoff/add_mp3 junkbstr: connect to: mp3.no ... OK OK junkbstr: accept connection ... scan: GET / HTTP/1.0 scan: Accept: */* scan: Accept-Language: no scan: Accept-Encoding: gzip, deflate scan: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) default scan: Host: mp3.no scan: Proxy-Connection: Keep-Alive crunch! scan: Cookie: dtpref_rows="20"; dtpref_cols="65" crunch! junkbstr: GPC mp3.no/ junkbstr: connect to: mp3.no ... OK scan: HTTP/1.0 502 Proxy Error scan: Date: Sat, 11 Mar 2000 13:36:49 GMT scan: Server: Apache/1.3.9 (Unix) PHP/3.0.13 mod_ssl/2.4.5 OpenSSL/0.9.4 scan: Connection: close crunch! scan: Content-Type: text/html scan: HTTP/1.0 502 Proxy Error scan: Date: Sat, 11 Mar 2000 13:37:40 GMT scan: Server: Apache/1.3.9 (Unix) PHP/3.0.13 mod_ssl/2.4.5 OpenSSL/0.9.4 scan: Connection: close crunch! scan: Content-Type: text/html --------------------------------- So, the questions are: 1. Will I solve this temorarily by switching to Apache/PCGI/FCGI? 2. What is wrong with medusa? Have anybody else experienced the same thing? 3. Does Junkbuster give you enough info? Or should I use some other logging product? (I can send the whole log if required. It's 13K.) Thanks in advance, Alexander.