psql could not connect to server No such file or directory Mac OS X

Question

Upon restarting my Mac I got the dreaded Postgres error   psql  could not connect to server  No such file or directory  Is the server running locally and accepting  connections on Unix domain socket   var run postgresql  s PGSQL 5432     The reason this happened is because my macbook froze completely due to an unrelated issue and I had to do a hard reboot using the power button  After rebooting I couldn t start Postgres because of this error

User · Answer

I removed  usr lib from the LD LIBRARY PATH and it worked  I was working in dockerfile postgres alpine

User · Answer

Hello world   The best but strange way for me was to do next things  1  Download postgres93 app or other version  Add this app into  Applications  folder   2  Add a row  command  into the file  bash profile  which is in my home directory     export PATH  Applications Postgres93 app Contents MacOS bin   PATH It s a PATH to psql from Postgres93 app  The row  command  runs every time console is started   3  Launch Postgres93 app from  Applications  folder  It starts a local server  port is  5432  and host is  localhost     4  After all of this manipulations I was glad to run   createuser -SRDP user name and other commands and to see that it worked  Postgres93 app can be made to run every time your system starts   5  Also if you wanna see your databases graphically you should install PG Commander app  It s good way to see your postgres DB as pretty data-tables  Of  course  it s helpful only for local server  I will be glad if this instructions help others who has faced with this problem

User · Answer

Go to  var log  and run cat postgres log Here you will find the reason for the failure of postgres  If it is a smart shut down then probably your icu4c version  C   library for Unicode  is not proper which is linked with postgres  So run the following commands   brew upgrade brew cleanup This should work

User · Answer

SUPER NEWBIE ALERT  I m just learning web development and the particular tutorial I was following mentioned I have to install Postgres but didn t actually mention I have to run it as well    Once I opened the Postgres application everything was fine and dandy

User · Answer

My problem ended up being that I was using Gas Mask  a hosts file manager for Mac   and I didn t have an entry for localhost in the hosts file I was using   I added   127 0 0 1 localhost   And that resolved my problem

User · Answer

None of the above worked for me  I had to reinstall Postgres the following way     Uninstall postgresql with brew   brew uninstall postgresql brew doctor  fix whatever is here  brew cleanup Remove all Postgres folders      rm -r  usr local var postgres rm -r  Users  lt username gt  Library Application  Support Postgres  Reinstall postgresql with brew   brew install postgresql Start server   brew services start postgresql You should now have to create your databases     createdb

User · Answer

Jagdish Barabari s answer gave me the clue I needed to resolve this  Turns out there were two versions of postgresql installed while only one was running  Purging all postgresql files and reinstalling the latest version resolved this issue for me

User · Answer

Another class of reasons why this can happen is due to Postgres version updates  You can confirm this is a problem by looking at the postgres logs  tail -n 10000  usr local var log postgres log  and seeing entries like  DETAIL   The data directory was initialized by PostgreSQL version 12  which is not compatible with this version 13 0   In this case  assuming you are on Mac and using brew   just run  brew postgresql-upgrade-database   Oddly  it failed on run 1 and worked on run 2  so try it twice before giving up

User · Answer

I m not entirely sure why  but my Postgres installation got a little bit screwed and some files were deleted resulting in the error OP is showing    Despite the fact that I am able to run commands like brew service retart postgres and see the proper messages  this error persisted    I went through the postgres documentation and found that my file  usr local var postgres was totally empty  So I ran the following    initdb  usr local var postgres   It seems some configurations took place with that command    Then it asked me to run this   postgres -D  usr local var postgres   And that told me a postmaster pid file already exists    I just needed to know if brew would be able to pick up the configs I just ran  so I tested it out    ls  usr local var postgres   That showed me a postmaster pid file  I then did brew services stop postgresql  and the postmaster pid file disappeared  Then I did brew services start postgresql  and VIOLA  the file reappeared    Then I went ahead and ran my app  which did in fact find the server  however my databases seem to be gone    Although I know that they may not be gone at all - the new initialization I did may have created a new data area  and the old one isn t being pointed to  I d have to look at where that s at and point it back over or just create my databases again    Hope this helps  Reading the postgres docs helped me a lot  I hate reading answers that are like  Paste this in it works   because I don t know what the hell is happening and why

User · Answer

This problema has many sources  and thus many answers  I ve experienced each one of them   1  If you have a crash of some sort  removing the  usr local var postgres postmaster pid file is probably required as postgres may not have handled it properly   But ensure that no process is running   2  Craig Ringer has pointed out in other posts that Apple s bundling of postgreSQL leads to pg gem installation issues  Setting the PATH environment variable is a solution   3  Another solution  is to uninstall and reinstall the gem   A brew update may be necessary as well   If you stumble upon this post  if you can pinpoint one of the sources  you ll save time

User · Answer

