Postgres.app Could not start on port 5432 - macos
I'm using http://postgresapp.com. In the menubar it gives the error " Could not start on port 5432." Similarly if I try to start the server from the terminal, I get:
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 also ran pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start
and got the output server starting but still get the same errors when connecting to psql.
If you are running your server on a macOS machine and installed Postgres through Homebrew, you can stop the current instance like this:
brew services stop postgresql
Then click the Elephant in the native menu-bar at the top of the screen and it should successfully startup.
You can stop the process by finding the PID with
lsof -i :5432
and then killing it with
kill -9 <PID>
If you've installed Postgres via another method (for example, from www.postgresql.org) and it's starting automatically at startup, you can prevent that Postgres from starting via the following:
sudo launchctl unload /Library/LaunchDaemons/com.edb.launchd.postgresql-X.X.plist
sudo rm -f /Library/LaunchDaemons/com.edb.launchd.postgresql-X.X.plist
TIP: use tab to autocomplete after the com.edb.launchd part to figure out what version is loading.
Restart Postgres.app and you should be good to go.
(from http://forums.enterprisedb.com/posts/list/1831.page;jsessionid=70621DC48C99EDE663A6A594B05F1A02#6782)
I was just having this exact issue. When I ran which psql it was pointing at the Postgres client tools installed with Lion:
/usr/bin/psql
Using a hint from Frank Wiles I ran ps auxw | grep post to confirm that postgres was running and that it was running on the right port, that also showed me the postgres.app path:
/Applications/Postgres.app/Contents/MacOS/bin/postgres.
So I edited by .bash_profile to export that directory. On first effort I added it to the end of the path. When I ran echo $PATH I could see that usr/bin was the first thing in the path, and which psql still gave the /usr/bin path. At that point a friend guided me in the right direction:
export PATH="/Applications/Postgres.app/Contents/MacOS/bin:${PATH}"
Start a new terminal window, then run which psql -- it should point to the postgres.app location and psql should fire up the postgres shell. Works fine now.
I have tried just about every solution to this problem that is out there. For me it always happens when my MacBook's battery dies, even if the computer is already sleeping. I was poking around in ~/Library/Application\ Support/Postgres/var-9.4 and I discovered another postmaster.pid file that I had not seen before. I deleted it, and now everything is back up and running! I am running the Postgres.app version, not the brew version.
Steps I took:
Make sure postgres.app is not running.
Run rm ~/Library/Application\ Support/Postgres/var-9.$X/postmaster.pid
If you don't have a var-9.$X directory, just run rm ~/Library/Application\ Support/Postgres/postmaster.pid
Restart postgres.app
Get back to developing cool stuff.
This command is a one-liner that instantly kills all PostgresSQL processes.
sudo kill -kill $(sudo lsof -t -i :5432)
This fixed all my problems on Mac OSX Mojave 10.14.1.
You my have another instance of postgres running, that is the only application interested in this port. You should use netstat and ps to determine this. Then stop the instance and uninstall it, you mayhave installed enterpiseDb for example, that is what I did.
I generally face this issue on my mac, and this fixes it for me always
rm /usr/local/var/postgres/postmaster.pid
brew services restart postgresql
Hope this is helpful
I had a similar problem where I could not connect to the Postgres.app even though the app itself said that it is running on port 5432.
I am not sure why, but even when I quit the app and checked that no postgres processes was running with ps -a. these files existed:
/tmp/.s.PGSQL.5432
and
/tmp/.s.PGSQL.5432.lock
My solution was to delete these files and then start the postgres.app again.
This is what worked for me:
$ sudo pkill -u postgres
Props to this resource:
https://github.com/PostgresApp/PostgresApp/issues/197#issuecomment-474534056
It can also happen that the PID is taken.
This ocurred to me when the Computer suffered an unexpected reboot.
If so, you must go to:
˜/Library/Application Support/Postgres/var-9.4
You can check that path in Postgres.app Preferences dialog.
And then, just remove the pid file
sudo rm postmaster.pid
And the server starts up right away.
When trying to open the Postgres app was getting that same error regarding post 5432 (on Mac OSX 10.10.5)
I did:
$ lsof -i | grep LISTEN
Saw which PID was running postgres at that port, did:
$ killall {pid} and then $ brew uninstall postgres
After that, restarted my Mac, and ran:
$ lsof -i | grep LISTEN again just to make sure. Saw no postgres running anywhere and was able to open the Postgres app without getting that warning.
Then I reinstalled postgres with $ brew install postgres
ANOTHER OPTION:
(I also tried this one time when the above approach didn't work and I could not kill any of the PID)
$ ps auxw | grep post
Saw a slew postgres processes, which I then sudo kill <PID>
Everything working fine now.
For those using mac, this code worked for me like charm.
sudo pkill -u postgres
At a guess, something else had taken port 5432 so the app chose to run on 5433 instead.
Why not just connect to Pg on port 5433, if that's where it's running? You have a /tmp/.s.PGSQL.5432 socket file, so you can connect with psql -p 5433 for UNIX domain socket connections. It'll also be listening on the same port with TCP/IP, so you can use psql -h localhost -p 5433 for TCP/IP and have your apps connect to port 5433 instead of 5432.
Change your .psqlrc to set the new port as default and you can forget it isn't on the default port.
I had similar problem when trying to use postgresql with rails. Updating my Gemfile to use new version of gem pg solve this problem for me. (gem pg version 0.16.0 works). In the Gemfile use:
gem 'pg', '0.16.0'
then run the following to update the gem
bundle install --without production
bundle update
bundle install
Mine failed to start up suddenly, and when I checked Console.app I saw:
com.heroku.postgres-service:
FATAL: could not create shared memory segment: Cannot allocate memory
DETAIL: Failed system call was shmget(key=5432001, size=3874816, 03600).
HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter. You can either reduce the request size or reconfigure the kernel with larger SHMALL. To reduce the request size (currently 3874816 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
The PostgreSQL documentation contains more information about shared memory configuration.
It turns out Postgres wouldn't start up because I had Wireshark (and X11) running. It worked fine after I quit Wireshark.
Good luck!
I resolved this problem by
Identifying what was running on port 5432 by using "netstat" in the CL, which was postgreSQL not Postgres
I located the directory that contained postgreSQL, which was root/Library/PostgreSQL
I ensured an instants of the application wasn't running via Activity Monitor
Then I deleted the folder and rebooted! Everything was fine!
Somehow I totally forgot that this socket file will be hidden because of the dot. Make sure you use ls -A /tmp/.s.PGSQL.5432 if you are checking to see if the socket is actually there.
You most likely has a PostgreSQL installed, deleted it and installed it again. PostgreSQL typically used port 5432 but if not available, increases to the next available one, in this case 5433. So, you probably chose this port on your second install.
I think you should check file:
/etc/services
and adjust rows below for your expected port number:
postgresql 5432/udp # PostgreSQL Database
postgresql 5432/tcp # PostgreSQL Database
After this you should restart your computer (simplest way).
I had the same issues:
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"?
In my case it was a corrupt host file on my mac. I was missing:
127.0.0.1 localhost
A quick easy way to check is to open terminal and type:
ping localhost
or:
scutil -r localhost
More info here
Hope it helps.
Netstat, ps aux, etc ... none showed 5432 in use. Checked /Library. Found PG9.6 old install still there. Did rm -rf and bang. Version 11 works fine.
I was losing my mind over this problem! i kept running
lsof -i | grep 5432
and nothing was showing up!
finally i ran it using sudo and a potgres client showed up.
so if anyone else has tried the lsof and went nowhere, try it with sudo.
sudo lsof -i | grep 5432
and then
sudo kill <the_pid_from_postgresql_found_from_lsof>
The same problem just happened to me. I had Postgres.app 9.2.4.1 running since a while. When I updated Mac OS X to 10.8.5, after the mandatory reboot it was not working anymore. I tried several things, including updating to 9.2.4.3 and neither after another reboot it was working.
I had to open the file /Users/$USER/Library/Application Support/Postgres/var/postgresql.conf and to:
uncomment line unix_socket_permissions = 0777
uncomment and adapt line unix_socket_directory = '/tmp'
After a restart, Postgres.app was running like a charm.
A file named "postmaster.pid" (in my $PGDATA directory) were preventing postgresql to start. It was a zombie file, placed there 10 days ago and when I brutally shut down the computer (pulling the plug, literally), no clean up process had the opportunity to remove that file.
beside all the helpful answers, you might also want to take a look at official page instructions :
postgressapp.com/documentation/remove.html
I had this same issue and mine was caused by some configuration issues I was having. Clearing the user configurations and reinstalling postgres in brew worked for me!
brew uninstall postgresql
rm -rf /usr/local/var/postgres
I ran the following:
psql --version then brew services stop postgresql#<VERSION>
finally, start your Postgres app on your Mac.
Related
Lost control over my MariaDB installation
I installed MariaDB on my mac with Macports but lost control over it, mysteriously. I can list the processes and I can login using a user with no privileges. But if I try to stop the database using the usual macports command (sudo port unload mariadb-10.1-server) I get the following error: /opt/local/etc/LaunchDaemons/org.macports.mariadb-10.1-server/org.macports.mariadb-10.1-server.plist: Could not find specified service I've tried installing and uninstalling but this doesn't change. How can I do a fresh install of MariaDB on my mac?
Perhaps you inadvertently installed another version of mariadb-server? You can check with: port echo active |grep mariadb- It is also possible that the server was started without using launchd and so can't be stopped with the command you were using. You can check with: sudo launchctl list |grep macports 'org.macports.mariadb-10.1-server' will be in the list if it is running under launchd.
I've deleted the directory where this installation was and reinstalled from Macports. That solved the problem.
Ubuntu 16 upgrade results incredibly slow wifi
I recently upgraded to Ubuntu16 from 14. Everything went fine, however my wifi connection went to a crawl. I actually experienced this on a previous system that I installed Ubuntu16 on and because of that, stuck with Ubuntu14 for as long as I could until version lag forced me to upgrade. I came across this solution that was referring to Ubuntu 17 https://askubuntu.com/questions/905288/extremely-slow-connection-after-17-04-update And it seemed to do the trick! The only issue is that now after a system suspend or boot-up, I have to run sudo systemctl restart systemd-resolved Otherwise I cannot connect to any server. Its not a huge deal, I've aliased it at this point, but it would be nice get it operating appropriately. Thanks for the help!
Download this link. If the download by the first link failed, download this file. Open the Terminal and run these commands on your ubuntu pc. cd rtlwifi_new-master make sudo make install sudo modprobe -rv rtl8723be sudo modprobe -v rtl8723be ant_sel=2 sudo ip link set wlp13s0 up sudo iw dev wlp13s0 scan
RabbitMmq on Mac can't start
I've installed rabbitmq on Mac OS X via homebrew, just a simple command: $ brew install rabbitmq but, when I start the server via rabbitmq-server, it occurs: ERROR: distribution port 25672 in use on localhost (by non-Erlang process?) I want to find some process that uses port 25672, but I can't find that really strange anyone knows the reason, thx a lot :)
Use sudo lsof -i :25672 to find the process. sudo may or may not be needed depending on user permissions.
Why can't I get the postgresql server to run?
Ok. I have been trying to solve this problem for several days. I installed, uninstalled, and reinstalled Postgresql 3 times. I followed precisely the instructions in this forum: https://dba.stackexchange.com/questions/42048/cant-connect-to-the-postgres-server-ls-tmp-s-pgsql-5432-no-such-file-or-dir I found this solution in many forums, so I tried to run: $ mkdir /var/pgsql_socket/ $ sudo mkdir /var/pgsql_socket/ $ ln -s /private/tmp/.s.PGSQL.5432 /var/pgsql_socket/ But this didn't work. When I try to start the server it still says there is another one running and then proceeds to fail every time I try to create a database or type "psql" I then tried to run the following in order to change the path of the commands from OS X's builtin version of postgres to my version and it seemed to work: $ cd /usr/local/bin $ rm postgres $ ln -s /Library/PostgreSQL/9.2/bin/postgres postgres $ rm psql $ ln -s /Library/PostgreSQL/9.2/bin/psql psql $ rm pg_ctl $ ln -s /Library/PostgreSQL/9.2/bin/pg_ctl pg_ctl So then I ran the following to create a user for postgres: $ sudo -u postgres createuser --superuser $Sarah $ sudo -u postgres createuser --superuser user_sarah $ sudo -u postgres psql postgres But it kept saying "unknown user postgres" I then tried to install the Ruby pg gem, but that also failed, saying there was a problem with necessary libraries. I have saved a text file of everything I tried to do in the terminal. Let me know if I should post that. Thanks. update: When I try to run this: $ pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start I get this: -bash: /usr/local/bin/pg_ctl: No such file or directory Which is different from a lot of other errors that I have seen posted on this problem.
first, you should verify that there is no postmaster running: ps -ef | grep postmaster. once you've verified the postmaster is not running, you should look into the postgresql command initd. Depending on your server installation, it may or may not be installed. You need to create a database before attempting to start postgres. It sounds to me like you got an installation that didn't install the main postgresql commands to /usr/bin, pg_ctl being one of these. FYI: the postgres account is not a login account and is automatically created when installing postgresql, so it should be there if you had a good installation. You cannot sudo as postgres if postgres is not in the sudoers file.
The homebrew install of PostgreSQL does not create or need a postgres account, so all the mentions of doing sudo -u postgresor ps -fu postgres don't apply to your case. The command brew info postgresql outputs various information about to start and stop it, you may read them. By contrast you don't want to put blind faith into what random users tell about how they "fixed" their non-working installation. In fact, the web carries a shocking amount of bad advice concerning PostgreSQL on MacOS X, and to me the answer you linked on dba.se is among them. It's wrong from start to finish, and you should note that it was not accepted as an answer. Certainly the author means well, but he fails to see that his own context can't be generalized to other installations. The worst part is the suggestion to delete in /usr/local/bin/ the binaries postgres, psql, pg_ctl and soft-linking them into supposed equivalents inside /Library/PostgreSQL/9.2/bin/. To me it just breaks the homebrew install. No wonder that after doing this you get this error: /usr/local/bin/pg_ctl: No such file or directory So my answer would be to reinstall postgresql with brew to restart from a clean state, then make sure that all postgres commands you launch are from /usr/local/bin, and always first read the server log file passed to pg_ctl if you have any doubt on anything PG-related.
psql: could not connect to server: No such file or directory (Mac OS X)
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.
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. Lots of people have similar issues but most the answers had to do with file permissions, whereas in my case things were different.
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 ~/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)
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
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
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
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
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
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.
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)
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.
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...
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
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.
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
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
For those running into this issue on M1 macs, try deleting this file and then restarting the brew service: rm /opt/homebrew/var/postgres/postmaster.pid
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.
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.
I had the same issue and it was due to an incompatible version after upgrading from version 11 to 13.2 Checking error log at: /usr/local/var/log/postgres.log Showed me: DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 13.2. To fix I ran: brew postgresql-upgrade-database And then started postresql with brew: brew services start postgresql
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.
I had this same concern when connecting trying to start a PostgreSQL database server on MacOS Monterey. When I run the command below to restart the PostgreSQL database server: brew services restart PostgreSQL It restarts but when I try to check the status of the PostgreSQL database server using the command below, I get an error: Name Status User File mysql started promisepreston ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist nginx started promisepreston ~/Library/LaunchAgents/homebrew.mxcl.nginx.plist postgresql error 256 root ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist Here's what worked for me: First, I checked the log file for the PostgreSQL database server to what was the cause of the error using the command below: cat /usr/local/var/log/postgres.log OR nano /usr/local/var/log/postgres.log The logs showed the following errors: "root" execution of the PostgreSQL server is not permitted. The server must be started under an unprivileged user ID to prevent possible system security compromise. See the documentation for more information on how to properly start the server. 2022-01-25 19:01:06.051 WAT [29053] FATAL: database files are incompatible with server 2022-01-25 19:01:06.051 WAT [29053] DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.1. For the root execution error I had to run the following command to fix file permissions that when messed us when I ran brew services with the sudo command prefix. Replace your-username with your MacOS username (in my case my username was promisepreston: # Stop postgresql sudo brew services stop PostgreSQL # In case service file is copied to ~/Library/LaunchAgents as well brew services stop postgresql # Fix permission of homebrew files sudo chown -R your-username:admin $(brew --prefix)/* For the database files are incompatible with server I had to simply upgrade the existing PostgreSQL data files which were created using version 13 to the latest PostgreSQL version on my computer which was 14.1 by running the following command below: brew postgresql-upgrade-database Afterwhich, I restarted the PostgreSQL database server: brew services restart PostgreSQL And then checked the status using the command below: brew services list Then I got the output below showing that everything was working fine: Name Status User File mysql started promisepreston ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist nginx started promisepreston ~/Library/LaunchAgents/homebrew.mxcl.nginx.plist postgresql started promisepreston ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist References: Brew PostgreSQL Starts But Process Is Not Running
I had a similar error. All of this is done from the command line (no sudo calls at all) I verified I had PostgreSQL installed psql -V (note that's a capital "V") I attempted to connect to the server: psql postgres THIS IS WHERE I EXPERIENCED THE ERROR OF THIS STACK OVERFLOW QUESTION After doing some research about possible fixes, I obviously had PostgreSQL installed, but I didn't have a default server in place. What I had to do was create a Custom Data Directory As far as I can tell, creating the custom data directory is the same as having a default server in place. Since this is a new machine (MacBook Pro 2021 using apple m1 chip), I wanted to find the easiest solution possible, and I believe this Custom Data Directory is just that. The remaining steps to fix this issue are as follows: From the home directory, I created an empty directory mkdir myData From the home directory, Initialized a server: initdb myData (throws a bunch of files into the myData directory) pg_ctl -D myData -l logfile start (starts the server) psql postgres (connects to the server) So, as someone fairly new to PostgreSQL and databases and SQL in general, couple notes: It is possible to "quit" the connection to the server, using \q (while connected to the server, it's also possible to type "help") It is also possible to "stop" the server, as well with pg_ctl -D myData stop At this point I now am certain I have PostgreSQL installed, have a server I can start and stop, and have the ability to connect to/disconnect from, that server.
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 ;)
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
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.
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.
#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.
I removed /usr/lib from the LD_LIBRARY_PATH and it worked. I was working in dockerfile postgres:alpine.
This answer worked for me: https://stackoverflow.com/a/45454567/15067545 on my ubuntu system. Command: sudo service postgresql restart.