Postgres DB not starting on Mac OSX: ERROR says: connections on Unix domain socket [closed] - macos

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I ve installed Postgresql and then ran a bunch of rails apps on my local Mac OSX Mountain Lion and created databases etc. Today after a while when I launched pgAdminIII and tried to launch a database server I got this error:
A quick google showed this post. More browsing pointed to the fact that there might be some sort of postmaster.pid file lying around that might be the root cause of this. If I delete that things would be fine.
However, before I go deleting stuff on my computer I wanted to make sure Im debugging this in a systematic way which would not result in more problems.
Somewhere I read that before deleting that file, I need to run this command:
ps auxw | grep post
If I get no results then, its OK to delete the file. Else not. Well, I got this result of that command:
AM 476 0.0 0.0 2423356 184 s000 R+ 9:28pm 0:00.00 grep post
So now of course Im throughly confused.
So what should I do?
Here is part of my postgres server error log:
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 171) running in data directory "/usr/local/var/postgres"?
Postgresql is still not running, still get the same error and nothing has changed. Im too chicken to delete things without checking on SO.
Could some of you experts please guide a noob.
Thanks

Answer 1

I had the same problem today on Mac Sierra. In Mac Sierra you can find postmaster.pid inside /Users/<user_name>/Library/Application Support/Postgres/var-9.6. Delete postmaster.pid and problem will be fixed.

Answer 2

This can happen if the database did not shut down correctly. To fix it simply delete the postmaster.pid file. The location differs based on your OS:
MacOS:
rm /Users/<user_name>/Library/Application\ Support/Postgres/var-9.6/postmaster.pid
or using Postgres.app:
rm /Users/<user>/Library/Application\ Support/Postgres/var-10/postmaster.pid
Linux:
rm /usr/local/var/postgres/postmaster.pid

Answer 3

I have the database working now.
Here are the steps I took:
I rebooted my computer
I opened the terminal and ran cd /
Then I did ls -la
Ensured that I could get to MackintoshHD/usr/local/var/postgres
Then did ls -la
Here I saw the postmaster.pid file
I ran this command cp postmaster.pid ~/Desktop which copied the
file to my desktop.I like to do this if I am deleting files. If
something does wrong i can put it back
Then I ran this command to remove the file from the postgres
directory rm -r postmaster.pid
I went to my pgadmin3 gui and fired it up. and Voila it worked :)
Thanks to #Craig Ringer for his help

Answer 4

I'm using Postgres.app, and the below worked for me:
I entered the commands into my terminal below, locating the Postgres folder beforehand and not using "justin".
$declare -x PGDATA="/Users/justin/Library/Application Support/Postgres/var-9.4"
$pg_ctl restart -m immediate
As Justin explains in his post, the output after this was:
waiting for server to shut down……………………………………………………… failed pg_ctl:
server does not shut down
After entering the command again:
$pg_ctl restart -m immediate
It worked and I got this message:
pg_ctl: old server process (PID: 373) seems to be gone starting server
anyway server starting LOG: database system was interrupted; last
known up at 2015-07-28 18:15:26 PDT LOG: database system was not
properly shut down; automatic recovery in progress LOG: record with
zero length at 0/4F0F7A8 LOG: redo is not required LOG: database
system is ready to accept connections LOG: autovacuum launcher started
Source