Hi List
With the new increased verbosity I managed to turn on, I've found something
interesting.
This was my definition in /etc/odbc.ini:
---
[ODBC Data Sources]
pgdb=PostgreSQL
[pgdb-cdr]
Driver = /usr/pgsql-9.4/lib/psqlodbc.so
ServerName=/tmp
Port=5432
UserName=asteriskcdruser
Password=1ndestruc#
Database=asteriskcdrdb
ReadOnly=No
Protocol=9.4
Trace=Yes
TraceFile=/tmp/odbc.log
ForceTrace=Yes
ConnSettings=
DSN=pgdb
ServerType=Postgres
Debug=1
DebugFile=/var/log/postgresql_debug.log
---
running
---
isql -v pgdb-cdr dbuser pass
---
gives in pg_log/postgresql-Tue.log the relevant error
---
< 2015-07-21 09:04:35.850 SAST >LOCATION: PerformAuthentication,
postinit.c:258
< 2015-07-21 09:04:35.856 SAST >LOG: 08006: could not send data to client:
Broken pipe
---
However, removing these two lines from /etc/odbc.ini
---
DSN=pgdb
ServerType=Postgres
---
changes the logged output to this
---
< 2015-07-21 09:21:24.018 SAST >LOG: 00000: connection received:
host=[local]
< 2015-07-21 09:21:24.018 SAST >LOCATION: BackendInitialize,
postmaster.c:4007
< 2015-07-21 09:21:24.019 SAST >LOG: 00000: connection authorized:
user=asteriskcdruser database=asteriskcdrdb
< 2015-07-21 09:21:24.019 SAST >LOCATION: PerformAuthentication,
postinit.c:258
< 2015-07-21 09:21:24.022 SAST >LOG: 00000: disconnection: session time:
0:00:00.004 user=asteriskcdruser database=asteriskcdrdb host=[local]
< 2015-07-21 09:21:24.022 SAST >LOCATION: log_disconnections,
postgres.c:4511
---
e. g. now the "broken pipe" error is gone, but I just get a virtually
instant disconnection.
The isql output remains the same:
---
# isql -v pgdb-cdr dbuser dbname
[S1000][unixODBC]The database does not exist on the server
or user authentication failed.
[ISQL]ERROR: Could not SQLConnect
---
but it appears that the REASON is now gone, e. g. no "broken pipe" logged by
Postgres?
This mean anything to anybody?
Thanks
Stefan
