Thread: QUE Failure
View Single Post
  #26 (permalink)  
Old 08-30-2006, 10:26 AM
tbullock tbullock is offline
Advanced Member
 
Posts: 232
Default

That would be great. I have been nosing around my maillogs, and I have a few questions.

I will open a port on the m firewall and send you a PM on how to connect.

Maybe we could hook up on MSN as well if you have time.

At this point I am suspecting that the backup script running on my backup machine might be hogging the Interface at night, causing the Que to basically crash and pile up with traffic. I stuck around a bit later last night (till 2:00AM), and things started going wrong around 11:20PM.

The errors generated during my attempts to manage the QUEUE via GUI seem to be related to the number of messages in the QUEUE. Once they dropped below 500 or so, I was able to start putting things on HOLD, DELETING, REQUEUEING etc, with generating the SOAP errors.

Mail server is currently working. I babied it through the rough patch last night and it has not gone down since.

I have also cancelled the RSYNC backup to the Zimbra Box. I will have to come up with another solution for backups.

Here is some examples in the log. Basically, Zimbra could no longer communicate with 127.0.0.1.

(TIMINGING OUT WITH LOOPBACK)

Aug 29 23:20:21 webmail postfix/smtp[28000]: 3310F174C460: to=<hflieger@westernavionics.com>, relay=127.0.0.1[127.0.0.1], delay=1206, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)


(QUE ACTIVE)

Aug 29 23:20:32 webmail postfix/qmgr[32052]: 2B75F174C46E: from=<samba-bounces+tbullock=avmax.ca@lists.samba.org>, size=3232, nrcpt=1 (queue active)
Aug 29 23:20:47 webmail postfix/qmgr[32052]: D9868174C46F: from=<werqytr@ATWONLINE.COM>, size=8003, nrcpt=1 (queue active)

(TIMING OUT WITH LOOPBACK)
Aug 29 23:23:06 webmail postfix/smtp[27373]: DB8F5174C45C: to=<alyxgoodnight@fcidms.com>, relay=127.0.0.1[127.0.0.1], delay=1206, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)

Aug 29 23:26:16 webmail postfix/smtp[29220]: 51B0E174C454: to=<pwong@avmax.ca>, relay=127.0.0.1[127.0.0.1], delay=1214, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)

Aug 29 23:26:44 webmail postfix/smtp[29428]: 13A64174C462: to=<dparkin@avmax.ca>, relay=127.0.0.1[127.0.0.1], delay=1213, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)

Aug 29 23:27:04 webmail postfix/smtp[29432]: 8EFE8174C45D: to=<tbullock@avmax.ca>, relay=127.0.0.1[127.0.0.1], delay=1213, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)

Aug 29 23:27:27 webmail postfix/smtp[29535]: 65425174C463: to=<tbullock@avmax.ca>, relay=127.0.0.1[127.0.0.1], delay=1207, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)
Aug 29 23:27:29 webmail postfix/smtpd[5615]: initializing the server-side TLS engine
Aug 29 23:27:48 webmail postfix/smtpd[5610]: 75E51174C472: client=host252-41.pool8259.interbusiness.it[82.59.41.252]

Aug 29 23:27:51 webmail postfix/smtp[29538]: A5AA5174C464: to=<bdave@avmax.ca>, relay=127.0.0.1[127.0.0.1], delay=1209, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)

Thanks for the input so far!
__________________
Cheers,

Travis

"Let's look at this from a standpoint of "Status". What exactly, on the Space Craft, IS working?"
-Flight Control, Apollo 13
Reply With Quote