Index: [Article Count Order] [Thread]

Date:  Tue, 17 Feb 2009 10:42:21 -0600
From:  "Gerald Waugh" <gwaugh (at mark) frontstreetnetworks.com>
Subject:  [coba-e:15091] Re: Mail servers
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <B449B27AB41D4DCE85EC7535009DF250@systemax>
In-Reply-To:  <200902171606.n1HG62Aa031561 (at mark) bugs.northernweb.net>
X-Mail-Count: 15091

Bill Berg wrote; Tuesday, February 17, 2009 10:06 AM
>  
> I don't know if that narrows down the problem, everything 
> worked except the
> dovecot:
> 
> [root@ ~]# service dovecot stop
> Stopping Dovecot Imap: [FAILED]
> [root@ ~]# service dovecot start
> Starting Dovecot Imap: Fatal: listen(0.0.0.0, 110) failed: 
> Address already in use [FAILED]
> 

You might try;
  killall -9 dovecot
then execute
  service dovecot start

Must have been two dovecot imap processes running.

Gerald

> On Tue, 17 Feb 2009 09:46:16 -0600, Gerald Waugh wrote
> > Bill Berg wrote; Tuesday, February 17, 2009 8:50 AM
> > >
> > > We have a strange issue with one of our BQ servers.
> > > If we have to reboot it, we cannot connect to the pop3
> > > mail server for the rest of that day. We can use webmail 
> just fine, 
> > > but it won't take any pop3 connections.
> > >
> > > Some process that runs during the night corrects the 
> problem, and we 
> > > can use regular email the next day.
> > >
> > > Does anybody know what process resets this mail function so I can 
> > > run it manually now?
> > >
> > service dovecot stop
> > service xinetd stop
> > killall -9 dovecot-auth
> > service dbrecover stop
> > service dbrecover start
> > service xinetd start
> > service dovecot start
> > service poprelayd restart
> >
> > Probably overkill, but might work...
> > And since it seems like you have an immediate problem.
> > Just paste into a 'root' shell session
> >
> > Gerald
>