Re: [Bigsister-general] bigsister performance

[Rob Verduijn <suppressed>]

Hi there again,

I've tested the patches but still the machine locks up.

I'm going with the "*.conn down=never" at the end of the bb_event
generator as a workaround for now.
This will be adequate because I do not deal with lost connections
outside offcie hours.
Bummer is I will not know about down time that happened when I am not
looking at the bigsister page.

Thanx for the help
Regards 
Rob


Op vr, 21-10-2005 te 08:27 +0200, schreef Rob Verduijn:
> Hi again,
> 
> Sorry for the delay but I was busy elsewere yesterday.
> 
> I've tried adding "*.conn down=never" to the end of my
> bb_event_generator (which I succeeded in).
> My provider was good enough to provide some down time on the network
> again so this was put to the test immediatly.
> Bigsister managed to stay up, no total lock up.
> 
> 
> 
> Since I do like to get an alert every now and then I am going to try the
> patch you provided.
> I'll let you know how it goes.
> 
> Already much thanx for the effort you are putting in this.
> 
> You da man Thomas :)
> 
> 
> Regards
> Rob
> 
> 
> 
> Op wo, 19-10-2005 te 18:36 +0200, schreef Thomas Aeby:
> > Hello,
> > 
> > On Wed, 2005-10-19 at 10:30 +0200, Rob Verduijn wrote:
> > > It seems there are an awfull lot of bsmon processes that took a serious
> > > bite out of the system resources.
> > > Swap file activity was soring and response at the command line took a
> > > dive.
> > 
> > Ok, are you willing to try a patch?
> > 
> > If you download
> > 
> > http://cvs.sourceforge.net/viewcvs.py/*checkout*/bigsister/bigsister/bsmonitor/Statusmon/bs_evgen.pm?rev=1.31
> > 
> > and replace the existing ...bin/Statusmon/bs_evgen.pm with it, and 
> > replace ...bin/Statusmon/grouping.pm with
> > 
> > http://cvs.sourceforge.net/viewcvs.py/*checkout*/bigsister/bigsister/bsmonitor/Statusmon/grouping.pm?rev=1.17
> > 
> > as well (re-start the Big Sister server after that), the number of
> > alerts per minute Big Sister will send can be limitted.
> > 
> > Add a line like
> > 
> >   *.* maxpermin=40
> > 
> > to bb_event_generator.cfg, and Big Sister will silently drop alert 
> > messages (but not the alarms themselves) exceeding the 40/min limit.
> > 
> > BTW: The default limit is set to 20/min, so you need not change
> > bb_event_generator.cfg at all if this is ok for you.
> > 
> > Best regards,
> > Tom
> > 
> > ----------------------------------------------------------------------------
> > Thomas Aeby, Kirchweg 52, 1735 Giffers, Switzerland, Tel: (+41)264180040
> > Internet: suppressed                       PGP public key available
> > ----------------------------------------------------------------------------
> > 
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Bigsister-general mailing list
> suppressed
> https://lists.sourceforge.net/lists/listinfo/bigsister-general



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bigsister-general mailing list
suppressed
https://lists.sourceforge.net/lists/listinfo/bigsister-general