Rep db was out of date yesterday (started getting some spam, had not been checked since 6/4), ran update and after, got the below messages. Also, now the two Ironports in cluster show different "Senderbase Network Status" - the one which gave these errors shows down, the other one shows up - Status checks show the same time. We've seen this on other clusters we manage today also... any recommendations?
The Critical message is:
An application fault occurred: ('_coro.pyx coro._coro.coro.raise_exception (coro/_coro.c:6902)|571', "<class 'coro._coro.DeadCoroutine'>", "<coro #187183 name='<bound method Child._watchdog of <heimdall.child.Child instance at 0x81e78fc8>>' dead=1 started=0 scheduled=0 at 0x88a70060>", '[_coro.pyx coro._coro._wrap1 (coro/_coro.c:8500)|757] [heimdall/child.py _monitor|669] [heimdall/child.py _stop_watchdog|1190] [_coro.pyx coro._coro.coro.raise_exception (coro/_coro.c:6902)|571]')
Version: 9.1.0-032
Serial Number: 842B2B6E84A5-84R5DQ1
Timestamp: 18 Jun 2015 08:34:24 -0500
quickly followed by:
The Critical message is:
An application fault occurred: ('_coro.pyx coro._coro.coro.raise_exception (coro/_coro.c:6902)|571', "<class 'coro._coro.DeadCoroutine'>", "<coro #187183 name='<bound method Child._watchdog of <heimdall.child.Child instance at 0x81e78fc8>>' dead=1 started=0 scheduled=0 at 0x88a70060>", '[_coro.pyx coro._coro._wrap1 (coro/_coro.c:8500)|757] [heimdall/child.py _monitor|669] [heimdall/child.py _stop_watchdog|1190] [_coro.pyx coro._coro.coro.raise_exception (coro/_coro.c:6902)|571]')
Version: 9.1.0-032
Serial Number: 842B2B6E84A5-84R5DQ1
Timestamp: 18 Jun 2015 08:39:24 -0500
Any help would be appreciated.
