Edge private cloud Not running (DEAD) [edge-postgres-server edge-qpid-server]

[Roaa]

Edge for private cloud version 4.19.06.00:

• edge-qpid-server
•  edge-postgres-server 

by some reason it is not running and we cannot start it.

When we run start command it shows UP,  but status shows Not running (DEAD).

edge-qpid-server log:

2022-01-04 12:19:53,314  main ERROR SERVICES.WEB - WebServiceImpl.start() : Error in starting WebService - unable to start container - Halting the boot up process!!

java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8083

Now I can't start them anymore

Please support me

Thanks

[dchiesa1]

Sorry you're having trouble. 

I'd suggest scanning the log files for those processes to determine what lead to them stopping.  If that is not something you feel you can do on your own, then I guess you should contact Apigee support. But be aware that 4.19.06 is out of support. The support team may ask you to upgrade before helping you.  😢😢😢

[Roaa]

Thanks for your cooperation ..

can you guide me which log files should I look into to determine the stopping reason ?

when I move to  cd /opt/apigee/var/log/edge-qpid-server/logs

which file like ( system.log or edge-qpid-server.log or something else )

[dchiesa1]

I would start with system.log 

That is the most likely place to look.  

[Roaa]

After scanning the log file for the qpid server I noticed the problem:

9.06-0.0.20115/webapps/api/,STARTING}{/opt/apigee/edge-qpid-server-4.19.06-0.0.20115/webapps/api} has uncovered http methods for path: /

2022-01-05 09:12:06,637  main INFO  o.e.j.s.h.ContextHandler - ContextHandler.doStart() : Started o.e.j.w.WebAppContext@2d35442b{Welcome,/,file:///opt/apigee/edge-qpid-server-4.19.06-0.0.20115/webapps/api/,AVAILABLE}{/opt/apigee/edge-qpid-server-4.19.06-0.0.20115/webapps/api}

2022-01-05 09:12:06,644  main ERROR SERVICES.WEB - WebServiceImpl.start() : Error in starting WebService - unable to start container - Halting the boot up process!!

java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8083

by using this command to check which process using port (8083):

netstat -na | grep 8083

I found one process listen to it 

Any suggestions? 

Thank you 

[dchiesa1 · Accepted solution]

Yes!  Stop the process. Or choose another port. 

You may want to speak with Apigee support ! 

[Roaa]

It would be better if we speak to Apigee support but our version out of support

[Roaa]

yes you are right after killing the process we could re-run it again 
thanks !

[dchiesa1]

Glad to hear you solved the problem!