Hi,

we installed a fresh kernel 2.4 system (SuSe 8.1) on our production system and 
now for the first time had one of those crashes I have been reporting in 
recent weeks again (lots of failed mallocs in knldiag and finally it 
crashes). could someone please take a look at the kernel parameters we're 
using? I cannot imagine that it's running out of physical memory as the 
machine has 2GB RAM and a rather small database (<1GB) and not much load 
(never more than 50 concurrent connections). we at first suspected faulty RAM 
modules and exchanged them but that made no difference.

our kernel.sem parameter looks a lot different from the one posted by Markus 
(see part of quoted email below). As I don't understand the exact meaning of 
the params (embarrassing but true) I don't want to fiddle around with them 
without some advice or a pointer to some documentation. 

please take a guess whether we have the kernel setup wrong or there is 
something else we should look for. please let me know if I should post any 
other parameters or provide any more info. this instability is really killing 
us.   

the knldiag, knldiag.err and rtedump for the crash can be downloaded at

http://www.signal7.de/sapdbcrash101502.tgz

here are the kernel parameters.

kernel.overflowgid = 65534
kernel.overflowuid = 65534
kernel.random.uuid = d14e035f-e04b-481c-b40b-25279634a6d3
kernel.random.boot_id = d66d8411-1fb0-4444-91e3-8dd7e8d29d60
kernel.random.write_wakeup_threshold = 128
kernel.random.read_wakeup_threshold = 8
kernel.random.entropy_avail = 4096
kernel.random.poolsize = 512
kernel.threads-max = 14336
kernel.cad_pid = 1
kernel.sem = 250        256000  32      1024
kernel.msgmnb = 16384
kernel.msgmni = 128
kernel.msgmax = 8192
kernel.shmmni = 4096
kernel.shmall = 1073741824
kernel.shmmax = 1073741824
kernel.shm-use-bigpages = 0
kernel.rtsig-max = 1024
kernel.rtsig-nr = 0
kernel.acct = 4 2       30
kernel.modprobe = /sbin/modprobe
kernel.printk = 1       4       1       7
kernel.ctrl-alt-del = 0
kernel.real-root-dev = 2049
kernel.cap-bound = -257
kernel.tainted = 0
kernel.core_uses_pid = 0
kernel.panic = 0
kernel.domainname = 
kernel.hostname = ha1
kernel.version = #3 SMP Wed Oct 9 15:50:46 CEST 2002
kernel.osrelease = 2.4.19-4GB-SMP
kernel.ostype = Linux
fs.file-max = 209713
fs.file-nr = 1724

Thanks in advance,

Robert



> >
> > This is our settings in /etc/sysctl.conf on a machine with 4 Gig of RAM:
> >
> > [root@aubir3p1 /root]# grep -v \# /etc/sysctl.conf
> > net.ipv4.ip_forward = 0
> > net.ipv4.conf.all.rp_filter = 1
> > net.ipv4.ip_always_defrag = 0
> > kernel.sysrq = 0
> > fs.file-max=32768
> >
> > kernel.shmmax=3221225472
> > kernel.sem=4096 512000 1600 2048
> > kernel.msgmax=16384
> > kernel.shmall=3221225472
> >
> > This applies to Kernel 2.4 of course :-)
> >
> >
> > Hope this helps.
> >
> > Greetings,

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to