I am currently trying to run a service using ruby on rails, while running the command rake db:schema:load
I got a password not provided error, checking my database.yml file I found this line:
#password:
I removed the comment but got the same error so I actually specified a dummy password like so:
password: dummy
Then I got this error
password authentication failed for user "ivan"
After this I tried this solution to actually set my password as dummy I still get the same error, my pg_hba.conf has the following line:
local all all peer
Changing peer to md5 produces the same error, after checking my postgres roles the only one listed is "postgres" not "ivan", what is the cause of this role appearing when trying to run my command and how do I fix it?
You need to create new user in postgres . please try below commands for creating new role and user
sudo su postgres
psql
du # for checking all existing roles
CREATE ROLE ivan WITH LOGIN SUPERUSER PASSWORD 'ivan123';
du # check whether this role created or not
then add database user name as 'ivan' and password as 'ivan123' in your database.yml
I'm using on online tutorial for homebrew to get Ruby on Rails working
https://gorails.com/setup/osx/10.11-el-capitan
Toward the end I am told to change config/database.yml's username to be the same as your OSX user account. I am unclear on how exactly to be accessing this infroamtion, and then even executing it.
I need to update the config/database.yml file to match the database username and password and I'm not sure how to be doing it from the terminal. Thank you!!
postgresql requires a role and a password in database.yml.
This tells you how to open postgresql console from terminal and create a role.
Step 1: Enter postgresql console from terminal
psql -d postgres -U username
Step 2: Create Role
create role rolename with createdb login password 'password1';
Use rolename as username and password1 as password in database.yml.
I am using Rubymine to connect to an Heroku hosted Postgres DB.
I was able to connect a few weeks ago, but now I am getting this error whenever I try to connect:
'The specified user/password combination is rejected:
FATAL: password authentication failed for user "X3v...'
My Heroku DB URL is:
postgres://<password>:X3vuEswiMHjkADaeI5RQvY4WI4#ec2-23-21-170-57.compute-1.amazonaws.com:5432/de8u1hq5ipli85
I am using JDBC to connect. In the "Data Source Properties" dialog box the (partial) URL is:
jdbc:postgresql://ec2-23-21-170-57.compute-1.amazonaws.com:5432/
And I have added my username and password to the User and Password fields.
In the advanced tab I have added
ssl = true
sslfactory = org.postgresql.ssl.NonValidatingFactory
I'm not sure what I have missed.
I understand this is not a solution, but it's works for me:
Take away the current connections to databases.
Driver Rollback and its settings to default.
sudo service postgresql restart
Now again connect.
I guess, but not sure, system uses same driver for the various editors (Idea, DataGrip, pgadmin3). It's setting a bottleneck.
If you have better solution, please write it here.
I'm not sure if this is still relevant, but you misinterpreted URL
In URL schema first gous user, then password
<protocol>://[<user>[:<password]#]<host>[:<port>]/...
so you mixed username with password
I chose postgresql for my database for rails but i ran into an apparently common error where 'FATAL: role "app" does not exist' when i try to run rake db:create:all. I found two solutions but im not sure which one is the right one to use. One website says to
su -
su - postgres
createuser -s Application
exit
exit
while the other says to
su - postgres
create role myapp with createdb login password 'password1'
what's the difference between the two? and which one should i use?
You should use this for the development environment only
Login in postgres console:
$> sudo -u postgres psql
create user with name rails and password:
=# create user rails with password 'password';
make user rails superuser:
=# alter role rails superuser createrole createdb replication;
create database projectname with owner rails:
=# create database projectname owner rails;
in database.yml:
development:
adapter: postgresql
encoding: unicode
database: projectname
pool:
username: rails
password: password
To create a user type this in your console
createuser
Enter the username and make it a superuser
Also you could add a password also by adding pwprompt to createuser like this
createuser --pwprompt
Next you enter pgsql as postgres and create your database
sudo -u postgres psql postgres
create database db_name owner user_name;
Hope it helps
Refer this site for more details
https://www.digitalocean.com/community/articles/how-to-install-and-use-postgresql-on-ubuntu-12-04
The second option is invalid. That does not work.
The first one:
I don't recommend the first one and depending on your operating system some of the steps are unnecessary.
You become a superuser and make the shell a login shell (as if you would log in directly). I think it is risky and not necessary. Why not suing directly to postgre user (that's just a matter of setup)?
You become postgre and make the shell a login shell
You create a superuser Application in PostgreSQL. So you have the privileges of a superuser for your application. I think that is risky too. Superuser for an application is very bad. Often you need createdb, login and password to get started and other privileges, if ever needed, can be added/revoked later.
You quit the postgres shell session.
You quit the superuser shell session
The second one:
That's not correct. You forget to execute psql command as second step. The second command would become the third. It would be like that.
You become postgres and make the shell a login shell
You log into postgres command shell by default with user postgres
You create a role myapp with options createdb, login and (usually by default encrypted) password with value password1.
The difference is that the first one grants superuser privileges to the Application role while the second grants only the listed permissions to the myapp role.
The second option is more secure. Among the two option opt for the seoconde one.
Note: In PostgreSQL a user is simply a role with login permission. It's more of a conceptual distinction. Technically a user and role are pretty much the same as far as I know.
I have installed PostgreSQL on my Mac OS Lion, and am working on a rails app. I use RVM to keep everything separate from my other Rails apps.
For some reason when I try to migrate the db for the first time rake cannot find the postgres user. I get the error
FATAL: role "postgres" does not exist
I have pgAdmin so I can clearly see there is a postgres user in the DB - the admin account in fact - so I'm not sure what else to do.
I read somewhere about people having issues with PostgreSQL because of which path it was installed in, but then I don't think I would have gotten that far if it couldn't find the db.
Actually, for some unknown reason, I found the issue was actually because the postgresql role hadn't been created.
Try running:
createuser -s -r postgres
Note that roles are the way that PostgreSQL maintains database permissions. If there is no role for the postgres user, then it can't access anything. The createuser command is a thin wrapper around the commands CREATE USER, CREATE ROLE, etc.
Recently i got this problem immediately after installing postgres.
If it comes immediately after installation, you might be missing the default user, postgres.
In that case, you can create default user postgres using below command.
createuser -s -U $USER
Ex: createuser -s -U $USER
enter your required role name: postgres
enter password for your the user:
It will prompt you to enter required database role name and password
Once you complete the process, you can login to the postgres console using below command
psql -U 'your_database_name'
Ex: psql -U postgres
Here, You need to enter the password if you have given any, while creating the user.
Hope it helps :)
I was on OSX 10.8, and everything I tried would give me the FATAL: role "USER" does not exist. Like many people said here, run createuser -s USER, but that gave me the same error. This finally worked for me:
$ sudo su
# su postgres
# createuser -s --username=postgres MYUSERNAME
The createuser -s --username=postgres creates a superuser (-s flag) by connecting as postgres (--username=postgres flag).
I see that your question has been answered, but I want to add this answer in for people using OSX trying to install PostgreSQL 9.2.4.
This message pops up, when the database user does not exist. Compare the manual here.
Multiple local databases cannot be the explanation. Roles are valid cluster-wide. The manual again:
Note that roles are defined at the database cluster level, and so are
valid in all databases in the cluster.
You must be ending up in another database-cluster. That would be another server running on the same machine, listening to a different port. Or, more likely, on a different machine.
Could it be that the message comes, in fact, from the remote server?
I met this issue right on when I first install the Heroku's POSTGRES.app thing. After one morning trial and error i think this one line of code solved problem. As describe earlier, this is because postgresql does not have default role the first time it is set up. And we need to set that.
sovanlandy=# CREATE ROLE postgres LOGIN;
You must log in to your respective psql console to use this psql command.
Also noted that, if you already created the role 'postgre' but still get permission errors, you need to alter with command:
sovanlandy=# ALTER ROLE postgres LOGIN;
Hope it helps!
In the Heroku documentation; Getting started whit rails 4, they say:
You will also need to remove the username field in your database.yml
if there is one so: In file config/database.yml remove: username:
myapp
Then you just delete that line in "development:", if you don't pg tells to the database that works under role "myapp"
This line tells rails that the database myapp_development should be
run under a role of myapp. Since you likely don’t have this role in
your database we will remove it. With the line remove Rails will try
to access the database as user who is currently logged into the
computer.
Also remember to create the database for development:
$createdb myapp_development
Repleace "myapp" for your app name
The installation procedure creates a user account called postgres that is associated with the default Postgres role. In order to use Postgres, you can log into that account. But if not explicitly specified the rails app looks for a different role, more particularly the role having your unix username which might not be created in the postgres roles.
To overcome that, you can create a new role, first by switching over to the default role postgres which was created during installation
sudo -i -u postgres
After you are logged in to the postgres account, you can create a new user by the command:
createuser --interactive
This will prompt you with some choices and, based on your responses, execute the correct Postgres commands to create a user.
Pass over a role name and some permissions and the role is created, you can then migrate your db
Could you have multiple local databases? Check your database.yml and make sure you are hitting the pg db that you want. Use rails console to confirm.
My answer was much more simple. Just went to the db folder and deleted the id column, which I had tried to forcefully create, but which is actually created automagically. I also deleted the USERNAME in the database.yml file (under the config folder).
In Ubuntu local user command prompt, but not root user, type
sudo -u postgres createuser username
username above should match the name indicated in the message "FATAL: role 'username' does not exist."
Enter password for username.
Then re-enter the command that generated role does not exist message.
I ended up here after attempting to follow Ryan Bate's tutorial on deploying to AWS EC2 with rubber. Here is what happened for me:
We created a new app using "
rails new blog -d postgresql
Obviosuly this creates a new app with pg as the database, but the database was not made yet. With sqlite, you just run rake db:migrate, however with pg you need to create the pg database first. Ryan did not do this step. The command is rake db:create:all, then we can run rake db:migrate
The second part is changing the database.yml file. The default for the username when the file is generated is 'appname'. However, chances are your role for postgresql admin is something different (at least it was for me). I changed it to my name (see above advice about creating a role name) and I was good to go.
Hope this helps.
After a bunch of installing and uninstalling of Postgres, here's what now seems to work consistently for me with Os X Mavericks, Rails 4 and Ruby 2.
In the database.yml file, I change the default usernames to my computer's username which for me is just "admin".
In the command line I run rake db:create:all
Then I run rake db:migrate
When I run the rails server and check the local host it says "Welcome aboard".
You might be able to workaround this by running initdb -U postgres -D /path/to/data or running it as user postgres, since it defaults to the current user. GL!