Memory leak?

S2S-Robert

Verified User
Joined
Jun 24, 2003
Messages
415
Location
The Netherlands
This is a log of what happend just minutes / seconds before the server crashed. Is there a memory leak somewhere?

Nov 28 00:35:29 server kernel: Out of Memory: Killed process 1979 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 1980 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 1981 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 1982 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 1983 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 2055 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 2056 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 2057 (mysqld). Nov 28 00:35:29 server kernel: Out of Memory: Killed process 2058 (mysqld). Nov 28 00:48:31 server kernel: Out of Memory: Killed process 28326 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28455 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28456 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28457 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28459 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28461 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28491 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28492 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28507 (mysqld). Nov 28 00:48:33 server kernel: Out of Memory: Killed process 28516 (mysqld). Nov 28 00:48:35 server kernel: Out of Memory: Killed process 2061 (named). Nov 28 00:48:35 server kernel: Out of Memory: Killed process 2063 (named). Nov 28 00:48:35 server kernel: Out of Memory: Killed process 2064 (named). Nov 28 00:48:38 server kernel: Out of Memory: Killed process 2065 (named). Nov 28 00:48:50 server kernel: Out of Memory: Killed process 2066 (named). Nov 28 00:49:12 server kernel: Out of Memory: Killed process 28537 (exim). Nov 28 00:49:50 server kernel: Out of Memory: Killed process 28548 (exim). Nov 28 00:50:49 server kernel: Out of Memory: Killed process 28559 (exim). Nov 28 00:51:51 server kernel: Out of Memory: Killed process 28564 (exim). Nov 28 00:52:22 server kernel: Out of Memory: Killed process 28567 (exim). Nov 28 00:52:55 server kernel: Out of Memory: Killed process 28574 (exim). Nov 28 00:53:03 server kernel: Out of Memory: Killed process 28546 (nrpe). Nov 28 00:53:05 server kernel: Out of Memory: Killed process 28578 (exim). Nov 28 00:53:06 server kernel: Out of Memory: Killed process 28580 (exim). Nov 28 00:53:08 server kernel: Out of Memory: Killed process 28583 (exim). Nov 28 00:53:17 server kernel: Out of Memory: Killed process 28585 (exim). Nov 28 00:53:23 server kernel: Out of Memory: Killed process 28589 (exim). Nov 28 00:53:26 server kernel: Out of Memory: Killed process 28591 (exim). Nov 28 00:53:28 server kernel: Out of Memory: Killed process 28593 (exim). Nov 28 00:53:32 server kernel: Out of Memory: Killed process 28603 (exim). Nov 28 00:53:33 server kernel: Out of Memory: Killed process 28606 (exim). Nov 28 00:53:33 server kernel: Out of Memory: Killed process 28607 (exim). Nov 28 00:53:36 server kernel: Out of Memory: Killed process 28609 (exim). Nov 28 00:53:39 server kernel: Out of Memory: Killed process 28610 (exim).
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
Hmm... possibly. The fact that it occurs just after the nightly tally it a bit too much to ignore (12:10 am). I'll try look for the possible cause (if its the dataskq)... but will take some serious debugging to find. Not saying it *is* the task queue, but I'll give it a very good check over.. It could also be the fact that it uses a lot of memory for the nightly tally, and it's not leaked.. but again, nothing is for sure at this point, I'll just start there.

John
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
Hello,

There were a few leaks in the dataskq.. not sure they'd be enough to cause that, but in any case, they're plugged up in 1.20.3. I created a memory tracking system which overloaded new and delete to use my own versions of them (not compiled in the release, as its very slow :)).

John
 

S2S-Robert

Verified User
Joined
Jun 24, 2003
Messages
415
Location
The Netherlands
phriendly-Mark said:
well, i guess its not running out of ram though normal usage :p what else is running?
Nothing :(

I don't have game servers running, I don't have additional software installed, I just have the DA and it's software installed. Yet it keeps on crashing on me.
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
One thing to check is the /etc/cron.d/directadmin_cron for the quotacheck line. Some machines really don't like it running at all and commenting it out might be in order:

Code:
5 0 * * 0 root /sbin/quotaoff -a; /sbin/quotacheck -caug; /sbin/quotaon -a;
to
Code:
#5 0 * * 0 root /sbin/quotaoff -a; /sbin/quotacheck -caug; /sbin/quotaon -a;
then
Code:
# service crond reload
John
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
Hello,

Yes, that's essentially the same thing. Just add a # in front of it and see if that makes any difference. Also, you might have to run that command manually from time to time to make sure that the quota files are correct. ( quotaoff -a; quotacheck -augm; quotaon -a; )

John
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
Hello,

Yes, you can run it weekly. The version i pasted above will run every Sunday morning.

John
 
Top