Re: Neddick installation - problem

[Phillip Rhodes (Fogbeam Labs)]

Authentication problems are usually a result of not having the settings in your pg_hba.conf file set just right.  For a test/demo deploy, the easiest way to get it working is to set postgres to just "trust" any IP connection on 127.0.0.1 for the "postgres" user.   Neddick defaults to using the postgres user (but you can change that if you want), and then you just have to add the argument

-U postgres

on the command line when you run the sql scripts using the psql command.

If you want to make the postgres connection secure, you'll need to enable real authentication in postgres.  That should all be documented in the postgres docs, but if you have trouble making it work, let us know and we'll see if we can help you get it sorted.


Phil

On Thu, Nov 13, 2014 at 5:32 AM, <xk...@nextoo.fr> wrote:

Hey,

I have some troubles with the deploying of Neddick when I must try this command-line in the sql :

psql -U $dbuser -d neddick -f quartz_sql.sql

I obtain this :

psql: FATAL:  authentification peer échouée pour l'utilisateur « -d »

I tried to solve this with this hints:

 http://stackoverflow.com/questions/8167602/django-connection-to-postgresql-peer-authentication-failed/8232004#8232004 

but it doesn't work, any ideas ?

Thanks.

--
You received this message because you are subscribed to the Google Groups "Fogcutter-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fogcutter-disc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.