Postgres could not connect to server

Ruby on-RailsDatabasePostgresqlMacosHomebrew

Ruby on-Rails Problem Overview

After I did brew update and brew upgrade, my postgres got some problem. I tried to uninstall postgres and install it again, but it didn't work as well.

This is the error message. (I also got this error message when I try to do rake db:migrate)

$ psql
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"?

How can I solve it?

Mac version: Mountain lion.

homebrew version: 0.9.3

postgres version: psql (PostgreSQL) 9.2.1

And this is what I did:

$ brew uninstall postgresql
Uninstalling /usr/local/Cellar/postgresql/9.2.1...
$ brew uninstall postgresql
Uninstalling /usr/local/Cellar/postgresql/9.1.4...
$ psql --version
bash: /usr/local/bin/psql: No such file or directory
$ brew install postgresql
==> Downloading
Already downloaded: /Library/Caches/Homebrew/postgresql-9.2.1.tar.bz2
==> Summary
/usr/local/Cellar/postgresql/9.2.1: 2814 files, 38M, built in 2.7 minutes
$ initdb /usr/local/var/postgres -E utf8
The files belonging to this database system will be owned by user "laigary".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default text search configuration will be set to "english".

initdb: directory "/usr/local/var/postgres" exists but is not empty
If you want to create a new database system, either remove or empty
the directory "/usr/local/var/postgres" or run initdb
with an argument other than "/usr/local/var/postgres".
$ mkdir -p ~/Library/LaunchAgents
$ cp /usr/local/Cellar/postgresql/9.2.1/homebrew.mxcl.postgresql.plist ~/Library/LaunchAgents/
$ launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
homebrew.mxcl.postgresql: Already loaded
$ pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start
server starting
$ env ARCHFLAGS="-arch x86_64" gem install pg
Building native extensions.  This could take a while...
Successfully installed pg-0.14.1
1 gem installed
$ psql --version
psql (PostgreSQL) 9.2.1
$ psql
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"?

Now, after I reinstalled homebrew, when I use $ psql, it doesn't show any error message.

But I run rake db:migrate in my Rails app, it shows:

could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?

/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:1213:in `initialize'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:1213:in `new'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:1213:in `connect'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:329:in `initialize'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `new'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `postgresql_connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:309:in `new_connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:319:in `checkout_new_connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:241:in `block (2 levels) in checkout'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:236:in `loop'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:236:in `block in checkout'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:233:in `checkout'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:96:in `block in connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:95:in `connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:404:in `retrieve_connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:170:in `retrieve_connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:144:in `connection'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:107:in `rescue in create_database'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:51:in `create_database'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:40:in `block (3 levels) in <top (required)>'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:40:in `each'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:40:in `block (2 levels) in <top (required)>'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:205:in `call'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:205:in `block in execute'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:200:in `each'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:200:in `execute'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:158:in `block in invoke_with_call_chain'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:151:in `invoke_with_call_chain'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/task.rb:144:in `invoke'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:116:in `invoke_task'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:94:in `block (2 levels) in top_level'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:94:in `each'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:94:in `block in top_level'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:133:in `standard_exception_handling'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:88:in `top_level'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:66:in `block in run'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:133:in `standard_exception_handling'
/usr/local/Cellar/ruby/1.9.3-p327/lib/ruby/1.9.1/rake/application.rb:63:in `run'
/usr/local/bin/rake:32:in `<main>'
Couldn't create database for {"adapter"=>"postgresql", "encoding"=>"unicode", "database"=>"riy_development", "pool"=>5, "username"=>nil, "password"=>nil}

Finally I've found a solution.

sudo mkdir /var/pgsql_socket/
sudo ln -s /private/tmp/.s.PGSQL.5432 /var/pgsql_socket/

This solution is a little tricky, but it works. Hope anyone has a better solution


This works for me as well.

rm /usr/local/var/postgres/

Ruby on-Rails Solutions

Solution 1 - Ruby on-Rails

Had a similar problem; a pid file was blocking postgres from starting up. To fix it:

$ rm /usr/local/var/postgres/
$ brew services restart postgresql

and then all is well.


For Apple M1 (Big Sur) users, do this instead:

