ProxySG & Advanced Secure Gateway

We can’t upgrade one pair of proxysg 300-5 from version 6.5.9.12 to 6.7.4.3, the error message we encountered during image installation  was “ failed to extract system image” .

Could you please help me what will be minor version need to upgrade .

Hi Lokesh, Refer this forum article : https://www.symantec.com/connect/forums/proxysg-proxysg-failed-upload-image?list_context_id=3668231&list_context_type=symantec_product

Hi Aboonaim Golandaz,

For us problem is while installing the image getting "Failed to extract the image".

Hi, Try the same step and let me know. The error which you are getting is because of certificate expire.

Hi Aboonaim,

We could see the below certificate error and whether this casuse the issue. I have read the article like In proxySG appliance the SSL context is used only for uploading system images to the ProxySG appliance

2019-12-19 04:48:20-00:00UTC  "Previous shutdown was not initiated from the management console"  0 60006:65   cag_reg_init.cpp:148
2019-12-19 04:48:21-00:00UTC  "License reinstalled"  0 540000:96   lic_admin_impl.cpp:3727
2019-12-19 04:48:22-00:00UTC  "CFSSL: Updated ca-cert 'BC_Engineering_CA' since it has been modified in the factory image"  0 140002:7D   tp_installer.cpp:876
2019-12-19 04:48:22-00:00UTC  "More recent or same version of trust package already installed"  0 300000:64   trust_package.cpp:961
2019-12-19 04:48:47-00:00UTC  "Licensing: Trial period already expired on 2013-06-02"  0 540000:96   lic_admin_impl.cpp:3931
2019-12-19 04:48:47-00:00UTC  "Licensing: new license state active"  0 540000:96   lic_admin_impl.cpp:1909
2019-12-19 04:48:47-00:00UTC  "DNS-Proxy admin started"  0 520000:96   dns_admin.cpp:688
2019-12-19 04:48:47-00:00UTC  "Executing image: Version: SGOS 6.5.9.12, Release id: 192685"  0 60006:1   boot_main.cpp:4159
2019-12-19 04:48:47-00:00UTC  "CFSSL: can't open keyring to read /legacy/cache_engine/persistent/replicated/volatile//config/v8/ssh/ssh_host_key"  0 300000:64   private_key_store.cpp:495
2019-12-19 04:48:47-00:00UTC  "Failed to read private key for /legacy/cache_engine/persistent/replicated/volatile//config/v8/ssh/ssh_host_key"  0 300000:1   cm.cpp:7185
2019-12-19 04:48:47-00:00UTC  "SSH: Could not load host key: /legacy/cache_engine/persistent/replicated/volatile//config/v8/ssh/ssh_host_key"  0 45000B:1   sgos_log.cpp:115
2019-12-19 04:48:47-00:00UTC  "SSH: Disabling protocol version 1. Could not load host key"  0 45000C:96   sgos_log.cpp:115

 

2019-12-19 04:48:48-00:00UTC  "Failed to create client context for profile bluecoat-appliance-certificate"  340010 340010:1   ssl_profile.cpp:1641
2019-12-19 04:48:48-00:00UTC  "Failed to create server context for profile bluecoat-appliance-certificate"  340010 340010:1   ssl_profile.cpp:1676
2019-12-19 04:48:49-00:00UTC  "Failed to create client context for profile bluecoat-drtr-profile"  340010 340010:1   ssl_profile.cpp:1641
2019-12-19 04:48:49-00:00UTC  "Failed to create server context for profile bluecoat-drtr-profile"  340010 340010:1   ssl_profile.cpp:1676
2019-12-19 04:48:49-00:00UTC  "Failed to create client context for profile _bluecoat-services-cloud"  340010 340010:1   ssl_profile.cpp:1641
2019-12-19 04:48:49-00:00UTC  "Failed to create server context for profile _bluecoat-services-cloud"  340010 340010:1   ssl_profile.cpp:1676
2019-12-19 04:48:49-00:00UTC  "Failed to create client context for profile _bluecoat-services-phs"  340010 340010:1   ssl_profile.cpp:1641
2019-12-19 04:48:49-00:00UTC  "Failed to create server context for profile _bluecoat-services-phs"  340010 340010:1   ssl_profile.cpp:1676

Thanks,

Raju

Hi,

Trying following command on CLI might solve the problem.

========

#load upgrade ignore-warnings

#restart upgrade

========

Regards,

ShoK

Hi

 I found a KB which discuss simailar issue you are facing.

https://support.symantec.com/us/en/article.tech257268.html

 

Regards,

Shok