Note that there are some explanatory texts on larger screens.

plurals
  1. POrake db:create fails, authentication problem with postgresql 8.4
    primarykey
    data
    text
    <p>first things first, please excuse my utter noobness. I really tried to find a solution out there, but now i'm stuck and completely clueless.</p> <p>i'm trying to deploy a rails 3 app on a distant server ; when developping on my local VM, no problem showed. But now, when i try to run </p> <pre><code>rake db:create </code></pre> <p>it fails, with error (here translated, since i'm french):</p> <pre><code>FATAL : password authentication failed for user &lt;&lt;mylogin&gt;&gt; </code></pre> <p>here's my database.yml :</p> <pre><code>login: &amp;login adapter: postgresql username: mylogin password: mypassword host: localhost port: 5432 encoding: UTF8 development: &lt;&lt;: *login database: somesite_development test: &lt;&lt;: *login database: somesite_test production: &lt;&lt;: *login database: somesite_production </code></pre> <p>the user "mylogin" has been created postgre-side with the command-line tool "createuser". It's authorized to create dbs. postgresql.conf configures the server to listen on localhost. I've tried many things with pg_hba.conf, none worked - whatever the method used (ident, password, md5) for user "mylogin" on 127.0.0.1, authentication fails - though i've never had problems connecting / creating dbs with psql.</p> <p>any clue ? </p> <p>EDIT: okay, found out how incredibly stupid i've been... the password for my user was simply not set ! I think i forgot the semicolon after </p> <p>ALTER USER xxxx WITH PASSWORD xxxx ;</p> <p>... i saw this by requesting "SELECT * FROM pg_shadow;" - the password field was empty. Three days of my life wasted because of this dumb mistake...</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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