The following two services are down in chef-server.
When i try restarting the service it will start and when I check back the status again it will be down again.
----------------------------------------logs of postgresql-------------------------------------------
2016-11-24_09:18:56.53277 WARNING: could not create listen socket for "0.0.0.0"
2016-11-24_09:18:56.53328 FATAL: could not create any TCP/IP sockets
2016-11-24_09:18:57.58564 LOG: could not bind IPv4 socket: Address already in use
2016-11-24_09:18:57.58568 HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2016-11-24_09:18:57.58570 WARNING: could not create listen socket for "0.0.0.0"
2016-11-24_09:18:57.58571 FATAL: could not create any TCP/IP sockets
2016-11-24_09:18:58.65030 LOG: could not bind IPv4 socket: Address already in use
2016-11-24_09:18:58.65033 HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
Seems postgres can’t start because something is using the port 5432, you can have a look at what with netstat -anpe - grep ':5432'.
Either it’s a dead process,or you have another postgres on the system using the port, a reboot should clean it up for the first case, for the later, you’re on your own, mixing chef-server with something else is not recommended unless you know what you’re doing.