gateway cannot start up with error "default exited with status 33" in sspc log

Products

• CA API Gateway
• API SECURITY
• CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
• CA API Gateway Enterprise Service Manager (Layer 7)
• STARTER PACK-7
• CA Microgateway

Issue/Introduction

Start the gateway fail with errors in 

/opt/SecureSpan/Controller/var/logs/sspc_X_0.log

default starting

default exited with status 33

default already running ; will attempt to take control of it

Usually this error indicates some one else already starts the gateway.

But in this case, the ps command shows that there is no running gateway process on the machine.

Cause

Before the Controller start the gateway process, it will check if the gateway process is running base on the gateway pid file,

/opt/SecureSpan/Gateway/node/default/var/ssg.pid

The gateway pid file will not be removed when stop the gateway, therefore, before the next time of launching the gateway, the OS has chance to allocate the same pid to another process.

Although the chance is low, but when it occurs, the gateway cannot start up 

Resolution

it will be fixed in gateway 10.

A work around can be, manually remove the gateway pid file,

/opt/SecureSpan/Gateway/node/default/var/ssg.pid

Additional Information

Defect ticket #DE418125