Thanks. It doesn't look like the import is actually doing anything. I upgraded to the latest version of Opsview and tried to run the import again. It still finishes with no time passed and it appears that nothing is added to the odw database.
-- Bill Campbell From: [email protected] [mailto:[email protected]] On Behalf Of Ton Voon Sent: Monday, June 14, 2010 11:50 AM To: Opsview Users Subject: Re: [opsview-users] Runtime db growing without bounds On 14 Jun 2010, at 15:40, Bill Campbell (NC) wrote: I have been running Opsview with around 150 hosts for about ten months and my runtime db is occupying 12GB of space. Isn't import_runtime supposed to remove data from runtime and optimize it in odw format? When I run import_runtime, it doesn't seem to do anything. I see this in the opsviewd.log: [2010/05/10 12:04:03] [import_runtime] [INFO] Starting [2010/05/10 12:04:03] [import_runtime] [INFO] Finished When import_runtime works, does it reduce the size as well as transferring info to the odw db? I need to reduce the space required so just moving data from runtime to odw won't help. What exactly does runtime hold that has caused it to grow so large so quickly? import_runtime pulls data from Runtime into ODW, but it leaves the cleanup to the housekeeping scripts. There was a bug in 3.7.0 where the overnight housekeeping scripts didn't run correctly. Either upgrade to 3.7.1 or revert this change: https://secure.opsera.com/wsvn/wsvn/opsview/trunk/opsview-core/bin/opsview_m aster_housekeep?op=diff <https://secure.opsera.com/wsvn/wsvn/opsview/trunk/opsview-core/bin/opsview_ master_housekeep?op=diff&rev=4236&peg=4236> &rev=4236&peg=4236 Ton
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
