This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed to upgrade config from V18.5 MR3 to V19.0 GA

Hi

I was trying upgrade the firmware from V18.5 MR3 to V19.0 GA.

console showing:

Migrating config from SFOS 18.5.3 MR-3-Build408 to SFOS 19.0.0 GA-Build317
ERROR(0x03): Failed to migrated config. Load default.

logs at /log/migration.log showing:

Old version is 18.509 and currentversion is 19.003
Database is upgrading to dbv19.000
Check migration for version dbv19.000
Applying migration for version dbv19.000
1513 2022-04-28 16:54:06.370 GMTERROR:  duplicate key value violates unique constraint "tbldataconfig_pkey"
1513 2022-04-28 16:54:06.370 GMTDETAIL:  Key (key)=(MaxNoTables24hr_tls) already exists.
1513 2022-04-28 16:54:06.370 GMTSTATEMENT:  insert into tbldataconfig (key,value) select 'MaxNoTables24hr_tls',101 where not exists (select key from tbldataconfig where key='MaxNoTables24hr_tls' and value=101);
psql:/_conf/DB/dbv19.000/corporate.sql:327: ERROR:  duplicate key value violates unique constraint "tbldataconfig_pkey"
DETAIL:  Key (key)=(MaxNoTables24hr_tls) already exists.
/bin/psql -1 -p 5432 -U pgroot -q  -d corporate -f /_conf//DB/dbv19.000/corporate.sql Failed
/bin/sh /_conf//DB/dbv19.000/migration.sh Failed
UPDATE 1
Stopping database
512 2022-04-28 16:54:07.153 GMTLOG:  received fast shutdown request
512 2022-04-28 16:54:07.153 GMTLOG:  aborting any active transactions
515 2022-04-28 16:54:07.153 GMTLOG:  shutting down
515 2022-04-28 16:54:08.067 GMTLOG:  database system is shut down
2022-04-28 16:54:08.164 GMT : Database stopped after 1 seconds
applymigration.sh exited with 1

16 May Update:

i have try re-image 18.5.3, import the same config and try upgrade to v19 again. still got same problem.

the case are opened, support still doing back-end checking. will keep updating.



This thread was automatically locked due to age.
Parents
  • For the overview:
    There are currently two different Issues identified and under investigation. If any of those IDs matches your current behavior, please raise a Support Case and refer the matching Bug ID: 

    1. Fail-safe after upgrade. In this scenario, the firewall will not boot anymore and go into fail-safe. For More Information about Fail-safe: https://support.sophos.com/support/s/article/KB-000036375?language=en_US 
    The Bug ID: NC-93936

    2. Factory Default after Upgrade. In this scenario, the firewall will boot in factory default (172.16.16.16 IP). You can go back to the old firmware. You see an error in the /log/migration.log: ERROR(0x03): Failed to migrated config. Load default.
    The Bug ID:  NC-94337

    Both issues seems to occur under rare condition. 

    __________________________________________________________________________________________________________________

Reply
  • For the overview:
    There are currently two different Issues identified and under investigation. If any of those IDs matches your current behavior, please raise a Support Case and refer the matching Bug ID: 

    1. Fail-safe after upgrade. In this scenario, the firewall will not boot anymore and go into fail-safe. For More Information about Fail-safe: https://support.sophos.com/support/s/article/KB-000036375?language=en_US 
    The Bug ID: NC-93936

    2. Factory Default after Upgrade. In this scenario, the firewall will boot in factory default (172.16.16.16 IP). You can go back to the old firmware. You see an error in the /log/migration.log: ERROR(0x03): Failed to migrated config. Load default.
    The Bug ID:  NC-94337

    Both issues seems to occur under rare condition. 

    __________________________________________________________________________________________________________________

Children