[smokeping-users] Issues with high speed curl probes

Russell Dwarshuis rjd at merit.edu
Tue Aug 11 20:10:00 CEST 2009


It's morse code: 'help me, i am trapped in a data center' ;-)

Seriously, I've seen the same broken line on graphs when I had a probe 
that was taking too long to run.  Check your config for a non-responsive 
host (assuming you have lots of other stuff in your config file).  You can 
turn on debugging if you can't spot the host by eyeballing the graphs.


                                           -Russell Dwarshuis

On Tue, 11 Aug 2009, Jonah Horowitz wrote:

> I was running this configuration for awhile and everything worked fine.
> We had a power outage at our data center, and when it came back up, the
> graphs (and the data) started looking like this:
>
>
>
> http://www.flickr.com/photos/aspenjonah/3811409039/sizes/o/
>
>
>
> I'm just wondering if anyone has seen something similar, or knows how to
> fix it.  I tried upping my forks parameter on my smokeping server, but
> that didn't seem to fix the problem.
>
>
>
> My config for the probe is:
>
>
>
> + Curl
>
> binary = /usr/bin/curl
>
> forks = 30
>
> offset = 50%
>
> timeout = 5
>
>
>
> ++ CurlSlow
>
> step = 300
>
>
>
> ++ CurlFast
>
> step = 60
>
>
>
> + LooksmartURLs
>
> menu = Looksmart URLs
>
> title = Looksmart URLs
>
> slaves = sh-mon1i
>
> probe = CurlFast
>
>
>
> ++ wwwLooksmartCom
>
> title = www.looksmart.com
>
> host = www.looksmart.com
>
> urlformat = http://%host%
>
>
>
>
>
> TIA,
>
>
>
> Jonah
>
>
>
>



More information about the smokeping-users mailing list