Running SMP 2.4.21 #2 SMP Kernel on single processor : Memory Leakage?
Quoted 1 line · Mehmet Ali Suzen
I am running RedHat Linux 9 Linux 2.4.21 SMP ...
Then you should contact a Red Hat Linux forum for support.
[email protected] for the most part only discusses fairly vanilla kernels, especially the ones published at
http://kernel.org. Perhaps you could try loading one of those kernels, and seeing if the problem exists there? If it does, please write back with more info.
- Dan
Signature · 3 lines
Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
Quoted 7 lines · Dan Kegel
Quoted 1 line · Mehmet Ali Suzen
I am running RedHat Linux 9 Linux 2.4.21 SMP ...
Then you should contact a Red Hat Linux forum for support.
[email protected] for the most part only discusses fairly vanilla kernels, especially the ones published at
it was a compiled kernel.
Quoted 16 lines
http://kernel.org. Perhaps you could try loading one of those kernels, and seeing if the problem exists there? If it does, please write back with more info.
- Dan
Signature · 9 lines
Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Mehmet Ali Suzen
Quoted 3 lines
Quoted 1 line
I am running RedHat Linux 9 Linux 2.4.21 SMP ...
Then you should contact a Red Hat Linux forum for support.
it was a compiled kernel.
Ah, if you were running a kernel.org kernel, apologies.
Quoted 5 lines
I am running RedHat Linux 9 Linux 2.4.21 SMP and memory usage is increasing regularly even if no heavy service like (radiusd,mysqld, httpd, named) is not running. After some time I get Out of Memory messages and system hungs!
It sounds stupid but we are running single cpu.
Would it be possible to have a memory leakage due to SMP operations? Board is Intel Server Board SE7501BR2
I haven't seen the problem you describe, so I'm shooting in the dark, but:
How long does the problem take to occur after boot? What kind of load are you putting on the system? Have you checked the output of ps and /proc/slabinfo to look for obvious bloats?
- Dan
Signature · 3 lines
Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
Quoted 3 lines · Dan Kegel
Quoted 1 line
it was a compiled kernel.
Ah, if you were running a kernel.org kernel, apologies.
No need. And we didn't want to apply rc in the production.
Quoted 4 lines
I haven't seen the problem you describe, so I'm shooting in the dark, but:
How long does the problem take to occur after boot?
Actually machine was up about 2 weeks for testing. After we got to production. It gets mad.
Quoted 1 line
What kind of load are you putting on the system?
Radiusd, mysqld, named and httpd are the most active processes.
Quoted 2 lines
Have you checked the output of ps and
/proc/slabinfoto look for obvious bloats?
Nothing in the process table generates expanding memory. 2-3 hours ago problem suddenly smears out.
We suspect that commenting in named.conf log options and reload rncd has solved the problem. Which is bizzare, because we have already tried without named.
Mehmet
PS: from named.conf
logging {
//channel syslog_errors {
// Syslog logging: typically daemon, if we choose local1, // some message still go to daemon (bug), so we leave daemon for now . // syslog daemon;
//syslog local1; severity info;
//};
//category default {
// syslog_errors; // you can log to as many channels
// default_syslog; // by default goes to daemon in syslog
//};
// ignore all "lame server" errors (only do this if none of the lame // servers belong to you; otherwise, fix them)
category lame-servers{ null; };
//category statistics { null; }; // We don't need stats for this server
// enable for testing/debugging:
//category default { file_log; syslog_errors; }; //category panic { file_log; };
//category packet { file_log; };
//category eventlib { file_log; };
//other categories; queries, cname, config, load, notify, parser, //response-checks, security, statistics, update, xfer-in, xfer-out
};