Completely remove both cleanup and categories from your IdoMysqlConnection and restart Icinga. It should then operate normally and you can go on to getting rid of that huge ibdata file. I have removed the "cleanup" section and it is working normally now. I did not Truncate the mentioned table but will plan this after understanding it properly and need to plan a downtime as it is a production server for us. I did try to shrink the "ibdata1" file by method explained by "Thomas".
I took the backup, deleted all the databases excluding mysql, information schema and performance schema. Then tried to restore database but was unable to do so. For that to work I had to create all the database file's which were dropped e,g director,graphite,icingaweb2,etc.
To make it work I had to import the icinga schema as we do while creating database for the first time and then it started working. However, the icingaweb2 started working but unfortunately all the director data was lost, don't know why. Even my graphite graphs were also not working. I imported graphite database schema and graphite started working but still director data was lost.
Please help, what can be done to restore all the host, services, templates, endpoints, zones, api-users, etc which were created by using director. But failed so, i had to recreate database first and then used the same command and was successfull. Could me please point me to the instructions you followed? Anyway, mysqldump will not restore data - please use mysql to do so.
Your backup should still be fine, so you can give the restore procedure another try. Unfortunetly, I deleted backup accidently so cannot restore the data. However, I am restoring my AMI now, we can give it a try again. Need to know step by step procedure to backup and restore the database. Can you please provide me that. I have restored my AMI now, We can do the shrinking procedure again. Need your help to perform this activity.
Help me out with the step by step procedure. Last but not lease make sure to have removed the categories setting from your IdoMysqlConnection and start Icinga. Truncated the hostchecks and servicechecks table. Thank You, Thomas for helping me out. You're welcome! Just in case we meet each other in person some day after Corona: you owe me a beer ;-. Sure, For that you need to travel Mumbai,India. Till then Stay Safe and Health Wishes. Skip to content.
Star 1. New issue. Jump to bottom. Linked pull requests. Copy link. First, temporarily stop mysql database, and take a cold backup of the whole database. In case something goes wrong, you can use this cold backup to restore. For details on mysqldump, refer to how to use mysqldump article. Next, drop all your database one by one. At this stage, the ibdata1 file, which is the MySQL system tablespace will be created from scratch, and in our example, it will not be GB anymore.
Now ibdata1 will be only few MB in size. I have one question. Is it possible or better jet would that work: I have a few databases.
Can I restore databases with rsync from that backup? If I restore all of them or just one of the database, would mysql work after such restore?
Should it also be deleted at 7? But how it will work with file per table? Save my name, email, and website in this browser for the next time I comment. Notify me of followup comments via e-mail.
All rights reserved Terms of Service. You can follow any responses to this entry through the RSS 2. You can leave a response , or trackback from your own site.
Right now it seems like Movable Type is the preferred blogging platform available right now. Name required.
Mail will not be published required. Notify me of followup comments via e-mail. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
Fix MySQL ibdata file size — ibdata1 file growing too large, preventing ibdata1 from eating all your server disk space Thursday, 2nd April Enjoy the disk saving! Hey long time now see, thanks for dropping back again! Gabriela Ascol says:. May 15, at pm. Google Chrome 4.
0コメント