[smokeping-users] ssh-keyscan error starting from boot only

[Peter Kristolaitis]

My guess would be that the SSH daemon hasn't started yet when Smokeping 
tries to start up.  Make sure that your init order puts SSH before 
Smokeping, and if necessary, maybe add a few seconds' delay to the 
Smokeping startup script.

It's kind of weird that the Smokeping init script would completely bomb 
out when one of the probes fail (it should probably just return UNDEF), 
but I suspect changing the init order for your services will work around 
the problem.

- Pete


On 01/23/2013 02:17 PM, Vinny_Abello at Dell.com wrote:
>
> Hello,
>
> I'm wondering if anyone has encountered this problem. We're running 
> smokeping 2.6.7 on FreeBSD 8.3. When the system boots up, the startup 
> script tries to start smokeping, but smokeping errors out on 
> initializing the ssh-keyscan probe with the following error:
>
> Starting smokeping.
>
> ### parsing dig output...OK
>
> ERROR: output of '/usr/bin/ssh-keyscan -t dsa,rsa,rsa1 127.0.0.1' does 
> not match (?i-xsm:^# \\S+ SSH-)
>
> at (eval 56) line 1
>
> /etc/rc: WARNING: failed to start smokeping
>
> The very strange thing is if I start smokeping using the same startup 
> script manually after the system has booted, I get no error at all and 
> everything works fine.
>
> Any thoughts on why this is and how I would go about correcting it?
>
> Thanks!
>
> -Vinny
>
>
>
> _______________________________________________
> 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/20130123/5b23aae7/attachment.htm