[Dovecot] Multiple dovecot processes stepping on each other
I have two instances of dovecot running, one for v6 and one for v4 connections. The only differences in the config files are: --- /etc/dovecot-ip6.conf Wed Aug 18 11:15:43 2004 +++ /etc/dovecot-ip4.conf Wed Aug 18 11:09:17 2004 @@ -10,7 +10,7 @@ # *** NOTE *** Some values HAVE been changed for OpenBSD use. # Base directory where to store runtime data. -base_dir = /var/dovecot-v6/ +base_dir = /var/dovecot-v4/ # Protocols we want to be serving: # imap imaps pop3 pop3s @@ -23,7 +23,7 @@ # "host:port", although with multiple protocols you probably want to move # this setting inside protocol imap/pop3 { ... } section, so you can # specify different ports for IMAP/POP3. -listen = [::] +listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. For the most part it is working, but every so often, the auth freaks out for one (random) account. The error for one example is below: Aug 18 11:13:12 gir dovecot: login: Authentication process 21082 doesn't exist Aug 18 11:13:12 gir dovecot: pop3-login: Internal login failure: phessler [208.201.244.164] This happens on both v4 and v6 connections, but infrequently. If you try again immediatly, it works. If I do a `ps -p 21082` I can see the process (dovecot-auth). This does not happen when I have only one dovecot process running. What is the best way to have multiple dovecot processes without them stepping on each others toes? This is on OpenBSD/macppc -current, running dovecot-1.0-test32. -- Mosher's Law of Software Engineering: Don't worry if it doesn't work right. If everything did, you'd be out of a job.
On 18.8.2004, at 23:30, Peter Hessler wrote:
I have two instances of dovecot running, one for v6 and one for v4 connections. The only differences in the config files are: .. For the most part it is working, but every so often, the auth freaks out for one (random) account. The error for one example is below:
Aug 18 11:13:12 gir dovecot: login: Authentication process 21082 doesn't exist
Is login_dir setting commented out in the config file? Or are you trying to somehow use a single dovecot-auth process for them? If not, this is a bit strange problem. They shouldn't know anything about each others in that case.
On Mon, 23 Aug 2004 08:35:04 +0300 Timo Sirainen tss@iki.fi wrote:
:On 18.8.2004, at 23:30, Peter Hessler wrote: : :> I have two instances of dovecot running, one for v6 and one for v4 :> connections. The only differences in the config files are: :.. :> For the most part it is working, but every so often, the auth freaks :> out for :> one (random) account. The error for one example is below: :> :> :> Aug 18 11:13:12 gir dovecot: login: Authentication process 21082 :> doesn't :> exist : :Is login_dir setting commented out in the config file? Or are you :trying to somehow use a single dovecot-auth process for them? If not, :this is a bit strange problem. They shouldn't know anything about each :others in that case. :
Do any other directories need to be seperated, or just login_dir? Seems to be working well for now.
It might be a good thing to do a s/\/var\/dovecot\//$base-dir/g so any changes to base-dir filter throughout the config file.
-- The truth of a proposition has nothing to do with its credibility. And vice versa.
On 23.8.2004, at 08:54, Peter Hessler wrote:
:Is login_dir setting commented out in the config file? Or are you :trying to somehow use a single dovecot-auth process for them? If not, :this is a bit strange problem. They shouldn't know anything about each :others in that case. :
Do any other directories need to be seperated, or just login_dir?
Seems to be working well for now.
Not directories, but there's ssl_parameters_file also.
It might be a good thing to do a s/\/var\/dovecot\//$base-dir/g so any changes to base-dir filter throughout the config file.
The default for login_dir is "login" which is relative to base_dir, so if you hadn't changed it there should have been no conflict. Hmm. Although in example config file they're commented out as absolute paths. Well, I think they're a bit clearer that way.
On Mon, 23 Aug 2004 09:00:19 +0300 Timo Sirainen tss@iki.fi wrote:
:> It might be a good thing to do a s/\/var\/dovecot\//$base-dir/g so any :> changes to base-dir filter throughout the config file. : :The default for login_dir is "login" which is relative to base_dir, so :if you hadn't changed it there should have been no conflict. Hmm. :Although in example config file they're commented out as absolute :paths. Well, I think they're a bit clearer that way.
I think it is clear either way. Using $base-dir makes it really easy to change paramaters.
-- When the going gets tough, the tough get empirical -- Jon Carroll
participants (2)
-
Peter Hessler
-
Timo Sirainen