API Gateway: Node is Not Running After Upgrading to 10.0

book

Article ID: 197793

calendar_today

Updated On:

Products

CA API Gateway API SECURITY STARTER PACK-7

Issue/Introduction

After upgrading the gateway, the node is not running and the status is WONT_START. Here is the sspc_0_0.log:


2020-08-20T11:09:52.124-0400 INFO    1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
2020-08-20T11:09:52.125-0400 WARNING 1 com.l7tech.server.processcontroller.ProcessController: Couldn't read API port file; will try default port
java.lang.NumberFormatException: For input string: "2124
"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:580)
        at java.lang.Integer.valueOf(Integer.java:766)
        at com.l7tech.server.processcontroller.ProcessController.getNodeApi(Unknown Source)
        at com.l7tech.server.processcontroller.h.getApi(Unknown Source)
        at com.l7tech.server.processcontroller.q.b(Unknown Source)
        at com.l7tech.server.processcontroller.q.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessController.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessController.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessControllerDaemon.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessControllerDaemon.main(Unknown Source)
2020-08-20T11:09:57.135-0400 INFO    1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
2020-08-20T11:09:57.135-0400 WARNING 1 com.l7tech.server.processcontroller.ProcessController: Couldn't read API port file; will try default port
java.lang.NumberFormatException: For input string: "2124
"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:580)
        at java.lang.Integer.valueOf(Integer.java:766)
        at com.l7tech.server.processcontroller.ProcessController.getNodeApi(Unknown Source)
        at com.l7tech.server.processcontroller.h.getApi(Unknown Source)
        at com.l7tech.server.processcontroller.q.b(Unknown Source)
        at com.l7tech.server.processcontroller.q.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessController.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessController.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessControllerDaemon.a(Unknown Source)
        at com.l7tech.server.processcontroller.ProcessControllerDaemon.main(Unknown Source)

Cause

When you migrate a database from GW 9.X cluster to GW 10.X standalone node, all of the nodes from the cluster will still appear in the cluster_info table. The GW is trying to contact a node that doesn't exist.

Environment

API Gateway: 10.0

Resolution

You will need to remove the node(s) that are no longer in use.

Before performing these steps, take a snapshot of your VM and/or take a backup copy of your MySQL ssg database.

1. Run command: mysql ssg -e "select * from cluster_info;"
2. Using the IP address, identify which node is the current node 
3. Remove the other node(s) with the following commands:
   mysql ssg -e "delete from cluster_info where name = 'GatewayX';" (X represents the number associated with the node you are trying to delete)
   mysql ssg -e "flush privileges;"
4. Restart the Gateway: service ssg restart