[sniffer] Re: Bad Matrix errors

2011-08-22 Thread Peer-to-Peer (Support)
McNeil Sent: Monday, August 22, 2011 4:32 PM To: Message Sniffer Community Subject: [sniffer] Re: Bad Matrix errors On 8/22/2011 4:04 PM, Peer-to-Peer (Support) wrote: Hello SNF, I think something broke. I'm seeing a lot of "Bad Matrix!" warnings in my logs.

[sniffer] Re: Bad Matrix errors

2011-08-22 Thread Pete McNeil
On 8/22/2011 4:04 PM, Peer-to-Peer (Support) wrote: Hello SNF, I think something broke.  I'm seeing a lot of "Bad Matrix!" warnings in my logs.   Likely started about an hour ago. Running MDaemon mai

[sniffer] Re: Bad Matrix errors

2011-08-22 Thread Pete McNeil
On 8/22/2011 4:04 PM, Peer-to-Peer (Support) wrote: Hello SNF, I think something broke.  I'm seeing a lot of "Bad Matrix!" warnings in my logs.   Likely started about an hour ago. Running MDaemon mai

[sniffer] Re: Bad Matrix!

2009-07-19 Thread Dusty Carden
Best I can tell around 6:30 AM CDT. -Original Message- From: "Pete McNeil" Sent 7/18/2009 1:28:55 PM To: "Message Sniffer Community" Subject: [sniffer] Re: Bad Matrix!NetEase Operations Manager wrote: > I had the same thing this morning. About 3400 before th

[sniffer] Re: Bad Matrix!

2009-07-18 Thread Pete McNeil
NetEase Operations Manager wrote: I had the same thing this morning. About 3400 before the new update fixed it. What time was your event? _M # This message is sent to you because you are subscribed to the mailing list . To unsu

[sniffer] Re: Bad Matrix!

2009-07-18 Thread NetEase Operations Manager
I had the same thing this morning. About 3400 before the new update fixed it. Dusty -Original Message- From: Message Sniffer Community [mailto:snif...@sortmonster.com] On Behalf Of Pete McNeil Sent: Saturday, July 18, 2009 08:54 To: Message Sniffer Community Subject: [sniffer] Re: Bad

[sniffer] Re: Bad Matrix!

2009-07-18 Thread Pete McNeil
Peer-to-Peer (Support) wrote: We saw the following error for about one hour this morning (6:30AM - 7:20AM EST). Assume it was a bad update, and once a new update arrived all corrected itself. Could this be a local issue, something that we may have been able to prevent, or something beyond our c