From: | Ian Pilcher <i(dot)pilcher(at)comcast(dot)net> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Problem w/ IDENT authentication |
Date: | 2004-07-26 16:42:23 |
Message-ID: | ce3c9f$com$1@sea.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Tom Lane wrote:
>
> Is it possible that jdbc tries to use an IPv6 rather than IPv4
> connection in your setup?
I just tried it with "jdbc:postgresql://127.0.0.1/tomcat4" with the same
result.
> It might be worth looking in the postmaster's stderr log to see if any
> more information about the connection failure is there. We often log
> information that we don't report to the client for security reasons.
Where can I find this log?
I've cranked up the logging verbosity in postgresql.conf:
#syslog = 0 # range 0-2; 0=stdout; 1=both; 2=syslog
syslog = 2
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'
# - When to Log -
#client_min_messages = notice # Values, in order of decreasing detail:
# debug5, debug4, debug3, debug2, debug1,
# log, info, notice, warning, error
client_min_messages = debug5
#log_min_messages = notice # Values, in order of decreasing detail:
# debug5, debug4, debug3, debug2, debug1,
# info, notice, warning, error, log, fatal,
# panic
log_min_messages = debug5
#log_error_verbosity = default # terse, default, or verbose messages
log_error_verbosity = verbose
#log_min_error_statement = panic # Values in order of increasing severity:
# debug5, debug4, debug3, debug2, debug1,
# info, notice, warning, error, panic(off)
log_min_error_statement = debug5
#log_min_duration_statement = -1 # Log all statements whose
# execution time exceeds the value, in
# milliseconds. Zero prints all queries.
# Minus-one disables.
#silent_mode = false # DO NOT USE without Syslog!
# - What to Log -
#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false
#log_connections = false
log_connections = true
#log_duration = false
#log_pid = false
#log_statement = false
#log_timestamp = false
#log_hostname = false
#log_source_port = false
All I see in the syslog for a failed connection is:
Jul 26 11:22:48 home postgres[24968]: [30-1] LOG: 00000: connection
received: host=127.0.0.1 port=34676
Jul 26 11:22:48 home postgres[24968]: [30-2] LOCATION: BackendFork,
postmaster.c:2395
Jul 26 11:22:51 home postgres[24968]: [31-1] FATAL: 28000: IDENT
authentication failed for user "tomcat4"
Jul 26 11:22:51 home postgres[24968]: [31-2] LOCATION: auth_failed,
auth.c:395
This doesn't tell me anything that I didn't already know.
--
========================================================================
Ian Pilcher i(dot)pilcher(at)comcast(dot)net
========================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-07-26 17:09:09 | Re: Charset problem on WHERE clause |
Previous Message | dgr | 2004-07-26 16:13:50 | SSL Connection Problems |