Thanks for the reply,

Although the hardware is 64bit, I did stick to the 32bit O.S. and packages.

2.6.9-67.0.1.ELsmp #1 SMP Fri Nov 30 11:51:05 EST 2007 i686 athlon i386
GNU/Linux

lgtoserv-7.4.1-1.i686.rpm



  


On Sun, 20 Jan 2008 22:11:26 -0500, Michael Nored <mrnored AT NETZERO DOT NET> 
wrote:

>This is from the 12/21/07 7.4.2. release notes:
>
>Running the Linux 64 bit package with the 2.6.x kernel may result in crashes
>LGTsc06585
>A compatibility issue with libc and pthreads libraries on Linux 2.6
>kernel-based
>environments causes problems when running the 64 bit package for Linux on
>platforms built on the 2.6.x kernel (for example, RedHat AS 4 and SUSE SLES
>9).
>Although operation may be normal at first, continued use of the 64 bit
>package
>with a 2.6.x kernel may result in crashes of various programs.
>It is recommended to use the 32 bit package when running with a 2.6.x
>kernel.
>Running a 32 bit package instead of the 64 bit package should have no
>operational
>impact. The 64 bit package can still be used for kernel version 2.4 Linux
>variants
>such as RedHat AS 3 and SUSE SLES 8.
>
>
>
>
>Michael Nored
>Consultant
>Nored Consulting, LLC
>
>M: (407) 399-8162
>T:  (352) 350-7142
>E: mnored AT Netzero DOT net
>
>-----Original Message-----
>From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
>Behalf Of Kevin West
>Sent: Sunday, January 20, 2008 7:47 PM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] Kernel Panic problem
>
>SERVER
>HP DL585 2 x 2.6GHz Processors
>8 GB RAM
>2 x 14 300GB SCSI HD arrays
>attached via ULTRA 320 Adapters (for D2D backup).
>
>LIBRARY
>HP MSL6060 (2 x Stacked)
>3 X LTO3 drives (SCSI)
>
>SOFTWARE
>Red Hat Enterprise Linux AS release 4 with kernel 2.6.9-67.0.1.ELsmp
>NetWorker 7.4.1.Build.335 Network Edition
>
>CLIENTS
>Total of 75 clients (Windows, Linux & Tru64)
>
>MODULES USED,
>Oracle for Linux, MSSQL, Microsoft cluster.
>
>SETUP
>All standard nothing special.
>
>PROBLEM
>Kenrel panic - not syncing: Out of memory and no killable processes...
>
>Have to do hard restart on the server
>
>WHAT INTRODUCED THIS PROBLEM.
>
>Was running REDHAT 3 and Networker 7.2.1 everything was fine.
>
>I needed to upgrade the OS to REDHAT 4 to take advantage of the better
>disk management.
>
>So I did the OS upgrade to Redhat 4, ran into problems with Networker
>7.2.1 the 2.6 kernel and the SCSI
>library.
>
>So the solution was to Upgrade Networker to 7.3 or above. So I choose
>Networker 7.4 (I have applied the patch as well), this fixed
>the SCSI problems but introduced the Kernel panic problem.
>
>Has anyone else had this problem or any suggestions.
>
>Cheers
>Kev
>--
>Kevin West
>Senior Server Support Officer
>Information Technology Directorate
>University of New England
>Phone: +61 2 6773 4276
>Fax:   +61 2 6773 3424
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and 
>type
>"signoff networker" in the body of the email. Please write to
>networker-request AT listserv.temple DOT edu if you have any problems with this
>list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and 
>type
"signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>=========================================================================

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER