Gateway not starting
Article ID: 142223
Updated On:
Products
Issue/Introduction
Gateway WONT START :
The most common symptom of this defect is caused by the API Gateway reporting a status of WONT_START in the Gateway configuration menu. The following log entries may also be seen in the Process Controller log:
com.l7tech.server.processcontroller.ProcessController: default crashed on startup with exit code 0
com.l7tech.server.processcontroller.ProcessController: default crashed on startup; copying its output:
com.l7tech.server.processcontroller.ProcessController: default wouldn't start; restarting...
Environment
Release : 10.x , 11.0
Component : APIGTW
Cause
The strongest indicator of this behavior would be verifying the permissions of certain configuration files after a restore. Navigate to /opt/SecureSpan/Gateway/node/default/etc/conf and observe whether the files have the following permissions:
-rw-rw-r-- 1 layer7 gateway 537 Apr 27 14:48 node.properties
-rw------- 1 layer7 gateway 42 Feb 26 01:28 omp.dat
-rw------- 1 layer7 gateway 53 Feb 26 01:28 ssglog.properties
-rw------- 1 layer7 gateway 737 Feb 26 01:28 system.properties
If the permissions are as described as above then the API Gateway in question has been impacted by this defect.
Resolution
Resolution
This behavior is caused by a defect in the product that does not set certain file permissions appropriately. Log in to the API Gateway via SSH or a console connection and perform the following procedure:
Log in to the API Gateway as the ssgconfig user
Select Option #3: Use a privileged shell (root)
Move to a specific configuration directory: cd /opt/SecureSpan/Gateway/node/default/etc/conf/
Modify the permissions of specific files: chmod 640 omp.dat ssglog.properties system.properties
Restart the API Gateway appliance
This defect has been registered with the API Management engineering staff and has been assigned development incident identifier SSG-9735. This defect is valid for all currently supported versions of the API Gateway.
Feedback
