[smokeping-users] SmokePing segfaults after upgrade to SuSE 11.0

[G.W. Haywood]

Hi there,

On Mon, 14 Jul 2008, System Support wrote:

> I just upgraded from SuSE 10.3 to 11.0, and started getting smokeping
> errors.
>
> I tried upgrading to SmokePing 2.4.1 and EchoPing 6.0.2 but there was
> not change.
>
> Jul 14 21:47:12 Buzzard smokeping.PL[3748]: EchoPingChargen: WARNING:
> "/usr/local/bin/echoping -t 5 -c -n 10 Buzzard" exited with status 1 -
> output follows
> Jul 14 21:47:13 Buzzard smokeping.PL[3748]: EchoPingChargen:
> readline error: 257 bytes read, 256 bytes requested (Illegal seek)
>
> Jul 14 22:09:05 Buzzard kernel: smokeping.PL[5715]: segfault at 2f00 ip
> b7be2906 sp bf9becf0 error 4 in libnss_mdns4_minimal.so.2[b7be2000+2000]
> Jul 14 22:09:41 Buzzard kernel: smokeping.PL[5758]: segfault at 2f00 ip
> b7be2906 sp bf9becf0 error 4 in libnss_mdns4_minimal.so.2[b7be2000+2000]

I don't recognize "smokeping.PL", is that what they call the SmokePing
script (in /usr/sbin?) on a SuSE system?

What's the time and date on the file /usr/local/bin/echoping, and given
that you just installed EchoPing 6.0.2, is that reasonable?

Did the SuSE upgrade provide a SmokePing package of some sort and
create a new SmokePing installation, or is it using the same scripts
and binaries as the older SuSE installation?  If it's a package
provided by SuSE it might be a packaging issue, you could either ask
on a SuSE list or (I'd suggest) rebuild everything from scratch - or
at least all the binaries, the scripts might be OK.  If you don't know
which are binaries and which are scripts, then anything that you can
read with a pager like 'less' is a script.  Do you have any problems
with other probes?

--

73,
Ged.