Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
cosmos
Contributor

Cannot import package Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz

Jump to solution

I'm upgrading some management servers (VMs) in HA to R80.40. Current management is at R80.30 / Jumbo HF 107.

On importing the package in CPUSE I get "Cannot import package Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz. It is not a valid CPUSE package. Contact Check Point Technical Services for further assistance."

DeploymentAgent.log reads "Import of package Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz Failed" directly after the Extract Package And Metadata: created extraction temp dir /var/log/upload/import_tmp" process.

Basic checks pass

I'm hoping it's something simple like the file extension (got .gz from web, CPUSE was expecting .tgz but renames to .tgz anyway).

 

Any ideas?

1 Solution

Accepted Solutions
cosmos
Contributor

Yup. Renamed to .tgz and the import works. Turns out a very old version of Google Chrome was used to download the file, for some reason it writes a .gz instead of .tgz. 

This is despite the indication that CPUSE renames the file (using rename: src |/var/log/upload//Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.gz| target, |/var/log/upload//Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz|)

Hope this helps anyone else facing the same issue.

View solution in original post

3 Replies
cosmos
Contributor

Yup. Renamed to .tgz and the import works. Turns out a very old version of Google Chrome was used to download the file, for some reason it writes a .gz instead of .tgz. 

This is despite the indication that CPUSE renames the file (using rename: src |/var/log/upload//Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.gz| target, |/var/log/upload//Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz|)

Hope this helps anyone else facing the same issue.

View solution in original post

Julian_Sanchez
Collaborator

comos what is your experience this days with SMS in R80.40? I am planning to migrate one sms in R80.30 smart1-225 to open server. 

cosmos
Contributor

Hi Julian

I'd consider R80.40 the gold standard to run in production today. I have customers running Multi-Domain and VSX with no critical issues.

It still has its typical quirks like SmartConsole rendering issues on high DPI displays and like always needs a lot of TLC 🙂