- Dxspider-support - mailman.hamserve.uk

cannot open /spider/data/dupefile
by Gabriel - EA6VQ 03 Feb '26

03 Feb '26

Since yesterday DXspider is not starting. I shows the message "cannot open /spider/data/dupefile" and the process ends. I confirm that there is no file "/spider/data/dupefile", so according to the documentation the file should be created in the DXDupe.pm module. BTW, this instance of DXspider is running on Windows. It was working fine until yesterday. It is not an issue with folder permissions. I have already confirmed that. I don't know what to do next.... I would appreciate your help. Thanks in advance. -- /*73. Gabriel - EA6VQ*/ /* */

2 1

Maintenance recommendations (II)
by Kin 03 Feb '26

03 Feb '26

Hi, Below is some data that may help identify issues between nodes. A value of "1" indicates that the node has reported an active connection with its peer. A value of "0" means that there was either no response from the node or that it reported a disconnection. "U" indicates the total number of connections. "D" indicates the total number of disconnections. Nodes that do not appear here are not necessarily operating correctly; these are simply the accumulated values at the time the data was read. All of this data comes from the analysis of PC92 frames transmitted on the network. Interconnections between nodes that do not use PC92 will never appear here — for the network, they effectively do not exist. There are nodes, such as ARC, that never emit PC92 frames. Some CCC nodes emit them, but most do not, and they do not behave in the same way as DXSpider nodes. Additionally, some DXSpider nodes do not use PC92 either because it is disabled or because they are running obsolete versions. In any case, this data indicates a problem between nodes, either because the link is not being established correctly or because the nodes are not fully compatible. Please note that the callsigns of the nodes shown in the list are those reported by the peer node. It is quite common to see nodes appearing with a different callsign (with or without SSID, or with a different SSID). This is usually a clear indication of configuration problems on the link. Some nodes shown in the list have not been properly defined, either because they are not defined as nodes at all or because they are defined with an incorrect node type. This will prevent the link from being established. The most common and correct configuration should include definitions such as: * set/spider * set/ccluster * set/node If the callsign of a peer node is incorrect, it must be corrected using the commands above and/or by verifying the connection configuration file. A typical and expected connection file should look like this: timeout 15 connect telnet <hostname or IP> <port> 'login: ' '<our node callsign>' 'assword:' '<password, if required>' In some cases, the login field does not contain the node’s actual callsign, but a different one. This is a common source of problems and should be corrected. If a sysop believes that they do not have an active link with one of the nodes shown in the list, the usual and recommended action is to inform the peer sysop and ask them to remove any pending or repeated connection attempts from their crontab. I hope this information helps clarify and resolve the issue. Please see the attached file. Kin EA3CV

4 5

Maintenance recommendations
by Kin 02 Feb '26

02 Feb '26

