Hi All, With the help of a suplier of us we installed a fresh server with CentOS 5 and copied over the files and DB's as in a new server migration. We used the mysqldump to export only the info we wanted. Runtime database was purged before all of this. Only 1.7Gb runtime DB instead op 140Gb !. Now happily working on new server with Opsview CE 3.11.1 PS: I've implemented the fix only to find out housekeeping was not working due to the massive DB size.
Met vriendelijke groet, Peter Plate ________________________________ From: Emilio Scalise [mailto:[email protected]] Sent: donderdag 10 februari 2011 14:55 To: Opsview Users Cc: Peter Plate Subject: Re: [opsview-users] Opsview CE 3.7.0 disk full You should upgrade or instead backport the fix, there were few lines changed. If you need help feel free to ask.. Regards Il 10/02/2011 11:29, Peter Plate ha scritto: Hello All, Yesterday I noticed the disk of our Debian 5 Opsview CE 3.7.0 installation was starting to full up. We inherited this setup so I thought it was also monitored but actually it was not. I checked the config if the housekeeping was on , and it was on 90 days. So today I came to the office only to see an Opsview Error while opening the webpage. A quick check showed me the disk is 100% full. I then noticed the housekeeping script had an bug that it was not cleaning up the DB's. My Disk is 147Gb and the DB file size is 101Gb. I'm in no way an debian admin, but I know a bit around the system. Now, how can I get my database down in size so I can start the housekeeping process correctly ? Peter _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
