An application fault occurred - Queue: Your queue has been corrupted; UNABLE TO Queue: Your queue has been corrupted; UNABLE TO REPAIR: unable to mount queueREPAIR: unable to mount queue

[MohamedCSE]

Hello All

We are facing a problem with ur IronPort since ysterday that there is no outgoing mails pass through the Ironport and the incoming mails as well

 we are recieving the below two messages

An application fault occurred: ('egg/omh.py get_concurrency_status|2154', "<type 'exceptions.AttributeError'>", "'NoneType' object has no attribute 'should_tarpit'", '[_coro.pyx coro._coro._wrap1 (coro/_coro.c:8475)|757] [egg/omh.py delivernow_host|7305] [egg/omh.py spawn_client|2192] [egg/omh.py over_concurrency_limit|2019] [egg/omh.py get_concurrency_status|2154]')

Version: 7.6.2-014

Queue: Your queue has been corrupted; UNABLE TO REPAIR: unable to mount queue: '(\'egg/gcq.py journal_scan_enqu|1800\', "<type \'exceptions.KeyError\'>", \'307412\', \'[egg/gcq.py mount|1388] [egg/gcq.py load|1016] [egg/scan_heap.py scan|154] [egg/gcq.py journal_scan_callback|1706] [egg/gcq.py journal_scan_enqu|1800]\')'

Version: 7.6.2-014

thanks in advance

[Robert Sherwin]

For this - you will need to open a support case directly for us to assist.  We'll need to get tunnel access to your appliance and review/repair.

7.6.2-014 is also end-of-life as of June 2013, so you would also be advised to upgrade your AsyncOS revision to a supported version:

http://www.cisco.com/web/ironport/asyncOS_esa_eol_dates.html

-Robert