Layer7 API Management

Expand all | Collapse all

SSG gateway unable to start after upgrade to 9.1

Sebastian van Voorn

Sebastian van VoornJul 01, 2016 03:47 AM

  • 1.  SSG gateway unable to start after upgrade to 9.1

    Posted Jul 01, 2016 03:44 AM

    After upgrading the API GateWay Appliance (9.0) to 9.1, the ssg software is unable to start.

    the boot process is not setting the processControllerPort (/opt/SecureSpan/Gateway/node/default/var/processControllerPort is empty).

    so the Node Status (Menu 2, 7) is STARTING

    My big question is what is setting the processControllerPort?

     

    Sebastian.



  • 2.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Jul 01, 2016 03:47 AM

    Excuse.. status is WONT_START



  • 3.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Jul 01, 2016 08:48 AM

    It seemed that the database upgrade was not executed... So we did.

    Now the Node status is STARTING..

    But now we can connect to the API GW using the policy manager. Before, we could not...



  • 4.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Jul 01, 2016 11:32 AM

    if you can connect via policy manager that means your gateway is up and running ..

    gateway could not start due to DB version mismatch .



  • 5.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Jul 07, 2016 07:10 AM

    Hi Kemal,

     

    Indeed it was the DB version mismatch..

    But the status is still STARTING instead of RUNNING.

    Any idea why this is?



  • 6.  Re: SSG gateway unable to start after upgrade to 9.1

    Broadcom Employee
    Posted Aug 23, 2016 09:29 PM

    Hi Sebastian,

    Is it still a problem?

    If it was DB version mismatch, did you upgrade the database? any problem?

    For statup problem, you may also check  the process control log,

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

     

    As well as the ssg log.

     

    It would be better to open a support ticket for further investigation.

     

    Regards,

    Mark



  • 7.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Aug 24, 2016 01:52 AM

    Hello Zhijun He,

    It is still the status, so we have opened a support ticket with our supplier.

    In the SSPC log we see:

    2016-08-23T06:54:53.240+0200 INFO    1 com.l7tech.server.processcontroller.ProcessController: Empty API port from '/opt/SecureSpan/Gateway/node/default/var/processControllerPort' API is disabled.



  • 8.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Aug 24, 2016 03:18 AM


  • 9.  Re: SSG gateway unable to start after upgrade to 9.1
    Best Answer

    Posted Aug 24, 2016 05:43 AM

    Solved it (myself)..

     

    Somehow Node Control was not set (after db upgrade?) on this port. When you set this, the port number is set in /opt/SecureSpan/Gateway/node/default/var/processControllerPort

     

    Greetings..



  • 10.  Re: SSG gateway unable to start after upgrade to 9.1

    Posted Sep 04, 2018 11:48 AM

    I haven't done any upgrade but I have a same issue since this morning and also I couldn't login to the policy manager to check whether Node control feature is enabled to the port 2124.



  • 11.  RE: Re: SSG gateway unable to start after upgrade to 9.1

    Posted Oct 11, 2019 02:24 PM
    Hi Karthick.Sundaresan,

    could you fix your issue?? I'm having the same problem.

    service restart every 10 minutes.

    2019-10-11T11:30:02.456-0500 INFO 1 com.l7tech.server.processcontroller.q: default started successfully
    2019-10-11T11:30:02.456-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: default started
    2019-10-11T11:39:21.529-0500 WARNING 1 com.l7tech.server.processcontroller.ProcessController: default is supposedly running but has not responded to a ping in 7,477ms. Will keep retrying up to 15,000 ms.
    2019-10-11T11:40:26.593-0500 WARNING 1 com.l7tech.server.processcontroller.ProcessController: default is supposedly running but has not responded to a ping in 96,492ms. Killing and restarting.
    2019-10-11T11:40:26.594-0500 WARNING 1 com.l7tech.server.processcontroller.ProcessController: Killing default
    2019-10-11T11:40:32.201-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: default crashed; restarting...
    2019-10-11T11:40:32.201-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:40:32.226-0500 INFO 1 com.l7tech.server.processcontroller.q: default starting
    2019-10-11T11:40:37.229-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:40:42.264-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:40:47.280-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:40:52.297-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:40:57.316-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:41:02.353-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:41:07.370-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:41:12.387-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: Getting API port from /opt/SecureSpan/Gateway/node/default/var/processControllerPort
    2019-10-11T11:41:17.404-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: /opt/SecureSpan/Gateway/node/default/var/processControllerPort does not exist yet, will try default port
    2019-10-11T11:41:22.435-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: /opt/SecureSpan/Gateway/node/default/var/processControllerPort does not exist yet, will try default port
    2019-10-11T11:41:27.455-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: /opt/SecureSpan/Gateway/node/default/var/processControllerPort does not exist yet, will try default port
    2019-10-11T11:41:32.471-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: /opt/SecureSpan/Gateway/node/default/var/processControllerPort does not exist yet, will try default port
    2019-10-11T11:41:37.497-0500 INFO 1 com.l7tech.server.processcontroller.ProcessController: /opt/SecureSpan/Gateway/node/default/var/processControllerPort does not exist yet, will try default port

    Regards.


  • 12.  RE: Re: SSG gateway unable to start after upgrade to 9.1

    Broadcom Employee
    Posted Oct 13, 2019 08:28 PM
    Dear Luis,
    You may also check the gateway ssg log, it should provide some clues.

    Regards,
    Mark


  • 13.  RE: SSG gateway unable to start after upgrade to 9.1

    Broadcom Employee
    Posted Oct 16, 2019 08:19 AM
    Hi,
    I believe you forgot DB Upgrade step.
    db version is 9.0 and your version should 9.1
    version information is stored in ssg.ssg_version table, it is just a string. set it to 9.1.00  start server , set ssg.version again to 9.0.00  and then try db upgrade.