OPERATIONAL DEFECT DATABASE
...
...
RabbitMQ process doesn't start on the FMC. This leads to a 'system processes are starting' message in the FMC UI.
PM status shows RabbitMQ fails to start while its predecessors start properly. The rabbit@localhost.log file will indicate errors 'not_a_dets_file' message when the /var/lib/rabbitmq/mnesia/rabbit@localhost/recovery.dets file is corrupt
Delete the /var/lib/rabbitmq/mnesia/rabbit@localhost/recovery.dets file & restart RabbitMQ from pmtool
In some circumstances the directory stucture in the work around might be wrong. Check: var-log/rabbitmq/log/crash.log Looking for: exception exit: {{badmatch,{error,{{{badmatch,{error,{not_a_dets_file,"/var/lib/rabbitmq/mnesia/rabbit@localhost/msg_stores/vhosts/45Y9RF6ZKMNMGGWS6HE9BFJT2/recovery.dets"}}}, In this situation the recovery.dets was in /var/lib/rabbitmq/mnesia/rabbit@localhost/msg_stores/vhosts/45Y9RF6ZKMNMGGWS6HE9BFJT2/recovery.dets
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
