Thread: PostgreSQL 9.0.4 crashing
PostgreSQL 9.0.4 is crashing intermittently in Windows 2008 R2 environment with following error in log file.
2012-05-31 03:15:54 IST LOG: server process (PID 49972) was terminated by exception 0xC000012D
2012-05-31 03:15:54 IST HINT: See C include file "ntstatus.h" for a description of the hexadecimal value.
2012-05-31 03:15:54 IST LOG: terminating any other active server processes
2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of another server process
2012-05-31 03:15:54 IST 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.
2012-05-31 03:15:54 IST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of another server process
I could find a related, known issue with 8.3.9 with ref. 5965; Is this issue fixed in 9.0.4?
Please help.
Regards,
Abhilash R
On Thu, May 31, 2012 at 4:57 AM, R, Abhilash (HP Software) <abhilash.r@hp.com> wrote: > PostgreSQL 9.0.4 is crashing intermittently in Windows 2008 R2 environment > with following error in log file. > > > > 2012-05-31 03:15:54 IST LOG: server process (PID 49972) was terminated by > exception 0xC000012D > > 2012-05-31 03:15:54 IST HINT: See C include file "ntstatus.h" for a > description of the hexadecimal value. > > 2012-05-31 03:15:54 IST LOG: terminating any other active server processes > > 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of > another server process > > 2012-05-31 03:15:54 IST 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. > > 2012-05-31 03:15:54 IST HINT: In a moment you should be able to reconnect > to the database and repeat your command. > > 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of > another server process > > > > I could find a related, known issue with 8.3.9 with ref. 5965; Is this > issue fixed in 9.0.4? After some googling I'm seeing some hints that you may have overcommitted virtual memory. How much memory do you have and what's shared buffers set to? Is this 32/64 bit? merlin
On 05/31/12 2:57 AM, R, Abhilash (HP Software) wrote: > 2012-05-31 03:15:54 IST LOG: server process (PID 49972) was > terminated by exception 0xC000012D Out of virtual memory Error exception 0xC000012D Your system is low on virtual memory. To ensure that Windows runs correctly, increase the size of your virtual memory paging file. For more information, see Help. thats the description of that fault code from MS Windows. so, something you did in server process 49972 ate up more memory than was available. a query that returns a huge result set can do this as the result set has to be collected in memory before it can be returned to the client. -- john r pierce N 37, W 122 santa cruz ca mid-left coast
It's an 8 CPU, 16GB RAM box with swap space configured to 24 GB. I could see windows Resource-Exhaustion Detector errors in event viewer saying - " Windows successfully diagnosed a low virtualmemory condition." around the time when postgreSQL crashed. Can this cause the crash? shared_buffers = 32MB It's a 64 bit box. Regards, Abhilash R -----Original Message----- From: Merlin Moncure [mailto:mmoncure@gmail.com] Sent: Friday, June 01, 2012 2:45 AM To: R, Abhilash (HP Software) Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] PostgreSQL 9.0.4 crashing On Thu, May 31, 2012 at 4:57 AM, R, Abhilash (HP Software) <abhilash.r@hp.com> wrote: > PostgreSQL 9.0.4 is crashing intermittently in Windows 2008 R2 environment > with following error in log file. > > > > 2012-05-31 03:15:54 IST LOG: server process (PID 49972) was terminated by > exception 0xC000012D > > 2012-05-31 03:15:54 IST HINT: See C include file "ntstatus.h" for a > description of the hexadecimal value. > > 2012-05-31 03:15:54 IST LOG: terminating any other active server processes > > 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of > another server process > > 2012-05-31 03:15:54 IST 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. > > 2012-05-31 03:15:54 IST HINT: In a moment you should be able to reconnect > to the database and repeat your command. > > 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of > another server process > > > > I could find a related, known issue with 8.3.9 with ref. 5965; Is this > issue fixed in 9.0.4? After some googling I'm seeing some hints that you may have overcommitted virtual memory. How much memory do you have and what's shared buffers set to? Is this 32/64 bit? merlin
What's work_mem and maintenance_work_mem set to? On Thu, May 31, 2012 at 10:30 PM, R, Abhilash (HP Software) <abhilash.r@hp.com> wrote: > It's an 8 CPU, 16GB RAM box with swap space configured to 24 GB. > > I could see windows Resource-Exhaustion Detector errors in event viewer saying - " Windows successfully diagnosed a lowvirtual memory condition." around the time when postgreSQL crashed. Can this cause the crash? > > shared_buffers = 32MB > > It's a 64 bit box. > > Regards, > Abhilash R > > -----Original Message----- > From: Merlin Moncure [mailto:mmoncure@gmail.com] > Sent: Friday, June 01, 2012 2:45 AM > To: R, Abhilash (HP Software) > Cc: pgsql-general@postgresql.org > Subject: Re: [GENERAL] PostgreSQL 9.0.4 crashing > > On Thu, May 31, 2012 at 4:57 AM, R, Abhilash (HP Software) > <abhilash.r@hp.com> wrote: >> PostgreSQL 9.0.4 is crashing intermittently in Windows 2008 R2 environment >> with following error in log file. >> >> >> >> 2012-05-31 03:15:54 IST LOG: server process (PID 49972) was terminated by >> exception 0xC000012D >> >> 2012-05-31 03:15:54 IST HINT: See C include file "ntstatus.h" for a >> description of the hexadecimal value. >> >> 2012-05-31 03:15:54 IST LOG: terminating any other active server processes >> >> 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of >> another server process >> >> 2012-05-31 03:15:54 IST 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. >> >> 2012-05-31 03:15:54 IST HINT: In a moment you should be able to reconnect >> to the database and repeat your command. >> >> 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of >> another server process >> >> >> >> I could find a related, known issue with 8.3.9 with ref. 5965; Is this >> issue fixed in 9.0.4? > > After some googling I'm seeing some hints that you may have > overcommitted virtual memory. How much memory do you have and what's > shared buffers set to? Is this 32/64 bit? > > merlin > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- To understand recursion, one must first understand recursion.
work_mem = 16MB not specificied the maintenance_work_mem setting in conf file(I thnk the default will work here and the value is 16MB?) Regards, Abhilash R -----Original Message----- From: Scott Marlowe [mailto:scott.marlowe@gmail.com] Sent: Friday, June 01, 2012 8:23 PM To: R, Abhilash (HP Software) Cc: Merlin Moncure; pgsql-general@postgresql.org Subject: Re: [GENERAL] PostgreSQL 9.0.4 crashing What's work_mem and maintenance_work_mem set to? On Thu, May 31, 2012 at 10:30 PM, R, Abhilash (HP Software) <abhilash.r@hp.com> wrote: > It's an 8 CPU, 16GB RAM box with swap space configured to 24 GB. > > I could see windows Resource-Exhaustion Detector errors in event viewer saying - " Windows successfully diagnosed a lowvirtual memory condition." around the time when postgreSQL crashed. Can this cause the crash? > > shared_buffers = 32MB > > It's a 64 bit box. > > Regards, > Abhilash R > > -----Original Message----- > From: Merlin Moncure [mailto:mmoncure@gmail.com] > Sent: Friday, June 01, 2012 2:45 AM > To: R, Abhilash (HP Software) > Cc: pgsql-general@postgresql.org > Subject: Re: [GENERAL] PostgreSQL 9.0.4 crashing > > On Thu, May 31, 2012 at 4:57 AM, R, Abhilash (HP Software) > <abhilash.r@hp.com> wrote: >> PostgreSQL 9.0.4 is crashing intermittently in Windows 2008 R2 environment >> with following error in log file. >> >> >> >> 2012-05-31 03:15:54 IST LOG: server process (PID 49972) was terminated by >> exception 0xC000012D >> >> 2012-05-31 03:15:54 IST HINT: See C include file "ntstatus.h" for a >> description of the hexadecimal value. >> >> 2012-05-31 03:15:54 IST LOG: terminating any other active server processes >> >> 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of >> another server process >> >> 2012-05-31 03:15:54 IST 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. >> >> 2012-05-31 03:15:54 IST HINT: In a moment you should be able to reconnect >> to the database and repeat your command. >> >> 2012-05-31 03:15:54 IST WARNING: terminating connection because of crash of >> another server process >> >> >> >> I could find a related, known issue with 8.3.9 with ref. 5965; Is this >> issue fixed in 9.0.4? > > After some googling I'm seeing some hints that you may have > overcommitted virtual memory. How much memory do you have and what's > shared buffers set to? Is this 32/64 bit? > > merlin > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- To understand recursion, one must first understand recursion.