From devilcfg at yahoo.fr Mon Jul 5 19:46:00 2010 From: devilcfg at yahoo.fr (X Y) Date: Mon, 5 Jul 2010 10:46:00 -0700 (PDT) Subject: [smokeping-users] CGI failed Message-ID: <405762.49614.qm@web25804.mail.ukl.yahoo.com> Hello, I'm trying to install smoketrace on my smokeping (with lighttpd) but I have a little problem. When I launch smoketrace, the status stay on "starting" and I see this on my lighttpd/error.log: 2010-07-05 19:18:25: (mod_cgi.c.998) CGI failed: No such file or directory /var/www/smokeping/tr.cgi mod_cgi.c.1001: aborted 2010-07-05 19:18:25: (mod_cgi.c.1235) cleaning up CGI: process died with signal 6 And I can't open tr.cgi with my browser too. The file tr.cgi is in the same file than tr.html and smokeping.cgi and I don't have any problem to open smokeping.cgi Anybody have an idea? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100705/08dcb5d2/attachment.htm From robert.mersberger at goldenliving.com Wed Jul 7 18:36:12 2010 From: robert.mersberger at goldenliving.com (Mersberger, Robert) Date: Wed, 7 Jul 2010 11:36:12 -0500 Subject: [smokeping-users] Optimizing Smokeping - how many tasks can I run Message-ID: <77AF43BAFA571044A7520788C54EDDEB030D5DEBDD@GLEXCH04401.GoldenLiving.Com> I am running version 20070126 with steps =120 and pings =10 and currently have 528 targets. I very seldom see warning message where step has been exceeded. How can I determine the max number of targets that will work under this configuration? Dose Smokeping (Fping) send out all 10 pings at the same time or does it cycle through each target. Trying to understand. Robert Mersberger LAN Consultant, Information Technology Phone 479-201-3442 Fax 479-478-3837 Email robert.mersberger at goldenliving.com www.Goldenliving.com Golden Living 1000 Fianna Way Fort Smith, AR 72919 ________________________________ Please consider the environment before printing this e-mail. CONFIDENTIAL NOTICE: This e-mail message and any attachment(s) (collectively, this 'Email') are intended only for the confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient named above or an agent responsible for delivering it to the intended recipient named above, you have received this Email in error. Please notify the sender immediately and permanently delete this Email and any copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100707/d9c5e011/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: Mersberger, Robert.vcf Type: text/x-vcard Size: 241 bytes Desc: Mersberger, Robert.vcf Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100707/d9c5e011/attachment.vcf From robert.mersberger at goldenliving.com Fri Jul 9 16:41:06 2010 From: robert.mersberger at goldenliving.com (Mersberger, Robert) Date: Fri, 9 Jul 2010 09:41:06 -0500 Subject: [smokeping-users] Optimizing Smokeping - how many tasks can I run Message-ID: <77AF43BAFA571044A7520788C54EDDEB030D5DEBF1@GLEXCH04401.GoldenLiving.Com> I am running version 20070126 with steps =120 and pings =10 and currently have 528 targets. I very seldom see warning message where step has been exceeded. How can I determine the max number of targets that will work under this configuration? Dose Smokeping (Fping) send out all 10 pings at the same time or does it cycle through each target. Trying to understand. Robert Mersberger LAN Consultant, Information Technology Phone 479-201-3442 Fax 479-478-3837 Email robert.mersberger at goldenliving.com www.Goldenliving.com Golden Living 1000 Fianna Way Fort Smith, AR 72919 ________________________________ Please consider the environment before printing this e-mail. CONFIDENTIAL NOTICE: This e-mail message and any attachment(s) (collectively, this 'Email') are intended only for the confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient named above or an agent responsible for delivering it to the intended recipient named above, you have received this Email in error. Please notify the sender immediately and permanently delete this Email and any copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100709/f994f34f/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: Mersberger, Robert.vcf Type: text/x-vcard Size: 241 bytes Desc: Mersberger, Robert.vcf Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100709/f994f34f/attachment.vcf From alter3d at alter3d.ca Fri Jul 9 16:57:59 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Fri, 09 Jul 2010 10:57:59 -0400 Subject: [smokeping-users] Optimizing Smokeping - how many tasks can I run In-Reply-To: <77AF43BAFA571044A7520788C54EDDEB030D5DEBF1@GLEXCH04401.GoldenLiving.Com> References: <77AF43BAFA571044A7520788C54EDDEB030D5DEBF1@GLEXCH04401.GoldenLiving.Com> Message-ID: <4C3738F7.4070500@alter3d.ca> FPing sends out its requests in parallel (more or less, it's actually a multi-threaded round-robin model). The way it will work with your config is that SmokePing will invoke FPing once every 120 seconds with all 528 targets, and FPing will poll the hosts in parallel. If the FPing process doesn't complete and return a result set within 120 seconds, SmokePing will kill it, issue the warning you're seeing, and then start the next poll cycle. There is no hard-and-fast rule to determining the maximum number of targets for any given steps and pings setting; it largely depends on the typical network conditions for your site(s); if you expect a lot of hosts to respond slowly or not at all on a frequent basis, you might need to lower pings or increase steps. The other option is to implement multiple probe instances -- you can configure SmokePing to use multiple FPing probe 'groups', and configure different groups of hosts to use different probes (e.g. probe A will handle hosts 0-99; probe B will handle hosts 100-199; etc). SmokePing will kick off one FPing process for each probe instance, but with the same pings and steps -- so instead of waiting for 500+ hosts to respond to 10 pings in 120 seconds, you're only waiting for 100 hosts. If one probe group exceeds the time limit, you'll still get results for the other ones. Unfortunately, the settings that will work best with your site are largely a function of experience and tuning; over time you'll tweak the settings to be appropriate to your site. As a first step, I recommend investigating the multiple-probe option, as it doesn't require changes to your RRD files. Check the SmokePing docs for information on how to set up multiple probes. - Peter On 09/07/2010 10:41 AM, Mersberger, Robert wrote: > I am running version 20070126 with steps =120 and pings =10 and > currently have 528 targets. I very seldom see warning message where > step has been exceeded. How can I determine the max number of targets > that will work under this configuration? > Dose Smokeping (Fping) send out all 10 pings at the same time or does > it cycle through each target. > Trying to understand. > Robert Mersberger > LAN Consultant, Information Technology > Phone 479-201-3442 > Fax 479-478-3837 > Email robert.mersberger at goldenliving.com > _www.Goldenliving.com_ > Golden Living > 1000 Fianna Way > Fort Smith, AR 72919 > > _ ________________________________ _ > Please consider the environment before printing this e-mail. > > CONFIDENTIAL NOTICE: > This e-mail message and any attachment(s) (collectively, > this 'Email') are intended only for the confidential use of > the recipient(s) named above. If the reader of this message > is not the intended recipient named above or an agent > responsible for delivering it to the intended recipient > named above, you have received this Email in error. > Please notify the sender immediately and permanently delete > this Email and any copies thereof. > > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100709/d083de0c/attachment.htm From alter3d at alter3d.ca Fri Jul 9 19:07:43 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Fri, 09 Jul 2010 13:07:43 -0400 Subject: [smokeping-users] Optimizing Smokeping - how many tasks can I run In-Reply-To: <77AF43BAFA571044A7520788C54EDDEB030D5DEBF6@GLEXCH04401.GoldenLiving.Com> References: <77AF43BAFA571044A7520788C54EDDEB030D5DEBF1@GLEXCH04401.GoldenLiving.Com> <4C3738F7.4070500@alter3d.ca> <77AF43BAFA571044A7520788C54EDDEB030D5DEBF6@GLEXCH04401.GoldenLiving.Com> Message-ID: <4C37575F.10505@alter3d.ca> Yup, you essentially have it right, though there a few minor issues... see my changes and comments, inline, below. - Peter On 09/07/2010 12:59 PM, Mersberger, Robert wrote: > Hope you don;t mind but I would like to pass my changes pass you to > verify my thought and actions are on the same path. > From what I understand after reading about multiple probe instances I > would like to change my config to the following. If this is correct > thinking how can I verify that it actually is working? There are a few ways to tell if it's working. The quick-n-dirty way is simply to check the process list on the machine... if you see multiple FPing processes, you're good. You can also spawn SmokePing in foreground mode and watch the output. > Here are my proposed changes > > + FPing > > binary = /usr/sbin/fping > > ++ FPingSNF_G1 > > offset = 0% > > ++ FPingSNF_G2 > > offset =25% > > ++ FPingOther > > offset 50% > You're missing the = character on the last probe. Also, it's not strictly necessary to use offsets at all, though it's not a bad idea either. The offset can be used to 'tweak' stuff so that network traffic (and thus network conditions) are a little more even across the probe period. If you're going to use offset, you might want to use 0% / 33% / 66% instead to space them evenly unless you have reason to do otherwise. > . > > . > > . > > *** Targets *** > > # Change to new FPing group = SNF_G1 > > # was probe = FPing > > probe = FPingSNF_G1 > > menu = Top > > title = Network Latency Grapher > > remark = Welcome to the SmokePing website of Golden Living \ > > Here you will learn all about latency and packate loss on our network. > > + SNFs > > menu = SNF's > > title = Beverly Skilled Nursing Facilities > > alerts = bigloss,someloss,startloss,rttdetect > > ++ 00001-00099 > > menu = 00001-00099 > > title =SNFs 00001-00099 > > +++ 00014 > > menu = 00014 > > title =00014 > > host = 00014berva > > # Note many other targets follow is and If I understand they will all > use FPingSNF_G1 for their probe/ > > ++ 02200-02399 > > # Change to new FPing group = SNF_G2 > > menu = 02200-02399 > > probe = FPingSNF_G2 > > title =02200-02399 > > +++ 02200 > > menu = 02200 > > title =02200 > > host = 02200rapsd > > # Note many other targets follow is and If I understand they will all > use FPingSNF_G2 for their probe/ > > + AseraCare > > # Change to new FPing group = Other > > menu = AseraCare > > title =AseraCare > > alerts = bigloss,someloss,startloss,rttdetect > > ++ 06370 > > menu = 06370 ASA > > probe = FPingOther > > title = ASA-06370 172.29.8.65 > > host = ASA-06370 > > ++ 06371 > > menu = 06371 ASA > > title =06371 Grand Island, NE ASA 172.29.0.129 > > host = ASA-06371 > > # Note many other targets follow is and If I understand they will all > use FPingOther for their probe/ > Actually, all of the following targets will use FPingSNF_G1 -- you've misplaced the "probe = " directive. If you want all hosts under the AseraCase tree to use the "Other" probe, it should be in the "+ AseraCare" block; in your example here, only "++ 06370" uses the Other probe; everything else in the AseraCare tree will inherit the default from the top level. Keep in mind that SmokePing's configuration is strictly hierarchical; settings pass from parents to children, not from children to siblings. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100709/6ac0a449/attachment-0001.htm From pete.hoffswell at davenport.edu Mon Jul 12 20:44:21 2010 From: pete.hoffswell at davenport.edu (Pete Hoffswell) Date: Mon, 12 Jul 2010 14:44:21 -0400 Subject: [smokeping-users] fping and tos Message-ID: Hello - I have installed the updated fping called fping-2.4b2_to4-ipv6 and upgraded my FPing.pm from svn, but I still get an error message when attempting to modify my configuration to use the fping tos = directive. fping -O works. path looks good for fping in config ERROR: /usr/local/smokeping/etc/config, line 194: unknown variable 'tos' Has anyone been successful in getting fping probe with tos to work? -- - pete.hoffswell at davenport.edu Network Manager http://www.davenport.edu 616-732-1101 From pete.hoffswell at davenport.edu Tue Jul 13 17:52:15 2010 From: pete.hoffswell at davenport.edu (Pete Hoffswell) Date: Tue, 13 Jul 2010 11:52:15 -0400 Subject: [smokeping-users] fping and tos Message-ID: Hello - I have installed the updated fping called fping-2.4b2_to4-ipv6 and upgraded my FPing.pm from svn, but I still get an error message when attempting to modify my configuration to use the fping tos = directive. fping -O works. path looks good for fping in config ERROR: /usr/local/smokeping/etc/config, line 194: unknown variable 'tos' Has anyone been successful in getting fping probe with tos to work? -- - pete.hoffswell at davenport.edu Network Manager http://www.davenport.edu 616-732-1101 From mh+smokeping-users at zugschlus.de Wed Jul 21 08:44:40 2010 From: mh+smokeping-users at zugschlus.de (Marc Haber) Date: Wed, 21 Jul 2010 08:44:40 +0200 Subject: [smokeping-users] miniloss example alert creates a lot of alternating alerts Message-ID: <20100721064440.GA17113@torres.zugschlus.de> Hi, when a network device is quite busy (for example, when backup of some servers connected to this device is going on), it's going to drop some packets, resulting in loss data like this: 00:35:23 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5% 00:35:52 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5%, 0% 00:48:53 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5% 00:49:23 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0% 00:49:53 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10% 00:50:23 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0% 00:53:54 loss: 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5% 00:54:24 loss: 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0%,0%, 0%, 0%, 0%, 0%, 0%, 5%, 0% When one has the miniloss alert from the smokeping_config defined, this causes the alarm to get raised and cleared multiple times over this rather short period of time: 00:35:23 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5% alarm raised 00:35:52 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5%, 0% alarm cleared 00:48:53 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5% alarm raised 00:49:23 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0% alarm cleared 00:49:53 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10% alarm raised 00:50:23 loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0% alarm cleared 00:53:54 loss: 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5% alarm raised 00:54:24 loss: 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0%,0%, 0%, 0%, 0%, 0%, 0%, 5%, 0% alarm cleared I am wondering whether it makes sense to clear the alarm just because there is a 0% in the last slot of the data being considered. This causes the alarm to flap in the case of occasional packet loss. I am thinking of either modifing the alarm so only go of for changes > 5 %, like +miniloss type = loss # in percent pattern = >5%,*12*,>5%,*12*,>5% comment = detected loss 3 times over the last two hours or to have it stay raised even if the current loss is 0%, like +miniloss type = loss # in percent pattern = >0%,*12*,>0%,*12*,>0%,*12* comment = detected loss 3 times over the last two hours or +miniloss type = loss # in percent pattern = >0%,*12*,>0%,*12*,>0%,*12*,>=0% comment = detected loss 3 times over the last two hours I would like to ask the more experienced users how you would act in my position. Would you ditch the miniloss alert altogether, would you modify it, and if so, how? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 From mayer at iiasa.ac.at Wed Jul 21 17:13:43 2010 From: mayer at iiasa.ac.at (Hans MAYER) Date: Wed, 21 Jul 2010 17:13:43 +0200 Subject: [smokeping-users] no graphics Message-ID: Dear smokeping users Environment: server: solaris 10, perl v5.8.4 , rrdtool-1.4.4 , apache-2.2.15 , smokeping-2.4.2 Browser: Mozilla firefox 3.6.6 or IE 8 at windows 7 I configured smokeping and the deamon is running very well. There is configured one target. Apache was configured with a vhost and a dedicated cgi directory. I copied these 2 cgi script to this directory. When I try to navigate with the browser to my target I don't see any graphics. Looking in the apache log, I see, script not found or unable to stat: /usr/local/smokeping-2.4.2/cgi/cropper this is correct as the cropper directory is not there (see error log v1) I copied the directory cropper with subtrees to the cgi Using any browser again no pictures. Now the apache log says: Permission denied: exec of '/usr/local/smokeping-2.4.2/cgi/cropper/lib/scriptaculous.js' ( see error log v2 ) This partially correct as this java-script is not executable, but is totally wrong as java-scripts should not and cannot be executed by the web server. This is a task for the browser ( IE or NS ) but not for apache. If I look at the cache dir the png files are there. Now I am a little bit confused. Why does the system search for java-scripts in cgi directories. It's not my first smokeping installation but to the others I installed, I don't have access anymore. I am sure it's only a little miss configuration on my site, but I am looking around since a day and I cannot find it. Any help would be nice. Kind regards Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100721/94ca3d69/attachment-0001.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: config Type: application/octet-stream Size: 2821 bytes Desc: config Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100721/94ca3d69/attachment-0005.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: httpd-vhosts.conf Type: application/octet-stream Size: 1225 bytes Desc: httpd-vhosts.conf Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100721/94ca3d69/attachment-0006.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: smokeping.ict.iiasa.ac.at-access_log_v1 Type: application/octet-stream Size: 1495 bytes Desc: smokeping.ict.iiasa.ac.at-access_log_v1 Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100721/94ca3d69/attachment-0007.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: smokeping.ict.iiasa.ac.at-error_log_v1 Type: application/octet-stream Size: 2783 bytes Desc: smokeping.ict.iiasa.ac.at-error_log_v1 Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100721/94ca3d69/attachment-0008.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: smokeping.ict.iiasa.ac.at-error_log_v2 Type: application/octet-stream Size: 4240 bytes Desc: smokeping.ict.iiasa.ac.at-error_log_v2 Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100721/94ca3d69/attachment-0009.obj From mh+smokeping-users at zugschlus.de Thu Jul 22 12:30:26 2010 From: mh+smokeping-users at zugschlus.de (Marc Haber) Date: Thu, 22 Jul 2010 12:30:26 +0200 Subject: [smokeping-users] miniloss example alert creates a lot of alternating alerts In-Reply-To: <20100721064440.GA17113@torres.zugschlus.de> References: <20100721064440.GA17113@torres.zugschlus.de> Message-ID: <20100722103026.GB21380@torres.zugschlus.de> Hi, On Wed, Jul 21, 2010 at 08:44:40AM +0200, Marc Haber wrote: > or to have it stay raised even if the current loss is 0%, like > > +miniloss > type = loss > # in percent > pattern = >0%,*12*,>0%,*12*,>0%,*12* > comment = detected loss 3 times over the last two hours this doesn't seem to work. With a pattern = >0%,*12*,>0%,*12*,>0%,*12* I had the alert (correctly) raised on this data line: loss: 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5% but it cleared a few minutes later on this: loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0% What am I doing wrong? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 From alter3d at alter3d.ca Thu Jul 22 13:15:16 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Thu, 22 Jul 2010 07:15:16 -0400 Subject: [smokeping-users] miniloss example alert creates a lot of alternating alerts In-Reply-To: <20100721064440.GA17113@torres.zugschlus.de> References: <20100721064440.GA17113@torres.zugschlus.de> Message-ID: <4C482844.9090009@alter3d.ca> Hi Marc; The solution to your problem depends a bit on the alerting requirements at your site -- for example, do you care if alerts are delayed by one ore more polling cycles in SmokePing? My first suggestion would be to define an alert something like this: +someloss type = loss pattern = 0%, 0%, 0%, 0%, 0%, >0%, >0%, >0% comment = Loss detected for last 3 polling cycles This alert definition will trigger when you have 3 *consecutive* polling cycles with some packet loss; this is different than the alert you tried (>0%, *12*, >0%, *12*, >0%, *12*) because the "*12*" in your pattern acts as a wildcard... it will match ANYTHING. So your alert pattern basically says "If we've seen >0% three times in the last 39 poll cycles, trigger an alert. Based on the data samples you provided, I believe a consecutive model would suit your needs better. If you need to get alerts sooner for actual problems, consider defining a second alert as well... something like: +bigloss type = loss pattern = 0%, 0%, 0%, >20% comment = We have sudden, severe packet loss If you enable both alerts on your hosts, you will get alerts when you have persistent, low-to-moderate (1-20%) loss on the links, but you'll get an alert immediately when there are bigger problems (>20% loss). I think these rules will probably serve you well as a baseline, but don't be afraid to experiment. I find it usually takes a couple weeks of testing & tweaking to find an optimum set of alerts for any given network simply due to different topology/architecturer, etc. - Peter On 21/07/2010 2:44 AM, Marc Haber wrote: > Hi, > > when a network device is quite busy (for example, when backup of some > servers connected to this device is going on), it's going to drop some > packets, resulting in loss data like this: > > 00:35:23 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5% > 00:35:52 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5%, 0% > 00:48:53 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5% > 00:49:23 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0% > 00:49:53 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10% > 00:50:23 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0% > 00:53:54 > loss: 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, > 0%, 0%, 5%, 0%, 10%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5% > 00:54:24 > loss: 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, > 0%, 5%, 0%, 10%, 0%,0%, 0%, 0%, 0%, 0%, 0%, 5%, 0% > > When one has the miniloss alert from the smokeping_config defined, > this causes the alarm to get raised and cleared multiple times over > this rather short period of time: > > 00:35:23 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5% > alarm raised > 00:35:52 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 10%, 0%, 0%, 5%, 0%, 5%, 0% > alarm cleared > 00:48:53 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5% > alarm raised > 00:49:23 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0% > alarm cleared > 00:49:53 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10% > alarm raised > 00:50:23 > loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, > 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 5%, 0%, 10%, 0% > alarm cleared > 00:53:54 > loss: 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, > 0%, 0%, 5%, 0%, 10%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5% > alarm raised > 00:54:24 > loss: 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, > 0%, 5%, 0%, 10%, 0%,0%, 0%, 0%, 0%, 0%, 0%, 5%, 0% > alarm cleared > > I am wondering whether it makes sense to clear the alarm just because > there is a 0% in the last slot of the data being considered. This > causes the alarm to flap in the case of occasional packet loss. > > I am thinking of either modifing the alarm so only go of for changes> > 5 %, like > > +miniloss > type = loss > # in percent > pattern =>5%,*12*,>5%,*12*,>5% > comment = detected loss 3 times over the last two hours > > or to have it stay raised even if the current loss is 0%, like > > +miniloss > type = loss > # in percent > pattern =>0%,*12*,>0%,*12*,>0%,*12* > comment = detected loss 3 times over the last two hours > > or > +miniloss > type = loss > # in percent > pattern =>0%,*12*,>0%,*12*,>0%,*12*,>=0% > comment = detected loss 3 times over the last two hours > > I would like to ask the more experienced users how you would act in my > position. Would you ditch the miniloss alert altogether, would you > modify it, and if so, how? > > Greetings > Marc > > From Al_Sorrell at troweprice.com Thu Jul 22 17:17:04 2010 From: Al_Sorrell at troweprice.com (Sorrell, Al) Date: Thu, 22 Jul 2010 11:17:04 -0400 Subject: [smokeping-users] Question about alert email lists Message-ID: <3899F44EE8372C44926752C5C84C13D34B70DCDC@OMTCP36040.corp.troweprice.net> Using SmokePing 2.4.2 on Solaris 8. Within my Solaris servers /etc/mail/aliases file, I have mailing lists set up in the conventional way, such as: cns_design: Al_sorrell at troweprice.com,Joe_User at troweprice.com,etc. If I try to just use "cns_design" on the Alerts->To= line, I get an error saying that I must have an email address. If I use it on an "alertee" line, and I have at least one "normal" email address, the config doesn't gripe, but others on the list don't get the notification, e.g.: alertee = Al_Sorrell at troweprice.com,cns_design Is this a non-feature or is there some other way to get this to work - the goal, of course, being to centralize the distribution lists in one place. Thanks, Al _________________________ Almon (Al) Sorrell Corporate Network Services | Network Engineering Consultant T. Rowe Price 4515 Painters Mill Road, TE9008 Owings Mills, MD 21117 Phone: 410-345-3042 (508-3042) Fax:410-345-3135 Email: Al_Sorrell at troweprice.com T. Rowe Price (including T. Rowe Price Group, Inc. and its affiliates) and its associates do not provide legal or tax advice. Any tax-related discussion contained in this e-mail, including any attachments, is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding any tax penalties or (ii) promoting, marketing, or recommending to any other party any transaction or matter addressed herein. Please consult your independent legal counsel and/or professional tax advisor regarding any legal or tax issues raised in this e-mail. The contents of this e-mail and any attachments are intended solely for the use of the named addressee(s) and may contain confidential and/or privileged information. Any unauthorized use, copying, disclosure, or distribution of the contents of this e-mail is strictly prohibited by the sender and may be unlawful. If you are not the intended recipient, please notify the sender immediately and delete this e-mail. From alter3d at alter3d.ca Fri Jul 23 00:26:06 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Thu, 22 Jul 2010 18:26:06 -0400 Subject: [smokeping-users] Question about alert email lists In-Reply-To: <3899F44EE8372C44926752C5C84C13D34B70DCDC@OMTCP36040.corp.troweprice.net> References: <3899F44EE8372C44926752C5C84C13D34B70DCDC@OMTCP36040.corp.troweprice.net> Message-ID: <4C48C57E.6050607@alter3d.ca> Al, How do you have the mail stuff set up in Smokeping? Are you using a 'mailhost = ' configuration directive, or are you letting it use sendmail? I've not run across this scenario personally (I usually have a dedicated smarthost machine, and always use full-qualified aliases), but I suspect that SmokePing doesn't recognize locally defined or not-fully-qualified aliases. Some things I would try: - Try things like cns_design at localhost or cns_design@$HOSTNAME.$TLD if your MTA is configured to allow those - If you're in Sendmail mode (no "mailhost =" directive), try using "mailhost = localhost" or something similar to see what happens. And vice versa: if you're in mailhost mode, try sendmail mode. - Find and remove the address-validation bits from the SmokePing code - Peter On 07/22/2010 11:17 AM, Sorrell, Al wrote: > Using SmokePing 2.4.2 on Solaris 8. > > Within my Solaris servers /etc/mail/aliases file, I have mailing lists set up in the conventional way, such as: > > cns_design: Al_sorrell at troweprice.com,Joe_User at troweprice.com,etc. > > If I try to just use "cns_design" on the Alerts->To= line, I get an error saying that I must have an email address. > If I use it on an "alertee" line, and I have at least one "normal" email address, the config doesn't gripe, but others on the list don't get the notification, e.g.: > > alertee = Al_Sorrell at troweprice.com,cns_design > > Is this a non-feature or is there some other way to get this to work - the goal, of course, being to centralize the distribution lists in one place. > > Thanks, > Al > > > _________________________ > Almon (Al) Sorrell > Corporate Network Services | Network Engineering Consultant > T. Rowe Price > 4515 Painters Mill Road, TE9008 > Owings Mills, MD 21117 > Phone: 410-345-3042 (508-3042) Fax:410-345-3135 > Email: Al_Sorrell at troweprice.com > > > > > T. Rowe Price (including T. Rowe Price Group, Inc. and its affiliates) and its associates do not provide legal or tax advice. Any tax-related discussion contained in this e-mail, including any attachments, is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding any tax penalties or (ii) promoting, marketing, or recommending to any other party any transaction or matter addressed herein. Please consult your independent legal counsel and/or professional tax advisor regarding any legal or tax issues raised in this e-mail. > > The contents of this e-mail and any attachments are intended solely for the use of the named addressee(s) and may contain confidential and/or privileged information. Any unauthorized use, copying, disclosure, or distribution of the contents of this e-mail is strictly prohibited by the sender and may be unlawful. If you are not the intended recipient, please notify the sender immediately and delete this e-mail. > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > From asterix2000 at gmail.com Mon Jul 26 20:35:22 2010 From: asterix2000 at gmail.com (Asterix2000) Date: Mon, 26 Jul 2010 20:35:22 +0200 Subject: [smokeping-users] Alarms every 30 minutes on smokeping Message-ID: How do I set a PATTERN so that when the packet loss is 100% send me an EMAIL ALARM and continue to send (email) every 30 MINUTES until the packet loss of the device is not 100%? From james.cornick at jchost.net Mon Jul 26 20:38:49 2010 From: james.cornick at jchost.net (James Cornick - JCHost.net) Date: Mon, 26 Jul 2010 13:38:49 -0500 Subject: [smokeping-users] Alarms every 30 minutes on smokeping In-Reply-To: References: Message-ID: <4C4DD639.3040905@jchost.net> You might consider using a 'all-clear' type of alarm so you know when it comes back online instantly. I think it's something like this: +NOLOSS type = loss # in percent pattern = >50%,>50%,>50%,==0%,==0%,==0% comment = Network is responding now. James Asterix2000 wrote: > How do I set a PATTERN so that when the packet loss is 100% send me an > EMAIL ALARM and continue to send (email) every 30 MINUTES until the > packet loss of the device is not 100%? > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > > From asterix2000 at gmail.com Mon Jul 26 20:52:05 2010 From: asterix2000 at gmail.com (Asterix2000) Date: Mon, 26 Jul 2010 20:52:05 +0200 Subject: [smokeping-users] Alarms every 30 minutes on smokeping In-Reply-To: <4C4DD639.3040905@jchost.net> References: <4C4DD639.3040905@jchost.net> Message-ID: I already have an alarm for "HOST UP" but the problem is that I've a lot of device and sometimes they go down for different reasons. A lot of them doesn't RESTART so, I've to check manually every single corrispondece of HOST UP with HOST DOWN to see who is already DOWN. Was simple if every 30 minutes I receive an host down alert email. But how to do that? For example if I want a DOWN mail every 15minutes I try with this : pattern ==0%,==0%,==0% .. but I receive the first email after 15 minutes and second, third, etc.. mail after 5 minutes! There isn't a pattern(or symbol) that reset the "previous memory"? 2010/7/26 James Cornick - JCHost.net : > You might consider using a 'all-clear' type of alarm so you know when it > comes back online instantly. > > I think it's something like this: > > +NOLOSS > type = loss > # in percent > pattern = >50%,>50%,>50%,==0%,==0%,==0% > comment = Network is responding now. > > James > > Asterix2000 wrote: >> >> How do I set a PATTERN so that when the packet loss is 100% send me an >> EMAIL ALARM and continue to send (email) every 30 MINUTES until the >> packet loss of the device is not 100%? >> >> _______________________________________________ >> smokeping-users mailing list >> smokeping-users at lists.oetiker.ch >> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >> >> > >