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.
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
MONITORING-FR
AvatarDavid GUENAULT
Membre de l'équipe Monitoring-fr
secrétaire de l'association
MONITORING-FR
----- Mail original -----
De: "Marc-Olivier Barre" <moba...@avencall.com>
À: shinken-devel@lists.sourceforge.net
Envoyé: Mardi 6 Septembre 2011 16:31:10
Objet: Re: [Shinken-devel] Memory leak in the Livestatus broker ?
On Tue, 2011-09-06 at 15:44 +0200, nap wrote:
>
>
> On Tue, Sep 6, 2011 at 3:13 PM, Marc-Olivier Barre
> <moba...@avencall.com> wrote:
> Hi,
>
> I might have stumbled on something a bit nasty. Using
> mk_multisite, when
> I try to retrieve a host or service history, one of the broker
> thread
> starts eating memory like crazy until the machine dies drowned
> in OOM
> process kills (like I said, kind of nasty :p)
>
> As far as I know, I'm running shinken 0.6.5 (from the
> tarball).
>
> I couldn't figure out a way to reproduce it outside of the
> mk_multisite
> GUI, but I guess sending the same request manually would give
> the same
> result. Thoughts ? Any more details needed ?
> Hi,
>
> The LS module got debug parameters. Please uncommetn debug and set
> debug_queries to 1 so we can got a trace of theses killing queries :)
> I vote for queries on the log table, but let look first at debug
> logs :)
>
> Thanks,
Well, I can confirm, but not in the expected way. Just to be on the safe
side and avoid going a second time to the datacenter to reboot the
machine (huhuhu...) I emptied the database and tried clicking on the
cursed host history button. No issue there, and no memory hungry
processes.
I had already tried setting debug and debug_queries to 1, but the debug
logs looked a lot like shit :) I didn't manage to get a query type out
of it... Might have missed it. I'll give it another try on a test server
when I get 5 minutes.
Cheers,
--
Marc-Olivier Barre
Avencall
10 bis, rue Lucien Voilin - 92800 Puteaux
Tél. : 0811 85 9486 (0811 85 XIVO)
http://www.avencall.com/
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
