Hello all,
I have a qmail server 1.03 on a X.2.8. Sometimes, the only authorized qmail-lspawn stops (concurrencylocal=1). The process remains but does nothing. ps -aux | grep qmail-lspawn shows a 'U' state for the process. Side effect is that following messages are queued but not delivered.
I tried to increase the concurrencylocal but there was much more problems.
The process ignore any 'kill' command, so I can't kill the process so that it would free qmail-lspawn to deliver other messages.
Only way for me is to reboot. When rebooted, it usually doesn't stop on the same message and so delivers all the mails (after a little qmailctl flush). But a few hours (sometimes a few days!) later, it stops again.
I suppose this is a lock problem but I can't see what to do to solve it.
If anybody has an idea about how to fix the fact that qmail-lspawn stops, it would be great. If nobody can, a better way to make qmail-lspawn quit/go on its work would be great too.
I have a qmail server 1.03 on a X.2.8. Sometimes, the only authorized qmail-lspawn stops (concurrencylocal=1). The process remains but does nothing. ps -aux | grep qmail-lspawn shows a 'U' state for the process. Side effect is that following messages are queued but not delivered.
I tried to increase the concurrencylocal but there was much more problems.
The process ignore any 'kill' command, so I can't kill the process so that it would free qmail-lspawn to deliver other messages.
Only way for me is to reboot. When rebooted, it usually doesn't stop on the same message and so delivers all the mails (after a little qmailctl flush). But a few hours (sometimes a few days!) later, it stops again.
I suppose this is a lock problem but I can't see what to do to solve it.
If anybody has an idea about how to fix the fact that qmail-lspawn stops, it would be great. If nobody can, a better way to make qmail-lspawn quit/go on its work would be great too.