Page 1 of 2
[SOLVED] Excessive resource usage: mysql (mysqld_safe)
Posted: 21 Apr 2014, 14:58
by betweenbrain
Since a recent package upgrade on a Debian 7 server, I have been receiving an excessive resource usage alert from LFD.
Account: mysql
Resource: Process Time
Exceeded: 1857 > 1800 (seconds)
Executable: /bin/dash
Command Line: /bin/sh /usr/bin/mysqld_safe
PID: 28390 (Parent PID:28390)
Killed: No
I've tried killing the process, hard restarting the server and added
to /etc/caf/csf.pignore, but the alerts continue.
It appears to be a result of the following package upgrades:
libmysqlclient18 5.6.17-1~dotdeb.1
mysql-client 5.6.17-1~dotdeb.1
mysql-client-5.6 5.6.17-1~dotdeb.1
mysql-client-core-5.6 5.6.17-1~dotdeb.1
mysql-common 5.6.17-1~dotdeb.1
mysql-server 5.6.17-1~dotdeb.1
mysql-server-5.6 5.6.17-1~dotdeb.1
mysql-server-core-5.6 5.6.17-1~dotdeb.1
Has anyone else come across this issue or have any suggestions other than adding mysql to the ignore list?
Best,
Matt
Re: Excessive resource usage: mysql (mysqld_safe)
Posted: 21 Apr 2014, 18:23
by Sergio
in csf.pìgnore add:
user:mysql
instead of the exe that you wrote and restart LFD
Re: Excessive resource usage: mysql (mysqld_safe)
Posted: 22 Apr 2014, 09:06
by betweenbrain
Thanks. I was actually hoping to avoid that. Is there no way to ignore that one executable?
Re: Excessive resource usage: mysql (mysqld_safe)
Posted: 22 Apr 2014, 15:11
by Sergio
Then, try this:
cmd:/bin/sh /usr/bin/mysqld_safe
Re: Excessive resource usage: mysql (mysqld_safe)
Posted: 01 May 2014, 17:51
by betweenbrain
My apologies for the delayed response.
Your last suggestion worked great, thanks!
Re: [SOLVED] Excessive resource usage: mysql (mysqld_safe)
Posted: 01 May 2014, 19:00
by Sergio
Glad it worked for you.
Re: [SOLVED] Excessive resource usage: mysql (mysqld_safe)
Posted: 09 Jan 2016, 20:36
by koms
Still getting alert, although I have the following lines in my csf.pignore
user:mysql
user:mysqld_safe //not sure if it make sense
cmd:/bin/sh /usr/bin/mysqld_safe
------------------------------------------------------
Time: Sat Jan 9 20:46:57 2016 +0100
Account: mysql
Resource: Process Time
Exceeded: 411454 > 1800 (seconds)
Executable: /usr/bin/bash
Command Line: /bin/sh /usr/bin/mysqld_safe
PID: 20551 (Parent PID:20551)
Killed: No
-------------------------------------------------
Re: [SOLVED] Excessive resource usage: mysql (mysqld_safe)
Posted: 14 Apr 2016, 15:48
by boristheblade
This issue is obviously not solved. I'm having the same issue both for mysql and libstoragemgmt.
The strange thing to me is that this number in red: "Exceeded: 91418 > 1800 (seconds)", keeps increasing. I dont understand what this means.. So stopping the messages from being send doesnt seem to be a proper solution to me.
@Koms: Do you have any updates on this issue? Did you find out what is going on? Thank you!
@Sergio: Do you have an idea of whats going on? I googled alot and I cant seem to find anything on this issue other than disabling the messages..
Thanks so much for your help
Re: [SOLVED] Excessive resource usage: mysql (mysqld_safe)
Posted: 21 Jun 2017, 15:41
by lucasdomonte
boristheblade wrote: ↑14 Apr 2016, 15:48
This issue is obviously not solved. I'm having the same issue both for mysql and libstoragemgmt.
The strange thing to me is that this number in red: "Exceeded:
91418 > 1800 (seconds)", keeps increasing. I dont understand what this means.. So stopping the messages from being send doesnt seem to be a proper solution to me.
@Koms: Do you have any updates on this issue? Did you find out what is going on? Thank you!
@Sergio: Do you have an idea of whats going on? I googled alot and I cant seem to find anything on this issue other than disabling the messages..
Thanks so much for your help
Did you find a solution to the excessive increase in memory usage?
Re: [SOLVED] Excessive resource usage: mysql (mysqld_safe)
Posted: 22 May 2018, 14:12
by vps_us
Did anyone manage to find the solution of this problem? I am having the same issue. I know how to disable the alerts by adding the user to ignore file, but I want to know why this is happening and how to fix the root cause rather than hiding the alerts? Thanks.