I just got an automated message from my system that /var is getting full.
named (9.2.4) up Server Load 0.56 (4 cpus) Memory Used 25.2 %
Swap Used 0.01 % Disk sda5 (/) 2 % Disk sdb1 (/backup) 9 % Disk sda1 (/boot) 13 % Disk sda7 (/home) 15 %
Disk sda8 (/tmp) 4 %
Disk sda3 (/usr) 49 %
Disk sda2 (/var) 82 %
I don't see anything out of the ordinary in there, and I haven't installed anything (other than the latest cpanel bug fix) in about a month...
Any ideas on how to address this (othe than the obvious of allocate more space to /var)
You want to stop MySQL to prevent any writing to the database during the moving of files (this will prevent access to all databases, so it might cause a tiny bit of downtime while you are moving data, nothing I'd be real concerned about) you also want to stop chkservd, to prevent it from restarting MySQL during this process.
It should also be noted that you can repeat these steps for different databases, just change large_database to the name of the database you want to move.
Those bin files are your mysql binary logs. They track any mysql activity and can be used to "replay" it later. If you have multiple mysql servers working in master / slave combo those logs are used for replication.
To remove them - login in mysql client and run RESET MASTER; query
I have but a single server running everything. No replication.
In addition to removing them, Can I turn them off so they don't write in the future? I've only been on this server a month!
You want to keep your recent transaction logs since the last database dump. If some idiot ever accidently drops a database, clears records,or performs a mass update, you can recover everything up to the point just before the accidental catastrophic event.
If you are happy enough with a nightly dump and don't care about anything from the backup point until the disaster then you can turn off logging in your my.cnf file. I suppose it depends how critical the data is.