dovecot - Mar 2009 - Fatal: write() failed to info log: Interrupted system call

Last night Dovecot stopped, and the last message in the log was:

Fatal: write() failed to info log: Interrupted system call

Would you please advise?

***

# dovecot -n
# 1.1.6: /usr/local/etc/dovecot.conf
Warning: mail_extra_groups setting was often used insecurely so it is now 
deprecated, use mail_access_groups or mail_privileged_group instead
# OS: FreeBSD 6.4-PRERELEASE i386
log_path: /var/log/dovecot.log
info_log_path: /var/log/dovecot.log
protocols: imap pop3 imaps
ssl_key_file: /etc/ssl/private/dovecot.key
login_dir: /var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
verbose_proctitle: yes
first_valid_gid: 0
mail_extra_groups: mail
mail_access_groups: mail
mail_location: maildir:~/Maildir
mail_debug: yes
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh 
tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh 
tb-extra-mailbox-sep
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
  verbose: yes
  debug: yes
  debug_passwords: yes
  passdb:
    driver: passwd-file
    args: /usr/local/etc/passwd.dovecot
  userdb:
    driver: passwd


-- 
Janos Dohanics

On Mar 17, 2009, at 11:06 AM, Janos Dohanics wrote:
> Last night Dovecot stopped, and the last message in the log was:
>
> Fatal: write() failed to info log: Interrupted system call
>
> Would you please advise?
A signal got sent to dovecot process while it was writing to a log  
file. But why exactly that happened, I don't know. Perhaps something  
outside Dovecot was sending it a signal. It would be simple to just  
make it ignore the EINTR error and retry, but I'm not really sure if  
it's a good idea to do it..