pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedfe_setauthsvc: invalid name. Ignoring... ERROR
4+ messages / 3 participants
[nested] [flat]
* fe_setauthsvc: invalid name. Ignoring... ERROR
@ 1999-08-15 20:16 Dutt H Kalapatapu <dutt@eudoramail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Dutt H Kalapatapu @ 1999-08-15 20:16 UTC (permalink / raw)
To: pgsql-interfaces
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.
I was running Linux5.2 earlier and I had no problem what's so ever
with the same code and I upgraded to Linux6.0(Redhat) and I get
this error. What could be the problem? and how should one rectify this error?
I am running a tight schedule and suddenly I find myself totally spending time on this error.
Thanks for any info.
-Dutt
---
---------------------
Dutt Kalapatapu
10611 Dabney Drive
Apt. No. 14
San Diego CA 92126
Phone: 619 253 4638
---------------------
Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] fe_setauthsvc: invalid name. Ignoring... ERROR
@ 1999-08-16 03:37 Clint Forgy <mo@midwestonline.com>
parent: Dutt H Kalapatapu <dutt@eudoramail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Clint Forgy @ 1999-08-16 03:37 UTC (permalink / raw)
To: ; +Cc: pgsql-interfaces
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] fe_setauthsvc: invalid name. Ignoring... ERROR
@ 1999-08-16 06:09 Dutt H Kalapatapu <dutt@eudoramail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Dutt H Kalapatapu @ 1999-08-16 06:09 UTC (permalink / raw)
To: Clint Forgy <mo@midwestonline.com>; +Cc: pgsql-interfaces
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. I am intersted in the solution which you had for apache since I will finally integrate 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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] fe_setauthsvc: invalid name. Ignoring... ERROR
@ 1999-08-16 14:24 Tom Lane <tgl@sss.pgh.pa.us>
parent: Dutt H Kalapatapu <dutt@eudoramail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 1999-08-16 14:24 UTC (permalink / raw)
To: Dutt H Kalapatapu <dutt@eudoramail.com>; +Cc: Clint Forgy <mo@midwestonline.com>; pgsql-interfaces
"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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~1999-08-16 14:24 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-08-15 20:16 fe_setauthsvc: invalid name. Ignoring... ERROR Dutt H Kalapatapu <dutt@eudoramail.com>
1999-08-16 03:37 ` Clint Forgy <mo@midwestonline.com>
1999-08-16 06:09 Re: [INTERFACES] fe_setauthsvc: invalid name. Ignoring... ERROR Dutt H Kalapatapu <dutt@eudoramail.com>
1999-08-16 14:24 ` Re: [INTERFACES] fe_setauthsvc: invalid name. Ignoring... ERROR Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox