[Dxspider-support] List of nodes with connection problems
Kin
ea3cv at cronux.net
Mon Jan 20 17:58:42 GMT 2025
Hi again,
Here is an example of what I am trying to transmit to you.
It is a REAL node that has 4 partners defined.
But really, it only has 1 working (PE1ITR-8), the other 3 are not sending
spots because the connection between nodes has not been initialised, only
the TCP/IP session.
If the link with PE1ITR-8 goes down, the node will be isolated even if it
has 3 more partners.
At one point you see this with the 'link' command:
Ave Obs Ping Next
Filters
Callsign Type Started Uptime RTT Count Int. Ping Iso?
In Out PC92? Address
EI7MRE DXSP 20-Jan-2025 1700Z 13m 27s 0.02 2 300 250
93.93.131.99
JA2YFF AR-C 20-Jan-2025 1700Z 13m 26s 999.00 0 300 100
138.64.131.174
PE1ITR-8 DXSP 16-Jan-2025 2114Z 3d 19h 58m 0.01 2 300 270
Y 212.227.171.124
SK3W DXSP 20-Jan-2025 1700Z 13m 27s 999.00 0 300 100
155.4.13.194
When 15 minutes have passed, spider has reached its time out, and TCP/IP
sessions are dropped. Only the link to PE1ITR-8 remains:
Callsign Type Started Uptime RTT Count Int. Ping Iso?
In Out PC92? Address
PE1ITR-8 DXSP 16-Jan-2025 2114Z 3d 20h 0.01 2 300 156
Y 212.227.171.124
When the cron is run on this node, it notices that there are 3 down links,
and proceeds to run a connect, but it is only TCP/IP:
Callsign Type Started Uptime RTT Count Int. Ping Iso?
In Out PC92? Address
EI7MRE DXSP 20-Jan-2025 1720Z 1m 16s 0.02 2 300 381
93.93.131.99
JA2YFF AR-C 20-Jan-2025 1720Z 1m 15s 999.00 1 300 381
138.64.131.174
PE1ITR-8 DXSP 16-Jan-2025 2114Z 3d 20h 6m 0.01 2 300 101
Y 212.227.171.124
SK3W DXSP 20-Jan-2025 1720Z 1m 16s 999.00 1 300 381
155.4.13.194
As soon as the 15 minutes are reached, the links will be down again.
And what are the reasons why these 3 links do not work?
In the case of JA2YFF, the sysop of this node should have executed the
command 'set/pinginterval 0 JA2YFF', because it is a connection between a
DXSpider and an ARC node.
If we look at the SK3W node, the cause is that there is no node with this
callsign, its callsign is indeed SK3W-6.
And where is the error? Possibly in the name of the connection file in
/spider/connect/SK3W, and in its crontab where SK3W has also been put. But
it should be SK3W-6.
I think it is so, because in this case everything indicates that the session
is started from this node (not from SK3W-6). But it could be that SK3W-6
started the session, if this is the case and the 'link' command shows us the
callsign SK3W, it is probable that SK3W-6 has put in its connection file
with this node 'login:' 'SK3W', instead of 'login:' 'SK3W-6'.
And what happens with EI7MRE?
Well, it is difficult to say for an outside observer, because EI7MRE is a
correct callsign of node.
It could be, I think:
1. An incorrect node type definition in either of the two nodes.
2. That it was not defined as a node, that is, the other node sees it as a
user, or vice versa.
This case is not unique, we can see in the previous message the list with
the annotations that I believe are the cause, but there are more nodes in
this situation.
Therefore, I think that solving it will first benefit the sysop of the
node(s) with problems, and then the rest of the network.
Regards,
Kin EA3CV
_____________________________________________
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Kin
via Dxspider-support
Enviado el: lunes, 20 de enero de 2025 17:56
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
CC: Kin <ea3cv at cronux.net>
Asunto: [Dxspider-support] List of nodes with connection problems
Hi,
Have been able to reduce some of the noise generated by misconfigurations,
but there are still nodes that inexplicably, having received emails through
this thread and personal mails, have not been able to solve the problems.
The collaboration of the Community is needed to keep the Network as good as
possible. Please, if you have any doubts, say so, otherwise it won't be
solved.
List updated at 1600 UTC 20250120
* The following DXSpider nodes that connect to an ARCluster node.
DXSpider sysops should run the following command:
set/pinginterval 0 <arc-node>
And include the command in /spider/scripts/startup for the future.
DXSpider ARC
-------- -------
IW9FRA-6 K1TTT
7N4TWL-7 JA2YYF
VE3EY-7 K1TTT
IW1QLH-6 JG1VGX-8
SV2HRT-2 JG1VGX-9
^
WRONG
* Nodes with a CONFIGURATION ERROR in their node callsign
Possibly the 'login' in /spider/connect/<node> is incorrectly defined.
Both nodes should make sure that their partner is well defined or use
set/lock <node>
CU3HY-2 SV5FRI <- does not exist, it is SV5FRI-1
GB7NHR EA7URG <- does not exist, it is EA7URG-5
KY9J-2 VE2PKT <- does not exist, it is VE2PKT-9
KY9J-2 VK5GR <- does not exist, it is VK5GR-2
OK2CQR-1 VA3UG <- does not exist, it is VE3ZIN-2
PY3NZ-8 PY4OG-2 <- does not exist, it is PY4OG-4
YO2LOJ-2 N2YO-4 <- does not exist, it is N2YO-2
* Nodes trying to connect to non-existent nodes
This is solved by deleting them from the crontab and executing set/user
<node> and set/lock <node>
BG2RVL-9 JA2YYF-9 <- does not exist
DJ4PK-2 HB9DRV-9 <- does not exist
IW1QLH-6 IW1QLH-2 <- is not a node
JG1VGX-9 JA2YYF-9 <- does not exist
^
WRONG
CS5ARTD-2 CT2IWW-2 <- exist ???
CS5SEL-5 CQ0PCV-9 <- not info ???
IZ0ORT-6 IZ0ORT-8 <- exist ???
EA4URE-3 ON3URE-2 <- password has been incorrectly defined
EA4URE-3 EA6VQ-1 <- password has been incorrectly defined
^
WRONG
* Nodes trying to connect to partners that do not have them defined as
nodes.
This is solved by deleting them from the crontab and executing set/user
<node> and set/lock <node>
F4IAA-3 CT1EBQ-9
IQ1LA-6 PA1RBZ
IZ0ORT-6 IW0ERQ-6
KB3CMT-2 GB7VAX
PE1ITR-8 IV3SCP-6
SK3W-6 N6WS-6
SV2HRT-1 CT1EBQ-9
W9TY-1 WA0O-9
* Nodes with configuration problems in one or both of the nodes of the pair.
This is solved by speaking the sysops or set/lock <node>
CT1EBQ-9 CS5SEL-5
DB0ALG-9 DB0PER
EI7MRE OP0P
F6KVP-3 F6BVP-3
R2AKT-9 RA3ATX-8
SK3W-6 OP0P
WA9PIE-2 DJ4PK-2
WB3FFV-2 VE6CIC-1
Thanks,
Kin EA3CV
<Archivo: Datos adjuntos sin título 00167.txt >>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 10786 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250120/d237f5f2/attachment-0001.bin>
More information about the Dxspider-support
mailing list