[Dxspider-support] Release candidate

[Kin]

Dirk,
 
I have installed the latest build 593 and after the cluster boots, I get the following repeatedly:
 
(*) Undefined subroutine &DXDupe::clean called at ./cluster.pl line 887.
(*)  at ./cluster.pl line 887.
(*)     main::per_5_sec(Mojo::IOLoop=HASH(0x7f835e2d2908)) called at /usr/local/share/perl5/site_perl/Mojo/IOLoop.pm line 220
(*)     Mojo::IOLoop::__ANON__(Mojo::Reactor::EV=HASH(0x7f835e2dfa38)) called at /usr/local/share/perl5/site_perl/Mojo/Reactor/Poll.pm line 141
(*)     eval {...} called at /usr/local/share/perl5/site_perl/Mojo/Reactor/Poll.pm line 141
(*)     Mojo::Reactor::Poll::_try(Mojo::Reactor::EV=HASH(0x7f835e2dfa38), "Timer", CODE(0x7f835b625f20)) called at /usr/local/share/perl5/site_perl/Mojo/Reactor/EV.pm line 70
(*)     Mojo::Reactor::EV::__ANON__(EV::Timer=SCALAR(0x7f835b190f28), 256) called at /usr/local/share/perl5/site_perl/Mojo/Reactor/EV.pm line 32
(*)     eval {...} called at /usr/local/share/perl5/site_perl/Mojo/Reactor/EV.pm line 32
(*)     Mojo::Reactor::EV::start(Mojo::Reactor::EV=HASH(0x7f835e2dfa38)) called at /usr/local/share/perl5/site_perl/Mojo/IOLoop.pm line 134
(*)     Mojo::IOLoop::start("Mojo::IOLoop") called at ./cluster.pl line 920
(*)     main::start_node() called at ./cluster.pl line 939
(*) Undefined subroutine &DXDupe::clean called at ./cluster.pl line 887.
(*) Mojo::Reactor::EV: Timer failed: Undefined subroutine &DXDupe::clean called at ./cluster.pl line 887.
(*)  at /usr/local/share/perl5/site_perl/Mojo/IOLoop.pm line 22.
 
Kin EA3CV
 
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Dirk Koopman via Dxspider-support
Enviado el: miércoles, 19 de marzo de 2025 16:29
Para: Dxspider-Support <dxspider-support at dxcluster.org>
CC: Dirk Koopman <djk at tobit.co.uk>
Asunto: [Dxspider-support] Release candidate
 
There is a release candidate in the test branch. Please take it out for a test drive.

sh/ver
DXSpider v1.57 (build 590 git: test/26b60706[r]) using perl v5.34.0 on Linux
Copyright (c) 1998-2025 Dirk Koopman G1TLH

A lot of work has taken place to harden the program to some network conditions that we may experience in upcoming contests.

There a number of configuration possibilities, please discuss them offline with me so that I get a handle on the correct values. To see the sort of output I am getting, type: set/deb spotdup into a console, and run a: watchdbg spotdup in another shell window.

15:23:52 (spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28074.0 call=BG0HP d=1742397780 text='FT8 +4 dB 1159 Hz TU 73' by=HA5WV node=HG8PRC ipaddr='85.90.180.26'
15:23:52 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XBG0HP|HA5WV|28074|FT84DB1159HZTU7  DUPE=>15:33:51Z
15:23:52 (spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28074.0 call=BG0HP d=1742397780 text='FT8 +4 dB 1159 Hz TU 73' by=HA5WV node=HG8PRC ipaddr=''
15:23:52 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XBG0HP|HA5WV|28074|FT84DB1159HZTU7  DUPE=>15:33:51Z
15:24:16 (spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28434.0 call=XQ3SK d=1742397840 text='5/9 in Css 73 Willy' by=YV5DR node=DH1TW-2 ipaddr='186.185.102.253'
15:24:16 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XXQ3SK|YV5DR|28434|59INCSS73WILLY 
15:24:16 (spotdup) Spot::add_dup: CHECK (QRG-CALL)  XXQ3SK|28434 
15:24:16 (spotdup) Spot::add_dup: CHECK (CALL)      XXQ3SK  
15:24:16 (spotdup) Spot::add_dup: CHECK (BY)        XYV5DR  
15:24:16 (spotdup) Spot::add_dup: CHECK (NODE)      XNDH1TW-2  
15:24:16 (spotdup) Spot::add_dup: CHECK (IPADDR)    X186.185.102.253  
15:24:16 (spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28434.0 call=XQ3SK d=1742397840 text='5/9 in Css 73 Willy' by=YV5DR node=DH1TW-2 ipaddr=''
15:24:16 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XXQ3SK|YV5DR|28434|59INCSS73WILLY  DUPE=>15:34:15Z
15:24:16 (spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=28434.0 call=XQ3SK d=1742397840 text='5/9 in Css 73 Willy' by=YV5DR node=DH1TW-2 ipaddr='186.185.102.253'
15:24:16 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XXQ3SK|YV5DR|28434|59INCSS73WILLY  DUPE=>15:34:15Z
15:24:17 (spotdup) Spot::add_dup: CHECK (+INPUT+)   freq=18104.2 call=OE8DDX d=1742397840 text='' by=KC0GU node=VE7CC-1 ipaddr='172.59.0.174'
15:24:17 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XOE8DDX|KC0GU|18104| 
15:24:17 (spotdup) Spot::add_dup: CHECK (QRG-CALL)  XOE8DDX|18104 
15:24:17 (spotdup) Spot::add_dup: CHECK (CALL)      XOE8DDX  
15:24:17 (spotdup) Spot::add_dup: CHECK (BY)        XKC0GU  
15:24:17 (spotdup) Spot::add_dup: CHECK (NODE)      XNVE7CC-1  
15:24:17 (spotdup) Spot::add_dup: CHECK (IPADDR)    X172.59.0.174  

For fun, open another shell window and type: watchdbg CHECK ' ADD| FLOOD' and run that beside the other shell window. Before you ask, I do have a pair of 32" 4K monitors...

Enjoy 

Dirk G1TLH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250320/ec0181a1/attachment-0001.htm>