Sorry, I do have /var/qmail/supervise/qmail-pop3d/log/run (with
permissions: -rw-rw-r--). I'll fix that and see what happens.
It looks like:
#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t \
/var/log/qmail/pop3d
Steven
-----Original Message-----
From: Steven Katz <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 10:24 AM
To: [EMAIL PROTECTED]
Subject: RE: qmail-pop3d not working?
Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while
pop was working) and got:
qmail-pop3d: up (pid 598) 1420 seconds
qmail-send: up (pid 594) 1420 seconds
qmail-smtpd: up (pid 595) 1420 seconds
qmail-pop3d/log: up (pid 28975) 0 seconds
qmail-send/log: up (pid 596) 1420 seconds
qmail-smtpd/log: up (pid 599) 1420 seconds
Then I did it again (when pop stopped working) and got:
qmail-pop3d: up (pid 598) 1678 seconds
qmail-send: up (pid 594) 1678 seconds
qmail-smtpd: up (pid 595) 1678 seconds
qmail-pop3d/log: up (pid 26225) 0 seconds
qmail-send/log: up (pid 596) 1678 seconds
qmail-smtpd/log: up (pid 599) 1678 seconds
Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps
increasing, even after it stops working.
However, doing 'ps auxw | grep pop3' while pop is working (up to 15
minutes after rebooting) gives me:
root 591 0.0 0.4 1272 344 ? S 09:06 0:00
supervise qmail-pop3d
root 596 0.0 0.6 1344 512 ? S 09:06 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
But doing it again when pop stops working gives me:
root 591 0.0 0.4 1272 344 ? S 09:06 0:00
supervise qmail-pop3d
root 596 0.0 0.6 1344 512 ? S 09:06 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
root 4454 0.0 0.6 1344 516 ? S 09:17 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
There does seem to be a connection to the second instance of tcpserver.
How can I find why and where the second tcpserver instance is being
initiated?
Thanks again, everyone.
Steven
-----Original Message-----
From: Rick Updegrove <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 10:22 AM
To: [EMAIL PROTECTED]
Subject: Re: qmail-pop3d not working?
Charles Cazabon said,
> You have two tcpserver instances, both trying to bind to the same
> interface(s) and port. At least one of those _has_ to be failing,
> and it should be showing up in your logs.
Steve said,
>>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
>> gives me:
I use this to check for status on supervised processes.
bash-2.04# cd /var/qmail/supervise; svstat * */log
qmail-pop3d: up (pid 658) 178697 seconds
qmail-send: up (pid 9480) 178696 seconds
qmail-smtpd: up (pid 3846) 178697 seconds
qmail-pop3d/log: up (pid 11946) 178697 seconds
qmail-send/log: up (pid 7901) 178697 seconds
qmail-smtpd/log: up (pid 13335) 178697 seconds
When you supervise, and one of the "seconds" columns stays at 0
seconds, you definitely have a problem. After you reboot, or better
yet, when your pop stops working, try that and see what happens.
Also, do not start pop3d from the command line if you are starting it
in your boot scripts, even if pop3 is not working properly.
Hope that helped
Rick Up
