We started with a software installation of version 11.0 and updated it by switching to Java JDK 17.0.18+8 and installing the ssg-11.1.00-17707.noarch.rpm package. This allowed us to start the system successfully yesterday, but today, when we tried the same procedure on the second node, it appears that Apigateway is not starting properly
11.1
The gateway did actually start successfully on this node. The log shows it fully booted, listeners were established, and it is processing LB_Health_Check requests normally by the end of the log. So the concern about it "not starting properly" is relate to delayed functionality or specific services failing, rather than a hard boot failure.
1.RemoteCacheAssertion Module Was Not Installed at Boot Time
and that was the root cause .
The RemoteCacheAssertion module (file: 8f4a57db52a523117d3f3edd9d177fcd5e0356a5ccab2ac6.aar) was not present in the standard assertions directory at startup. It was only loaded dynamically at 11:43:31, few minutes after the boot , when you uploaded it via the Gateway Manager console.
On Node 2, the RemoteCacheAssertion .aar file was missing from the Gateway's modular assertions directory (/opt/SecureSpan/Gateway/runtime/modules/assertions/). This .aar is not part of the standard 11.1 RPM package — it is a third-party/custom assertion that must be manually copied to this directory before starting the Gateway.
On Node 1, this file was already present (presumably copied during or before the first upgrade), so it loaded cleanly at boot. Node 2 was missed.
Copy the RemoteCacheAssertion .aar file from Node 1 to the same assertions directory on Node 2 before starting the Gateway:------- This fixed the issue . it should be put inside , /opt/SecureSpan/Gateway/runtime/modules/assertions/
Then restart the SSG service. The module will load at boot like the other 11.1 .aar files, and all 89+ affected policies will be properly initialized from the start.