Thread: ERROR: xlog flush request 17/4D6C2720 is not satisfied
hi
My Postgres Server reports the next error message in log files.
“ERROR: xlog flush request 17/4D6C2720 is not satisfied --- flushed only to 17/4CE03418”
Although Server up, Postgres does not function as expected - simple commands like “select * from <table>” or “drop database” fails with this error
What is the cause ? how can I overcome?
Thanks,
Yuval Sofer
BMC Software
CTM&D Business Unit
DBA Team
972-52-4286-282
On Sun, Nov 28, 2010 at 6:37 AM, Sofer, Yuval <Yuval_Sofer@bmc.com> wrote: > Although Server up, Postgres does not function as expected - simple commands > like “select * from <table>” or “drop database” fails with this error > What happened to your postgres server recently? Did it crash? Did you have a hardware failure? Did the whole server crash? Did someone kill -9 postgres? For real help, we need details about what hardware you've got (particularly on what disk subsystem is attached for the postgres data), which OS + version you are running, and which version of postgres.
On Sun, Nov 28, 2010 at 4:37 AM, Sofer, Yuval <Yuval_Sofer@bmc.com> wrote: > hi > > My Postgres Server reports the next error message in log files. > > “ERROR: xlog flush request 17/4D6C2720 is not satisfied --- flushed only to > 17/4CE03418” > > Although Server up, Postgres does not function as expected - simple commands > like “select * from <table>” or “drop database” fails with this error > > What is the cause ? how can I overcome? Drive full?
Hi The problem occurred in customer site DB - Postgres version 8.2.4 OS - windows Server 2008 R2 He reported about storage problems which triggered node switch (it is postgres installation on windows 2008 cluster) But now although postgres.exe is running, it is not really functioning… Yuval -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Vick Khera Sent: Monday, November 29, 2010 2:47 AM To: pgsql-general Subject: Re: [GENERAL] ERROR: xlog flush request 17/4D6C2720 is not satisfied On Sun, Nov 28, 2010 at 6:37 AM, Sofer, Yuval <Yuval_Sofer@bmc.com> wrote: > Although Server up, Postgres does not function as expected - simple commands > like “select * from <table>” or “drop database” fails with this error > What happened to your postgres server recently? Did it crash? Did you have a hardware failure? Did the whole server crash? Did someone kill -9 postgres? For real help, we need details about what hardware you've got (particularly on what disk subsystem is attached for the postgres data), which OS + version you are running, and which version of postgres. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
No, many free GBs on drive... More info: The problem occurred in customer site DB - Postgres version 8.2.4 OS - windows Server 2008 R2 He reported about storage problems which triggered node switch (it is postgres installation on windows 2008 cluster) Butnow although postgres.exe is running, it is not really functioning… Thanks -----Original Message----- From: Scott Marlowe [mailto:scott.marlowe@gmail.com] Sent: Monday, November 29, 2010 3:54 AM To: Sofer, Yuval Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] ERROR: xlog flush request 17/4D6C2720 is not satisfied On Sun, Nov 28, 2010 at 4:37 AM, Sofer, Yuval <Yuval_Sofer@bmc.com> wrote: > hi > > My Postgres Server reports the next error message in log files. > > “ERROR: xlog flush request 17/4D6C2720 is not satisfied --- flushed only to > 17/4CE03418” > > Although Server up, Postgres does not function as expected - simple commands > like “select * from <table>” or “drop database” fails with this error > > What is the cause ? how can I overcome? Drive full?
2010/11/29 Sofer, Yuval <Yuval_Sofer@bmc.com>: > He reported about storage problems which triggered node switch (it is postgres installation on windows 2008 cluster) > But now although postgres.exe is running, it is not really functioning… > Sounds to me like your clustering software caused some data loss/corruption. Have you ever tested cluster failover before putting it in production? Did it cause this problem then?