[Dxspider-support] List of incorrectly configured nodes
Enrico Lorenzoni
iu3azc at gmail.com
Mon Feb 3 21:56:35 GMT 2025
Hi Rui,
perhaps the version in cluster.pl is obtained with git
https://github.com/latchdevel/DXspider/blob/mojo/perl/cluster.pl#L563
but you delete it in your docker image?
https://github.com/ruilvo/dxspider-deployment/blob/master/dxspider/Dockerfile#L47
I'd give it a try without removing git, it should help.
73 de IU4AZC Enrico
Il giorno lun 3 feb 2025 alle ore 21:17 Rui Oliveira via Dxspider-support <
dxspider-support at tobit.co.uk> ha scritto:
> Hi,
>
> I fixed the problem with CT2IWW-2 pointing to N2KI's node. There was a
> wrong config. file from bad copy pasting.
>
> About CS5ARTD-2 in general:
>
> The DXSpider node is up to date. It’s updated regularly.
> However, it does not report a version number. I don’t know why, and we
> have asked for help about this before.
>
> The full story (which I told N2KI before today, but I'll say it again
> for everybody):
>
> I (when I say “I” I mean myself, Rui, the technical admin of the system)
> use a modified Docker container to host the DXSpider node. We (when I
> say we, I mean the ARETD group) run a very sophisticated VPS with
> multiple services running together. Right now, it’s 3 websites with 7
> different services running. For us, the isolation provided by Docker is
> essential for the smooth running of things. Not using it is not an option.
>
> The Docker setup used to host DXSpider is this:
> https://github.com/ruilvo/dxspider-deployment
> If you look at this file:
>
> https://github.com/ruilvo/dxspider-deployment/blob/master/dxspider/Dockerfile#L40
> you see that the container always clones the repository from the top of
> the tree when the image is built.
> This is actually how I update DXSpider. I save the configuration, nuke
> the container image, and rebuild.
> I’m using the mojo branch. It’s set here:
>
> https://github.com/ruilvo/dxspider-deployment/blob/master/docker-compose.yml#L24
>
> Now, the version number. Whenever you login into our server, it just says:
> `running DXSpider V build
> Capabilities: ve7cc rbn`
>
> Why is the version number empty? I don’t know. I haven’t managed to
> figure it out.
>
> If you manage to figure out what is wrong and how we can improve, we
> would very much like doing so as well. We're always getting complains
> about our version number, but I keep the system up to date very regularly.
>
> Extra thoughts:
> Is the problem that I am cloning the repository from the top of the
> tree? Does DXSpider use any kind of tags for official release versions
> on git? And that’s maybe why our server doesn’t provide one? Because the
> top of the tree doesn’t have one?
>
> Any help?
>
> Thanks.
> Rui, CT7ALW
>
> Às 07:48 de 03/02/2025, dxspider-support-request at tobit.co.uk escreveu:
> > Date: Mon, 3 Feb 2025 08:47:53 +0100
> > From: "Kin"<ea3cv at cronux.net>
> > To: "'The DXSpider Support list'"<dxspider-support at tobit.co.uk>
> > Subject: [Dxspider-support] List of incorrectly configured nodes
> > Message-ID:<020201db760f$f0102ae0$d03080a0$@cronux.net>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Hi,
> >
> > With the collaboration of some sysops, part of the noise on the network
> has
> > been reduced, but not enough.
> > There are still quite a few sysops who have not resolved their connection
> > issues with their partners.
> >
> > Some sysops have done everything possible to communicate with their
> > partners, and due to a lack of response, they have removed their partner
> > from their crontab.
> >
> > Throughout several messages, I have sometimes pointed out what the
> problem
> > might be and suggested a possible solution, but in most cases, I have not
> > received the necessary engagement.
> >
> > When it is not possible to solve the issue through dialogue, the only
> > options left are:
> > set/lock
> > set/badip
> >
> > There are still nodes running very old versions that refuse to update,
> > despite the available tools that make migrating to the Mojo branch, and
> even
> > to its latest build, easier.
> > This outdatedness also contributes to undesirable node behaviors, which
> Dirk
> > has addressed in his latest releases. Please update for the sake of
> > everyone.
> >
> > Here is the data from 2025-02-02:
> >
> > Summary of Pairs with A/D > 24
> > Node-1 Node-2 Conn Disc ALL
> > ----------------------------------------
> > 7N4TWL-7 JA2YYF 0 115 115
> > 7N4TWL-7 JA2YYF-9 63 62 125
> > 9A0DXC HG8PRC 30 15 45
> > BG2RVL-9 JA2YYF-9 64 65 129
> > CS5ARTD-2 CT2IWW-2 0 142 142
> > CS5SEL-5 CQ0PCV-9 72 72 144
> > CT1EBQ-9 CS5SEL-5 72 72 144
> > CU3HY-2 ES3V-3 12 13 25
> > CU3HY-2 SV5FRI 143 70 213
> > DB0ALG-9 DB0PER 21 56 77
> > DB0PER DB0PER-1 16 9 25
> > DJ4PK-2 HB9DRV-9 180 90 270
> > DO5SSB-2 ES3V-3 9 31 40
> > EA3CV-8 N4VFF-2 24 21 45
> > EI7MRE OP0P 71 70 141
> > EI7SDX ON4KST 0 62 62
> > ES3V-3 ES3V-2 0 54 54
> > F4IAA-3 CT1EBQ-9 0 144 144
> > F6BVP-3 F6KVP-3 85 70 155
> > F6KVP-3 F6BVP-3 73 71 144
> > GB7DXG-1 GB7BAA 0 286 286
> > GB7NHR ON0DXC 15 15 30
> > GB7VAX SQ3MZM-3 1 29 30
> > HG8PRC 9A0DXC 26 15 41
> > HG8PRC F6GCP-3 15 15 30
> > HG8PRC KC9AOP-1 16 16 32
> > HI8S-8 NL7S 72 72 144
> > I8ZSE-1 SV1IW-9 0 143 143
> > IK7NXU-6 IZ3LSV-6 32 16 48
> > IQ1LA-6 PA1RBZ 1 83 84
> > IV3SCP-6 IZ3LSV-6 30 16 46
> > IW1PSC-6 PA1RBZ 0 63 63
> > IW1QLH-6 JG1VGX-8 16 15 31
> > IW2NOY-2 LZ7A 28 0 28
> > IW8PGT-9 IZ3LSV-6 32 16 48
> > IW9FRA-6 K1TTT 70 70 140
> > IZ0FKE IZ0ORT-8 0 59 59
> > IZ0FKE SV1IW-9 0 139 139
> > IZ0FKE-6 VE7CC 0 48 48
> > IZ0ORT-6 IW0ERQ-6 0 144 144
> > IZ0ORT-6 IZ0ORT-8 76 77 153
> > IZ3LSV-6 IK7NXU-6 20 16 36
> > IZ3LSV-6 IV3SCP-6 24 16 40
> > IZ3LSV-6 IW8PGT-9 16 16 32
> > JG1VGX-9 JA2YYF-9 64 65 129
> > K4GSO-2 N2KI 8 27 35
> > K4JW N4VFF-2 26 15 41
> > KB3CMT-2 GB7VAX 0 143 143
> > KB3CMT-2 PY2ZEN-6 0 143 143
> > KC9AOP-1 HG8PRC 32 16 48
> > KC9AOP-1 N4VFF-2 34 20 54
> > KD4WLE-4 K1TTT 0 69 69
> > KD4WLE-4 N2KI 8 27 35
> > KM3T-10 KM3T-5 0 69 69
> > KY9J-2 ON0DXC 17 17 34
> > KY9J-2 VE2PKT 144 72 216
> > KY9J-2 VK5GR 144 75 219
> > N2YO-2 YO2LOJ-2 72 71 143
> > N4VFF-2 EA3CV-8 28 7 35
> > N4VFF-2 KC9AOP-1 22 11 33
> > N7OD GB7MBC 0 136 136
> > N7OD IZ0FKE 0 141 141
> > N7OD ON0DXC 31 31 62
> > N7OD W1DX 0 144 144
> > NL7S HI8S 72 0 72
> > OK0DXI SR4DXC 30 15 45
> > OK2CQR-1 VA3UG 174 90 264
> > ON0DXC EI7MRE 71 70 141
> > ON0DXC JA2YFF 61 60 121
> > ON0DXC OP0P 44 0 44
> > ON0DXC SK3W 71 71 142
> > ON3URE-2 EA4URE-3 0 144 144
> > PY1NB-4 N2KI 6 27 33
> > PY3NZ-8 ON0DXC 16 16 32
> > PY3NZ-8 PY4OG-2 144 72 216
> > PY4OG-4 PY3NZ-8 72 72 144
> > SK3W-6 N6WS-6 0 119 119
> > SK3W-6 OP0P 71 71 142
> > SQ3MZM-3 GB7VAX 2 28 30
> > SR4DXC OK0DXI 32 16 48
> > SV2HRT-1 CT1EBQ-9 0 141 141
> > SV5FRI-1 CU3HY-2 72 72 144
> > SV5FRI-1 VE6CIC-1 72 72 144
> > VE2PKT-9 KY9J-2 72 72 144
> > VE3EY-7 K1TTT 71 70 141
> > VE3ZIN-2 OK2CQR-1 172 90 262
> > VE6CIC-1 SV5FRI 72 0 72
> > VE6CIC-1 WB3FFV 72 0 72
> > VE6DXC VE3CGR-5 36 0 36
> > VK5GR-2 KY9J-2 72 143 215
> > W9TY-1 WA0O-9 0 1435 1435
> > WA9PIE-2 DJ4PK-2 90 90 180
> > WB3FFV-2 VE6CIC-1 72 72 144
> > YO2LOJ-2 N2YO-4 72 71 143
> > ----------------------------------------
> > Total 3866 7187 11053
> >
> > Not both nodes of a pair are incorrectly configured.
> > If any sysop would like more information on the possible cause of their
> > connection failure, please refer to previous messages.
> >
> >
> > 73 de Kin EA3CV
>
> _______________________________________________
> 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/20250203/b69f141e/attachment.htm>
More information about the Dxspider-support
mailing list