Ticket #575 (closed Bug report: invalid)

Opened 10 years ago

Last modified 10 years ago

Try to install the Auth server but can't connect to Postgresql server

Reported by: martin@… Owned by:
Priority: blocker Milestone: Not yet assigned to a Milestone
Component: Auth server, Install script Version:
Keywords: Cc:

Description

I'm installing tha lastes version including theport patch on a CentOS 5.3 64 bit Everything is going right until the instal want to connect to the database.

Unable to connect to database! Please make sure the server is online and the database "wifidog" exists. Also 'postgresql.conf' and 'pg_hba.conf' must allow the user "wifidog" to open a connection to it on host "localhost" port 5432 to continue. See the error above for clues on what the problem may be.

Please go back and retry with correct values, or fix your server configuration.

In installed it on a clean server with a fresh CentOS 5.3 install.

Change History

Changed 10 years ago by pierrelucbacon@…

I posted a ticket about that issue:

http://dev.wifidog.org/ticket/574

A patch is also attached so that you can specify which port you need to use. With Postgresql 8.3, default port changed from 5432 to 5433.

Still waiting to have the patch merged into svn, but it should be easy to apply manually.

Changed 10 years ago by martin@…

That patch was allready installed. I still get the same message about a connection problem.

Changed 10 years ago by ScarEye

This is what I did on my fresh new CentOS 5.3 installation and it fixed the problem.

Edit the pg_hba.conf substituting 'ident sameuser' with 'md5 samerole':

default settings:

local all all ident sameuser host all all 127.0.0.1/32 ident sameuser host all all ::1/128 ident sameuser

new settings:

local all all md5 samerole host all all 127.0.0.1/32 md5 samerole host all all ::1/128 md5 samerole

Restart postgresql server again service postgresql restart

Regards, ScarEye?

Changed 10 years ago by benoitg

  • status changed from new to closed
  • resolution set to invalid

Postgresql config issue

Note: See TracTickets for help on using tickets.