Toon posts:

PostgreSQL op Windows 2003 standaard server

Pagina: 1
Acties:

Verwijderd

Topicstarter
LS,

Ik heb een Windows 2003 server draaien met IIS6, MYSQL en POSTGRESQL.
Nu heb ik het al drie keer gehad in 2 dagen dat de postmaster service van POSTGRESQL gestopt is, zie hier de melding in event log:

The description for Event ID ( 0 ) in Source ( postmaster ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: postmaster : Win32 Process Id = 0xA44 : Cygwin Process Id = 0xA44 : `postmaster' service stopped.

En deze in postgresql log:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
DEBUG: all server processes terminated; reinitializing shared memory and semaphores
IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough core

This error usually means that PostgreSQL's request for a shared
memory segment exceeded available memory or swap space.
To reduce the request size (currently 1441792 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 64) and/or
its max_connections parameter (currently 32).

The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.

DEBUG: database system was interrupted at 2005-02-02 17:24:47 WEST
DEBUG: checkpoint record is at 0/A062340
DEBUG: redo record is at 0/A062340; undo record is at 0/0; shutdown FALSE
DEBUG: next transaction id: 80845; next oid: 133048
DEBUG: database system was not properly shut down; automatic recovery in progress
DEBUG: ReadRecord: record with zero length at 0/A062380
DEBUG: redo is not required
DEBUG: database system is ready


Service starten en er is geen probleem meer.
Hebben jullie dit ook wel eens gehad?

Alvast bedankt voor de reacties!

[ Voor 52% gewijzigd door Verwijderd op 03-02-2005 12:35 ]


  • richard_kraal
  • Registratie: September 2001
  • Laatst online: 24-03-2025
wat voor server is het?

geheugen brak?

Verwijderd

Move PNS > SA

Verwijderd

Topicstarter
richardkraal schreef op donderdag 03 februari 2005 @ 14:15:
wat voor server is het?

geheugen brak?
DL380
Geheugen is prima.
Denk zelf ergens een config fout in POSTGRESQL???