Re: Running SMP 2.4.21 #2 SMP Kernel on single processor : Memory Leakage?

[Mehmet Ali Suzen]

On Sat, Aug 23, 2003 at 09:39:17AM -0700, Dan Kegel wrote:
> > 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.

> 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.

> What kind of load are you putting on the system?

Radiusd, mysqld, named and httpd are the most active processes.

> Have you checked the output of ps and /proc/slabinfo to
> 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
};


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/