| Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment | Clearing apt cache gave me enough space to start a mysql client. What actually happened was the mysql database had grown to 26GB and filled the disk. I had assumed that myZM started before VideoTape and started filling it's small disk with recordings. There are 5 HD sources in total but only 4 work (1 has been down for months) Events/recordings are stored on VideoTape but the mysql database is on myZM. my ZM is two virtual machines, one for Zoneminder (called myZM from here on) and another on a different server with big disks shared via NFS (called VideoTape). I *think* it was running before but I can't tell for sure. History: Long power cut took down all servers. Situation: ZM wasn't running, gave a database error I've solved but I'm posting details in case this affects other people, there are two many variables for me to think this is anything other than my installation (so, most likely this is not a bug). Also, truncate needs disk space (remove files or add disk so it can work) Tl dr = reduced database size on disk using mysql + truncate table (Frames, Events, Logs). Warning - read all posts and replies, I later discovered all events were deleted after truncating the database! bbunge suggests a command that may be a lot more effective!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |