Problem when upgrade FireSIGHT

ms.borikarn.th · ‎05-16-2016

We found an error when try to upgrade Network Sensor Patch. Any Idea what the cause?

OUT: Verifying archive integrity...OUT: All good.
OUT: Uncompressing Cisco Network Sensor Patch / Fri Mar 25 14:01:08 UTC 2016OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: ..OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: .OUT: ...OUT: ...OUT: ....OUT: ..OUT: ...OUT: ..OUT: .OUT: .OUT: ...OUT: ..OUT: ...OUT: .OUT: .OUT: .OUT: .OUT: ..OUT: .OUT: .OUT: .OUT: ......OUT: .OUT: .OUT: ..OUT: ..OUT: ..OUT: .OUT: ...OUT: ..OUT: .OUT: ..OUT: .OUT: .OUT: .OUT: ...OUT: .OUT: .OUT: .OUT: ...OUT: .OUT: ..OUT: .OUT: .OUT: ..OUT: .OUT: ..OUT: .OUT: .OUT: ..................................................................................
OUT: [160516 8:54:04] ###################
OUT: [160516 8:54:04] # UPGRADE STARTING
OUT: [160516 8:54:04] ###################
OUT: END_SCRIPT_000_start_100_start_messages_sh=1 #[160509 8:51:10]
OUT: [160516 8:54:04] BEGIN 000_start/100_start_messages.sh
OUT: END_SCRIPT_000_start_101_run_pruning_pl=1 #[160509 8:51:35]
OUT: [160516 8:54:05] SKIP 000_start/101_run_pruning.pl
OUT: END_SCRIPT_000_start_102_check_sru_install_running_pl=1 #[160509 8:51:36]
OUT: [160516 8:54:05] SKIP 000_start/102_check_sru_install_running.pl
OUT: END_SCRIPT_000_start_105_check_model_number_sh=1 #[160509 8:51:37]
OUT: [160516 8:54:05] BEGIN 000_start/105_check_model_number.sh
OUT: END_SCRIPT_000_start_106_check_HA_updates_pl=1 #[160509 8:51:39]
OUT: [160516 8:54:06] SKIP 000_start/106_check_HA_updates.pl
OUT: END_SCRIPT_000_start_107_version_check_sh=1 #[160509 8:51:41]
OUT: [160516 8:54:06] BEGIN 000_start/107_version_check.sh
OUT: END_SCRIPT_000_start_108_check_sensors_ver_pl=1 #[160509 8:51:42]
OUT: [160516 8:54:08] SKIP 000_start/108_check_sensors_ver.pl
OUT: END_SCRIPT_000_start_109_check_HA_MDC_status_pl=1 #[160509 8:51:44]
OUT: [160516 8:54:08] SKIP 000_start/109_check_HA_MDC_status.pl
OUT: END_SCRIPT_000_start_110_DB_integrity_check_sh=1 #[160509 8:52:15]
OUT: [160516 8:54:08] SKIP 000_start/110_DB_integrity_check.sh
OUT: END_SCRIPT_000_start_111_FS_integrity_check_sh=1 #[160509 8:52:16]
OUT: [160516 8:54:08] SKIP 000_start/111_FS_integrity_check.sh
OUT: END_SCRIPT_000_start_112_CF_check_sh=1 #[160509 8:52:17]
OUT: [160516 8:54:09] SKIP 000_start/112_CF_check.sh
OUT: [160516 8:54:09] ** enabling SCRIPT_RECOVERY_MODE for 000_start/113_EO_integrity_check.pl
OUT: [160516 8:54:09] BEGIN 000_start/113_EO_integrity_check.pl
OUT: [160516 8:56:56] FAILED 000_start/113_EO_integrity_check.pl
OUT: [160516 8:56:56] ====================================
OUT: [160516 8:56:56] tail -n 10 /var/log/sf/Cisco_Network_Sensor_Patch-5.4.1.6/000_start/113_EO_integrity_check.pl.log

Marvin Rhoads · ‎05-16-2016

Try this workaround:

Run the following commands to temporarily bypass the filesystem check:
sudo su -
touch /.skip_fsic
Then re-run the upgrade.

Source: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCur64403/?referring_site=ss

If that doesn't work, I recommend you open a TAC case for more detailed investigation.

nspasov · ‎05-16-2016

Hi there. I faced the same issue when trying to upgrade from 5.4.x to 6.x. I tried several different things but nothing worked. So I got tired of playing around with it so I re-imaged mine and restored from a good db backup.

If that is not an option for you then I would recommend opening a TAC case. TAC might be able to do some DB repair and help you through this.

I hope this helps!

Thank you for rating helpful posts!

Jetsy Mathew · ‎05-17-2016

Hello Borikarn,

There are several script which checks the database tables during the upgrade.

The error that you are facing is related with the EO containers and EO integrity tables. For this , its must that you should contact TAC since this is only done under the supervision of escalation team.

Whenever you face this EO integirty check errors, dont try any workaround by your own or don't try to skip the error by creating skip integrity check file. EO integrity check will fail due to specific UUID's which can be corrupted. Thus after analyzing the database we need to repair the UUID. Hence please contact TAC so that they can discuss with the escalation team and do the needful.

Rate if my post helps you.

Regards

Jetsy