pg.ddx.io pgsql-testers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Mark Watson <mark.watson@jurisconcept.ca>
To: 'Greg Smith' <greg@2ndquadrant.com>
Cc: pgsql-testers@postgresql.org
Subject: Re: 9.1Beta1 - Repeatable Crash on Windows
Date: Tue, 10 May 2011 08:15:30 -0400
Message-ID: <CD8A2AD4ACBE464CAD8929DAA6DFD39C@Gateway> (raw )
In-Reply-To: <4DC88CFF.9020301@2ndquadrant.com >
References: <BANLkTikq8DrkJho-533tHRq3uDc9kjQrNQ@mail.gmail.com >
<4DC85DF3.9030105@agliodbs.com >
<BANLkTi=Z6M2CbFGrrxqyVZZp4q4Ugho6ZQ@mail.gmail.com >
<4DC86132.20604@agliodbs.com >
<4DC87067.4050101@2ndQuadrant.com >
<BANLkTi=JcpNNEZafZFdLYBqMpOFi_kB57w@mail.gmail.com >
<4DC88CFF.9020301@2ndquadrant.com >
-----Message d'origine-----
De : pgsql-testers-owner@postgresql.org [mailto:pgsql-testers-owner@postgresql.org] De la part de Greg Smith
Envoyé : 9 mai 2011 20:55
À : Richard Broersma
Cc : pgsql-testers@postgresql.org
Objet : Re: [TESTERS] 9.1Beta1 - Repeatable Crash on Windows
Richard Broersma wrote:
> Here is what the logs show:
>
> 2011-05-09 07:49:37 PDT LOG: server process (PID 2848) was terminated
> by exception 0xC0000005
>
Too bad, that's just a generic "accessed memory you shouldn't have"
exception. Not much help narrowing down the source. That could be a
driver or hardware issue, but since you say it's repeatable that seems
less likely.
At this point, fork in the road. If someone else can reproduce this on
another Windows system, they may be able to run with it. But if you can
spare some time to dig further, the instructions at
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
go over how to trace into where it's actually failing at yourself. If
you run PostgreSQL on Windows, that's good defensive practice to fit in
on a day it's not an emergency to do so. (The same is true of any
platform, it just takes more time to setup on Windows)
------------------------
I can reproduce the same exception in another manner. I tried to get a stack trace but cannot seem to attach to the process using either process explorer or WinDBG. I reproduced this using the current beta pgAdmin by right-clicking on Login Roles, select New login role, Role name test, password testp, and selecting all role privliges then OK. The service crashes. PID 5432 below is the pgAdmin process.
My log file (sorry about the French):
2011-05-10 08:00:26 EDT LOG: processus serveur (PID 5432) a été arrêté par l'exception 0xC0000005
2011-05-10 08:00:26 EDT ASTUCE : Voir le fichier d'en-tête C « ntstatus.h » pour une description de la valeur
hexadécimale.
2011-05-10 08:00:26 EDT LOG: arrêt des autres processus serveur actifs
2011-05-10 08:00:26 EDT ATTENTION: arrêt de la connexion à cause de l'arrêt brutal d'un autre processus serveur
2011-05-10 08:00:26 EDT DÉTAIL: Le postmaster a commandé à ce processus serveur d'annuler la transaction
courante et de quitter car un autre processus serveur a quitté anormalement
et qu'il existe probablement de la mémoire partagée corrompue.
2011-05-10 08:00:26 EDT ASTUCE : Dans un moment, vous devriez être capable de vous reconnecter à la base de
données et de relancer votre commande.
2011-05-10 08:00:26 EDT ATTENTION: arrêt de la connexion à cause de l'arrêt brutal d'un autre processus serveur
2011-05-10 08:00:26 EDT DÉTAIL: Le postmaster a commandé à ce processus serveur d'annuler la transaction
courante et de quitter car un autre processus serveur a quitté anormalement
et qu'il existe probablement de la mémoire partagée corrompue.
2011-05-10 08:00:26 EDT ASTUCE : Dans un moment, vous devriez être capable de vous reconnecter à la base de
données et de relancer votre commande.
2011-05-10 08:00:26 EDT LOG: tous les processus serveur se sont arrêtés, réinitialisation
2011-05-10 08:00:36 EDT FATAL: le bloc de mémoire partagé pré-existant est toujours en cours d'utilisation
2011-05-10 08:00:36 EDT ASTUCE : Vérifier s'il n'y a pas de vieux processus serveur en cours d'exécution. Si c'est le
cas, fermez-les.
- Mark Watson
view thread (19+ messages) latest in thread
Message-ID: <CD8A2AD4ACBE464CAD8929DAA6DFD39C@Gateway>
Permalink: ../CD8A2AD4ACBE464CAD8929DAA6DFD39C@Gateway/
Also on: postgresql.org/message-id/CD8A2AD4ACBE464CAD8929DAA6DFD39C@Gateway
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-testers@postgresql.org
Cc: mark.watson@jurisconcept.ca, greg@2ndquadrant.com
Subject: Re: 9.1Beta1 - Repeatable Crash on Windows
In-Reply-To: <CD8A2AD4ACBE464CAD8929DAA6DFD39C@Gateway>
References: <BANLkTikq8DrkJho-533tHRq3uDc9kjQrNQ@mail.gmail.com> <4DC85DF3.9030105@agliodbs.com> <BANLkTi=Z6M2CbFGrrxqyVZZp4q4Ugho6ZQ@mail.gmail.com> <4DC86132.20604@agliodbs.com> <4DC87067.4050101@2ndQuadrant.com> <BANLkTi=JcpNNEZafZFdLYBqMpOFi_kB57w@mail.gmail.com> <4DC88CFF.9020301@2ndquadrant.com> <CD8A2AD4ACBE464CAD8929DAA6DFD39C@Gateway>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox