[Dovecot] Command output: Failed to write to log file
Hi
dovecot -n at end of message.
Jul 13 09:41:56 findb postfix/smtpd[15996]: connect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/smtpd[15996]: 3B7EF56ABA: client=unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/cleanup[15999]: 3B7EF56ABA: message-id=<26CDBD30F4FE1D4FB6FB5F6D16BCA93E0E5B7777AD@RVEB1SRVMSGCCR1.c ymru.nhs.uk> Jul 13 09:41:56 findb postfix/qmgr[15667]: 3B7EF56ABA: from=<>, size=1711, nrcpt=1 (queue active) Jul 13 09:41:56 findb postfix/smtpd[15996]: disconnect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=<enduser@thishost.com>, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file)
Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ?
[/var/log]# dovecot -n # 1.2.10: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 x86_64 Red Hat Enterprise Linux Server release 5.2 (Tikanga) log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_access_groups: mail mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: root@localhost mail_plugins: sieve auth default: debug: yes passdb: driver: pam userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/ log_path: /var/log/dovecot.log
Many thanks Nick .
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5273 (20100712) __________
The message was checked by ESET NOD32 Antivirus.
On 13.7.2010, at 9.53, Nick Lunt wrote:
Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=<enduser@thishost.com>, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file)
Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ?
See http://wiki.dovecot.org/LDA#logging, especially the part about Postfix's mailbox_size_limit.
-----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: 13 July 2010 12:45 To: Nick Lunt Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Command output: Failed to write to log file
On 13.7.2010, at 9.53, Nick Lunt wrote:
Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=<enduser@thishost.com>, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file)
Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ?
See http://wiki.dovecot.org/LDA#logging, especially the part about Postfix's mailbox_size_limit.
Aha that must be it, thanks for the pointer, much appreciated. Nick.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5273 (20100712) __________
The message was checked by ESET NOD32 Antivirus.
participants (2)
-
Nick Lunt
-
Timo Sirainen