For sake of Lord, I'm unable to understand why postgres is complaining about password authentication(using ActiveRecord).
sudo -u postgres psql rdb
This work (no password is asked)
local all postgres peer
# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all peer
# IPv4 local connections:
host all all 127.0.0.1/32 md5
But when connecting with an ORM like ActiveRecord it complains.
ActiveRecord::Base.establish_connection(adapter: 'postgresql', username: 'postgres', database: 'rdb')
The server requested password-based authentication, but no password was provided.
This a basic setup and I was expecting this to work all the time. My last resort would be to allow trust or md5(on pg_hba.conf) but before I move ahead with that can some please provide me with some pointer as to why the above did not work.
Just an update postgres is running at localhost
The sudo command is triggering the local all postgres peer restriction, not asking for a password. The ActiveRecord configuration with the postgresql adapter uses this:
:host - Defaults to a Unix-domain socket in /tmp. On machines without
Unix-domain sockets, the default is to connect to localhost.
Do you have working sockets on your machine? Is /tmp writeable? It might be the case that a TCP connection to 127.0.0.1 is used, triggering the password check as indicated by md5.
Related
I have been stuck with the following issue, which is popular question that was asked multiple times but none has worked for me. I see the following error when trying to rake db:create or rails s:
ActiveRecord::ConnectionNotEstablished (fe_sendauth: no password supplied)
I tried to create a new DB user but my psql fails with the following error:
Password for user <root_username>:
psql: error: FATAL: password authentication failed for user "<root_username>"
I've updated my pg_hba.conf file to use the trust method as suggested by many answers:
# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all <root_username> trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
local replication all trust
host replication all 127.0.0.1/32 trust
host replication all ::1/128 trust
Finally, this is what my database.yml file looks like:
development:
<<: *default
database: datab_development
#username: datab
#host: localhost
I am using OSX 11 (Big Sur). Been hitting walls since this morning, any help would be greatly appreciated! Thanks!
I'm trying to restore a backup to my localhost machine to review the data - so that I can actually make sure the backup is working. I'm using Heroku, postgres, and rails.
I clean installed the app, so there is no data in the localhost database. I ran db:reset, and db:migrate.
Here is the string I'm trying to use for pg_restore:
pg_restore --verbose --clean --no-acl --no-owner -h localhost -p 3000 -U ian -d backup_production latest.dump
The error I receive says:
"connection to database "backup_production" failed: server closed the connection unexpectedly"
I've never had to do this before, so any help would be appreciated. I assume that development is what localhost uses (instead of test or production)?
I'm not sure what I'm missing, but I'll answer any question you may have.
Thanks a lot.
edit,. Here is a question, for this database string I assumed that I need to to use all the localhost information, because I created a backup using heroku capture/download. Am I wrong in that assumption? Should I instead be using the database name and port, etc, from the heroku credentials?
Turns out, I shouldn't have added the port. Removing -p 3000 , made this command work.
Try this
Edit the postgre configuration file typing in terminal
sudo gedit /etc/postgresql/POSTGRE_VERSION/main/pg_hba.conf
Then change your configuration to this
# Database administrative login by Unix domain socket
local all all trust
# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
Restart your postgre server
sudo /etc/init.d/postgresql restart
This should be the solution to access without password
I am new to postgresql. I am trying to use postgresql with ruby on rails. I have just installed postgresql and I have just created my database. But when I try to run postgresql on localhost on port 5432 I get the above error.
Yeah, I figured out the solution:
I changed my settings in pg_hba.conf to
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
where initially instead of trust it was md5.
Then just doing service postgresql restrart did the trick!!
I am creating a rails app and want to use postgresql. I have installed pgadmin, postgres sever on Ubuntu 14.04. I've tried creating a connection through pgAdmin but not able to create it. I am unable to configure pgadmin to create a connection to pg server.
I've tried editing the /etc/postgresql/9.3/main/pg_hba.conf file, but I get the following error:
FATAL: Peer authentication failed for user "postgres"
here is 'pg_hba.conf' file
Database administrative login by Unix domain socket
local all postgres peer
TYPE DATABASE USER ADDRESS METHOD
"local" is for Unix domain socket connections only
local all all peer
IPv4 local connections:
host all all 127.0.0.1/32 md5
IPv6 local connections:
host all all ::1/128 md5
Allow replication connections from localhost, by a user with the
replication privilege.
local replication postgres peer
host replication postgres 127.0.0.1/32 md5
host replication postgres ::1/128 md5
I would be grateful if someone could provide some help with configuration.
This is a VERY common error when you first install postgres, it defaults to using "postgres" as the user. You need to add your current user as a user in Postgres: Postgresql: password authentication failed for user "postgres"
First, you can reset the password for postgres:
sudo -u postgres psql
ALTER USER postgres PASSWORD 'newPassword';
But I would also/instead create a user for your current account (As a Superuser):
CREATE ROLE user_name WITH LOGIN SUPERUSER CREATEDB CREATEROLE REPLICATION;
Edit: The above command must be run from psql, so doing "sudo -u postgres psql" to access postgres is required either way.
Source: https://www.digitalocean.com/community/tutorials/how-to-use-roles-and-manage-grant-permissions-in-postgresql-on-a-vps--2
you can also try connecting through pgAdmin with the following configuration..
On CentOS, I am trying to use rake to migrate data from sqlite3 to postgresql.
When I try to connect to PostgreSQL using the command line:
psql -d <db> -U <user> -W
I get:
psql: FATAL: Peer authentication failed for user "blah"
For testing I even set method to trust for psql. Here are the contents of my pg_hba.conf:
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
Any ideas what might be wrong?
Thanks
Restart PostgreSQL and if that fails post the full pg_hba.conf for us to look at.
Either PostgreSQL has not reloaded this file or you are looking at the wrong pg_hba.conf.