[Dovecot] Configuration problem?
I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening:
--------------------- Dovecot Begin ------------------------
Dovecot was killed, and not restarted afterwards.
**Unmatched Entries** dovecot: imap(anne): Connection closed bytes=205614/894243: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=24296/89310: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=24526/76772: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=26254/75778: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=27948/134120: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=29304/116087: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=34802/914087: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=4457/11719: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=5322/184434: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=61388/106618: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=6164/21347: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=7914/89868: 1 Time(s) dovecot: imap: Server shutting down. bytes=1309821/4473013: 1 Time(s) dovecot: imap: Server shutting down. bytes=14215/97371: 1 Time(s) dovecot: imap: Server shutting down. bytes=1459/9382: 1 Time(s) dovecot: imap: Server shutting down. bytes=1688/26161: 1 Time(s) dovecot: imap: Server shutting down. bytes=1705/5038: 1 Time(s) dovecot: imap: Server shutting down. bytes=3146/79269: 1 Time(s) dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled): 1 Time(s)
---------------------- Dovecot End -------------------------
dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Scientific Linux release 6.1 (Carbon) mail_location = maildir:~/Maildir/ mbox_write_locks = fcntl passdb { driver = pam } protocols = imap ssl_cert =
/etc/dovecot/dovecot.conf: - everything being defaults, as far as I can see, apart from these lines:
# Protocols we want to be serving. protocols = imap listen = *, :: mail_location = maildir:~/Maildir/ maildir_copy_with_hardlinks = yes
Is it really expecting an mbox file?
I'm completely bogged down with this - my previous setup was fine, but the old config file doesn't work with this system. Any help and/or pointers would be greatly appreciated.
Anne
On Mon, Feb 06, 2012 at 05:33:01PM +0000, Anne Wilson wrote:
I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening:
--------------------- Dovecot Begin ------------------------
Dovecot was killed, and not restarted afterwards.
You shut dovecot down and does not restart it.
**Unmatched Entries** dovecot: imap(anne): Connection closed bytes=205614/894243: 1 Time(s)
[..]
dovecot: imap(anne): Disconnected: Logged out bytes=7914/89868: 1 Time(s)
The user closed the connection.
dovecot: imap: Server shutting down. bytes=1309821/4473013: 1 Time(s)
[..]
dovecot: imap: Server shutting down. bytes=3146/79269: 1 Time(s)
The server closed the connection due to a shutdown command.
dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled): 1 Time(s)
Dovecot did what it just said: it started.
Your logwatch is to old to knew about the messages dovecot emits to syslog.
HTH Dennis
[..]
On 6 February 2012 17:49, Dennis Guhl dg@dguhl.org wrote:
On Mon, Feb 06, 2012 at 05:33:01PM +0000, Anne Wilson wrote:
I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening:
--------------------- Dovecot Begin ------------------------
Dovecot was killed, and not restarted afterwards.
You shut dovecot down and does not restart it.
It appears to be doing things without my intervention. Despite the reports that it kept shutting down, Dovecot continued to serve messages throughout the day.
**Unmatched Entries** dovecot: imap(anne): Connection closed bytes=205614/894243: 1 Time(s)
[..]
dovecot: imap(anne): Disconnected: Logged out bytes=7914/89868: 1 Time(s)
The user closed the connection.
dovecot: imap: Server shutting down. bytes=1309821/4473013: 1 Time(s)
[..]
dovecot: imap: Server shutting down. bytes=3146/79269: 1 Time(s)
The server closed the connection due to a shutdown command.
dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled): 1 Time(s)
Dovecot did what it just said: it started.
Your logwatch is to old to knew about the messages dovecot emits to syslog.
HTH Dennis
[..]
You mean the version of logwatch is too old? I'm beginning to wonder whether running an Enterprise version is such a good idea after all.
Anne
On Tue, Feb 07, 2012 at 08:08:24AM +0000, Anne Wilson wrote:
On 6 February 2012 17:49, Dennis Guhl dg@dguhl.org wrote:
On Mon, Feb 06, 2012 at 05:33:01PM +0000, Anne Wilson wrote:
I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening:
--------------------- Dovecot Begin ------------------------
Dovecot was killed, and not restarted afterwards.
You shut dovecot down and does not restart it.
It appears to be doing things without my intervention. Despite the reports that it kept shutting down, Dovecot continued to serve messages throughout the day.
The messages logwatch shows appeared at some time within the analysed period and are not necessarily in a time sorted order. Btw do not rely on any summary of log files but look into the log yourself.
[..]
You mean the version of logwatch is too old? I'm beginning to wonder
Yes, the current version is 7.4.0 from march 2011 (http://www.logwatch.org).
whether running an Enterprise version is such a good idea after all.
I don't know Scientific Linux but I use Debian stable on all my server and I'm very happy with it. Nonetheless do I manually upgrade some packages wich added needed features or are maintained by upstream.
It is crucial to know and understand the philosophy behind a distribution and to decide if this works for you and if you can live with the caveats resulting.
Dennis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/02/12 11:57, Dennis Guhl wrote:
On Tue, Feb 07, 2012 at 08:08:24AM +0000, Anne Wilson wrote:
On 6 February 2012 17:49, Dennis Guhl dg@dguhl.org wrote:
On Mon, Feb 06, 2012 at 05:33:01PM +0000, Anne Wilson wrote:
I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening:
--------------------- Dovecot Begin ------------------------
Dovecot was killed, and not restarted afterwards.
You shut dovecot down and does not restart it.
It appears to be doing things without my intervention. Despite the reports that it kept shutting down, Dovecot continued to serve messages throughout the day.
The messages logwatch shows appeared at some time within the analysed period and are not necessarily in a time sorted order. Btw do not rely on any summary of log files but look into the log yourself.
[..]
Actually, this morning there aren't the same messages, so perhaps I was restarting services while trying to get it right - in fact it seems very likely that that was so. Today there are a few like
dovecot: imap(anne): Disconnected: Logged out bytes=11892/21219: 1Time(s)
I presume that refers to clients logging out of the imap connection? In which case, I can forget about that.
I normally read the summary each morning and refer directly to the logs if I see something that looks unusual. Occasionally, as in this case, there are entries that I don't understand and I ask those who do :-)
You mean the version of logwatch is too old? I'm beginning to wonder
Yes, the current version is 7.4.0 from march 2011 (http://www.logwatch.org).
whether running an Enterprise version is such a good idea after all.
I don't know Scientific Linux but I use Debian stable on all my server and I'm very happy with it. Nonetheless do I manually upgrade some packages wich added needed features or are maintained by upstream.
It is crucial to know and understand the philosophy behind a distribution and to decide if this works for you and if you can live with the caveats resulting.
I've run CentOS for maybe 4 years, and it's similar to SL, both being RHEL clones, but maintained by different communities. On a server (even though this is a very "mild" server, being only file and print serving) the older packages are rarely a problem.
I appreciate the time and trouble you are taking to educate me :-)
Anne
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8xQSsACgkQj93fyh4cnBdynQCeO6tY/798/6YonBALxJ0baZcy qG4AoIEHcZWsjIqhz4v3+SMk76FLhjIk =/T9e -----END PGP SIGNATURE-----
participants (2)
-
Anne Wilson
-
Dennis Guhl