Thread: Connections Crashing
Hi,
We are using Postgres 8.3.1 binary distribution, and copying the same along with software installation.
From last some time we have started getting error as message dialog showing error 0xC0000142 and after that, connections are crashing.
Windows login is administrator user and Postgres user, we are creating before hand.
Postgres logs shows following
LOG: execute <unnamed>: select stpsetting0_.NF_DEVICE_ID as NF14_1_, stpsetting0_.ID as ID1_, stpsetting0_.ID as ID74_0_, stpsetting0_.NF_ENABLED as NF2_74_0_, stpsetting0_.NF_BASE_TYPE as NF3_74_0_, stpsetting0_.NF_PROTOCOL_SPECS as NF4_74_0_, stpsetting0_.NF_PRIORITY as NF5_74_0_, stpsetting0_.NF_VLAN_ID as NF6_74_0_, stpsetting0_.NF_OPTION1 as NF7_74_0_, stpsetting0_.NF_OPTION2 as NF8_74_0_, stpsetting0_.NF_HOLD_TIME as NF9_74_0_, stpsetting0_.NF_FORWARD_DELAY as NF10_74_0_, stpsetting0_.NF_BRIDGE_MAX_AGE as NF11_74_0_, stpsetting0_.NF_BRIDGE_HELLO_TIME as NF12_74_0_, stpsetting0_.NF_BRIDGE_FORWARD_DELAY as NF13_74_0_, stpsetting0_.NF_DEVICE_ID as NF14_74_0_ from networkManager.NT_STP_SETTINGS stpsetting0_ where stpsetting0_.NF_DEVICE_ID=$1
DETAIL: parameters: $1 = '6698'
LOG: execute S_2: COMMIT
LOG: server process (PID 8156) was terminated by exception 0xC0000142
HINT: See C include file "ntstatus.h" for a description of the hexadecimal value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
What can be possible reasons for that and whats the solution.
Thanks,
Shahbaz A. Tyagi wrote: > We are using Postgres 8.3.1 binary distribution, and copying the same along > with software installation. Can you reproduce this with a more recent version of 8.3 (8.3.7 is current). > From last some time we have started getting error as message dialog showing > error 0xC0000142 and after that, connections are crashing. > LOG: server process (PID 8156) was terminated by exception 0xC0000142 > > HINT: See C include file "ntstatus.h" for a description of the hexadecimal > value. A bit of googling suggests this is STATUS_DLL_INIT_FAILED, and although I'm not a Windows expert I'd expect that to be an error you only see on startup, rather than after PostgreSQL has been running for a while. Could it be an anti-virus package interfering? Do you have any more information on the situation? Are the machines running XP/Vista/Server 2003? Do you only see it on 32/64-bit? Do some machines show this problem while others are OK? -- Richard Huxton Archonet Ltd
Hi, Its not happening in all the machines, its only some machines. I am testing on XP 32 bit. Its coming only while running Postgres and accessing the DB. Strange part is that some machines are getting restarted as soon as it gets the error. Thanks, -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Richard Huxton Sent: Thursday, May 14, 2009 1:59 AM To: Shahbaz A. Tyagi Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Connections Crashing Shahbaz A. Tyagi wrote: > We are using Postgres 8.3.1 binary distribution, and copying the same along > with software installation. Can you reproduce this with a more recent version of 8.3 (8.3.7 is current). > From last some time we have started getting error as message dialog showing > error 0xC0000142 and after that, connections are crashing. > LOG: server process (PID 8156) was terminated by exception 0xC0000142 > > HINT: See C include file "ntstatus.h" for a description of the hexadecimal > value. A bit of googling suggests this is STATUS_DLL_INIT_FAILED, and although I'm not a Windows expert I'd expect that to be an error you only see on startup, rather than after PostgreSQL has been running for a while. Could it be an anti-virus package interfering? Do you have any more information on the situation? Are the machines running XP/Vista/Server 2003? Do you only see it on 32/64-bit? Do some machines show this problem while others are OK? -- Richard Huxton Archonet Ltd -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On Wed, May 13, 2009 at 4:22 PM, Shahbaz A. Tyagi <shahbaz.tyagi@sphere.ae> wrote: > Hi, > > Its not happening in all the machines, its only some machines. I am testing > on XP 32 bit. Its coming only while running Postgres and accessing the DB. > > Strange part is that some machines are getting restarted as soon as it gets > the error. So, do you have antivirus on these machines or not?
AntiVirus is not running. -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Scott Marlowe Sent: Thursday, May 14, 2009 3:35 AM To: Shahbaz A. Tyagi Cc: Richard Huxton; pgsql-general@postgresql.org Subject: Re: [GENERAL] Connections Crashing On Wed, May 13, 2009 at 4:22 PM, Shahbaz A. Tyagi <shahbaz.tyagi@sphere.ae> wrote: > Hi, > > Its not happening in all the machines, its only some machines. I am testing > on XP 32 bit. Its coming only while running Postgres and accessing the DB. > > Strange part is that some machines are getting restarted as soon as it gets > the error. So, do you have antivirus on these machines or not? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Shahbaz A. Tyagi wrote: > Hi, > > Its not happening in all the machines, its only some machines. I am testing > on XP 32 bit. Its coming only while running Postgres and accessing the DB. > > Strange part is that some machines are getting restarted as soon as it gets > the error. You mean the whole machine crashes and restarts? That shouldn't even be possible. >> From last some time we have started getting error as message dialog > showing >> error 0xC0000142 and after that, connections are crashing. > >> LOG: server process (PID 8156) was terminated by exception 0xC0000142 It's probably worth making sure you are logging connections (log_connections) and are recording the PID in the log-lines (log_line_prefix). http://www.postgresql.org/docs/8.3/interactive/runtime-config-logging.html Presumably this error is occuring when a new connection is made, but it would be sensible to make sure. -- Richard Huxton Archonet Ltd