The following commands helped me out  The issue was with the PostgreSQL data version  Once upgraded  it started working fine for me  brew upgrade postgresql brew postgresql-upgrade-database brew services restart postgresql

User · Answer

Here is my way   launchctl unload   Library LaunchAgents homebrew mxcl postgresql plist rm  usr local var postgres postmaster pid launchctl load   Library LaunchAgents homebrew mxcl postgresql plist

User · Answer

if your postmaster pid is gone and you can t restart or anything  do this   pg ctl -D  usr local var postgres -l  usr local var postgres server log start  as explained here initially

User · Answer

For me  the solution was simply restart my computer   I first tried restarting with Brew services and when that didn t work  restarting seemed like the next best option to try before looking into some of the more involved solutions   Everything worked as it should after

User · Answer

If you re on macOS and installed postgres via homebrew  try restarting it with   brew services restart postgresql   If you re on Ubuntu  you can restart it with either one of these commands   sudo service postgresql restart  sudo  etc init d postgresql restart

User · Answer

Maybe this is unrelated but a similar error appears when you upgrade postgres to a major version using brew  using brew info postgresql found out this that helped   To migrate existing data from a previous major version of PostgreSQL run  brew postgresql-upgrade-database

User · Answer

I just got the same issue as I have put my machine ubuntu  for update and got below error      could not connect to server  No such file or directory Is the server   running locally and accepting connections on Unix domain socket     var run postgresql  s PGSQL 5432     After completing the updating process when I restart my system error gone  And its work like charm as before   I guess this was happened as pg was updating and another process started

User · Answer

WARNING  If you delete postmaster pid without making sure there are really no postgres processes running you  could permanently corrupt your database   PostgreSQL should delete it automatically if the postmaster has exited     SOLUTION  This fixed the issue--I deleted this file  and then everything worked    usr local var postgres postmaster pid   --  and here is how I figured out why this needed to be deleted     I used the following command to see if there were any PG processes running  for me there were none  I couldn t even start the PG server   ps auxw   grep post  I searched for the file  s PGSQL 5432 that was in the error message above  i used the following command   sudo find   -name  s PGSQL 5432 -ls   this didn t show anything after searching my whole computer so the file didn t exist  but obviously psql  wanted it to  or  thought it was there   I took a look at my server logs and saw the following error   cat  usr local var postgres server log   at the end of the server log I see the following error   FATAL   pre-existing shared memory block  key 5432001  ID 65538  is still in use HINT   If you re sure there are no old server processes still running  remove the shared memory block or just delete the file  postmaster pid    Following the advice in the error message  I deleted the postmaster pid file in the same directory as server log  This resolved the issue and I was able to restart    So  it seems that my macbook freezing and being hard-rebooted caused Postgres to think that it s processes were still running even after reboot  Deleting this file resolved  Hope this helps others  Lots of people have similar issues but most the answers had to do with file permissions  whereas in my case things were different

User · Answer

I was facing a similar issue here I solved this issue as below   Actually the postgres process is dead  to see the status of postgres run the following command   sudo  etc init d postgres status   It will says the process is dead just start the process  sudo  etc init d postgres start

User · Answer

I ve had to look up this post several times to solve this issue  There s another fix  which will also applies to similar issues with other running programs   I just discovered you can use the following two commands     top   This will show all the currently running actions with their pid numbers  When you find postgres and the associated pid    kill pid number

User · Answer

I faced the same problem for psql  PostgreSQL  9 6 11  what worked for me - remove postmaster pid  --  rm  usr local var postgresql 9 6 postmaster pid restart postgres  -- brew services restart postgresql 9 6 If postmaster pid doesn t exist or the above process doesn t work then run -- sudo chmod 700   usr local var postgresql 9 6

User · Answer

The causes of this error are many so first locate your log file and check it for clues  It might be at  usr local var log postgres log or  usr local var postgres server log or possibly elsewhere  If you installed with Homebrew you can find the location in   Library LaunchAgents homebrew mxcl postgresql plist

User · Answer

This happened to me after my Mac  High Sierra  froze and I had to manually restart it  press and hold the power button   All I had to do to fix it was  do a clean restart

User · Answer

I had the same issue  Most of the times  the problem is the fact that there s a leftover file   usr local var postgres postmaster pid  which works for most people  but my case was different - I tried googling this issue for last 3 hours  uninstalled postresql on OSX through brew  purged the database  nothing worked   Finally  I noticed that I had an issue with brew that whenever I tried to install anything  it popped   Error  Permission denied   rb sysopen -  private tmp github api       or something like it at the end of an install   I simply did sudo chmod -R 777  private tmp and it finally works   I m writing this down because this might be a solution for someone else

[macos] psql: could not connect to server: No such file or directory (Mac OS X)

Examples related to macos

Examples related to postgresql