Michael W. Lucas wrote:
Hi,
After a few months of use, our NagVis database grew to 23GB and
overwhelmed my (tiny) server. Shutting down the system, dropping the
database, and recreating it solved my issues.
Surely someone has already written a script to purge the NagVis
database on a
Hi,
After a few months of use, our NagVis database grew to 23GB and
overwhelmed my (tiny) server. Shutting down the system, dropping the
database, and recreating it solved my issues.
Surely someone has already written a script to purge the NagVis
database on a regular basis, trimming old data
On Friday 19 June 2009, Michael W. Lucas wrote:
After a few months of use, our NagVis database grew to 23GB and
overwhelmed my (tiny) server. Shutting down the system, dropping the
database, and recreating it solved my issues.
This isn't a NagVis issues, this is a ndoutils issue. You need to
I had a similar problem with my ndoutils and mysql. If you are using
MySQL and aren't using replication, don't forget to first clear and then
turn off binary logs - those files get huge very quickly.
Michael W. Lucas wrote:
Hi,
After a few months of use, our NagVis database grew to 23GB and
On Friday 19 June 2009, Kevin Keane wrote:
I had a similar problem with my ndoutils and mysql. If you are using
MySQL and aren't using replication, don't forget to first clear and then
turn off binary logs - those files get huge very quickly.
Yea, binary logs can be a pain to, I am working on