Hi, * It is advisable to have PC92 enabled, in particular: set/var $DXProt::pc92_ad_enabled = 1 set/var $DXProt::pc92c_ipaddr_enable = 1 Although it may not always be feasible, it would be beneficial to encourage our CCC neighbor nodes to enable PC92, even in a limited form. This can significantly help when network-related issues arise. * It is also recommended to periodically review the neighboring nodes we currently have configured. Some nodes may change, disappear, or stop responding, yet we may continue sending requests to them indefinitely. * Keeping the node software up to date is essential, as many network-related issues are resolved in newer versions. * Please note that the RBN servers SK0MMR and SK1MMR are not typical DXSpider nodes. They must be explicitly defined as RBN nodes, for example: set/rbn SK0MMR set/rbn SK1MMR Finally, some examples of failed connections between nodes include: Conn: number of connections Disc: number of disconnections Node-1 Node-2 Conn Disc ALL ---------------------------------------- DB0ERF-5 ON0DXC 0 105 105 DH1TW-2 AE5E 0 43 43 DH1TW-2 N6WS-6 0 900 900 ED1ZAC-5 CT1EBQ-9 0 88 88 EI7SDX ON4KST 0 38 38 F6KVP-3 MB6WV 0 90 90 G1FEF-2 G4BFG-9 0 179 179 G3FCA-4 G3FCA-8 179 0 179 IZ7AUH-6 IZ7AUH-6 0 900 900 HB9VQQ-2 N6WS-6 0 900 900 HI8S-8 M0IPU-4 0 90 90 I8ZSE-1 F4BWT-3 0 90 90 IQ1LA-6 PA1RBZ 0 90 90 IW1QLH-6 IW1QLH-2 252 0 252 K1AX-11 VE7CC-1 0 28 28 KB3CMT-2 GB7VAX 0 89 89 KB3CMT-2 PA4JJ-2 0 88 88 KB3CMT-2 PY2ZEN-6 0 90 90 KF8I-3 KB8PMY-3 0 90 90 M0KGX-3 N2WQ-1 0 33 33 ON0DXC SK1MMR 0 37 37 PA0ESH-3 N2WQ-1 0 31 31 PY3NZ-8 KC9AOP-1 0 180 180 PY4OG-4 GB7DJK 0 90 90 R2DGO-1 OP0P 0 39 39 SM7IUN-1 HI8S-8 0 90 90 SM7IUN-2 DL0PF 0 133 133 UA4CC AE5E 0 30 30 UF3K-1 R1BLH-1 0 900 900 VE3ZIN-2 HI8S-8 0 90 90 VE6CIC-1 SV5FRI 45 0 45 W6RFU JG1VGX-9 0 90 90 W6RFU VE6DXC 0 90 90 WB3FFV-2 AE5E 0 40 40 YV5KXE IK4PKL 0 90 90 73 de Kin EA3CV

4 3

CTY-3607 Country Files - 31 January 2026
by Jim Reisert AD1C 31 Jan '26

31 Jan '26

The Country (CTY) Files were updated on 31 January 2026: https://www.country-files.com/cty-3607-31-january-2026/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-31-january-2026/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 31 January 2026 (CTY-3607) VER20260131, Version entity is East Malaysia, 9M6 Added/changed Entities/Prefixes/Callsigns: * WE9G/KC4 is Antarctica, CE9 in ITU zone 73 * HC8M/5 is Ecuador, HC * LU3EMN/W is Argentina, LU in ITU zone 16 Removed Entities/Prefixes/Callsigns: Although I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us

1 0

CTY-3606 Country Files - 29 January 2026
by Jim Reisert AD1C 29 Jan '26

29 Jan '26

The Country (CTY) Files were updated on 29 January 2026: https://www.country-files.com/cty-3606-29-january-2026/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-29-january-2026/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 29 January 2026 (CTY-3606) VER20260129, Version entity is Azores, CU Added/changed Entities/Prefixes/Callsigns: * VK0TBC is Antarctica, CE9 in CQ zone 29, ITU zone 70 * TX5EU is Austral Islands, FO/a * AB3AH is United States, K in CQ zone 4, ITU zone 8 * AG7XY is Hawaii, KH6 * KN6PHX is Alaska, KL * LU7AA/D and LU7AA/G are both Argentina, LU * LU3EMN/XA and LU7AA/Y are both Argentina, LU in ITU zone 16 * R103AE and R103ME are both European Russia, UA * RK4PA/9 is Asiatic Russia, UA9 in ITU zone 20 * RU4B/4 is Asiatic Russia, UA9 in CQ zone 16 Removed Entities/Prefixes/Callsigns: * IT9MRM/N in Sicily, *IT9 * BG2LTC/0 in China, BY * DL0NOT/EMCOM in Fed. Rep. of Germany, DL * AM65OJE in Spain, EA * TX9A in Austral Islands, FO/a * TO9W in St. Martin, FS * HC8M/5 in Ecuador, HC * IT9KWL/0 in Italy, I * N4UPX in United States, K * K7DWJ in Hawaii, KH6 * LU8APF/D in Argentina, LU * R1941MB, R1941OM, R9FCS/4 and UG4I/P in European Russia, UA * RV7B/9 in Asiatic Russia, UA9 Although I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us

1 0

