Layer7 API Management

  • Private Community
Back to discussions
Expand all | Collapse all

Best practice: reboot the API GateWay machine before upgrade?

  • 1.  Best practice: reboot the API GateWay machine before upgrade?

    Posted May 17, 2018 03:03 AM

    We have upgraded all our API GateWays from 9.1 to 9.2 CR07.

    We started with DEV, then TEST, followed by QA and finally PROD.

    QA and PROD are MySQL clustered environments.

    On all our non-production environments we encountered some minor issues, which we could explain. And these environments are rebooted more often (for different reasons). Production is stable and running for over a year.

    So when we finally started to upgrade the first production machine, we encountered a very strange error in the platform upgrade:

    com.l7tech.server.processcontroller.patching.PatchServiceApiImpl: Output from patch install: rm: cannot remove `/opt/SecureSpan/Platform/data/cache': Directory not empty

    We could not explain why this was happening!

    So what we did was cleaning the install error (How to resolve ERROR state during APIGW 9.1 platform upgrade? ), rebooted the machine and started the upgrade again.. 

    And it worked!

    So what we did after this on every machine is first reboot and then start the upgrade!

    Result: No issues during the upgrade.

     

    Does anybody have the same experience?



  • 2.  Re: Best practice: reboot the API GateWay machine before upgrade?

    Posted Jan 20, 2019 10:23 AM

    Thanx for this post, this helped us to find a workaround to install the v9.3.00 platform patch!

     

    We tried to upgrade from v9.2.00-CR08 to platform patch v9.3.00 (CA_API_PlatformUpdate_64bit_v9.3.00-RHEL.L7P) but this resulted in a patch install ERROR.
    We also found this 'Output from patch install: rm: cannot remove `/opt/SecureSpan/Platform/data/cache': Directory not empty' in our CA API Gateway host log file (/opt/SecureSpan/Controller/var/logs/sspc_X_0.log). 
    The procedure which worked for us:
    - Start ssgconfig menu on the CA API Gateway and with the patch menu upload the CA API Gateway platform patch v9.3.00.
    - Exit the patch menu and perform Reboot the API Gateway with the ssgconfig menu.
    - After the reboot, start the ssgconfig menu again and then install the v9.3.00 platform patch.

    Uploading the patch and immediately installing the platform patch, which in my opinion is logical and should work, will fail with a path install error. The reboot seems to clear the cache directory which is checked in the installation of the patch.