ok, thanks…I'll keep looking for the problem… Really icinga2 looks good, I have one master node, one small satellite node which does just a couple of http checks and then one satellite node on a remote location, with about ~80 remote clients connected.
Cluster check on the master reports 2 connected endpoints - the http checker satellite and the remote location satellite, that's right. [root@icinga2-cz-master log]# pwd /var/lib/icinga2/api/log [root@icinga2-cz-master log]# du -sh 1.3G Cluster check on the http checker satellite reports 1 connected endpoint - the master icinga2 instance, that's right. [root@icinga2-cz-checker log]# pwd /var/lib/icinga2/api/log [root@icinga2-cz-checker log]# du -sh 396M Cluster check on the remote location satellite instance reports 81 connected endpoints - that's 80 remote clients and the remaining 1 is the master icinga2 instance, that's correct. [root@remote-icinga-satellite log]$ pwd /var/lib/icinga2/api/log [root@remote-icinga-satellite log]$ du -sh 757M This amount of data is just for one day, I cleared up it yesterday... So, something I got definitelly wrong there. On Wed, Sep 2, 2015 at 11:41 AM Michael Friedrich < michael.friedr...@netways.de> wrote: > Hi > > Sent from my iphone w/ free typos. > > Am 01.09.2015 um 18:25 schrieb Martin Stiborsk? < > martin.stibor...@gmail.com<mailto:martin.stibor...@gmail.com>>: > > Hello, > I wanted to ask about the replay log. I've found the other questions here > on this topic and I know > http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/troubleshooting#troubleshooting-cluster-replay-log, > but still: > > The /var/lib/icinga2/api/log on my satellite icinga2 instance grows bigger > and bigger. > First it was about ~800MB, then I found a problem in the configuration and > I though that's it, but it turns out that was not the root cause. > Now I cleaned the replay log and started the instance fresh. The directory > is now 84MB in size, it grows maybe 10MB/hour (wild guess). > > Everything looks good - I can see the test results in icingaweb2, no > pending checks, it looks to be working. > Nothing interesting in the debuglog. > Cluster health check without errors. > > How often is the directory cleared up by default? > > Once the logs are replayed to the reconnected instance they are cleared up. > > I could wait to find out, but the /var parition on the satellite is just > 2GB...need to make it bigger soon :) > > Still looks like one of your nodes isn't connected. > > Kind regards, > Michael > > > Thanks! > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org<mailto:icinga-users@lists.icinga.org> > https://lists.icinga.org/mailman/listinfo/icinga-users > > -- > Michael Friedrich, DI (FH) > Senior Developer > > NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg > Tel: +49 911 92885-0 | Fax: +49 911 92885-77 > GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 > http://www.netways.de | michael.friedr...@netways.de > > ** OSBConf 2015 - September - osbconf.org ** > ** OSMC 2015 - November - netways.de/osmc ** > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users >
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
