topic Re: Alert: high : mdb: Exited 4 times, waiting x seconds to retry in General Topics

Alert: high : mdb: Exited 4 times, waiting x seconds to retry

lewis — Fri, 09 Jan 2015 17:34:16 GMT

Has anyone encountered the following alert message from your Panorama? Or do you know what it means? We have tried to restart the management plain through ssh but now since the restart we can not connect through the web interface. We have logged a ticket to support but was checking here to see if anyone has experienced this alert? Our panorama is currently at 6.0.1

SYSTEM ALERT : high : mdb: Exited 4 times, waiting 120 seconds to retry

SYSTEM ALERT : high : mdb: Exited 4 times, waiting 150 seconds to retry

SYSTEM ALERT : high : mdb: Exited 4 times, waiting 180 seconds to retry

etc, etc, etc

Thanks in advance.

Re: Alert: high : mdb: Exited 4 times, waiting x seconds to retry

Mystique — Fri, 09 Jan 2015 17:54:53 GMT

Hello,

This is a known bug ID 62321 and fixed in 6.0.2 build.

For workaround, TAC will need to delete some corrupted mongodb journal files manually from root. Please continue to work with support to purge few files from root to gain access.

Hope this helps

Re: Alert: high : mdb: Exited 4 times, waiting x seconds to retry

lewis — Fri, 09 Jan 2015 18:04:52 GMT

Thanks, have just rebooted the box. Will likely look at upgrading sooner than later

Re: Alert: high : mdb: Exited 4 times, waiting x seconds to retry

Mystique — Mon, 12 Jan 2015 18:48:48 GMT

Hello Lewis,

Thanks for the update.

Rebooting the device might not fix the issue.

Temporary fix is to remove corrupted files from root and permanent fix is to upgrade to 6.0.2 or later version.

Note: Please mark answers as "correct answer" or "helpful answer" if it helped in anyway.

Thanks

Re: Alert: high : mdb: Exited 4 times, waiting x seconds to retry

lewis — Mon, 12 Jan 2015 19:11:24 GMT

We ended up rebooting as everything seemed to lockup...this may have been a mistake as it took a number of hours before it became usable again. Long story short we have upgraded to 6.1.1 and are now functional. Thanks for your assistance.