topic Hi, in Network Security

upgrade failure to 5.3

pjkaczmarzyk — Tue, 12 Mar 2019 13:01:01 GMT

Greetings,

I am trying to upgrade to 5.3(from 5.2.0.5) and I get an error(The DC is a VM):

Update Installation Failed : [ 8%] Fatal error: Error running script 000_start/113_EO_integrity_check.pl

How can I fix this problem or skip this check?

root@Sourcefire-VM:/var/log/sf/Sourcefire_3D_Defense_Center_S3_Upgrade-5.3.0# cat main_upgrade_script.log

[160516 11:38:53] ###################
[160516 11:38:53] # UPGRADE STARTING
[160516 11:38:53] ###################
[160516 11:38:53] SKIP   /var/sf/upgrade-scripts/5.3.0/000_start/004_correct_fsic.sh
[160516 11:38:54] BEGIN 000_start/100_start_messages.sh
[160516 11:38:54] BEGIN 000_start/101_run_pruning.pl
[160516 11:39:04] SKIP   000_start/102_check_sru_install_running.pl
[160516 11:39:04] BEGIN 000_start/105_check_model_number.sh
[160516 11:39:04] SKIP   000_start/106_check_HA_updates.pl
[160516 11:39:05] BEGIN 000_start/107_version_check.sh
[160516 11:39:05] BEGIN 000_start/108_check_sensors_ver.pl
[160516 11:39:06] SKIP   000_start/109_check_HA_MDC_status.pl
[160516 11:39:06] SKIP   000_start/110_DB_integrity_check.sh
[160516 11:39:06] SKIP   000_start/111_FS_integrity_check.sh
[160516 11:39:06] SKIP   000_start/112_CF_check.sh
[160516 11:39:06]   ** enabling SCRIPT_RECOVERY_MODE for 000_start/113_EO_integrity_check.pl
[160516 11:39:06] BEGIN 000_start/113_EO_integrity_check.pl
[160516 11:39:57]   FAILED 000_start/113_EO_integrity_check.pl
[160516 11:39:57]   ====================================
[160516 11:39:57]     tail -n 10 /var/log/sf/Sourcefire_3D_Defense_Center_S3_Upgrade-5.3.0/000_start/113_EO_integrity_check.pl.log
[160516 11:39:57] Fatal error: Error running script 000_start/113_EO_integrity_check.pl
[160516 11:39:57] Exiting.
[160516 11:39:57] Attempting to remove upgrade lock
[160516 11:39:57] Success, removed upgrade lock

root@Sourcefire-VM:/var/log/sf/Sourcefire_3D_Defense_Center_S3_Upgrade-5.3.0/000_start# cat 110_DB_integrity_check.sh.log
**********************************************************
[160516 09:25] Starting script: 000_start/110_DB_integrity_check.sh
Entering 000_start/110_DB_integrity_check.sh...
Sourcefire Linux OS 5.2.0-208
For details on DB integrity check warnings and errors, please read:
/var/log/sf/Sourcefire_3D_Defense_Center_S3_Upgrade-5.3.0/DBCheck.log
Beginning DB integrity check now.
getting filenames from [/usr/local/sf/etc/db_updates/index]
getting filenames from [/usr/local/sf/etc/db_updates/base-5.2.0]
no dude file [/usr/local/sf/etc/db_updates/5.2.0.1] assume no database updates
getting filenames from [/usr/local/sf/etc/db_updates/5.2.0.2]
getting filenames from [/usr/local/sf/etc/db_updates/5.2.0.3]
no dude file [/usr/local/sf/etc/db_updates/5.2.0.4] assume no database updates
no dude file [/usr/local/sf/etc/db_updates/5.2.0.5] assume no database updates
/usr/local/sf/etc/db_exceptions/db_exceptions.yaml
running database integrity check with the following options:
- use exception directory /usr/local/sf/etc/db_exceptions
- check refererences
- check enterprise objects
- check schema
- check required data
- log to file /var/log/sf/Sourcefire_3D_Defense_Center_S3_Upgrade-5.3.0/DBCheck.log
- log to stderr
After Checking DB, Warnings: 0, Fatal Errors: 0
Database integrity check was successful
Database Integrity check succeeded

Exiting 000_start/110_DB_integrity_check.sh.

Hi

yogdhanu — Wed, 18 May 2016 11:11:32 GMT

Upgrade failures at this script generally mean Corrupt or Stale (Old revision) entries in the EO repository.

cat 000_start/113_EO_integrity_check.pl.log |grep -i error

check whats the error there and based on that old data might need to be deleted.

Hi

pjkaczmarzyk — Wed, 18 May 2016 12:47:22 GMT

I greped the log on the ERROR (I tried the upgrade multiple times so that most likely explains why I see the same entry a few times):

root@Sourcefire-VM:/var/log/sf/Sourcefire_3D_Defense_Center_S3_Upgrade-5.3.0# cat 000_start/113_EO_integrity_check.pl.log |grep -i ERROR -A1 -B1
    Checking c88eed77-0ee7-4c2e-a6c7-8b055f2be518
    ERROR found!
    Checking de61f817-df61-11e2-b009-848f69e36dd2
--

Total errors: 1
EOIC failed
--
    Checking c88eed77-0ee7-4c2e-a6c7-8b055f2be518
    ERROR found!
    Checking de61f817-df61-11e2-b009-848f69e36dd2
--

Total errors: 1
EOIC failed
--
    Checking c88eed77-0ee7-4c2e-a6c7-8b055f2be518
    ERROR found!
    Checking de61f817-df61-11e2-b009-848f69e36dd2
--

Total errors: 1
EOIC failed

Hi ,

Aastha Bhardwaj — Wed, 18 May 2016 13:36:12 GMT

Hi ,

We would probably need to check further on these EO entries , we would also need to repair the tables .

I would advise you to open up a TAC case so that we can check further on this.

Regards,

Aastha Bhardwaj

Rate if that helps!!!

Opening a TAC case is I think

pjkaczmarzyk — Thu, 19 May 2016 05:38:59 GMT

Opening a TAC case is I think not an option as that VM runs on an test license(We wanted to test upgrade procedures for our devices).

Is there a way I can bypass those errors or any instruction how to fix them?

Hi,

Nikhil Vaidya — Fri, 20 May 2016 16:21:58 GMT

Hi,

Since these are EO errors, we would need to see what these corrupted ones are before providing you with instructions on how they can be fixed. Since a TAC case is not an option for you, you can re-image the device to the needed version

Thanks

Re: Hi

jerry_young — Fri, 18 May 2018 16:00:48 GMT

I have the same errors while upgrading:

"Checking e2077cca-6394-4cb3-852e-cd79499eb713
Checking c88eed77-0ee7-4c2e-a6c7-8b055f2be518
ERROR found!
Checking de61f817-df61-11e2-b009-848f69e36dd2
Checking 39ec3498-d903-11e2-b009-848f69e36dd2"

was there a fix for this ?

TIA.