By dbtoomey
This morning, all the sites were down and I tried to ssh into the server. After failing to log in, I accessed the server through the DO Console and saw a memory overflow error which apparently led to a segfault. I felt I had no choice but to roll back to a prior snapshot. I rebooted PostgreSQL, but I kept getting something like the following:
shutdown [FAIL]
start {OK}
After each Postgres reboot, I get the same as above. When I check to see if Postgres is running, it shows that it is running.
I switched to the postgres user, and $psql and threw this error:
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
I added the localhost path to the /.bash_config and now I have error about not being able to access with the following errors:
psql: could not connect to server: Connection refused
Is the server running on host [local IP adress] and accepting
TCP/IP connections on port 5432?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
On the server, can you run:
sudo netstat -plunt
If Postgres is running and listening on port 5432, you should see a line like:
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1295/postgres
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.