dovecot - Feb 2007 - --log-error and the mysterious "not starting" problem

I've finally upgraded to 1.0.rc21.  If I run "dovecot
--log-error", then
dovecot fails to start. The following appears in the log:

Feb  5 10:54:00 taurus1 dovecot: Dovecot v1.0.rc21 starting up
Feb  5 10:54:00 taurus1 dovecot: This is Dovecot's error log

Without --log-error, it will start up fine from command-line.

Dovecot still fails to start, as near as I can tell, in the specific
condition that it is being started from a non-interactive shell and
there is a mail_plugin set in "protocol imap".  mail plugins set for
pop or lda do not cause this problem.  The failure to start appears in
only two instances that I can see: on boot, or by a monitoring script
if dovecot crashes, or, since I haven't seen dovecot die, when I
manually stop it to see if the monitoring program will restart it.

With the above problem, if the init script has --log-error when I try
to make the monitoring program restart dovecot, then nothing still gets
logged.

-- 
Marshal Newrock, Ideal Solution LLC
http://www.idealso.com

On 5.2.2007, at 18.07, Marshal Newrock wrote:
> I've finally upgraded to 1.0.rc21.  If I run "dovecot
--log-error",
> then
> dovecot fails to start. The following appears in the log:
>
> Feb  5 10:54:00 taurus1 dovecot: Dovecot v1.0.rc21 starting up
> Feb  5 10:54:00 taurus1 dovecot: This is Dovecot's error log
>
> Without --log-error, it will start up fine from command-line.
Yes, that's exactly what it's supposed to do. I didn't think it
could
have been understood any other way :) The reason for --log-error's  
existence is that some people just can't seem to find the error logs,  
but once they do there's really no need to find them again.
> Dovecot still fails to start, as near as I can tell, in the specific
> condition that it is being started from a non-interactive shell and
> there is a mail_plugin set in "protocol imap".  mail plugins set
for
> pop or lda do not cause this problem.  The failure to start appears in
> only two instances that I can see: on boot, or by a monitoring script
> if dovecot crashes, or, since I haven't seen dovecot die, when I
> manually stop it to see if the monitoring program will restart it.
By "fails to start" what exactly do you mean? It does one of the  
following:

  - log an error message
  - exit with non-zero exit code
  - crash

What does strace -f -o log dovecot show?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20070205/993f1c12/attachment.bin>

On Mon, 2007-02-05 at 11:07 -0500, Marshal Newrock
wrote:
> Dovecot still fails to start, as near as I can tell, in the specific
> condition that it is being started from a non-interactive shell and
> there is a mail_plugin set in "protocol imap".  mail plugins set
for
> pop or lda do not cause this problem.  The failure to start appears in
> only two instances that I can see: on boot, or by a monitoring script
> if dovecot crashes, or, since I haven't seen dovecot die, when I
> manually stop it to see if the monitoring program will restart it.
It wrote the error message to stderr, but I guess it wasn't shown in the
screen or logged?

Anyway, fix here:
http://dovecot.org/list/dovecot-cvs/2007-February/007637.html

Another workaround would be to set imap_capability manually so Dovecot
doesn't need to run the dump-capability process (it checks if plugins
added more capabilities).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20070212/9c9f23ac/attachment.bin>