Note that if you do not specify a database name, it defaults to the database user name, which might or might not be the right thing. The database you are trying to connect to does not exist. The indicated database user name was not found. Check the password you are providing, or check your Kerberos or ident software if the complaint mentions one of those authentication types. Messages like this indicate that you contacted the server, and it is willing to talk to you, but not until you pass the authorization method specified in the pg_hba.conf file. As the message suggests, the server refused the connection request because it found no matching entry in its pg_hba.conf configuration file.įATAL: password authentication failed for user "andym" This is what you are most likely to get if you succeed in contacting the server, but it does not want to talk to you. Hope this helps methodically troubleshoot this issue.Authentication failures and related problems generally manifest themselves through error messages like the following:įATAL: no pg_hba.conf entry for host "123.123.123.123", user "andym", database "testdb" If the postgres server is not started, please try restarting the postgres instance with the command as appropriate to the operating system you are using.įor Mac OS the command to restart was brew services restart postgresql The process is not running at all or there is some other issue, which can again be seen in the log (which can be found with the steps above). Once you get the port, which was 5488 in my case, connect to postgres server with an option "-p" to connect (replace with the port found from the log): psql -p 5488 #add host and other options as neededī. So, you can grep that as well like: egrep "*listening*" /usr/local/var/log/postgres.log Open the log file and confirm the port number from the log line like below: Now if I try to connect with it, psql asks for a password. I reassigned all its ownerships to user postgres, removed the user, and then created it again with CREATE USER jack. There are other articles on how to check the statusįind the log location with the pid (5833 is the pid of postgres from the above command, replace the pid with your pid from the command output you get): $ lsof -p 5833 | grep log I used to have a user, say jack in postgresql, and then I forgot what the password. You can confirm postgres server status with pg_ctl or other commands to confirm. If you DO NOT get the output like above, most likely the postgres server is not running. Got the pid of 5833 from the output below: UID PID PPID C STIME TTY TIME CMDĥ01 5833 1 0 12:07PM ? 0:00.13 /usr/local/opt/postgresql/bin/postgres -D /usr/local/var/postgres Maybe the port is not the default port used (which is 5432)- How to confirm this? ps -ef | grep UID & ps -ef | grep postgres This issue might occur for one of the reasons below:Ī. The solution is as simple as reinstalling the gem. When you install the ‘pg’ gem, it detects which version of Postgres is installed and sets the domain socket path appropriately. The fix is simple, if a little suprising. At no point had I told Rails to connect to postgres on that path, Rails had assumed it, and now its assumptions were wrong. I could’ve messed around with the config and made Postgres use the domain socket it was previously, or told Rails explictly how to connect, but both of those approaches seemed like work I shouldn’t have to do. The problem was that the new version of Postgres listens on /tmp/.s.PGSQL.5432 instead. Is the server running locally and acceptingĬonnections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"? Even though Postgres was definitely running, suddenly I was getting:Ĭould not connect to server: No such file or directory (PG::ConnectionBad) However, trouble struck once I tried to run any specs that needed to connect to Postgres. The process was smooth and pg_upgrade is a very handy tool. I recently upgraded Postgres from 9.2 to 9.3 using brew upgrade postgres. I was looking for a long time, and this was the most clean and neat solution:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |