On Tue, 2011-09-06 at 18:44 +0200, David GUÉNAULT wrote:
> well i'm currently using exactly the same setup as you and gerrard had
> an eye on it and it is related to the size of the sqlite database (and
> also with check_mk generating a lot of passives events .....)
> try vacum the database to keep only 2 days and test accessing logs
> again. If mutisite freeze just shutdown shinken and remove the
> livestatus.db and launch livestatus. You does not need to reboot the
> server at all.
Wrong. If a server that you can only access with ssh goes into an OOM
frenzy, you do need to move to the datacenter to reboot the machine.
Trust me :)
It isn't always necessary if caught early enough though.
> here is an example to keep only to days of logs and vacuum the
> database
> sqlite3 livestatus.db "delete from logs where time < strftime('%s',
> 'now') - 3600*24*2"sqlite3 livestatus.db VACUUM
That'll be handy. Thanks !
--
Marc-Olivier Barre
Avencall
10 bis, rue Lucien Voilin - 92800 Puteaux
Tél. : 0811 85 9486 (0811 85 XIVO)
http://www.avencall.com/
------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
