[Dovecot] [Fwd: mulitple instance run problem]

[Stewart Dean]

As I said in my original note:
> I was instructed to create a second config file with different listen 
> ports and a separate base_dir.  I did so and invoked dc with -c 
> pointing to dovecot2.conf. 
This second and different config file had different listen ports and a 
different base_dir.  So what Gabriele Fergola and

Odhiambo Washington suggest has already been done.....


Gabriele Fergola wrote:
> Hi Stewart,
> i'm veeeeeery new and noob about doveccot so i suppose a solution or 
> where is the problem.
> i think the problem is auth daemon....
>
>  3671 ?        Ss     0:00 /usr/local/sbin/dovecot
>  3672 ?        S      0:00 dovecot-auth
>  5756 ?        S      0:00 dovecot-auth -w
> u can see dovecot start dovecot and dovecot-auth.
>
> The realy problem u can have is with dovecot-auth because all 2 
> istance use the same port(socket) for the login.
>
> i don't know how to solve the problem in second istance but for test i 
> prefer use a virtual machine make with VirtualBox.
>
> Best reguards
> Gabriele Fergola
>
>
>
> On 6/7/07, *Stewart Dean* <sdean at bard.edu <mailto:sdean at bard.edu>> wrote:
>
>     I hour and 14 minutes later (14:59:38) the "imap-login: Can't
>     connect to
>     auth server at default: Connection refused" messages started up again.
>     I am now doing a kill -7 and fully restarting the primary instance of
>     dovecot
>
>     Stewart Dean wrote:
>     > As I explained, I want to be able to run a second instance of DC
>     > through another port to do testing while not interrupting the users
>     > using the primary instance in the the regular port.  I was
>     instructed
>     > to create a second config file with different listen ports and a
>     > separate base_dir.  I did so and invoked dc with -c pointing to
>     > dovecot2.conf.
>     >
>     > Jun  7 10:04:23 mercury mail:info dovecot: Dovecot v1.0.0
>     starting up
>     >
>     > I pointed my client at the non-SSL port, and everything worked
>     > fine....until 3 hours later.  The client wasn't getting things
>     > through, so I checked the syslog on the dc server where I saw
>     rapidly
>     > repeating errmsgs:...
>     >
>     > Jun  7 12:51:07 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 12:58:55 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 12:58:59 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 12:59:01 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 12:59:05 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     >
>     > and many more, then......
>     >
>     > Jun  7 13:34:20 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 13:36:30 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 13:36:54 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     >
>     > I kill the second instance.....but things don't clear
>     up....rather I
>     > now get a different errmsg....which must be from the primary dc
>     > instance, since the 2nd instance and all of its children are gone (I
>     > checked the ps)
>     >
>     > Jun  7 13:39:20 mercury mail:err|error dovecot: login:
>     Authentication
>     > process 10
>     > 89784 doesn't exist
>     > Jun  7 13:40:00 mercury mail:err|error dovecot: imap-login: Can't
>     > connect to aut
>     > h server at default: Connection refused
>     > Jun  7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't
>     > connect to aut
>     > h server at default: Connection refused
>     > Jun  7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't
>     > connect to aut
>     > h server at default: Connection refused
>     >
>     > Finally I do a kill -1 of the primary instance and that cleans
>     things up
>     >
>     > Jun  7 13:45:46 mercury mail:warn|warning dovecot: SIGHUP received -
>     > reloading configuration
>     >
>     > Is there something I'm doing wrong?  Have other people run two
>     > instances without problem?  I tried starting the second instance and
>     > killing it immediately thereafter....that wnet OK, but it hasn't
>     been
>     > 3 hours yet.
>     >
>
>     --
>     ====
>     Stewart Dean, Unix System Admin, Henderson Computer Resources
>     Center of Bard College, Annandale-on-Hudson, New York  12504
>     sdean at bard.edu <mailto:sdean at bard.edu>  voice: 845-758-7475, fax:
>     845-758-7035
>
>

-- 
====
Stewart Dean, Unix System Admin, Henderson Computer Resources 
Center of Bard College, Annandale-on-Hudson, New York  12504  
sdean at bard.edu  voice: 845-758-7475, fax: 845-758-7035