Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
On Thu, Mar 01, 2007 at 08:32:57AM -0500, Merlin Moncure wrote: > > Following an emergency downgrade back to 8.1, the kernel panics went > away. Note that I don't believe for a second that the database was > the root cause here...research suggest that the problem is due to some > type of bug in the scsi driver. Exactly why 8.2 brings this out is a > mystery...working on getting an enterprise kernel on the server. Probably it's pushing some part of the I/O system harder than 8.1, thus exposing the bug faster. //Magnus ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
On 2/26/07, Merlin Moncure <[EMAIL PROTECTED]> wrote: On 2/23/07, Tom Lane <[EMAIL PROTECTED]> wrote: > "Merlin Moncure" <[EMAIL PROTECTED]> writes: > > On friday we upgraded a critical backend server to postgresql 8.2 > > running on fedora core 4. > > Umm ... why that particular choice of OS? Red Hat dropped update > support for FC4 some time ago, and AFAIK the Fedora Legacy project > is not getting things done. How old is the kernel you're using? Linux mojo 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 i686 i386 GNU/Linux Unfortunately, the decision about which kernel to run is more or less out of my hands. I would personally really dislike fedora and would much prefer to be running centos/redhat as. That said, your comments and those of others are very helpul in regards to fixing that. we tried update to the latest via yum update with no help. as promised, here is the best photo of the panic we could get: http://img144.imageshack.us/my.php?image=dumpic6.jpg We did an emergency downgrade to 8.1 and will monitor the situation...the decision to get a new server has already been made and hopefully it will be on a more stable platform. big thanks to all who took a few minutes out of their day to lend a hand. Following an emergency downgrade back to 8.1, the kernel panics went away. Note that I don't believe for a second that the database was the root cause here...research suggest that the problem is due to some type of bug in the scsi driver. Exactly why 8.2 brings this out is a mystery...working on getting an enterprise kernel on the server. merlin ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
On Mon, Feb 26, 2007 at 15:57:02 +0200, Devrim GUNDUZ <[EMAIL PROTECTED]> wrote: > > Upgrading OS will probably solve your problem; since there is no way to > upgrade FC4 kernel unless you want to compile kernel source on your > system. And good luck with that. Fedora still back patches stuff from later kernels than the one you think you have based on the name. Building a Linus kernel and getting the right mix of versions to work on a particular version of Fedora might be hard to do. If you can find the patch that fixes the problem, your best bet (assuming you have to use FC4) would be to try to apply that fix to the latest Fedora kernel for FC4. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
On Fri, Feb 23, 2007 at 18:14:25 -0500, Tom Lane <[EMAIL PROTECTED]> wrote: > "Merlin Moncure" <[EMAIL PROTECTED]> writes: > > On friday we upgraded a critical backend server to postgresql 8.2 > > running on fedora core 4. > > Umm ... why that particular choice of OS? Red Hat dropped update > support for FC4 some time ago, and AFAIK the Fedora Legacy project > is not getting things done. How old is the kernel you're using? The Fedora Legacy project is officially gone now. ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
Hi, On Mon, 2007-02-26 at 08:24 -0500, Merlin Moncure wrote: > we tried update to the latest via yum update with no help. As Tom stated, FC4 is no more supported; therefore you won't be able to get newer kernel via yum. > as promised, here is the best photo of the panic we could get: > http://img144.imageshack.us/my.php?image=dumpic6.jpg ...bad locking... The picture reminded me a SCSI driver bug in older kernels -- I google'd again now and I saw a post that says "native drivers are being used in FC5+ kernels". If this is the real case, you may hit the problem sometime later. Upgrading OS will probably solve your problem; since there is no way to upgrade FC4 kernel unless you want to compile kernel source on your system. Regards, -- Devrim GÜNDÜZ PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
On 2/23/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Merlin Moncure" <[EMAIL PROTECTED]> writes: > On friday we upgraded a critical backend server to postgresql 8.2 > running on fedora core 4. Umm ... why that particular choice of OS? Red Hat dropped update support for FC4 some time ago, and AFAIK the Fedora Legacy project is not getting things done. How old is the kernel you're using? Linux mojo 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 i686 i386 GNU/Linux Unfortunately, the decision about which kernel to run is more or less out of my hands. I would personally really dislike fedora and would much prefer to be running centos/redhat as. That said, your comments and those of others are very helpul in regards to fixing that. we tried update to the latest via yum update with no help. as promised, here is the best photo of the panic we could get: http://img144.imageshack.us/my.php?image=dumpic6.jpg We did an emergency downgrade to 8.1 and will monitor the situation...the decision to get a new server has already been made and hopefully it will be on a more stable platform. big thanks to all who took a few minutes out of their day to lend a hand. merlin ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
On 2/23/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Merlin Moncure" <[EMAIL PROTECTED]> writes: > On friday we upgraded a critical backend server to postgresql 8.2 > running on fedora core 4. Umm ... why that particular choice of OS? Red Hat dropped update support for FC4 some time ago, and AFAIK the Fedora Legacy project is not getting things done. How old is the kernel you're using? > At this juncture we are going to downgrade the postmaster back to 8.1 > and see if that fixes the panics. Even assuming that Postgres is related to the panics, I don't think you will find anyone maintaining that a kernel panic is not the kernel's problem. If an application *is* able to provoke a kernel panic, the standard description of the problem would be "critical kernel security flaw". I vaguely remember running into spinlock problems with FC4 and it wasn't due to PostgreSQL. We didn't have database running on FC4. If you are running a critical server you should switch to atleast CentOS.
Re: [GENERAL] [HACKERS] urgent: upgraded to 8.2, getting kernel panics
"Merlin Moncure" <[EMAIL PROTECTED]> writes: > On friday we upgraded a critical backend server to postgresql 8.2 > running on fedora core 4. Umm ... why that particular choice of OS? Red Hat dropped update support for FC4 some time ago, and AFAIK the Fedora Legacy project is not getting things done. How old is the kernel you're using? > At this juncture we are going to downgrade the postmaster back to 8.1 > and see if that fixes the panics. Even assuming that Postgres is related to the panics, I don't think you will find anyone maintaining that a kernel panic is not the kernel's problem. If an application *is* able to provoke a kernel panic, the standard description of the problem would be "critical kernel security flaw". regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
