Thread: FW: Creating DataBases on Suse LINUX Platform
oops forgot to send this to the group... apologies. Larry -----Original Message----- From: Cook, Larry ISC Sent: April 11, 2005 10:22 AM To: 'brew@theMode.com' Subject: RE: [NOVICE] Creating DataBases on Suse LINUX Platform Hi Brew... Thanx for responding.. I tried that already... as i figured that is how it should work, however, still get the same error message --> could not connect to database template1: FATAL: IDENT authentication failed for user "postgres". This really has me baffled. Do you think upgrading to 8.1 would help? I am getting a little frustrated trying to get this project going and don't really want to use Oracle. Any other suggestions? Thanx for your time, Larry -----Original Message----- From: brew@theMode.com [mailto:brew@theMode.com] Sent: April 11, 2005 10:14 AM To: 'pgsql-novice@postgresql.org' Subject: Re: [NOVICE] Creating DataBases on Suse LINUX Platform Larry..... > You will need to become the operating system user under which PostgreSQL > was installed (usually postgres) to create the first user account. > According to the sys people it was installed over the network; > presumably as the "root" user. Yes, but even if it was installed on linux as root it creates the linux user postgres as the root user of postgreSQL. Log in to the linux box as root and then su to postgres. i.e. su - postgres Then create the database and database users there. brew ========================================================================== Strange Brew (brew@theMode.com) Check out my Stock Option Covered Call website http://www.callpix.com and my Musician's Online Database Exchange http://www.TheMode.com ========================================================================== ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
"Cook, Larry ISC" <Larry.Cook@isc.ca> writes: > ...however, still get the same error message --> could not connect to > database template1: FATAL: IDENT authentication failed for user "postgres". If you really are logged in as postgres, the only other reason for this failure that I can think of is that the postmaster couldn't verify your identity. That should always work if you are connecting to it via a Unix socket ... but if you are connecting via TCP/IP then that requires an ident daemon, which most people don't run by default. So maybe the problem is you are specifying "-h localhost" or some variant? Worst case, you could turn off the authentication check (by changing pg_hba.conf) for long enough to create some initial user accounts. But it'd be better to figure out what's going wrong, because it really should work. regards, tom lane