[Dovecot] dovecot starts and exit immediately? - help needed
Since nobody answered my previous question on dovecot marking new mails as old mails, I decided to build a version of dovecot of my own to debug.
I downloaded and compiled dovecot 1.0 (stable). After setting up the conf file, I ran dovecot but it exited immediate with status 0. As a result, remote client cannot connect and retrieve mails.
There is no man page, and I only found two command line options, -F and -c. None of these options seem to matter.
Any suggestions? I must have done something simple and wrong here.
Jun
On Fri, 2005-07-22 at 07:35 -0700, James Sun wrote:
Since nobody answered my previous question on dovecot marking new mails as old mails, I decided to build a version of dovecot of my own to debug.
I downloaded and compiled dovecot 1.0 (stable). After setting up the conf file, I ran dovecot but it exited immediate with status 0. As a result, remote client cannot connect and retrieve mails.
There is no man page, and I only found two command line options, -F and -c. None of these options seem to matter.
Any suggestions? I must have done something simple and wrong here.
It exits immediately because it leaves itself running to background, unless -F option is given.
If it also dies immediately after, look at the log file to see what error it gives. There should always be one, unless it's the dovecot process itself that crashes (which you can notice with -F if it says segmentation fault afterwards).
In my case dovecot did not go to background.
In fact even if I ran dovecot -F, it still exists with stauts 0;
I suspect I might have done something wrong in config file. The config file is sufficiently different from 0.99 rpm that I dare not copy it. Here is the config I am having
protocols = imap imaps pop3 pop3s protocol imap { login_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/imap-login mail_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/imap } protocol pop3 { login_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/pop3-login mail_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/pop3 } auth_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/dovecot-auth auth default { mechanisms = plain passdb = pam userdb = passwd user = root }
Jun
On 7/22/05, Timo Sirainen tss@iki.fi wrote:
On Fri, 2005-07-22 at 07:35 -0700, James Sun wrote:
Since nobody answered my previous question on dovecot marking new mails as old mails, I decided to build a version of dovecot of my own to debug.
I downloaded and compiled dovecot 1.0 (stable). After setting up the conf file, I ran dovecot but it exited immediate with status 0. As a result, remote client cannot connect and retrieve mails.
There is no man page, and I only found two command line options, -F and -c. None of these options seem to matter.
Any suggestions? I must have done something simple and wrong here.
It exits immediately because it leaves itself running to background, unless -F option is given.
If it also dies immediately after, look at the log file to see what error it gives. There should always be one, unless it's the dovecot process itself that crashes (which you can notice with -F if it says segmentation fault afterwards).
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQBC4Qo+yUhSUUBViskRAh4BAJ4o1ldXrHCLdRrcIh2G3ld0Iep+owCdFio7 HrQAoEo6K/KFP0MwKt+EGiY= =MT4o -----END PGP SIGNATURE-----
On 22.7.2005, at 18:29, James Sun wrote:
In my case dovecot did not go to background.
In fact even if I ran dovecot -F, it still exists with stauts 0;
I suspect I might have done something wrong in config file. The config file is sufficiently different from 0.99 rpm that I dare not copy it. Here is the config I am having
If there is an error in config file, Dovecot writes error message to log file. Find the "Dovecot starting" message from log (/var/log/mail.log?) and see if there are any errors after it. Much easier that way than to start guessing where the problem might be.
On 7/22/05, Timo Sirainen tss@iki.fi wrote:
On 22.7.2005, at 18:29, James Sun wrote:
In my case dovecot did not go to background.
In fact even if I ran dovecot -F, it still exists with stauts 0;
I suspect I might have done something wrong in config file. The config file is sufficiently different from 0.99 rpm that I dare not copy it. Here is the config I am having
If there is an error in config file, Dovecot writes error message to log file. Find the "Dovecot starting" message from log (/var/log/mail.log?) and see if there are any errors after it. Much easier that way than to start guessing where the problem might be.
Yes, there is an error about "passdb = pam". I changed it to "passdb = passwd" and it now works!
I will do more probing. You will hear more if it does not go well. :) Thanks for the replies.
Jun
participants (2)
-
James Sun
-
Timo Sirainen