Christian Spoo wrote:
I've been running net-mail/courier-imap version 4.0.1 for quite a while
but suddenly it refuses to restart.
"Suddenly" ?
Yes because I rebooted the machine. Normally, Courier should start
because it's activated using rc-update but it simply doesn't.
Perhaps I should mention that courier-authlib runs without problems.
Then - taking into account the following about the logs - it may be a
permission issue.
Check the user authlib and courier-imap run as, and whether it looks
like this has changed.
Also check the auth log for info on this.
A /etc/init.d/courier-imapd restart simply fails.
Fails how - what is in the system and mail logs ?
www ~ # /etc/init.d/courier-imapd start
* Starting courier-imapd ...
[ !! ]
www ~ # tail -n 100 /var/log/mail/current | grep courier
www ~ # tail -n 100 /var/log/everything/current | grep courier
www ~ #
As you can see, none of these two logfiles contains anything regarding
Courier.
I can run the server manually by issuing the following:
/usr/lib/courier-imap/couriertcpd -address=0
-stderrlogger=/usr/lib/courier-imap/courierlogger
-stderrloggername=imapd -maxprocs=40 -maxperip=10
-pid=/var/run/imapd.pid -nodnslookup -noidentlookup 143
/usr/sbin/imaplogin /usr/sbin/courier-imapd .Maildir
Have you compared this cmdline with the one run by the initscript ?
This is the cmdline which is run by the initscript. I added a "set -x"
on top of /usr/lib/courier-imap/gentoo-imapd.rc trying to debug this
script. That way I got this command.
This is exactly why I'm so stuck about this. The initscript should run
this line and apparently it does but the imapd doesn't start, at least
when invoked by the initscript. In a regular shell I can run it without
problems as I stated above.
Christian
--
[email protected] mailing list
