Symantec Access Management

 View Only
  • 1.  SPS TroubleShooting

    Posted Jul 14, 2017 03:36 AM

    Hello All,

     

    I am facing an issue in my already existing SPS configuration the SHUT_DOWN_PORT, AJP_PORT are not showing up and service is down. I am also getting the below error when i restart the SPS instance :

     

    [root@00001 proxy-engine]# ./sps-ctl stop

    Apache has been successfully stopped..

    Attempting to stop Secure Proxy Engine..

    Sending stop message to server...

    Cannot stop Proxy Engine

    Unable to stop the Proxy Engine..

    Proxy Engine may not be initialized or may not be running.

    Consult Proxy Engine logs for details.

     

    [root@00001 proxy-engine]# ./sps-ctl start

    Successfully Started Apache..

    Proxy Engine (pid ) already running. Cannot be started.

     

    Can somebody please guide, what could be the possible issue and how can i do some troubleshooting at my end. It stopped suddenly and it was working fine and showing both SHUT_DOWN_PORT, AJP_PORT as well.

     

    Thank You

    Ankur Taneja



  • 2.  Re: SPS TroubleShooting

    Posted Jul 14, 2017 03:44 AM

    Hello,

     

    Did you checked the SPS server.log to see why TomCat is not starting ?

    Was it working before ?

    Have you made any changes to the server.conf ?

     

    Hope it helps,

    Julien



  • 3.  Re: SPS TroubleShooting

    Posted Jul 14, 2017 05:00 AM

    Hello Julien,

     

    Yes, it was working before and suddenly stopped . There has been no change in server.conf file or to the full SPS configuration (no change at all) and nothing is present in the log as well /opt/app/CA/secure-proxy/sps/proxy-engine/logs/sag-error.log .

     

    Anything else i can do at my end to troubleshoot this more?

     

    Thank You

    Ankur Taneja



  • 4.  Re: SPS TroubleShooting
    Best Answer

    Posted Jul 14, 2017 05:03 AM

    Hi Ankur,

     

    Please delete sps.pid under tmp folder before starting the proxy engine. please stop the proxy engine and delete sps.pid from tmp folder and start the proxy engine.

     

    [root@malsi07-I198976 tmp]# ls -ltr sps.pid
    -rw-r--r--. 1 nobody nobody 6 Jul 13 18:33 sps.pid
    [root@malsi07-I198976 tmp]# pwd
    /opt/CA/secure-proxy/proxy-engine/tmp
    [root@malsi07-I198976 tmp]#

     

    Thanks,

    Sharan



  • 5.  Re: SPS TroubleShooting

    Posted Jul 14, 2017 05:16 AM

    Hello Sharana,

     

    Thanks, This helped and it's up now.



  • 6.  Re: SPS TroubleShooting

    Posted Feb 04, 2018 10:32 PM

    Can we know the cause of this and how to prevent such errors from happening ?



  • 7.  Re: SPS TroubleShooting

    Posted Feb 05, 2018 04:23 AM

    Hi,

     

    I feel SPS is not stopped properly, So might be the reason for  pid file is not deleted automatically.

     

    Thanks,

    Shankar