[Dxspider-support] Node pairs that never connect

[Kin]

Hi,

This is an extension of my last listing.

Not always a sh/conn, who or link ensures that the connection has been
established beyond the session level. If it is not established at the
application level, it can be confusing. Logs help to verify if the whole
initialisation process has been completed correctly.

Some errors detected:

F4GVE-2 --> IW1QLH-2 and IW1QLH-33 are not nodes. Please execute: set/user
IW1QLH-2 IW1QLH-33
PY3NZ-8 --> IW1QLH-2 is not node. Please execute: set/user IW1QLH-2
SM7IUN-2 --> SK1MMR It is not really a network node.
VE7CC-1 --> RBN  It is not really a network node.

Partners that do not establish the connection, or if it is established it
does not seem to be completed correctly. Multiple attempts to reconnect
permanently:

7N4TWL-7 <--> JA2YYF-9
9A0DXC <--> DB0SUE-7 (DB0SUE-7 no longer exists)
BG2RVL-9 <--> JA2YYF-9
CS5ARTD-2 <--> CT2IWW-2
CS5SEL-5 <--> CQ0PCV-9
CT1EBQ-9 <--> CS5SEL-5
CU3HY-2 <--> SV5FRI (callsign error, it's not SV5FRI, it's SV5FRI-1)   
DB0HGW-6 <--> DB0SUE-7 (DB0SUE-7 no longer exists) 
DB0OVN-6 <--> DB0SUE-7 (DB0SUE-7 no longer exists)
DJ4PK-2 <--> HB9DRV-9
DO5SSB-2 <--> DB0OVN-6 (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> WB3FFV-2 (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> 9A0DXC (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> DB0HGW-6 (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> WA9PIE-2 (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> HB9DRV-9 (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> KB2SYD-5 (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 <--> OH2J (Possibly DO5SSB-2 is not defined as partner)
DO5SSB-2 --> EA4URE-2 (DO5SSB-2 cannot connect because not defined in
EA4URE-2)
EA2RCF-5 <--> OP0P
EA4RCH-5 <--> DL9GTB-1
EA6VQ-1 --> EA4URE-3 (EA6VQ-1 is not sending password to EA4URE-3)
EA7URG-5 <--> GB7NHR
EA7URG-5 <--> DB0SUE-7 (DB0SUE-7 no longer exists)
EI7MRE <--> UT1U
EI7MRE <--> OP0P
EI7SDX <--> ON4KST
F1FCA-2 <--> PA4JJ-3
F1FCA-2 <--> KF8MZ-3
F4EYQ-1 <--> N6WS-6
F4IAA-3 <--> CT1EBQ-9
GB7DXG-1 <--> VE9SC
GB7NHR <--> EA7URG (callsign error, it's not EA7URG, it's EA7URG-5)
IK2DUW-6 <--> IW2OHX-6
IK8HJC-6 <--> M0KGX-3
IW1PSC-6 <--> PA1RBZ
IW1PSC-6 <--> IK2XDE-6
IW1QLH-6 <--> JG1VGX-8
IW1QLH-6 <--> PY5JO-11
IW5ECF-6 <--> K1TTT
IW5ECF-6 <--> WC2L
IW9FRA-6 <--> K1TTT
JE3YEK <--> JA2YYF-9
JG1VGX-9 <--> JA2YYF-9
KB3CMT-2 <--> PY2ZEN-6
KB3CMT-2 <--> GB7VAX
KD4WLE-4 <--> K1TTT
KE2L-5 <--> DO5SSB-2 (Possibly DO5SSB-2 is not defined as partner)
KF8I-3 <--> F1FCA-2
KM3T-10 <--> KM3T-5
KY9J-2 <--> VE2PKT
KY9J-2 <--> VK5GR
N2YO-2 <--> YO2LOJ-2
OH2J <--> DB0SUE-7 (DB0SUE-7 no longer exists)
OK2CQR-1 <--> VA3UG
ON3URE-2 <--> EA4URE-3 (ON3URE-2 is not sending password to EA4URE-3)
ON3URE-2 <--> EA3CV-3 (ON3URE-2 is not sending password to EA3CV-3)
PE1ITR-8 <--> IV3SCP-6
PE1ITR-8 <--> OP0P
PI4NOS-1 <--> PI4NOS-2
PY1NB-4 <--> N6WS-6
PY1TSP-1 <--> DH1TW-2
PY3NZ-8 <--> PY4OG-2
PY3NZ-8 <--> VE9SC
PY3NZ-8 <--> PY4OG-2
PY4OG-4 <--> PY3NZ-8
R2AKT-9 <--> RA3ATX-8
R2AKT-9 <--> R2DGO-1
R2DGO-1 <--> OP0P
RA3ATX-9 <--> R2AKT-9
SK3W-6 <--> OP0P
SK3W-6 <--> N6WS-6
SM6HOC-6 <--> M0KGX-3
SM7IUN-1 <--> M0KGX-3
SP6PWS-2 <--> SP6MI-2
SV1IW-9 <--> M0KGX-3
SV2HRT-1 <--> CT1EBQ-9
SV2HRT-1 <--> HB9VQQ-2
SV5FRI-1 <--> VE6CIC-1
SV5FRI-1 <--> LA3WAA-6
SV5FRI-1 <--> CU3HY-2
SV5FRI-1 <--> JA2YYF-9
TA2NC <--> IK7IMO-6
VE2PKT-9 <--> KY9J-2
VE3EY-7 <--> K1TTT
VE3TOK-1 <--> VE3LNZ-1
VE3TOK-1 <--> VE3CLG-1
VE3TOK-1 <--> VA3BAL-1
VE3ZIN-2 <--> OK2CQR-1
VE3ZIN-2 <--> M0KGX-3
VE9SC <--> PY3NZ
VK5GR-2 <--> KY9J-2
W8BS-2 <--> OP0P
WA9PIE-2 <--> DO5SSB-2  (Possibly DO5SSB-2 is not defined as partner)
WA9PIE-2 <--> DB0SUE-7 (DB0SUE-7 no longer exists)
WA9PIE-2 <--> DJ4PK-2
WB3FFV-2 <--> HB9DRV-9
YO2LOJ-2 <--> N2YO-4

Merry christmas.

Kin

EA3CV-2 dxcluster.cronux.net 7300
https://clustermap.cronux.net/map.html
https://clustermap.cronux.net/route_finder.html


-----Mensaje original-----
De: Kin <ea3cv at cronux.net> 
Enviado el: miércoles, 25 de diciembre de 2024 18:44
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
Asunto: Node pairs that never connect

Hi,

The following list shows nodes that are trying to establish a connection
with another node (possibly their partner), but are unsuccessful.
You can clearly see that the attempts respond to a cadence defined in your
crontab.
It is possibly a misconfiguration in your connection, or that the pair is
not well defined or is blocked.
This generates unwanted traffic that will be generated ad infinitum.
It is important to verify that the connections are established and
maintained, at least for a few minutes.
Not all of them are there, just some. Those that do not use pc9x, will not
appear.

CS5ARTD-2 to CT2IWWW-2
DO5SSB-2 to EA4URE-2
F1FCA-2 to PA4JJ-3
F1FCA-2 to SV5FRI-2
F4EYQ-1 to N6WS-6
F4IAA-3 to CT1EBQ-9
HG8PRC to HB9ON-9
IQ8DO-6 to IK5ZUK-6
JE3YEK to JA2YYYF-9
KB3CMT-2 to GB7VAX
KY9J-2 to VK5GR
KY9J-2 to VE2PKT
PY1NB-4 to N6WS-6
R2AKT-9 to R2DGO-1
R2DGO-1 to OP0P
SV1IW-9 to M0KGX-3
SV2HRT-1 to CT1EBQ-9
SV2HRT-1 to HB9VQQ-2
TA2NC to IK7IMO-6
WB3FFV-2 to HB9DRV-9
WB3FFV-2 to VE6CIC-1

If you could check your configurations, I would appreciate it.

Merry christmas.

Kin

EA3CV-2 dxcluster.cronux.net 7300
https://clustermap.cronux.net/map.html
https://clustermap.cronux.net/route_finder.html