Tobi, On 12.12.2005 17:30 Tobias Oetiker wrote
> Arnold, > > dont use filter for this. use @include. > > and create separate smokeping instances that only share the > datastore location. > > for each you @include its config ... and for the viewing app you > can @include all the configs ... > > also note that the 1.2 series has the ability to fork, this may > help ... > > if smokeping does not complete a cycle in the time alloted it would > complain in the logfile ... thank you for the hints. > so there may be another problem ... > I've copied the whole config to another host and don't see the problem on this host while it is still on the original one where *all* RTT go up during prime time. Any ideas? Best regards, Arnold > cheers > tobi > Today Arnold Nipper wrote: > >> Dear all, >> >> I have a quite big config >> >> step = 300 >> pings = 20 >> >> FPing: probing 254 targets >> FPing6: probing 55 targets >> EchoPingSmtp: probing 1 targets >> EchoPingHttp: probing 1 targets >> >> and my impression is that smokeping is not able to get thru all these >> targets. The reason why I'm thinking this is, that smokeping has to many >> false positives. It detects losses and high rtt where no loss and no >> high rtt is. >> >> Hence I was happy to run across the --filter option. I've divided my >> config into 6 parts, but after starting the second smokeping I get >> >> ERROR: I Quit! Another copy of /usr/local/smokeping/bin/smokeping >> (28067) seems to be running. >> Check /var/run/smokeping/smokeping.pid >> >> >> Any idea to get around this? >> >> >> >> TIA, Arnold >> > -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: [EMAIL PROTECTED] phone: +49 6224 9259 299 mobile: +49 172 2650958 fax: +49 6224 9259 333 -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/smokeping-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
