[tpop3d-discuss] tpop3d[2209]: net_loop: timed out client

Matthew Trent mtrent at localaccess.com
Wed, 10 Dec 2003 14:57:28 -0800


On Wednesday 10 December 2003 02:45 pm, Arkadiusz Miskiewicz wrote:
> > The last couple times I've seen this, it's been big (multi-megabyte)
> > messages with attachments. Is that what you're seeing too?
>
> One of posted logs here was showing ~ 2MB message, second only ~8kb.

Oops, yeah, I could have figured that out myself...

> Anyway take a look at my first log sent to mailing list
>
> Dec 10 17:11:12 gucio tpop3d[2209]: do_retr: client
> [7]abakus(195.116.149.253): sending message 39 (2205377 bytes)
>
> so ~2MB
>
> Dec 10 17:11:12 gucio tpop3d[2209]: do_retr: client
> [7]abakus(195.116.149.253): sent message 39
>
> tpop3d finished sending message to client
>
> Dec 10 17:18:00 gucio tpop3d[2209]: connection_sendresponse: client
> [7]abakus(195.116.149.253): sent `-ERR You can hang around all day if you
> like. I have better things to do.'
> Dec 10 17:18:00 gucio tpop3d[2209]: net_loop: timed out client
> [7]abakus(195.116.149.253)
> Dec 10 17:18:01 gucio tpop3d[2209]: connections_post_select: client
> [7]abakus(195.116.149.253): finished session for `abakus ' with mysql
>
> Dec 10 17:18:01 gucio tpop3d[2209]: connections_post_select: client
> [7]abakus(195.116.149.253): disconnected; 64/719042 byte s read/written
>
> but only 719042 bytes written? Message was ~2MB and tpop3d wrote ,,sent
> message''! Looks like some tpop3d bug.

My -v log seemed to give the correct number of bytes at the end, but it said 
"sending" and "sent" within a few seconds of each other for a 3mb message and 
a dialup user. 14 minutes later (probably about the right amount of time for 
the download over dialup), it ended with that looked like a normal finish. No 
timeout. The user swears his progress bar never moved and the client just 
stalled, though. I have other, non verbose, logs from earlier where I can see 
him try to download the same message and got a timeout. He said he got 8 
copies of it. And again, the messages weren't moved to the 'cur' folder.
-- 
Matt
Systems Administrator
Local Access Communications
360.330.5535