Okay, I read the FAQ.

I looked at my postgresql.conf file and didn't see "#tcpip_socket" set,
either to true or false.

I'm also attaching the tail of the log, even though I could connect to
the database using the command line client.


2006-11-18 19:27:22 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
2006-11-18 19:27:22 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
2006-11-18 19:27:23 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
2006-11-18 19:27:23 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
2006-11-18 19:27:24 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
2006-11-18 19:27:24 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
2006-11-18 19:27:24 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
2006-11-18 19:27:24 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
2006-11-18 19:27:25 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
2006-11-18 19:27:25 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

And while we're on it, setting that variable caused the PostgreSQL
server to lock up Yast when I was restarting it that way.

John Meyer wrote:
> Okay, I read the FAQ.
>
> I looked at my postgresql.conf file and didn't see "#tcpip_socket" set,
> either to true or false.
>
> I'm also attaching the tail of the log, even though I could connect to
> the database using the command line client.
>
>
>
> ------------------------------------------------------------------------
>
> 2006-11-18 19:27:22 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
> 2006-11-18 19:27:22 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
> 2006-11-18 19:27:23 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
> 2006-11-18 19:27:23 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
> 2006-11-18 19:27:24 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
> 2006-11-18 19:27:24 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
> 2006-11-18 19:27:24 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
> 2006-11-18 19:27:24 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
> 2006-11-18 19:27:25 MST jmeyer jmeyer LOG: could not connect to Ident server at address "127.0.0.1", port 113: Connection refused
> 2006-11-18 19:27:25 MST jmeyer jmeyer FATAL: Ident authentication failed for user "jmeyer"
>
>
> ------------------------------------------------------------------------
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFFX8T1bHd4gglFmoARAlWwAJwMBnoJeILL81EbhfUIKb V5tWQO9gCeOCbX
HvCMTB+zDDl4cEt/ziVbn80=
=A3fW
-----END PGP SIGNATURE-----

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

John Meyer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> And while we're on it, setting that variable caused the PostgreSQL
> server to lock up Yast when I was restarting it that way.

File a bug with the Yast developers.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Saturday 18 November 2006 21:44, John Meyer wrote:
> John Meyer wrote:
> > Okay, I read the FAQ.
> >
> > I looked at my postgresql.conf file and didn't see "#tcpip_socket" set,
> > either to true or false.
> >
> > I'm also attaching the tail of the log, even though I could connect to
> > the database using the command line client.
> > ------------------------------------------------------------------------
> > 2006-11-18 19:27:22 MST jmeyer jmeyer LOG: could not connect to Ident
> > server at address "127.0.0.1", port 113: Connection refused 2006-11-18
> > 19:27:22 MST jmeyer jmeyer FATAL: Ident authentication failed for user
<snip>

Most likely your problem is that your webserver isnt running as user jmeyer
which your current ident config would require. You can either reconfigure
the web server, reconfigure your ident setup, or change your authentication
method in postgresql. HTH.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings