[Dxspider-support] Corrupted storable string crash

[Dirk Koopman]

Saki

A very good question. AFAIK only two nodes crashed, at roughly the same 
time, using different operating systems and different perls. Both on 
spots and both in (apparently) the same way - which shouldn't be 
possible on a properly installed perl installation - as the components 
are part of the standard perl distribution.

Still looking....

73 Dirk G1TLH

On 14/08/2019 07:24, dd5xx--- via Dxspider-support wrote:
> So why does this happen only to some users but not to everyone? My 
> spider did not crash.
> 73
> Saki, DD5XX
> *Gesendet:* Mittwoch, 14. August 2019 um 01:07 Uhr
> *Von:* "Dirk Koopman via Dxspider-support" <dxspider-support at tobit.co.uk>
> *An:* "Mike McCarthy, W1NR" <lists at w1nr.net>, "The DXSpider Support 
> list" <dxspider-support at tobit.co.uk>
> *Cc:* "Dirk Koopman" <djk at tobit.co.uk>
> *Betreff:* Re: [Dxspider-support] Corrupted storable string crash
> This is the problem.
>
> On 13/08/2019 23:16, Mike McCarthy, W1NR wrote:
> > 1565532003^Storable binary image v122.15 more recent than I am (v2.9) at
> > /usr/lib64/perl5/vendor_perl/Storable.pm line 4
> > 18.
> > 1565532003^ at /usr/lib64/perl5/vendor_perl/Storable.pm line 418.
> > 1565532003^ eval {...} called at
> > /usr/lib64/perl5/vendor_perl/Storable.pm line 418
> > 1565532003^
>
> Please send me the answers to:
>
> which perl
>
> and
>
> perl -v
>
> and
>
> perl -e 'print  "@INC\n"'
>
> Please check how many versions of Storable.pm you have on the system.
> it's possible you may have more than one version on your system. Use:
>
> locate Storable.pm
>
> (install mlocate and do a sudo updatedb if you don't have locate 
> installled)
>
> You may get several answers but on my Ubuntu 18.04 system it's located
> at /usr/lib/x86_64-linux-gnu/perl/5.26.1/Storable.pm and I am using perl
> 5.26. and on 16.04 it's perl 1.22.1 and
> /usr/lib/x86_64-linux-gnu/perl/5.22.1/Storable.pm. On a recent RPi
> version of Debian it lives in /usr/share/perl/5.28.1/Memoize/Storable.pm.
>
> The versions of a data item and Storable.pm have to match or at least
> have the same or later version of Storable.pm than the version used to
> create the data item. The message suggests that the Storable.pm that
> cluster.pl is using is EARLIER than the version used to create the entry
> in qsl.v1. So using the version of Storable.pm that is in 'vender_perl'
> is very suspicious. In theory, this shouldn't be possible, and on a
> completely standard perl installation that is older than the data it
> isn't. But something is clearly screwed up here. If it's any comfort,
> this did happen to me several years ago and it was a screwed up perl
> installation.
>
> Also check what the system thinks is the version of Berkeley DB it
> thinks your qsl.v1 is, try:
>
> file qsl.v1
>
> I get
>
> qsl.v1: Berkeley DB (Btree, version 9, native byte-order)
>
> On my Ubuntu 18.04 system it's located at
> /usr/lib/x86_64-linux-gnu/perl/5.26.1/Storable.pm and I am using perl
> 5.26. and on 16.04 it's perl 1.22.1 and
> /usr/lib/x86_64-linux-gnu/perl/5.22.1/Storable.pm.
>
> If all else fails let's continue this offline.
>
> 73 Dirk G1TLH
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20190814/d7bb38a1/attachment.html>