New clear/dbspots command for MySQL/MariaDB spot cleanup - MOJO
by Kin 25 Jan '26

25 Jan '26

Hi, For those using MySQL/MariaDB as the native backend to store DXSpider spots and who want to remove old spot records, I have created a new command called: clear/dbspots It is very easy to use: just pass a date in YYYYMMDD format, and all spots older than the start of that date (00:00 UTC) will be deleted, while newer records are preserved. ### Installation Download the command from: https://raw.githubusercontent.com/EA3CV/dxspider_info/main/clear/dbspots.pl and copy it into: /spider/local_cmd/clear/ You can do this with: mkdir -p /spider/local_cmd/clear && \ wget -qO /spider/local_cmd/clear/dbspots.pl \ "https://raw.githubusercontent.com/EA3CV/dxspider_info/main/clear/dbspots.pl" && \ chmod 755 /spider/local_cmd/clear/dbspots.pl Then, from the DXSpider console, reload local commands: load/cmd ### Usage examples Example where no records match the purge criteria: clear/dbspots 20260101 No rows to delete. Cutoff: 2026-01-01 00:00:00Z (epoch 1767225600) Example where old spots are removed: clear/dbspots 20260126 Deleting 570 spot rows with time < 2026-01-24 00:00:00Z (epoch 1769212800) ... Done. Deleted: 570. Note: indexes are not harmed. After large purges you MAY run: OPTIMIZE TABLE spot; (off-peak) I hope this is useful for those running DXSpider with an SQL backend. 73 de Kin EA3CV

1 0

Change of Callsign
by Ken Sharman 23 Jan '26

23 Jan '26

Hi All I have changed my personal callsign from G7VJA too G5NOW Can i just edit my personal details in dxspider or is the another way the DXspider callsign is still GB7HTL, no change there. and how do i rename my G7VJA-2 dx spider to the new callsign, (it my test system) i remember a message a while ago about renaming, but forgot who it was from. regards Ken G5NOW ex G7VJA

1 0

CTY-3605 Country Files - 23 January 2026
by Jim Reisert AD1C 23 Jan '26

23 Jan '26

The Country (CTY) Files were updated on 23 January 2026: https://www.country-files.com/cty-3605-23-january-2026/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-23-january-2026/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 23 January 2026 (CTY-3605) VER20260123, Version entity is Hong Kong, VR Added/changed Entities/Prefixes/Callsigns: * GB5CC is Guernsey, GU * ND9M is in ITU zone 8, not ITU zone 7 * ND9M is in CQ zone 5, not CQ zone 4 * N6US is United States, K in CQ zone 4, ITU zone 7 * W4UWC is United States, K in CQ zone 4, ITU zone 8 * WX8C is United States, K in CQ zone 5, ITU zone 8 * N4ZSU is Hawaii, KH6 * KI5SXN is Alaska, KL * KF9EM is Puerto Rico, KP4 * LU8DCH/D is Argentina, LU * ZV9MS is Brazil, PY * ZV8AC, ZV8AM, ZV8RO and ZV8RR are all Brazil, PY in ITU zone 12 * ZV2DF and ZV2TO are both Brazil, PY in ITU zone 13 * LU1ZA is South Orkney Islands, VP8/o Removed Entities/Prefixes/Callsigns: * IT9IFM/0 in Italy, I * N4HUA in Alaska, KL * KH2RU in Puerto Rico, KP4 * LU4DOV/D in Argentina, LU * RL1I/P in European Russia, UA * R2ET/9 and RY0AAN/P in Asiatic Russia, UA9 Although I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us

1 0

set/password not working properly
by Andrea Timpanaro 22 Jan '26

22 Jan '26

Hi, all users that have a password configured by the sysop are not able to change it by their own with the command set/password They get error "not allowed". Any other experiencing this issue? Thanks andrea iz2lsc -->

2 6

Name change
by jarmo 21 Jan '26

21 Jan '26

Cluster OH1RCF changed into OH1AF, no connection changes, only name... Jarmo, oh1mrr Sysop OH1AF, former OH1RCF

1 0