Le 08/12/13 21:38, Timo Sirainen a écrit :
On 7.12.2013, at 6.22, Philippe Lelédy <dove...@leledy.fr> wrote:
I first let base_dir = with it's default value of /var/dovecot.
I changed my mind and now I have
doveconf -n
# 2.1.17: /etc/dovecot/dovecot.conf
# OS: OpenBSD 5.4 amd64 ffs
base_dir = /var/run/dovecot/
After a few days, imap clients couldn't login. Here the problem
Dec 04 17:03:16 imap-login: Fatal: Corrupted SSL parameters file:
/var/dovecot/ssl-parameters.dat
Dec 04 17:03:16 imap-login: Fatal: Corrupted SSL parameters file:
/var/dovecot/ssl-parameters.dat
Dec 04 17:03:16 master: Error: mkdir(/var/dovecot) failed: Read-only file system
Dec 04 17:03:16 master: Error: safe_mkstemp(/var/dovecot/mounts.tmp.) failed:
No such file or directory
Dec 04 17:03:16 master: Error: file_dotlock_open(/var/dovecot/instances)
failed: No such file or directory
Dec 04 17:03:16 ssl-params: Fatal: creat(/var/dovecot/ssl-parameters.dat.tmp)
failed: No such file or directory
You still have state_dir=/var/dovecot (and don’t place it under /var/run/, it’s
meant to be durable).
doveconf -a | grep state_dir
gives nothing.
Adding state_dir = /var/run/dovecot to dovecot.conf gives
doveconf -n -c dstate
# 2.1.17: dstate
doveconf: Fatal: Error in configuration file dstate line 116: Unknown
setting: state_dir
What to do ?
