FMC blank login screen

[tmoore]

I'm evaluating FMC version 6.6.2 on VMware and it was working fine. But now when I try to login through the gui I get the message that the "connection is not private" (using the self signed certificate).  If I select proceed to site I'm presented with a blank screen.  I no longer get the login screen.  Get the similar response with Chrome, IE or Firefox.  When I ran a capture with wireshark I see a Encrypted Alert (21) the a FIN ACK. 

Any idea why this is happening?  Was working fine for a few weeks.  I can ssh into FMC and I rebooted but still get a blank page when trying login via the browser. 

[mikael.lahtela · Accepted solution]

Hi,

Can you see if the FMCv guest is hitting any limits in vmware?
Give it more than 8Gb ram and try a restart.

br, Micke

[tmoore]

No all the VMware resources look good.  I did increase the memory to 16G just to see if it would make a difference but still just getting a blank screen after the reboot

[mikael.lahtela]

I got the same error in a different system and I don't think the wireshark error message is the problem.
There might be some DB issue, did you have any unexpected power failures?
If this is a lab environment I would recommend a fresh install.
If you have support for it you could try contact Cisco TAC.

br, Micke

[tmoore]

Yes I did another install and that one was OK when brought online received the login screen.  Did the wireshark also and saw the same alert so I guess that is just how it works.  These are just test\evals so I don't have support as of yet we are planning on putting in order for FMC.  Its weird that this happened on our eval device don't want to run into the same issue once we are in production.

[mikael.lahtela]

I have been running these for a while now without same issue.
Did you do any upgrade or something?
Because you can get a corrupted database if you try and upgrade and it fails, then try to reboot to solve the issue.
But the systems in production environments has been stable for me.

br, Micke

[tmoore]

Could be; it does look like an update was applied to esx host and the vm's rebooted. Need to talk to the admin to see what was being done.