[imp] Zero Sized Reply
Caylan Van Larson
caylan at cs.und.edu
Tue Jul 29 08:36:39 PDT 2003
On 29 Jul 2003, Adam Williams wrote:
> > I am experiencing a similar error however I am not using squid. What
> > happens if you bypass squid? In my experience this only happens when I
>
> We've had this "Zero Sized Reply" intermittantly for ages. Squid is not
> a factor.
I'm no squid expert but "Zero Sized Reply" sounds pretty generic. That's
the reason I wanted to get squid out of the picture via "bypass squid."
> > have more than one attachment. Here are some other symptoms I'm having
> > while sending a message with >1 attachments:
I'm sticking by my:
>1 attachment = frozen browser
or in Fernando's case:
>1 attachment = frozen proxy => "Zero Sized Reply"
> We have it when sending any kind of message. I'll bet if you check your
> log you'll see that an apache process abended. Since multiple people
> may be serviced by that one httpd, on a large network it will
> simultaneously happen to several people.
I'd have to disagree. Here is my reasoning:
* Immediately after apache restart:
--SNIP
Current Time: Tuesday, 29-Jul-2003 10:30:14 CDT
Restart Time: Tuesday, 29-Jul-2003 10:30:13 CDT
Parent Server Generation: 7
Server uptime: 1 second
Total accesses: 0 - Total Traffic: 0 kB
CPU Usage: u0 s0 cu0 cs0
0 requests/sec - 0 B/second -
1 requests currently being processed, 4 idle servers
W____...........................................................
................................................................
................................................................
................................................................
--SNAP
* Immediately after sent composition of an email w/ 2 attachments:
--SNIP
Current Time: Tuesday, 29-Jul-2003 10:31:39 CDT
Restart Time: Tuesday, 29-Jul-2003 10:30:13 CDT
Parent Server Generation: 7
Server uptime: 1 minute 26 seconds
Total accesses: 10 - Total Traffic: 15 kB
CPU Usage: u.23 s.02 cu0 cs0 - .291% CPU load
.116 requests/sec - 178 B/second - 1536 B/request
2 requests currently being processed, 4 idle servers
__W_W_..........................................................
................................................................
................................................................
................................................................
--SNAP
* Now it's frozen so I hit send 15 more times and wait 30 seconds:
--SNIP
Current Time: Tuesday, 29-Jul-2003 10:32:23 CDT
Restart Time: Tuesday, 29-Jul-2003 10:30:13 CDT
Parent Server Generation: 7
Server uptime: 2 minutes 10 seconds
Total accesses: 11 - Total Traffic: 19 kB
CPU Usage: u.28 s.03 cu0 cs0 - .238% CPU load
.0846 requests/sec - 149 B/second - 1768 B/request
37 requests currently being processed, 0 idle servers
WWWWWWWWWWWWWWWWWWWWWWWSWSWWSSWSSSSSS...........................
................................................................
................................................................
................................................................
--SNAP
* Here is a minute later:
--SNIP
Current Time: Tuesday, 29-Jul-2003 10:33:23 CDT
Restart Time: Tuesday, 29-Jul-2003 10:30:13 CDT
Parent Server Generation: 7
Server uptime: 3 minutes 10 seconds
Total accesses: 21 - Total Traffic: 170 kB
CPU Usage: u.55 s.08 cu0 cs0 - .332% CPU load
.111 requests/sec - 916 B/second - 8.1 kB/request
27 requests currently being processed, 9 idle servers
WWWWWWWWWWWWWWWWWWWWWWW_W_W___WW____............................
................................................................
................................................................
................................................................
--SNAP
Now, when this happens I can not even log into horde/imp. Everything to
do with horde is broken. However, do not assume the entire apache web
server is dead. I can still get server-status (pretty obvious from above)
and any other virtual hosts work fine (even if they use php).
Does anyone have any clue or seen anything like this before?
Thanks for your help and reading :)
Caylan Van Larson
More information about the imp
mailing list