Is the server running on host localhost 1 and accepting TCP IP connections on port 5432

Question

Before anything  please note that I have found several similar questions on Stack Overflow and articles all over the web  but none of those helped me fix my issue    PG Error could not connect to server  Connection refused Is the server running on port 5432  PG  ConnectionBad - could not connect to server  Connection refused psql  could not connect to server  Connection refused   Now  here is the issue    I have a Rails app that works like a charm  With my collaborator  we use GitHub to work together  We have a master and an mvp branches  I recently updated my git version with Homebrew  Mac   We use Foreman to start our app locally    Now  when I try to launch the app locally  I get the following error   PG  ConnectionBad at   could not connect to server  Connection refused     Is the server running on host  localhost     1  and accepting     TCP IP connections on port 5432  could not connect to server  Connection refused     Is the server running on host  localhost   127 0 0 1  and accepting     TCP IP connections on port 5432    I tried to reboot my computers several times   I also checked the content of  usr local var postgres   PG VERSION      pg dynshmem     pg multixact    pg snapshots    pg tblspc       postgresql conf base            pg hba conf     pg notify       pg stat         pg twophase     postmaster opts global          pg ident conf   pg replslot     pg stat tmp     pg xlog         server log pg clog         pg logical      pg serial       pg subtrans     postgresql auto conf   As you can see  there is no postmaster pid file in there   Any idea how I could fix this

User · Answer

If you want to restart Postgresql on Linux  then you have to use the following command    etc init d postgresql restart

User · Answer

I resolved the issue via this command  pg ctl -D  usr local var postgres start   At times  you might get this error  pg ctl  another server might be running  trying to start server anyway   So  try running the following command and then run the first command given above   pg ctl -D  usr local var postgres stop

User · Answer

Most likely it s because your system shutdown unexpectedly  Try  postgres -D  usr local var postgres   You might see   FATAL   lock file  postmaster pid  already exists HINT   Is another postmaster  PID 449  running in data directory   usr local var postgres      Then try  kill -9 PID   example  kill -9 419   And it should start postgres normally

User · Answer

run  postgres -D  usr local var postgres and you should see something like    FATAL   lock file  postmaster pid  already exists  HINT    Is another postmaster  PID 379  running in data directory   usr local var postgres     Then run kill -9 PID in HINT  And you should be good to go

User · Answer

Step 1  cd  etc postgresql 12 main   open file named postgresql conf sudo nano postgresql conf  add this line to that file listen addresses        then open file named pg hba conf sudo nano pg hba conf  and add this line to that file host  all  all 0 0 0 0 0 md5  It allows access to all databases for all users with an encrypted password restart your server sudo  etc init d postgresql restart

User · Answer

I encountered a similar problem when I was trying to connect my Django application to PostgreSQL database  I wrote my Dockerfile with instructions to setup the Django project followed by instructions to install PostgreSQL and run Django server in my docker-compose yml  I defined two services in my docker-compose-yml  services    postgres      image   quot postgres latest quot      environment        - POSTGRES DB abc       - POSTGRES USER abc       - POSTGRES PASSWORD abc     volumes        - pg data  var lib postgresql data    django      build        command  python  code manage py runserver 0 0 0 0 8004     volumes        -    app     ports        - 8004 8004     depends on        - postgres   Unfortunately whenever I used to run docker-compose up then same err  used to pop up  And this is how my database was defined in Django settings py  DATABASES          default              ENGINE    django db backends postgresql            NAME    abc            USER    abc            PASSWORD    abc            HOST    127 0 0 1            PORT    5432            OPTIONS                  client encoding    UTF8                        So  In the end I made use of docker-compose networking which means if I change the host of my database to postgres which is defined as a service in docker-compose yml will do the wonders  So  Replacing  HOST    127 0 0 1    gt     HOST    postgres  did wonders for me  After replacement this is how your Database config in settings py will look like  DATABASES              default                  ENGINE    django db backends postgresql                NAME    abc                USER    abc                PASSWORD    abc                HOST    postgres                PORT    5432                OPTIONS                      client encoding    UTF8

User · Answer

First I tried      lsof -wni tcp 5432   but it doesn t show any PID number    Second I tried      Postgres -D  usr local var postgres   and it showed that server is listening    So I just restarted my mac to restore all ports back and it worked for me

User · Answer

This worked for me  run  sudo lsof -i   lt port number gt   after that it will display the PID which is currently attached to the process   After that run sudo kill -9  lt PID gt   if that doesn t work  try the solution offered by user8376606 it would definitely work

User · Answer

I often encounter this problem on windows the way I solved the problem is Service - Click PostgreSQL Database Server 8 3 -  Click the second tab  log in  - choose the first line  the local system account

User · Answer

In my case I forgot to change the database from postgres  on my production  back to sqlite3 which I was using for development

User · Answer

I had almost just as same error with my Ruby on Rails application running postgresql mac   This worked for me   brew services restart postgresql

User · Answer

This could be caused by the pid file created for postgres which has not been deleted due to unexpected shutdown  To fix this  remove this pid file   Find the postgres data directory  On a MAC using homebrew it is  usr local var postgres   other systems it might be  usr var postgres   Remove pid file by running  rm postmaster pid   Restart postgress  On Mac  run  brew services restart postgresql

User · Answer

The postgresql server might be down and the solution might be as simple as running  sudo service postgresql start  which fixed the issue for me

User · Answer

I have faced the same issue and I was unable to start the postgresql server and was unable to access my db even after giving password  and I have been doing all the possible ways   This solution worked for me   For the Ubuntu users  Through command line  type the following commands   1 service --status-all  which gives list of all services and their status  where     refers to running and  -  refers that the service is no longer running   check for postgresql status  if its  -  then type the following command  2 systemctl start postgresql  starts the server again   refresh the postgresql page in browser  and it works  For the Windows users   Search for services  where we can see list of services and the right click on postgresql  click on start and server works perfectly fine

User · Answer

You most likely ran out of battery and your postgresql server didn t shutdown correctly    The easiest workaround is to download the official postgresql app and launch it  it will force the server to start  http   postgresapp com

User · Answer

For Docker users  In my case it was caused by excessive docker image size  You can remove unused data using prune command   docker system prune --all --force --volumes   Warning  as per manual  docker system prune --help       This will remove          all stopped containers   all networks not used by at least one container   all dangling images   all dangling build cache

User · Answer

It also gives the same error if you just stop your PostgreSQL app  You just need to start it again   PostgreSQL 11

User · Answer

This worked in my case   brew uninstall postgresql rm -fr  usr local var postgres  brew install postgresql

User · Answer

Wild stab in the dark  You re on a machine with an IPv6 resolver where localhost defaults to the IPv6 address   1  but listen addresses in postgresql conf is set to 127 0 0 1 or 0 0 0 0 not   or you re using an older PostgreSQL built with a C library that doesn t have transparent IPv6 support  Change listen addresses to localhost and make sure localhost resolves to both the IPv4 and IPv6 addresses  or set it to   1  127 0 0 1 to explicitly specify both IPv4 and IPv6  Or just set it to   to listen on all interfaces   Alternately  if you don t care about IPv6  connect to 127 0 0 1 instead of localhost  See this Google search or this Stack Overflow search for more information   Posting despite my close-vote because I voted the question for migration

User · Answer

In my case  I have changed the port in postgresql conf file and restart postgresql services in  Run   gt  service msc   gt  Restart  now retry

[ruby-on-rails] Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432?

Examples related to ruby-on-rails

Examples related to ruby

Examples related to postgresql

Examples related to ruby-on-rails-3

Examples related to ruby-on-rails-4