tgriep wrote:There was a bug fixed in version 4.1.0 of Fusion that fixed the issue of the MYSQL database that would grow to a very large size.
Here is the entry from the changelog.
Added fix for large mysql ibdata files -BH
So after you upgrade the server, that should be fixed.
The large log files, I would have to see the log rotate file from the server so can you post the following file.
What version of Fusion is the server currently running?
This is version 4.0.1
Is there way to cleanup DB or should we re-spin FUSION all over again?
- I cannot assign more space and see no point in doing so because this is a product problem fixed in newer version
Without knowing how many servers that are fused and the number of checks on each server, it is hard to give an exact number on how much storage is needed for your server.
Lets try and force the truncate to see if the tables can be shrunk.
Run the following as root
tgriep wrote:Without knowing how many servers that are fused and the number of checks on each server, it is hard to give an exact number on how much storage is needed for your server.
Lets try and force the truncate to see if the tables can be shrunk.
Run the following as root
Thanks for the data. The only way I found to shrink the ibdata1 data file that MYSQL uses it to dump the database, stop MYSQL, delete the file and restore the database.
I can create a procedure for you but I would so get some information from the Fusion server.
Can you post your /etc/my.cnf file and any file in the /etc/my.cnf.d folder if any exists?
Run this as root and post it.
tgriep wrote:Thanks for the data. The only way I found to shrink the ibdata1 data file that MYSQL uses it to dump the database, stop MYSQL, delete the file and restore the database.
I can create a procedure for you but I would so get some information from the Fusion server.
Can you post your /etc/my.cnf file and any file in the /etc/my.cnf.d folder if any exists?
Run this as root and post it.