[Mailman-Developers] Mailman error after restoring backup

[Mark Sapiro]

On 03/10/2015 01:13 PM, jovino Borret wrote:
> 
> The problem is that after restarting Postfix and Mailman, many error
> messages
> 
> Is been logged in the /var/log/mailman. He is some examples:
> 
> 1)      /var/log/mailman/post   
> 
>  
> 
>               Mar 10 15:20:20 2015 (1454) post to uerjxxi from
> weber at globo.com, size=3146,
> message-id=<EA367EE3-C7A4-4B8E-8464-D5B246CE68F4 at globo.com>, 206 failures


This doesn't say much. The smtp-failure log is more informative.


> 2)      /var/log/mailman/qrunner
> 
>  
> 
> Mar 10 15:20:46 2015 (1449) ArchRunner qrunner caught SIGTERM.  Stopping.
> 
> Mar 10 15:20:46 2015 (1449) ArchRunner qrunner exiting.


And is there a message like

Mar 10 15:20:46 2015 (pppp) Master qrunner detected subprocess exit
(pid: 1449, sig: xxx, sts: xx, class: ArchRunner, slice: 1/1)

in the log too.

It's hard to say much from this without seeing all the qrunner log
messages from this time frame and error log messages too if any.

> 3)      /var/log/mailman/smtp-failure
> 
>  
> 
> Mar 10 17:07:23 2015 (1701) delivery to lullimilman at uol.com.br failed with
> code -1: Server not connected


This could occur if you started Mailman before Postfix and Mailman had
messages queued. Are these messages still occurring?


> I am sure that Postfix is running ok (I have done some tests).
> 
>  
> 
> I think Mailman is not "talking" with Postfix, I mean it is not working
> properly with Postfix.


If there is an ongoing problem between Mailman and Postfix and the
Postfix logs don't help, see the FAQ article at
<http://wiki.list.org/x/4030716> for a way to get more debugging info.

Also, I suggest stopping Mailman completely (see
<http://wiki.list.org/x/4030715> for info on this) and then starting it
again to see if that helps.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan