This is a multi-part message in MIME format.
------_=_NextPart_001_01C9DED3.758738E6
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
We're using postgresql-8.3.5-1.
Lately, once in a while, the PostgreSQL service crashes and the
following appears in the log. Any idea what could cause that?
I believe there are two problems here: one is the process 2604 exiting
with code 128, and the other one is the re-initialization failure with
the following fatal message: "BST FATAL: pre-existing shared memory
block is still in use".
2009-05-27 10:39:41 BST LOG: server process (PID 2604) exited with exit
code 128
2009-05-27 10:39:41 BST LOG: terminating any other active server
processes
2009-05-27 10:39:41 BST WARNING: terminating connection because of
crash of another server process
2009-05-27 10:39:41 BST 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.
2009-05-27 10:39:41 BST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2009-05-27 10:39:41 BST WARNING: terminating connection because of
crash of another server process
2009-05-27 10:39:41 BST 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.
2009-05-27 10:39:41 BST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2009-05-27 10:39:41 BST WARNING: terminating connection because of
crash of another server process
2009-05-27 10:39:41 BST 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.
2009-05-27 10:39:41 BST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2009-05-27 10:39:41 BST WARNING: terminating connection because of
crash of another server process
2009-05-27 10:39:41 BST 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.
2009-05-27 10:39:41 BST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2009-05-27 10:39:41 BST WARNING: terminating connection because of
crash of another server process
2009-05-27 10:39:41 BST 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.
2009-05-27 10:39:41 BST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2009-05-27 10:39:41 BST WARNING: terminating connection because of
crash of another server process
2009-05-27 10:39:41 BST 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.
2009-05-27 10:39:41 BST HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2009-05-27 10:39:41 BST LOG: all server processes terminated;
reinitializing
2009-05-27 10:39:42 BST FATAL: pre-existing shared memory block is
still in use
2009-05-27 10:39:42 BST HINT: Check if there are any old server
processes still running, and terminate them.
Thanks,
Moshe.
The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
************************************************************ ************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************ ************************
------_=_NextPart_001_01C9DED3.758738E6
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
[at] font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
[at] font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
..MsoChpDefault
{mso-style-type:export-only;}
[at] page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal>Hi,<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>We’re using =
postgresql-8.3.5-1.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Lately, once in a while, the PostgreSQL service =
crashes and
the following appears in the log. Any idea what could cause =
that?<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>I believe there are two problems here: one is the =
process
2604 exiting with code 128, and the other one is the re-initialization =
failure
with the following fatal message: “BST FATAL: pre-existing =
shared memory
block is still in use”.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST LOG: server process (PID 2604) exited with exit code =
128<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST LOG: terminating any other active server =
processes<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another =
server process<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST 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.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the =
database and
repeat your command.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another =
server process<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST 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.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the =
database and
repeat your command.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another =
server process<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST 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.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the =
database and
repeat your command.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another =
server process<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST 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.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the =
database and
repeat your command.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another =
server process<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST 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.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the =
database and
repeat your command.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another =
server process<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST 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.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the =
database and
repeat your command.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:41
BST LOG: all server processes terminated; =
reinitializing<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:42
BST FATAL: pre-existing shared memory block is still in =
use<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>2009-05-27 10:39:42
BST HINT: Check if there are any old server processes still =
running, and
terminate them.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'><o:p> </o:p></span></p>
<p class=3DMsoNormal>Thanks,<o:p></o:p></p>
<p class=3DMsoNormal>Moshe.<o:p></o:p></p>
</div>
</body>
<br><br>
The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.<br>
<br><br>
<br> <br> ************************************************************ ************************<br>This footnote confirms that this email message has been scanned by<br>PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.<br> ************************************************************ ************************<br><br>
</html>
------_=_NextPart_001_01C9DED3.758738E6--
