Databases
StackOverflow2013
Postsdbo
POrake db:create:all FATAL : password authentication failed
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POrake db:create:all FATAL : password authentication failed
    primarykey
    data
    text
    <p>I am trying to follow this <a href="http://railscasts.com/episodes/342-migrating-to-postgresql" rel="nofollow noreferrer">railscast</a> tutorial. Now I am in the step, where you create the database with rake db:create:all, but I got this error message :</p> <pre><code>FATAL: password authentication failed for user aldila </code></pre> <p>I made the user aldila through pgAdmin, by right-clicking the login role and add user aldila with password.</p> <p>So, here is my database.yml :</p> <pre><code>development: adapter: postgresql host: localhost encoding: unicode database: my_app_development pool: 5 username: aldila password: *mypass* test: adapter: postgresql host: localhost encoding: unicode database: my_app_test pool: 5 username: aldila password: *mypass* production: adapter: postgresql host: localhost encoding: unicode database: my_app_production pool: 5 username: aldila password: *mypass* </code></pre> <p>Here is my pg_hba.conf</p> <pre><code># TYPE DATABASE USER ADDRESS METHOD # 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. #host replication postgres 127.0.0.1/32 md5 #host replication postgres ::1/128 md5 </code></pre> <p>Maybe there is something's wrong with the installing of PostreSQL, because if I type psql --version on my command, this is what I got :</p> <pre><code>'psql' is not recognized as an internal or external command, operable program or batch file. </code></pre> <p>But I have no idea what went wrong. I install it from <a href="http://www.postgresql.org/" rel="nofollow noreferrer">here</a> and pick download the installer from EnterpriseDB for all supported versions.</p> <p>I know there are already similar questions like this, but I follow <a href="https://stackoverflow.com/questions/5817301/rake-dbcreate-fails-authentication-problem-with-postgresql-8-4">this one</a> and <a href="https://stackoverflow.com/questions/13439276/rails-deploying-to-heroku-many-problems">this one</a>, but I still get the same error message. I would be really appreciated, if anyone could help. Thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USishwr
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POrake db:create:all FATAL : password authentication failed
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you using `devise`? Maybe you forgot to add `password_confirmation`.
      singulars
      1. POrake db:create:all FATAL : password authentication failed
      1. UScortex
    2. CONo, I don't. Do you mean to create the login role for database? I used pgAdmin and add login role through pgAdmin, if that's what you mean.
      singulars
      1. POrake db:create:all FATAL : password authentication failed
      1. USishwr
    3. COWhat OS are you using?
      singulars
      1. POrake db:create:all FATAL : password authentication failed
      1. USSean
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload