Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: SIGSEGV happens over once a day
- From: Tomasz Ostrowski <tometzky(at)batory(dot)org(dot)pl>
- To: Richard Yen <richyen(at)iparadigms(dot)com>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: SIGSEGV happens over once a day
- Date: Mon, 15 May 2006 12:51:57 +0200
- Message-id: <20060515105156.GA18840@batory.org.pl> <text/plain>
On Thu, 11 May 2006, Richard Yen wrote:
> I'm experiencing signal 11 (segmentation fault) failures on the
> master node of a 3-node Slony-I cluster. In the past week, we've
> averaged a little more than one segfault per day (11 times in the
> past 10, including today). Any ideas what's going on?
Looks like hardware error. Failed fan. Processor/RAM/HDD overheating.
Try "memtest86" and "cpuburn" testing for several hours.
Regards
Tometzky
--
...although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
Winnie the Pooh
- References:
- SIGSEGV happens over once a day
- From: Richard Yen
- SIGSEGV happens over once a day
- Prev by Date: postgresql-[any version] from FreeBSD ports - startup problems after crash
- Next by Date: Re: BUG #2439: pgAdmin III v1.4.1 fails to compile with GCC 4.1.0
- Previous by thread: Re: SIGSEGV happens over once a day
- Next by thread: possible bug in SELECT with UNION
- Indexes: