The daemon is not responding.

[pbabu6001]

The Warning message is:

The case application tried and failed 3 times to successfully complete an update. This may be due to a network configuration issue or temporary outage.

Version: 9.7.1-066

Serial Number:

Timestamp: 27 Aug 2018 09:06:51 -0400

After we got the above alert, we are unable to connect the IronPort through https.

mail01.com> status 

Enter "status detail" for more information.   

Couldn't obtain mail stats - mail01.com:

mail01.com> status detail


Couldn't obtain mail stats - resmail01.zurich.com: The daemon is not responding.

[dmccabej]

Hello,

If you receive a 'daemon not responding' when performing a status detail then that means there's something wrong with the primary mail processing service. On 9.7.1, this can be resolved from the front-end by performing a resetqueue from the CLI; however, please note this is destructive and wipes out the entire WorkQ and Delivery Queues. Those symptoms are common after a power failure, though, there could also be other causes.

It would be best to open a TAC case and we can try to perform a soft-repair of the mail queues and a quick health check to make sure everything else is running smooth.

Thanks!

-Dennis M.

[pbabu6001]

resetqueue isn't working and giving the error as "Unknown command or missing feature key: resetqueue" Thanks.

[dmccabej]

Unfortunately that's not much information to go off of. Had the ESA just rebooted at that time?

Thanks!

-Dennis M.

[Lemat]

There is a hiiden command "repairqueue", which solves nothing for my case:

> repairqueue

Do you want to repair or clean the queue?
1. Repair.
2. Clean.
[1]> 1

The mail flow will be stopped through out the repair/cleanup process
WARNING:
This utility does a best effort to repair the queue.
Not all queues corruptions can be repaired.
Are you sure you want to proceed? [N]> y
Checking generation checksum files
MGA Status: stopped
Rebuilding the queue
loading existing checkpoints...
journal_gen=16 pos=0 next_mid=246832907
mid_map msgs:1962 rcpts:3820 (recipient miscount of 0)
dehyd.chk: entries: 0 msgs:0 rcpts:0
gen016 load stops at 0
scanning journal 16@400000000...
Traceback (most recent call last):
File "/usr/build/iproot/ap/ipoe/ipoe/bootstrap.py", line 55, in <module>
File "/data/lib/python2.6_10_amd64_nothr/runpy.py", line 128, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/data/lib/python2.6_10_amd64_nothr/runpy.py", line 34, in _run_code
exec code in run_globals
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/repair_gcq.py", line 816, in <module>
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/repair_gcq.py", line 373, in repair
EOFError
(Machine example.com)> repairqueue

Do you want to repair or clean the queue?
1. Repair.
2. Clean.
[1]> 2

The mail flow will be stopped through out the repair/cleanup process
Cleanup finished
(Machine example.com)> status

Enter "status detail" for more information.

Couldn't obtain mail stats - example.com: The daemon is not responding.