- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Upgrade to R80.30 fails
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Upgrade to R80.30 fails
Standalone full HA deployment running R80.10 in a test lab environment.
Trying to upgrade to R80.30 using the following guide:
I've exported the R80.30_T200_Fresh_Install_and_Upgrade_Security_Gateway.tgz file from a separate (LIVE) firewall and imported this onto the 2nd cluster member as the cluster doesn't have internet connectivity.
When attempting to upgrade (right click and selecting 'Upgrade') the installation fails shortly after. Here is a copy of the install log:
[11/08/19 - 15:44:59][18264 4126043024]:------ Installing: ------
[11/08/19 - 15:45:00][18264 4126043024]:------ Validating Install: ------
[11/08/19 - 15:45:00][18264 4126043024]:/var/log/CPda/metadata/CheckPoint#Major#All#6.0#5#0#R80.30_GW_T200/tmp//major.conf file is in wrong format, unknown key: NEW_UPGRADE_VERSION
[11/08/19 - 15:45:00][18264 4126043024]:Error: Could not read config file /var/log/CPda/metadata/CheckPoint#Major#All#6.0#5#0#R80.30_GW_T200/tmp//major.conf
Any assistance with this would be greatly appreciated.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is your CPUSE Gaia Deployment Agent out of date? I've seen weird issues when there isn't a new enough version to support the package you are trying to use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is your CPUSE Gaia Deployment Agent out of date? I've seen weird issues when there isn't a new enough version to support the package you are trying to use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Once the deployment agent was up to date, the upgrade worked successfully.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
