vm-pop3d dead but subsys locked ?

sHuKKo

Verified User
Joined
Jun 24, 2003
Messages
89
Location
on the net!
Sometimes my vm-pop3d dies without giving any error.
When I try to restart the service

service vm-pop3d restart

it says

vm-pop3d dead but subsys locked

so I

rm -f /var/lock/subsys/vm-pop3d

and then restart

But this problem is really annoying because when pop3d is dead everthing is dead according to my clients :)

I examine the /var/log/maillog and /var/log/messeges files but there were no specific cause for this problem.

I was using vm-pop3d 1.16 and exim 3.x I upgraded to latest versions released to exim 4.x and vp-pop3d 1.17 but still this problem happens some time to time.

I guess due to heavy mail usage on my server or anything else sometimes vm-pop3d dies silently but I dont have much more idea.
Please help ;)
 
Hmm... Perhaps try loading more deamons?
Edit /etc/init.d/vm-pop3d
and change
daemon vm-pop3d -d 10 -t 600
to
daemon vm-pop3d -d 20 -t 600

or a value more appropriate...

*or* (this might be better)

Set up vm-pop3d to be run from the xinetd.. which should be rock solid and never die.
1) turn of DA checking for the program:
/usr/local/directadmin/data/admin/services.status
set: vm-pop3d=OFF
2) turn off the boot script:
chkconfig vm-pop3d off
3) setup xinet.d
edit /etc/xinetd.d/pop3 and add:
Code:
# default: on
# description: pop3
service pop3
{
        disable = no
        socket_type             = stream
        wait                    = no
        user                    = root
        server                  = /usr/sbin/vm-pop3d -t 600
        nice                    = 10
}
4) restart xinetd:
service vm-pop3d stop #(if its running)
service xinetd restart

John
 
I already use
daemon vm-pop3d -d 20 -t 600
for about 2 days.
and it seems stable.

But as I wrote in my original post vm-pop3d dies in no certain time. So I think I will change it to xinetd option now for better stability.

Thanks for your reply.. I will try and see :)
 
IMPORTANT!

Hi

After increasing the -d stuff to 30 and still having some problems I at last switch to xinetd and my vm-pop3d seems ok right now.
For anybody who wants to swtich to xinetd option there is some misconfiguration in /etc/xinetd.d/pop3 example above.

it MUST be like that for a non problem working vm-pop3d:

Code:
# default: on
# description: pop3
service pop3
{
        log_on_success += DURATION USERID
        log_on_failure += USERID
        port = 110
        socket_type = stream
        user = root
        server = /usr/sbin/vm-pop3d
        server_args = -t 600
        wait = no
        nice = 10
}
 
My Fedora 1 build requried the

server_args = -i -t 600

instead of the tags being at:

server = /usr/sbin/vm-pop3d -t 600

CK
 
Last edited:
Back
Top