[Dxspider-support] For all sysops
Peter
pc2a at pi4cc.nl
Sun Feb 19 13:45:45 GMT 2023
Hi Kin
I think the mistake is that after a update the sysops don't restart the
node to avoid loose of users....
Thats why you see with your script a old version.
Peter
PC2A
Op 19-2-2023 om 14:30 schreef David Spoelstra via Dxspider-support:
> Kin-
>
> Thank you for your email and thank you for all your work. I've got a
> few questions and suggestions:
>
> 1. By your own admission, the method of determining versions seems
> flawed. Maybe we find a method that works 100% before we send out more
> block lists?
> 2. Are we going to send out unblock lists, or only block lists? Maybe
> we can get this automated somehow? Do I need to personally go to all
> my users (who have all left to other nodes since they are contesters)
> and the nodes I was connected to and convince them that I'm no longer
> blocked?
> 3. The first date I can find on this reflector with a block list with
> my node on it was Feb 17. It's Feb 19 today. I only have time for ham
> radio on the weekends. Before I could even read the reflector email, I
> got a call from a user on my node that I wasn't getting any spots.
> Maybe we could give people a week or two (especially if there is a big
> contest like ARRL International DX CW this weekend) to respond if they
> see themselves on a block list before they get blocked?
>
> Also Kin, thanks for your offer of connecting to your node. But all my
> users are contesters and they have left me for W9YB (an AR-Cluster)
> since my cluster stopped getting spots during one of the biggest
> contests so I'll probably be taking my cluster down and using W9YB
> myself. Sad since I see my cluster has been on 24x7 since Nov 1, 2010
> "DXSpider V1.55, build 0.82 (git: b7512d7) started".
>
> Thanks for all your hard work over the years Dirk!
>
> -David, N9KT
>
>
> On Sun, Feb 19, 2023 at 6:44 AM Kin <ea3cv at cronux.net> wrote:
>
> Dear David,
>
> I have just run:
>
> sh/view N9KT
>
> Node Version Build PC9X via PC92
>
> N9KT-2 5455 229 Yes Yes Yes
>
> 1 Nodes found
>
> As you can see, my dxspider (Mojo build 497) tells me that you are
> using a rather old build.
>
> When I ran:
>
> rcmd N9KT-2 sh/ver
>
> RCMD 'sh/ver' sent to N9KT-2
>
> EA3CV from EA3CV-2 19-Feb-2023 1133Z dxspider >
>
> N9KT-2:DXSpider v1.55 (build 250 git: master/9fb58f4a[r]) using
> perl v5.32.1 on Linux
>
> I see you're actually on 250.
>
> I don't know why the first information is wrongly displayed, but
> the method of using *rcmd* is very limited because there are quite
> a few sysops that don't allow it, so I discarded it.
>
> I'm sorry you were excluded and I hope you will be quickly
> reinstated as it was an unintentional mistake.
>
> It's good to know that there are people like you who help other
> sysops, I appreciate that selflessness, but I think your way of
> expressing yourself is not the most appropriate. I've also been
> put on the badnodes list for sending ANNs that users didn't like,
> and it didn't occur to me to get that way with the sysop who did
> it, who, by the way, I was helping with the update of his node.
>
> It's very easy and cheap to attack, the hard part seems to be that
> it's possible for mistakes to be made when tackling a change of
> this magnitude.
>
> I'm sorry for what happened and hope it gets fixed as soon as
> possible. But if you want, I'll set you up on my node until they
> unblock.
>
> Sorry for my English.
>
> Kin EA3CV
>
> *De:* David Spoelstra <davids at mediamachine.com>
> *Enviado el:* domingo, 19 de febrero de 2023 12:28
> *Para:* The DXSpider Support list <dxspider-support at tobit.co.uk>
> *CC:* Kin <ea3cv at cronux.net>
> *Asunto:* Re: [Dxspider-support] For all sysops
>
> Kin-
>
> I'm pissed. I was just able to sit down and go through these
> emails from the last couple of days.
>
> I went to lockout these nodes to be on the *team* when I find my
> own node in your list as "N9KT-2 5455 229".
>
> My node auto updates once a day. I went back through my logs and
> I've been on build 250 since AT LEAST Feb 9th (as far back as my
> logs go).
>
> Even your own github list
> "https://github.com/EA3CV/dxspider_info/blob/main/Node_version/Master-20230219.txt"
> has me listed as "N9KT-2 5455 250"
>
> So, your data is CRAP!
>
> How do we know that the rest of your data is good? How many good
> nodes have been locked out because of your CRAP data?
>
> Also, you mentioned that you tried to contact each of us. I did a
> search and came up with nothing from you. I even went through my
> spam folder looking for something from you. I don't know which
> email address you were using, but the address on
> "https://www.dxcluster.info/telnet/index.php" is correct and has
> been correct for years. I run a consulting company and receive
> 100+ emails a day to that address so I know it works.
>
> So is this why I noticed today that suddenly I'm not connected to
> about five nodes I used to connect to?
>
> YOUR DATA IS CRAP!
>
> To think how many node owners I've helped over many years and to
> now have my node blocked because of your CRAP data really pisses
> me off! I even helped some of the BIG nodes like WA9PIE get on
> DXSpider!
>
> -David, N9KT
>
> On Fri, Feb 17, 2023 at 5:58 AM Kin via Dxspider-support
> <dxspider-support at tobit.co.uk> wrote:
>
> Hi all,
>
> I think it is time to get involved and play as a team.
>
> After having tried to contact all the spider nodes by email,
> the following list (except for error, sri) have not replied or
> have not been located. I therefore ask you to block them.
>
> It may seem very drastic, but we need the involvement of most
> of the sysops if we want to solve the problems we have.
>
> The blocking should be done so that we can inform those sysops
> of the changes that have occurred and the need to update their
> nodes. They can then be unblocked.
>
> For those of you who think this doesn't affect you because
> you're on your own, I think you're making a big mistake, and
> you'll realise it when you find yourself excluded from the
> *team*. This is a request for help to get a necessary change
> for our Community.
>
> This list is not just for us to ask for help and advice, it is
> for us to answer those requests for help. There are sysops who
> only show up here when they have problems, and when you ask
> for their help they don't even answer you, this behaviour is
> not part of the ideals of our hobby. We count on you?
>
> If you can, update your details at:
> https://www.dxcluster.info/telnet/submit.php
> <https://www.dxcluster.info/telnet/submit.php%20> which will
> appear at https://www.dxcluster.info/telnet/index.php
> <https://www.dxcluster.info/telnet/index.php>
>
> Execute command
>
> *set/lockout <node>*
>
> *disc <node>*
>
> and verify with:
>
> *sh/lockout <node>*
>
> Unlockout is done like this:
>
> *unset/lockout <node>*
>
> And the list of those affected:
>
> *Column1 Column2 Column3*
> 9M2PJU-1 5455 196
> A61BK-1 5455 198
> AB2VY-12 5455 200
> AB2VY-2 5455 203
> AB2VY-3 5455 215
> AB2VY-6 5455 199
> AB2VY-7 5455 210
> AB2VY-9 5455 249
> AI3I-15 5455 203
> CS5ARLC-1 5455 197
> CT1EBQ-9 5455 204
> DB0HGW-6 5455 216
> DB0IUZ-6 5455 249
> DB0OVN-6 5455 249
> DB0PRA-9 5455 115
> DB0RBS-11 5455 249
> DB0TUD-6 5455 100
> DB0UHI-9 5455 166
> DD5XX-10 5455 196
> DG2KBC-1 5455 82
> DK7ET-4 5455 248
> DK7ET-5 5455
> DL1FLW-1 5455 249
> DQ8Z 5455 204
> EA2RKS-2 5455 249
> EA5URM-5 5455 216
> EA7URG 5455
> EA7URG-5 5455 196
> ED3ZAK-5 5455 249
> EW8AX-1 5455 115
> F4ERG-3 5455 199
> F4GVE-2 5455 175
> F4IAA-3 5455 249
> F5MZN-3 5455 33
> F6KVP-3 5455 141
> F8KHI-3 5455 198
> G7VJR-5 5455 115
> GB7BEX-9 5455 204
> GB7DXX 5455 115
> GB7IPF 5455 198
> GB7KUX-4 5455 249
> GB7NHR 5455 166
> HA5KDR-3 5455 249
> HA6DX 5455 32
> HB9IAC-8 5455 115
> HG6DXC 5455
> I0INU-6 5455 216
> I0OJJ-6 5455 250
> IK2DUW-6 5455 166
> IK4PKL-6 5455 115
> IQ1GP-6 5455 249
> IQ1LA-6 5455 196
> IQ5KG-6 5455 52
> IQ8PQ-6 5455 166
> IQ8RB-6 5455 166
> IQ8XF 5455 249
> IR2UGI-5 5455 250
> IR2UGI-6 5455 249
> IR4FOC-6 5455 216
> IR4U-6 5455 216
> IT9FTP-6 5455 236
> IT9OBK-6 5455 200
> IV3BVK-5 5455 216
> IW1QLH-6 5455 163
> IW2EVH-6 5455 171
> IW8PGT-9 5455 115
> IW9FDD-6 5455 82
> IW9HHF-8 5455 216
> IZ0AWG-6 5455 115
> IZ0ORT-6 5455 216
> IZ5IIN-6 5455 190
> IZ5ILU-6 5455 198
> IZ6RND-6 5455
> IZ8DMZ-6 5455 171
> JH1RFM-9 5455 216
> K0PIR-2 5455 181
> K2LS 5455 82
> K4JW 5455 65
> K4KYD 5455 249
> K4KYD-2 5455 249
> K8QIK-3 5455 80
> KB2FAF-12 5455 249
> KB8UVN-2 5455 73
> KC5PQX-9 5455 249
> KC9AOP-1 5455 229
> KG4OOL-2 5455 249
> KY9J-2 5455 216
> LZ0DXC 5455 249
> M0KGX-3 5455 217
> MX0ONL 5455 115
> N4DW-9 5455 166
> N8NM 5455 249
> N9KT-2 5455 229
> NA7KR-3 5455 250
> NL7S 5455 250
> NP3N 5455 203
> NR0Q-2 5455 217
> NR1X-3 5455 166
> OH1RCF 5455 250
> OK0DXI 5455 52
> OK2CQR-1 5455 250
> ON0LLV-5 5455 249
> ON3URE-2 5455 216
> ON4KST-2 5455 216
> PD0SIM-2 5455
> PY1TSP-1 5455 197
> PY2ZEN-6 5455 250
> PY4OG-2 5455 229
> SK6AW-2 5455 166
> SM4ONW-14 5455 218
> SM6EAT-6 5455 249
> SM6HOC-14 5455 218
> SM6HOC-2 5455 218
> SM6HOC-6 5455 218
> SM6YOU-2 5455 82
> SM6YOU-4 5455 166
> SM6YOU-7 5455 82
> SR2PUT 5455 197
> SR4DXC 5455 198
> SR9DDF-12 5455 200
> SV2HRT-1 5455 115
> SV5BYR-7 5455 217
> UA4CC 5455 115
> VA3MW-7 5455 249
> VE1CFB 5455 38
> VE2PKT-9 5455 166
> VE3MIS-2 5455 210
> VE3XPG-3 5455
> VE6DXC 5455 100
> VK3HRA-2 5455 185
> W1DX-2 5455 82
> W1NR 5455 250
> W1NR-9 5455 250
> W6RFU 5455 216
> W6RGG-2 5455 89
> W9AEK 5455 158
> WT3Q 5455 136
> WW1R-9 5455 82
> YO2LOJ-2 5455
>
> 73 de Kin EA3CV
>
> _______________________________________________
> 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/20230219/caafec8a/attachment-0001.htm>
More information about the Dxspider-support
mailing list