|
Name: Dennis
Huebner Email: [EMAIL PROTECTED] PostgreSQL
version: 8.0 Operation
system: Windows
XP Professional Short
description: No connection to Server Hi
there, I
have trouble with newer versions of postgresql. On
every version of postgresql the only thing I changed at the 'postgresql.conf'
is 'max_connections = 500'. Otherwise
I used default installation. I'm
using a telephony-system with 30 lines and I generate calls to this system. Now
the system looks into the postgres-database if the calling number is present
and after that receives the calls. With
every older postgres-version up to 8.0.0-rc3 (this is the last working version)
everything is all right. The
database-system checks for the user and gives back the results. This
works on all 30 lines parallel. On
newer versions (higher than rc3) the connections were refused or could not be
established by the server. Here
is my pg_log file: 2005-02-02
14:28:55 LOG: database system was shut
down at 2005-02-02 14:28:54 W. 2005-02-02
14:28:55 LOG: checkpoint record is at
0/CB9A70 2005-02-02
14:28:55 LOG: redo record is at 0/CB9A70;
undo record is at 0/0; shutdown TRUE 2005-02-02
14:28:55 LOG: next transaction ID: 1548;
next OID: 17948 2005-02-02
14:28:56 LOG: database system is ready 2005-02-02
14:30:45 LOG: server process (PID 5972)
exited with unexpected status 128 2005-02-02
14:30:45 LOG: terminating any other
active server processes 2005-02-02
14:30:45 WARNING: terminating connection
because of crash of another server process 2005-02-02
14:30:45 DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server process exited abnormally and possibly corrupted shared
memory. 2005-02-02
14:30:45 HINT: In a moment you should be
able to reconnect to the database and repeat your command. . Several
times... . 2005-02-02
14:30:45 WARNING: terminating connection
because of crash of another server process 2005-02-02
14:30:45 DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit, because
another server process exited abnormally and possibly corrupted shared memory. 2005-02-02
14:30:45 HINT: In a moment you should be
able to reconnect to the database and repeat your command. 2005-02-02
14:30:45 LOG: all server processes
terminated; reinitializing 2005-02-02
14:30:45 LOG: database system was
interrupted at 2005-02-02 14:28:56 W. 2005-02-02
14:30:45 LOG: checkpoint record is at
0/CB9A70 2005-02-02
14:30:45 LOG: redo record is at
0/CB9A70; undo record is at 0/0; shutdown TRUE 2005-02-02
14:30:45 LOG: next transaction ID: 1548;
next OID: 17948 2005-02-02
14:30:45 LOG: database system was not
properly shut down; automatic recovery in progress 2005-02-02
14:30:45 LOG: record with zero length at
0/CB9AB0 2005-02-02
14:30:45 LOG: redo is not required 2005-02-02
14:30:45 FATAL: the database system is
starting up 2005-02-02
14:30:45 LOG: database system is ready I
hope you can help me. Kind regards, |
