Thread: Re: [INTERFACES] fe_setauthsvc: invalid name. Ignoring... ERROR

I finally figured out why I am gettting an authentication failure. The problem was my previous code has the declaration
forPgDatabase like this.
 

PgDatabase * myDatabase = new PgDatabase("dbname=template1");

I was running this code on solaris and everything was working fine.  I looked at the PgDatabase class and figured out
thatwe no longer need that 'dbname='.  Now my code looks like this:
 

PgDatabase * myDatabase = new PgDatabase("template1");

and I could now run this from the command line.  I am intersted in the solution which you had for apache since I will
finallyintegrate the code with apache.
 

Thanks in advance
-Dutt


---

-Dutt H Kalapatapu
www.hydbazaar.com

On Mon, 16 Aug 1999 03:37:19   Clint Forgy wrote:
>Dutt H Kalapatapu wrote:
>> 
>> Some body already had this problem( mo@midwestonline.com).  I am
>> trying to connect to database using PgDatabase interface and I get
>> an error saying "fe_setauthsvc: invalid name, ignoring..".  I thought
>> this was permission problem so I made myself the superuser of the
>> database and ran initdb and I still get this error.
>
>Hi Dutt,
>
>That was me having that problem.  I was trying to use postgres via cgi
>for some dynamic content on a virtually hosted system.  I was having
>that problem with cgi apps *only* but not the command line.  I can't
>remember the exact fix off the top of my pointy head but Tom Lane
>suggested the fix.  I remember that it had something to do with apache
>running as user nobody, and when the cgi app started, the perl
>environment didn't have the correct userid in its environment.  I can go
>through my notes if you're interested.  It sounds somewhat related, but
>since you're having the same problem at the command line, I'm not sure
>which way to point you.
>
>-- 
>Clint Forgy
>"Paving the Information Gravel Road for the Midwest"
>http://www.midwestonline.com
>ICQ: 8443021                Make Code, Not War
>
>


Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com

"Dutt H Kalapatapu" <dutt@eudoramail.com> writes:
> I finally figured out why I am gettting an authentication failure. The
> problem was my previous code has the declaration for PgDatabase like
> this.

> PgDatabase * myDatabase = new PgDatabase("dbname=template1");

> I was running this code on solaris and everything was working fine.  I
> looked at the PgDatabase class and figured out that we no longer need
> that 'dbname='.  Now my code looks like this:

> PgDatabase * myDatabase = new PgDatabase("template1");

>  and I could now run this from the command line.

Hmm, that explains a couple of things.  The first example (with dbname=)
is correct for Postgres 6.5 and later, because PgDatabase's constructor
now takes a conninfo string a la PQconnectdb.  Older releases used to
just take a database name, IIRC.  So, you are apparently using a
back-rev Postgres on your "new" setup.

I had looked at the code in fe_setauthsvc() and was unable to figure out
a reason for it to fail (it's almost dead code, anyway) --- but I was
looking at the current code.  I do seem to recall that pre-6.5 libpq++
would deliver this misleading error message on pretty much any failure
to connect, including specifying a wrong database name.

I'd recommend upgrading to 6.5.1 ASAP.
        regards, tom lane