On Thu, 14 Feb 2002, Scott Dale Robison wrote:
> Ok, I'm having some problems I never had until upgrading from 1.2 to
> 1.4/1.5.
> For a reason unknown to me, XMail tends to 'freeze' and will not process any
> requests (POP3 or SMTP). When XMail enters this state there are *many*
> sockets left in varying states as reported by netstat. I'm running Debian
> Linux
> kernel 2.4.17.
>
> Now, to give you an idea for what I mean by the netstat report, allow me to
> C&P
> the last one I received:
>
> Active Internet connections (w/o servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 0 0 webducky.com:smtp 216-73-102-153.ocd:3884 SYN_RECV
> tcp 0 0 webducky.com:smtp 207.233.132.20:1998 SYN_RECV
> tcp 0 0 webducky.com:smtp 64.5.230.158:4262 SYN_RECV
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44233
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44136
> CLOSE_WAIT
> tcp 7 0 webducky.com:ssh 65.193.106.34:61645
> ESTABLISHED
> tcp 0 0 webducky.com:ssh 65.193.106.34:61645
> ESTABLISHED
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44171
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44235
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44139
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44107
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp qmail3.bulk.yahoo.:3886
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44234
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44138
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44173
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp mail13.transcentiv:1754
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp n25.groups.yahoo.:34104
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44172
> CLOSE_WAIT
> tcp 1 0 webducky.com:pop3 ppp-66-124-115-190:1486
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44140
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44175
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44239
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44143
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44174
> CLOSE_WAIT
> tcp 1 0 webducky.com:pop3 ppp-66-124-115-190:1388
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44193
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44161
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44257
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp imo-r09.mx.aol.co:63686
> CLOSE_WAIT
> tcp 0 0 webducky.com:ssh 65.193.106.34:61668
> ESTABLISHED
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44192
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44160
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp imo-r09.mx.aol.co:50727
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp n11.groups.yahoo.:41922
> CLOSE_WAIT
> tcp 1 0 webducky.com:pop3 pc-62-30-49-169-st:1526
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44259
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44162
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44258
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44261
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44229
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44260
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44135
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44230
> CLOSE_WAIT
> tcp 1 0 webducky.com:pop3 ppp0008.firese:zebrasrv
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44185
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44121
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44184
> CLOSE_WAIT
> tcp 0 0 webducky.com:www 157.91.105.5:5731
> TIME_WAIT
> tcp 1 0 webducky.com:pop3 pc-62-30-49-169-st:1518
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44123
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44186
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44122
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44189
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44125
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44124
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44191
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44159
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44190
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp mta100.cheetahmail:1442
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44158
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44158
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44241
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44145
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44240
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44144
> CLOSE_WAIT
> tcp 1 0 webducky.com:pop3 ppp-66-124-115-190:1457
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44243
> CLOSE_WAIT
> tcp 0 0 webducky.com:smtp smtp3.intervolved:20089
> ESTABLISHED
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44147
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44115
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44242
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44146
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44114
> CLOSE_WAIT
> tcp 1 0 webducky.com:pop3 pc-62-30-49-169-st:1504
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp imo-r09.mx.aol.co:54546
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp glimmer.focusdata:57670
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp hawk.mail.pas.ear:50319
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44183
> CLOSE_WAIT
> tcp 1 0 webducky.com:smtp imo-r09.mx.aol.co:65232
> CLOSE_WAIT
> tcp 7 0 webducky.com:smtp r77h130.afo.net:44182
> CLOSE_WAIT
>
> You'll note the great bulk of them are from r77h130.afo.net connecting to
> smtp.
> Now, it seems odd to me that so many of these sockets are left in a
> CLOSE_WAIT
> state. To try to clean things up, I ran the /etc/init.d/xmail stop script
> (which took 16
> minutes to execute). Even after that, the above list of sockets was still
> present.
> Not until I killed all the XMail processes (most of which were marked
> defunct;
> 3 or 4 were not, of which 1 or 2 were parent processes) did the sockets
> clean up
> after themselves.
>
> Any thoughts? I'm using the binaries provided by the RPM after processing it
> through alien to get a DEB. Most of the time it works fine, but once or
> twice a day
> I have to reset it.
Ok :
1) do not use the RPM and rebuild it from scratch ( see doc )
2) add the line 'ulimit -c 20000' to the startup script
/etc/rc.d/init.d/xmail to generate a core if something happens
- Davide
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
