05-05-2020 09:25 AM
Hi.
I don't have TAC support on the Firewall so thought I would try my luck here.
I been upgrading the FMC and sensors to bring them uptodate
5.4 -> 6.0
6.0 -> 6.0.1
6.0.1 -> 6.1
6.1 -> 6.4
it was going well until - 6.0.1 -> 6.1 when it failed and I had to roll back with the script.
Since the rollback I cannot access the GUI anymore - it just sits on "System processes are starting, please wait"
Going on 36 hours now, I have restarted the services, rebooted the box (vm on esxi host) but no luck. CLI is accessible to me.
I tried to push the upgrade again to see if by chance it would go though but its failing on
[200505 15:41:25] Fatal error: Error running script 000_start/110_DB_integrity_check.sh
Looking in the logs - there seems to be a lot of fatal errors
After Checking DB, Warnings: 70, Fatal Errors: 570
looking at the fatal errors it just all seems to be missing data
here is a few examples on different tables
[Tue May 5 15:39:32 2020][FATAL] [missing data] table [ssl_flow_errors], row [125,ASYNC_OP_IN_PROGRESS]
[Tue May 5 15:39:31 2020][FATAL] [missing data] table [static_analysis_status], row [2,Analysis Failed,0]
[Tue May 5 15:39:28 2020][FATAL] [missing data] table [ssl_flow_status], row [9,Handshake Error]
[Tue May 5 15:39:26 2020][FATAL] [missing data] table [ssl_flow_messages], row [1,HELLO_REQUEST]
I dont see any other errors apart from missing data so I dont know if this is hugely important.
I tried running a repair on all the tables that were listed but it doesnt seem to do anything. All the errors remain.
sudo repair_table.pl ssl_cert_status
getting filenames from [/usr/local/sf/etc/db_updates/index]
getting filenames from [/usr/local/sf/etc/db_updates/base-6.0.1]
Processing table ssl_cert_status.
If anyone has any fixes that would be appreciated.
Is it even possible to skip the DBcheck and just go on with the upgrade.
or even drop the tables to get past this and the upgrade would re-populate them?
At this stage I am looking at deleting the VM and sensors and re-installing everything again and configuring it up again from scratch which is not ideal
Thanks
Solved! Go to Solution.
05-05-2020 09:54 AM
Please open a TAC service request.
That type of error would require a TAC engineer to have a look at the database under the covers. It's HIGHLY recommended to NOT try this yourself.
05-05-2020 09:54 AM
Please open a TAC service request.
That type of error would require a TAC engineer to have a look at the database under the covers. It's HIGHLY recommended to NOT try this yourself.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide