FMC login page hung at "System processes are starting, please wait." Remained hung over night

[garyewhite]

Login page hung saying system processes are starting... it's been hours...

gui status follows...

admin@Sourcefire3d:  sudo pmtool status | grep -i gui

mysqld (system,gui,mysql) - Running 3853
httpsd (system,gui) - Running 3856
sybase_arbiter (system,gui) - Waiting
vmsDbEngine (system,gui) - Down
ESS (system,gui) - Running 3858
DCCSM (system,gui) - Down
Tomcat (system,gui) - Down
VmsBackendServer (system,gui) - Down
mojo_server (system,gui) - Running 3881

Any ideas?

Thanks!

-G

[kylemiller452225788]

We have a fix!

My ESXI host crashed and I was having the same error as you when I opened up the FMC web GUI I could not login and the error message  "System processes are starting, please wait." was present.  Apparently there is a unsolved bug with FMC CSCvt18051 that upon reloading the GUI processes do not start up on there own.  However there is a work around.  Console into your firepower linux OS and Delete the /var/lib/rabbitmq/mnesia/rabbit@localhost/recovery.dets file & restart RabbitMQ from pmtool.  The command for that is pmtool restartbyid RabbitMQ.  Give that a try and my gui started operating normally afterward.  Hope it works for you as well.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt18051

currently there is no fix for this bug as up 6/15/2021 when Im writing this.

[Marvin Rhoads]

@kylemiller452225788 

Thanks for sharing the BugID.

[Kasper Elsborg]

I had the same problem after an uncontrolled power outage.

I don't have any recovery.dets in /var/lib/rabbitmq/mnesia/rabbit@localhost/

but the "pmtool restartbyid RabbitMQ" did the trick.

Br. Kasper

[WilliamMalta19560]

Hi, Team. 

I was facing the same issue 'system processes are starting' message in the FMC Gui.

I noticed that some services does not start.
root@FMC:/Volume/home/admin# pmtool status | grep -i gui
mysqld (system,gui,mysql) - Running 21366
httpsd (system,gui) - Running 21369
sybase_arbiter (system,gui) - Waiting
vmsDbEngine (system,gui) - Running 21370
ESS (system,gui) - Running 21412
DCCSM (system,gui) - Running 22241
Tomcat (system,gui) - Down
VmsBackendServer (system,gui) - Down
mojo_server (system,gui) - Running 21860
root@FMC:/Volume/home/admin#

I have tried to restart services, but did not worked
pmtool restartbyid Tomcat
pmtool restartbyid VmsBackendServer

My solution was reboot FMC with reboot command under root user.

root@FMC:/Volume/home/admin# uptime
21:52:44 up 1 min, 1 user, load average: 4.49, 1.41, 0.49
root@FMC:/Volume/home/admin# pmtool status | grep -i gui
mysqld (system,gui,mysql) - Running 5851
httpsd (system,gui) - Running 5854
sybase_arbiter (system,gui) - Waiting
vmsDbEngine (system,gui) - Running 5855
ESS (system,gui) - Running 5896
DCCSM (system,gui) - Running 6765
Tomcat (system,gui) - Running 6902
VmsBackendServer (system,gui) - Running 6903
mojo_server (system,gui) - Running 5961
root@FMC:/Volume/home/admin#

[acobosm]

Hi WilliamMalta19560, for me, your reboot workarround was usefull but in my case, I have to add ´sudo´ at the bigining of the ´pmtool status´ command.

Thanks a lot.

[laurathaqi]

Hi community,

Does someone has a solution for this problem? Happening on 6.6.1 Virtual on my Environment. 

Looking forward to hearing from you.

Best,

Laura

[balaji.bandi]

Look athe BUG - https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt18051

Fixed in 7.0  so an upgrade is required.

[Kasper Elsborg]

I'm running 7.2

Br. Kasper

[balaji.bandi]

Looks the bug still persists, time for contact TAC,

[Alan Inman]

This worked for me (6.1.x) (Cisco Documentation

1. Log into the CLI of the FireSIGHT Management Center.
2. Elevate your privilege level to the root user mode:
   

   admin@FireSIGHT:~$ sudo su -

3. Enter this command into the CLI in order to restart the console:
   

   root@FireSIGHT:~# /etc/rc.d/init.d/console restart
   

Within 30 seconds of running the command the error message on the GUI cleared and I was able to login

[niranjan biswas]

Afterwards please follow the steps:

• Type: expert
• Type: sudo su
• Enter the password
• Type: pmtool restartByType gui
• Wait 1-2 minutes and try to access the GUI again.