On Tue, 2009-01-13 at 18:20 +0100, Jürgen Geuter wrote:
> On Mon, 2009-01-12 at 11:06 -0500, Timo Sirainen wrote:
> > On Fri, 2009-01-09 at 19:04 +0000, Juergen Geuter wrote:
> > > After a while dovecot does not allow SSL connections anymore because the
> > > SSL parameters in the file /var/run/dovecot/login/ssl-parameters.dat
> > > get corrupted. The file then has exactly 80 bytes size.
> > > When that happens the log gets an entry like the following for every
> > > connection attempt:
> > >  
> > >  v1068 dovecot: imap-login: read(ssl-parameters.dat) failed: Unexpected 
> > > EOF
> > 
> > I've never heard this happening with anyone.
> 
> If you search for the "dovecot: imap-login: read(ssl-parameters.dat)
> failed: Unexpected EOF" error message in your favourite search engine
> you will find a few hits which are all rather old though.

The one problem that wasn't too old happened when running two dovecot
instances. This was fixed in Dovecot. But I guess you're not running two
instances?

> > > I disabled the auto-regeneration of that file in the dovecot
> > > configuration via the "ssl_parameters_regenerate: 0" setting, but still
> > > on every restart of the server the file is generated with wrong data.
> > 
> > It shouldn't be regenerated at startup as long as the file exists. Do
> > you have it in /var/lib/dovecot?
> 
> No, the default place for it to reside seems to
> be /var/run/dovecot/login/ssl-parameters.dat (which is probably purged
> each restart?). The configuration file has no directive as this link
> (http://markmail.org/message/ymdg3f3minq7asb2) shows: The place seems to
> only be configurable at ./configure time.

The file is first created to $prefix/var/lib/dovecot/ssl-parameters.dat.
From there it is either hard linked or copied to
base_dir/login/ssl-parameters.dat. It's never deleted from the /var/lib/
directory. That's the reason it's generated there, so that after reboots
Dovecot wouldn't always have to regenerate the ssl-parameters.dat.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to