Cactiusers.org

After fixing the mysqld.log issue yesterday i left the server running and came in this morning to find the following error.



Any help would be most appreciated. Thank you.

After digging a bit further I have found additional error messages such as



I ran the command on /var/log shows that the mysqld.log is again at 15GB after only a day of running.

The best place to start would be to figure out what exactly is in mysqld.log, so that you can figure out what is filling it up. Run "tail -f /var/log/mysqld.log" to see the last bit of the file.

Maybe you have it set to log every SQL command, which would be a good way to kill any server.

Here is what I found using tail


Figuring that the files were somehow removed I searched for them and found the following

After some research on forums.cacti.net I came across a post that mentioned one of the errors that I was getting and it led me in the direction of checking the mysql db's for errors and then repairing them. I ran the following commands

the mysqlcheck on the syslog db fixed the error I was getting with that and the mysqlcheck on cacti db fixed a few errors but i was still getting errors related to mactrack. I then imported mactrack.sql,stopped and started mysqld and the error messages no longer appeared in mysqld.log. Here is the command i used for importing the mactrack table:


Thank you again Jimmy for taking the time to give me some pointers it is very much appreciated.