$ rm /opt/homebrew/var/postgres/
$ brew services restart postgresql

Solution 2 - Ruby on-Rails

This sometimes happens when brew does a postgres upgrade, causing the data files to become incompatible with the new server.

In my case, it happened when upgrading from 9.3 to 9.4.

OS X/Homebrew:

Try running postgres -D /usr/local/var/postgres -- it will give you a much more verbose output if postgres fails to start. Or open the log file at /usr/local/var/log/postgres.log (/opt/homebrew/var/log/postgres.log on Mac M1) and look for the line "FATAL: database files are incompatible with server"

In my case, running rm -rf /usr/local/var/postgres && initdb /usr/local/var/postgres -E utf8 removed my old databases and then reinitialized the postgres db schema. (THIS WILL DESTROY YOUR DATA)

Thanks to for that solution. Full instructions for a thorough re-install can be found here: How to completely uninstall and reinstall Homebrew Postgres - Test Double Blog (Again, if you're on an M1 Mac then substitute the /opt/homebrew/var path wherever it says /usr/local/var)

After regenerating my databases (with rake db:create) everything worked fine again.

Finally, links in the comments point to this possible solution that preserves your data, but I haven't tried it: How to upgrade PostgreSQL from version 9.6 to version 10.1 without losing data - Stack Overflow

Solution 3 - Ruby on-Rails

Found a solution that worked for me here:

You basically run the following command to manually start the server:

pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start

Solution 4 - Ruby on-Rails

If installing and uninstalling postgres with brew doesn't work for you, look at the logs of your postgresql installation or:

postgres -D /usr/local/var/postgres

if you see this kind of output:

LOG:  skipping missing configuration file "/usr/local/var/postgres/"
FATAL:  database files are incompatible with server
DETAIL:  The data directory was initialized by PostgreSQL version 9.4, which is not compatible with this version 9.6.1.

Then try the following:

rm -rf /usr/local/var/postgres && initdb /usr/local/var/postgres -E utf8

Then start the server:

pg_ctl -D /usr/local/var/postgres -l logfile start


Solution 5 - Ruby on-Rails

Upgrading the database works for me

brew postgresql-upgrade-database

Solution 6 - Ruby on-Rails

On Yosemite, if the pid file is blocking Postgres from starting and you have a launchctl daemon trying (and failing) to load the database daemons, then you'll need to unload the plist file:

$ launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist

Then remove the pid file

$ rm /usr/local/var/postgres/

Then reload the launchctl daemon

$ launchctl load ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist

Solution 7 - Ruby on-Rails

For anyone reading this and using, you may need host: localhost in your database.yml.

Solution 8 - Ruby on-Rails

brew services start postgres 

worked for me!

Solution 9 - Ruby on-Rails

The problem can also be attributed to a crashed process that left file behind. I do this and work's:

$ brew services stop postgresql
$ rm /usr/local/var/postgres/ # adjust path accordingly to your install
$ brew services start postgresql

Solution 10 - Ruby on-Rails

Check that the socket file exists.

$ ls -l /tmp/.s.PGSQL.5432
srwxrwxrwx  1 you  wheel  0 Nov 16 09:22 /tmp/.s.PGSQL.5432

If it doesn't then check your postgresql.conf for unix_socket_directory change.

$ grep unix_socket /usr/local/var/postgres/postgresql.conf
#unix_socket_directory = ''		# (change requires restart)
#unix_socket_group = ''			# (change requires restart)
#unix_socket_permissions = 0777		# begin with 0 to use octal notation

Solution 11 - Ruby on-Rails

The problem is because there is already a running service on the port 5432 and we cannot establish psql socket connection through this port.

I removed the socket file

rm -rf /tmp/.s.PGSQL.5432/

Then I reinitialized postgres services

postgres -D /usr/local/var/postgres

This worked for me.

Solution 12 - Ruby on-Rails

The most fool proof way around this is to do

brew reinstall postgresql

This will keep your user permission etc all intact and everything is reset to new. Works all the time !

Solution 13 - Ruby on-Rails

In my case, the trouble was caused by Mac OS updating. Upgrading PostgreSQL solved the issue.

# upgrade database version solved the trouble
$ brew postgresql-upgrade-database

However, this error is quite common and has multiple possible reasons, you shouldn’t fully rely on my solution above.

Solution 14 - Ruby on-Rails

This is actually what you are supposed to do:

you should instead look at /usr/local/var/postgres/

and then look at the first line of the file - this is the bad PID


ps aux | grep <PID>

for example:

ps aux | grep 12345

then do

kill <PID>

for example

kill 12345

Assuming it's still running

do not listen to the accepted answer it is bad and will corrupt your data!!!

Solution 15 - Ruby on-Rails

This worked for me . I didn't have to remove any file

brew postgresql-upgrade-database

Solution 16 - Ruby on-Rails

Changing postresql or database.yml config settings, changing $PATH, or creating symlinks were all unnecessary for me. All I needed to do was gem uninstall pg and then bundle (or gem install pg).

The issue was that the pg gem had been installed before homebrew postgres, so was picking up the settings from the version of postgres that comes with MacOS. Reinstalling it (and thus rebuilding the native extension) fixed the problem.

Solution 17 - Ruby on-Rails

This happened to me when I upgraded from 9.3.4 to 9.5 as the databases are incompatible without upgrading.

I used pg_upgrade as follows:

Stop postgres

$ brew services stop postgresql

Upgrade the databases:

$ pg_upgrade \
   -d /usr/local/var/postgres \
   -D /usr/local/var/postgres9.5 \
   -b /usr/local/Cellar/postgresql/9.3.4/bin/ \
   -B /usr/local/Cellar/postgresql/9.5.0/bin/ \

Archive the old databases:

 $ mv /usr/local/var/postgres /usr/local/var/
 $ mv /usr/local/var/postgres9.5 /usr/local/var/postgres

Restart postgres:

 $ brew services start postgresql

Updated Gems (for rails / active record) :

 $ gem uninstall pg
 $ gem uninstall activerecord-postgresql-adapter
 $ bundle install

Solution 18 - Ruby on-Rails

For MacOS BigSur, homebrew postgres:

  • rm /opt/homebrew/var/postgres/
  • brew services restart postgresql

Solution 19 - Ruby on-Rails

Psql option

-h hostname --host=hostname

: Specifies the host name of the machine on which the server is running. If the value begins with a slash, it is used as the directory for the Unix-domain socket.

$ grep "port\|unix_socket" /etc/postgresql/9.1/main/postgresql.conf
port = 5433				                            # (change requires restart)
unix_socket_directory = '/var/run/postgresql'		# (change requires resta

$ netstat -nalp | grep postgres
unix  2      [ ACC ]     STREAM     LISTENING     106753   4349/postgres       /tmp/.s.PGSQL.5432
unix  2      [ ACC ]     STREAM     LISTENING     10377 1031/postgres       /var/run/postgresql/.s.PGSQL.5433

Run psql with -host Option

$ psql -p 5433 -h /var/run/postgresql

No need to make a soft link

Solution 20 - Ruby on-Rails

If postgres was installed using homebrew, you can fix this by running:

brew link postgres

Solution 21 - Ruby on-Rails

This worked for me (as a mix of previous answers):

$ rm /usr/local/var/postgres/

$ pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start


Solution 22 - Ruby on-Rails

I faced the same problem for psql (PostgreSQL) 9.6.11.

what worked for me -

remove -- rm /usr/local/var/[email protected]/

restart postgres -- brew services restart [email protected]

If this also doesn't work then run -- sudo chmod 700 /usr/local/var/[email protected]

Solution 23 - Ruby on-Rails

Came across this issue too on MacOS Sierra and when we ran pg_ctl as described above we then had the following error pg_ctl: no database directory specified and environment variable PGDATA unset. So we followed the steps here which solved our issue, namely:

mkdir ~/.postgres

initdb ~/.postgres

pg_ctl -D ~/.postgres start

Solution 24 - Ruby on-Rails

I got same issue because I'm using a wrong Postgres's username in code. I logged into postgres psql -d postgres and enter \du to take role name and correct Postgres's username.

So when you guys face this issue, you guys need to make sure you're using correct Postgres username, password, hostname and database...

Hope this will help anyone

Solution 25 - Ruby on-Rails

If you shut down your system without quitting psql, postgres would not have removed some files.

I didn't find the file in the location usr/local/var/postgres

So I did the below: >### brew services start postgresql

The above command should let you start postgres

Solution 26 - Ruby on-Rails

So i stubled upon this after the rails db:create command. Setting up the environment in a macOS Catalina 10.15.3.

First thing that i checked was the flow that got me here. After ensuring that that all things had went smoothly and there was no error that might had escaped my mind i tried the most popular solutions from here but none of the seemed to work.

So far the only error i was seeing was the

$ psql 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"?

So i needed some more specific information about what was happening. Due to that reason i decided to look at the postgres logfile which is located at


So after opening the log i saw this error

LOG: starting PostgreSQL 12.2 on x86_64-apple-darwin19.3.0, compiled by Apple clang version 11.0.0 (clang-1100.0.33.17), 64-bit LOG: could not translate host name "localhost", service "5432" to address: nodename nor servname provided, or not known WARNING: could not create listen socket for "localhost" FATAL: could not create any TCP/IP sockets LOG: database system is shut down

So this is a bit more explanatory and specific. The problem is something about that PostgreSQL cannot "see" and resolve the localhost server.

So next thing i did was to check the /etc/hosts file whose default contents should look like this:

# Host Database
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##   localhost broadcasthost
::1          localhost 

After comparing the above with mine i saw that in mine this line was different and commented (!).

#::1             localhost

So i removed the # symbol in front of the line saved the file and re run the

rails db:create 

and the database was succesfully initiated.

Solution 27 - Ruby on-Rails

I ran into this issue after trying to restore/drop/create a db while other processes were accessing them. MacOSX/Homebrew fix was:

  1. close all other accessing processes rails server, rails console, guard, etc...
  2. load/unload using the commands found in brew info postgres
  3. run restore/drop/create from before

Solution 28 - Ruby on-Rails

FWIW this happened to me today, but what happened was that I was running Ubuntu updates at the time, which were likely updating Postgres. Once the update completed, I was able to connect without a hitch.

For completeness' sake, I was trying to retrieve records from the database from a Rails console:

development (main):0 > a = MyModel.find 73694
PG::ConnectionBad: 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"?

Solution 29 - Ruby on-Rails

It looks like your psql doesn't run. You should run it before connect. You can do that using for Mac OS only. (Download and install this app Open the app, and you have a PostgreSQL server ready and awaiting new connections. Close the app, and the server shuts down. You also can find this info here Hope this will help you.

Solution 30 - Ruby on-Rails

It is because a previous server a still running, try closing everything down and re-running your application.

Solution 31 - Ruby on-Rails

For those who use this command and doesn't work or the file is not there and are using Ruby on Rails

> rm /usr/local/var/postgres/

Or any other command and just keep on failing.

I solved this problem uninstalling with Brew. I had to uninstall with brew 2 times, because at the first uninstall there will remain another version of postgresql, with the second uninstall the process will be completed.

Install postgresql with Brew

Then drop, create and migrate the data bases of the project

(Don't forget to start the postgresql server)

Solution 32 - Ruby on-Rails

¿Are you recently changed the pg_hba.conf? if you did just check for any typo in:

"local" is for Unix domain socket connections only

local all all password

IPv4 local connections:

host all all password

IPv6 local connections:

host all all ::1/128 password

Sometimes a simple mistake can give us a headache. I hope this help and sorry if my english is no good at all.

Solution 33 - Ruby on-Rails

This happens when postgres server is not running. Steps to properly install Postgres via Homebrew on MAC :

  1. brew install postgres

  2. initdb /Users/<username>/db -E utf8 [This initializes postgres to use the given directory as the database directory. Normally it is not adviced to use the user directory for database storage. Edit sudoers file to add initdb and similar commands and then run initdb on /usr/local/var/postgres]

  3. pg_ctl -D /Users/<username>/db -l logfile start [After getting success with step 2 it will prompt to run step 3. This command manually starts the server.]

Solution 34 - Ruby on-Rails

I got this same error. Turns out postgres just wasn't running at all (it is usually always running in the background, but for whatever reason it wasn't today).

If this is the case, just type postgres in the command line of your project directory

Solution 35 - Ruby on-Rails

After a tremendous amount of back and forth, it really came down to the pg gem version I was using. On mavericks, pg version 0.15.1 would not connect to port 5432 but version 0.17.1 works just fine - very odd.

Solution 36 - Ruby on-Rails

For me it was an apache upgrade that caused the problem. I could still run psql in console or call db directly from kdevelop. Also it worked to add "host=localhost" to connection string.

BUT the real problem was that apache had changed to private tmp.

Solution: Update /usr/lib/systemd/system/apache2.service and change PrivateTmp=true to PrivateTmp=false.

I am working on OpenSuse OS, but I guess that something similar could happen on Mac.

Solution 37 - Ruby on-Rails

Had the same problem. Upgrading DB did the trick! postgresql-upgrade-database

Solution 38 - Ruby on-Rails

I simply restarted postgres:

brew services restart postgresql

There was no need to remove

Solution 39 - Ruby on-Rails

This worked for me: rm /usr/local/var/postgres/

Solution 40 - Ruby on-Rails

If you're on a M1 mac and you installed postgresql with the M1 version of homebrew, this shloud work:

$ rm /opt/homebrew/var/postgres/
$ brew services restart postgresql

Solution 41 - Ruby on-Rails

I found that after installing the latest patch to Postgres 9.6, all my executables (postgres, psql, pg_dump, pg_restore etc) got dropped and I had to relink them. Fortunately Homebrew can do this for you:

brew link --force postgresql # (or in my case, `[email protected]`)

Solution 42 - Ruby on-Rails


sudo systemctl start postgresql@12-main

Here my postgresql version is 12.

Solution 43 - Ruby on-Rails

I was working on a project on my MacBook M1 (Air) and had opened some tabs and suddenly my Postgres server stopped and starting giving the below error :

psql: could not connect to server: Connection failed Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"

I tried many solutions like ;

  1. updating brew and Postgres.
  2. restarting servers.
  3. Tried to kill the process from the command line.

But sadly , nothing worked for me.

And Finally, I thought of restarting my mac . And to my surprise, the postgres server started working pretty much fine the way it used to do before. I think there must have been some problem with the Postgres directories. But I am glad that , it worked.

I recommend you, to go through the above-mentioned options first before restarting.


Solution 44 - Ruby on-Rails

For Mac OS Catalina, this worked

$ rm /usr/local/var/postgres/
$ brew services restart postgresql

Solution 45 - Ruby on-Rails

For macOS Monterey, I used brew services restart postgresql.

brew install postgresql
createdb mydb
createdb: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file or directory
	Is the server running locally and accepting connections on that socket?

brew services restart PostgreSQL
==> Successfully started `postgresql` (label: homebrew.mxcl

Solution 46 - Ruby on-Rails

The Cause

Lion comes with a version of postgres already installed and uses those binaries by default. In general you can get around this by using the full path to the homebrew postgres binaries but there may be still issues with other programs.

The Solution

curl | sh


Solution 47 - Ruby on-Rails

Just two steps to run the database after the Installation (Before that ensure your logged as postgres user)

> # Installed-Dirs/bin/postmaster -D Installed-Dirs/pgsql/data

For an example:

[postgres@localhost bin]$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data

Step-2 : Run psql from the Installed path (To check where you installed '#which postgres' will use to find out the installed location)

[postgres@localhost bin]$ psql 

Solution 48 - Ruby on-Rails

I used the Bitnami stack and installed as non-root user psql. On using psql I did receive the mentioned error.

Turns out, there are 2 versions of psql

  1. a root level psql prepackaged in the linux distro. This points to /usr/bin/psql
  2. a non-root level psql installed by the Bitnami stack. This points to /bitnami/postgresql/postgresql/bin/psql

You might want to change the alias of the psql, so that it points to the non-root user.

alias psql='/bitnami/postgresql/postgresql/bin/psql'

The above worked for me on doing psql -U postgres

Solution 49 - Ruby on-Rails

The data directory contains an old file / The data directory contains an unreadable file PostgreSQL puts a file named in the data directory to store the process id of the PostgreSQL server process. If PostgreSQL crashes, this file can contain an old pid that confuses PostgreSQL. You can fix this issue by deleting the file. However, you must make sure that PostgreSQL is really not running. Open Activity Monitor and make sure that there are no processes named ‘postgres’ or ‘postmaster’.

If you delete the file while PostgreSQL is running, bad things will happen.


Solution 50 - Ruby on-Rails

If you are facing the issue while upgrading Postgres (or after upgrading), please follow the steps mentioned here to safely transfer data between versions, which will resolve the issue:

Upgrade PostgreSQL 9.6.5 to 10.0 using Homebrew (macOS)

Solution 51 - Ruby on-Rails

One of the cause will be make sure the size of the disk is not full execute the command postmaster -D path of the postgres

Solution 52 - Ruby on-Rails

For us, we had to define localhost in the psql command like the following:

psql -h localhost -U postgres

Not sure why the -h doesn't default to localhost...

Solution 53 - Ruby on-Rails

I had to fix the permissions for a directory:

sudo chmod 0750 /usr/local/var/postgres

Solution 54 - Ruby on-Rails

What worked for me I had 2 versions of PostgreSQL while running brew services list

Name           Status  User           Plist
consul         stopped                
docker-machine stopped                
mysql          stopped                
postgresql     started homebrew.mxcl.postgresql.plist
postgresql@9.6 stopped                
redis          stopped                
runit          stopped                
unbound        stopped                
vault          stopped 

and just launched the other version brew services start [email protected]

Solution 55 - Ruby on-Rails

In my case, I was running other project using docker-compose and I had to stop postgresql with sudo service postgresql stop && docker-compose up -d postgres && docker-compose up rails

To fix this error in my new project, I just had to run: sudo service postgresql restart and then it just fixed it.

Solution 56 - Ruby on-Rails

I have macOS Catalina (10.15.6) and PostgreSQL 12.

When I run brew services start postgresql, brew said it start PostgreSQL without problem, but it does not show when I get ps auxw | grep post.

To solve it, I install from this link, and install and press Init button.

It will find your databases and show it to you.

Solution 57 - Ruby on-Rails

MacOS Big Sur seemed to renamed the Application\ Support folder to ApplicationSupport. So the updated Path would be:

(or "/var-<YOUR PG VERSION>")

Solution 58 - Ruby on-Rails

This is how it fixed this error for me on my MacOS (I had used homebrew to install postgres) :

> cd /opt/homebrew/var
> rm -rf postgres
> initdb ./postgres -E utf8
> pg_ctl -D ./postgres -l logfile start
> rm postgres/
> brew services restart postgresql
> createdb $(whoami)

Solution 59 - Ruby on-Rails

Quickest solution which worked for me:

  1. Find the postgres process that's running already in the port configured for postgres
lsof -i:5432
  1. Find the process id of postgres and kill them
kill -9 <pid>

Solution 60 - Ruby on-Rails

Solution for MacOS M1 Monterey

rm /opt/homebrew/var/postgres/
brew services restart postgresql


All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionGary LaiView Question on Stackoverflow
Solution 1 - Ruby on-RailsjonathanpbergerView Answer on Stackoverflow
Solution 2 - Ruby on-RailsFreePenderView Answer on Stackoverflow
Solution 3 - Ruby on-RailsMosab SasiView Answer on Stackoverflow
Solution 4 - Ruby on-RailssvelandiagView Answer on Stackoverflow
Solution 5 - Ruby on-RailsTomer GView Answer on Stackoverflow
Solution 6 - Ruby on-RailsRyan AtallahView Answer on Stackoverflow
Solution 7 - Ruby on-RailsDavid WinieckiView Answer on Stackoverflow
Solution 8 - Ruby on-RailsrldView Answer on Stackoverflow
Solution 9 - Ruby on-RailsrldView Answer on Stackoverflow
Solution 10 - Ruby on-RailsjrwrenView Answer on Stackoverflow
Solution 11 - Ruby on-RailsAbdullah GürsuView Answer on Stackoverflow
Solution 12 - Ruby on-RailsattaboyabhiproView Answer on Stackoverflow
Solution 13 - Ruby on-RailsHany Moh.View Answer on Stackoverflow
Solution 14 - Ruby on-Railsuser1596067View Answer on Stackoverflow
Solution 15 - Ruby on-RailsSuneet SrivastavaView Answer on Stackoverflow
Solution 16 - Ruby on-RailsJohnView Answer on Stackoverflow
Solution 17 - Ruby on-RailsstujoView Answer on Stackoverflow
Solution 18 - Ruby on-RailsCarlos GómezView Answer on Stackoverflow
Solution 19 - Ruby on-RailsJuno ChooView Answer on Stackoverflow
Solution 20 - Ruby on-RailsCl LocalView Answer on Stackoverflow
Solution 21 - Ruby on-RailsRamon DiogoView Answer on Stackoverflow
Solution 22 - Ruby on-RailsPiyush SawariaView Answer on Stackoverflow
Solution 23 - Ruby on-RailsAustinView Answer on Stackoverflow
Solution 24 - Ruby on-RailsBrilliant-DucNView Answer on Stackoverflow
Solution 25 - Ruby on-RailsAshwinView Answer on Stackoverflow
Solution 26 - Ruby on-RailsdimivrnView Answer on Stackoverflow
Solution 27 - Ruby on-RailsTomFuertesView Answer on Stackoverflow
Solution 28 - Ruby on-RailsRuy DiazView Answer on Stackoverflow
Solution 29 - Ruby on-RailslisykView Answer on Stackoverflow
Solution 30 - Ruby on-RailsKamara JōbView Answer on Stackoverflow
Solution 31 - Ruby on-RailsEsteban EcheverryView Answer on Stackoverflow
Solution 32 - Ruby on-RailsSergio ZapataView Answer on Stackoverflow
Solution 33 - Ruby on-RailsSouvik DasView Answer on Stackoverflow
Solution 34 - Ruby on-RailsBenjamin DunphyView Answer on Stackoverflow
Solution 35 - Ruby on-RailsAnthonyView Answer on Stackoverflow
Solution 36 - Ruby on-RailskaahView Answer on Stackoverflow
Solution 37 - Ruby on-RailsannaView Answer on Stackoverflow
Solution 38 - Ruby on-RailsSajad RastegarView Answer on Stackoverflow
Solution 39 - Ruby on-RailsThomas Van HolderView Answer on Stackoverflow
Solution 40 - Ruby on-RailsLéonard HenriquezView Answer on Stackoverflow
Solution 41 - Ruby on-RailsPJSCopelandView Answer on Stackoverflow
Solution 42 - Ruby on-RailsShifaTView Answer on Stackoverflow
Solution 43 - Ruby on-RailsKirandeep KaurView Answer on Stackoverflow
Solution 44 - Ruby on-RailsSuneet SrivastavaView Answer on Stackoverflow
Solution 45 - Ruby on-RailsshinView Answer on Stackoverflow
Solution 46 - Ruby on-RailsSocoMView Answer on Stackoverflow
Solution 47 - Ruby on-RailsJayakumar Jai J ElumalaiView Answer on Stackoverflow
Solution 48 - Ruby on-RailsThyagView Answer on Stackoverflow
Solution 49 - Ruby on-RailsSelvView Answer on Stackoverflow
Solution 50 - Ruby on-RailsTᴀʀᴇǫ MᴀʜᴍᴏᴏᴅView Answer on Stackoverflow
Solution 51 - Ruby on-RailsAjay TakurView Answer on Stackoverflow
Solution 52 - Ruby on-RailshookncView Answer on Stackoverflow
Solution 53 - Ruby on-RailsDavid MoralesView Answer on Stackoverflow
Solution 54 - Ruby on-RailsJulius KvedarasView Answer on Stackoverflow
Solution 55 - Ruby on-RailsAnyelo PetitView Answer on Stackoverflow
Solution 56 - Ruby on-RailsEsmaeilView Answer on Stackoverflow
Solution 57 - Ruby on-RailsKarl AdlerView Answer on Stackoverflow
Solution 58 - Ruby on-RailsSaeed HadikhanlooView Answer on Stackoverflow
Solution 59 - Ruby on-RailsArunSelvam P MView Answer on Stackoverflow
Solution 60 - Ruby on-RailsKhoi NgoView Answer on Stackoverflow