[Dxspider-support] New version of Mojo (dx command fixed)
Jan
cluster at pa4jj.nl
Thu Jan 30 19:06:26 GMT 2025
I see the same here on my nodes
73
Jan PA4JJ
Op 30-1-2025 om 19:24 schreef ken Sharman via Dxspider-support:
> Hi Keith
> I get this when i type sh/dx g6nhu
> 7074.0 G6NHU 30-Jan-2025 1659z test
> Ken G7VJA - GB7HTL
>> On 01/30/2025 5:07 PM GMT Keith, G6NHU via Dxspider-support
>> <dxspider-support at tobit.co.uk> wrote:
>> To test this further, I’ve just logged onto one of my partner nodes
>> (MX0NCA-2) as G0PKT. This node is running build 559.
>>
>> The spots I’ve sent today from my node of G0PKT don’t show on his node.
>>
>> Now I've submitted a spot on his node
>>
>> 'dx 7074 g6nhu test'
>>
>> Then tried to look for it
>>
>> ’sh/dx g6nhu'
>>
>> sh/dx: 'g6nhu' not found
>>
>> When I do the same check on my node, the spot isn’t there.
>>
>> When I look on PI4CC who is running build 547, the spot is there.
>>
>> Checking another node running build 559 (R5ACQ-1), the spot is
>> missing as well.
>>
>> These aren’t self spots, this is just normal spotting. I’m convinced
>> something isn’t right.
>>
>> 73 Keith G6NHU
>>
>>
>> On 30 Jan 2025 at 14:58 +0000, Keith, G6NHU via Dxspider-support
>> <dxspider-support at tobit.co.uk>, wrote:
>>> I already have that variable set, I’ve had it configured that way
>>> since March 2023!
>>>
>>> If you notice, some of those spots aren’t self spots. Some were
>>> (G0PKT spotting itself) but others that don’t appear locally were
>>> G6NHU spotting G0PKT.
>>>
>>> There are no instances of ‘swore’ in the debug log and no instances
>>> of ’trying to self spot’ either.
>>>
>>> 73 Keith G6NHU
>>>
>>> On 30 Jan 2025 at 14:25 +0000, Dirk Koopman via Dxspider-support
>>> <dxspider-support at tobit.co.uk>, wrote:
>>>> Which means that you are probably getting a message like this in
>>>> the debug:
>>>>
>>>> (DXCommand) G1TLH-2 swore: 7050 g1tlh (with words:G1TLH)
>>>> (*) spotter G1TLH/G1TLH
>>>> (DXCommand) G1TLH/G1TLH trying to self spot below 1240000KHz (7050
>>>> g1tlh) from 82.68.205.1, not passed on to cluster
>>>>
>>>> I treat self spotting as "swearing" so it dumps you off after three
>>>> (configurable) attempts.
>>>>
>>>> My memory is not what it was, but I am still detecting a silent
>>>> majority of sysops not liking self-spotting.
>>>>
>>>> As it's getting near to contest time, I am holding off any more
>>>> updates that alter the main code so you will have to set
>>>> $Spot::minselfspotqrg = *0* if that's what you want to allow on
>>>> your node. This only affects _locally_ connected users, not any
>>>> incoming spots.
>>>>
>>>> Dirk G1TLH
>>>>
>>>> On 30/01/2025 13:33, Keith, G6NHU via Dxspider-support wrote:
>>>>> Considering this is where this all started from with the
>>>>> discussion about self spotting, I noticed this.
>>>>>
>>>>> sh/var $Spot::minselfspotqrg
>>>>> $Spot::minselfspotqrg = *1240000*
>>>>>
>>>>> Shouldn’t the default be 0 now as per this:
>>>>> https://mailman.tobit.co.uk/pipermail/dxspider-support/2023-March/018036.html ?
>>>>>
>>>>>
>>>>> 73 Keith G6NHU.
>>>>> On 30 Jan 2025 at 13:17 +0000, Keith, G6NHU via Dxspider-support
>>>>> <dxspider-support at tobit.co.uk>, wrote:
>>>>>> I’m not sure it’s quite right.
>>>>>>
>>>>>> I sent some test self spots from within a normal telnet session.
>>>>>>
>>>>>> So this is G0PKT self spotting and also G6NHU sending spots for
>>>>>> G0PKT.
>>>>>>
>>>>>> When I do a sh/dx g0pkt, from the telnet session, this is what I
>>>>>> see. The spot isn’t showing.
>>>>>>
>>>>>> sh/dx g0pkt
>>>>>> G0PKT de G6NHU-2 30-Jan-2025 1308Z dxspider >
>>>>>> 7074.0 G0PKT 21-Jan-2025 1440Z test
>>>>>> <G0PKT>
>>>>>>
>>>>>>
>>>>>> I see the same if I do the same command from a console session.
>>>>>>
>>>>>> However, if I do an rcmd to one of my partners, the test spots I
>>>>>> made from both G0PKT and from G6NHU show.
>>>>>>
>>>>>> rcmd pi4cc sh/dx g0pkt
>>>>>> RCMD 'sh/dx g0pkt' sent to PI4CC
>>>>>> G6NHU de G6NHU-2 30-Jan-2025 1308Z dxspider >
>>>>>> PI4CC: 7074.0 G0PKT 30-Jan-2025 1245Z test
>>>>>> <G0PKT>
>>>>>> PI4CC: 7074.0 G0PKT 30-Jan-2025 1238Z test
>>>>>> <G0PKT>
>>>>>> PI4CC: 7074.0 G0PKT 30-Jan-2025 1237Z <G6NHU>
>>>>>> PI4CC: 7074.0 G0PKT 30-Jan-2025 1214Z <G6NHU>
>>>>>> PI4CC: 7074.0 G0PKT 21-Jan-2025 1440Z test
>>>>>> <G0PKT>
>>>>>>
>>>>>>
>>>>>> Here’s the same command locally in the console.
>>>>>>
>>>>>> sh/dx g0pkt
>>>>>> G6NHU de G6NHU-2 30-Jan-2025 1311Z dxspider >
>>>>>> 7074.0 G0PKT 21-Jan-2025 1440Z test
>>>>>> <G0PKT>
>>>>>>
>>>>>>
>>>>>> It’s as though the spots have been sent but not shown or stored
>>>>>> locally.
>>>>>>
>>>>>> Can anyone test the same please, post some spots and then see if
>>>>>> they are shown on the local node as well as remote ones.
>>>>>>
>>>>>> 73 Keith G6NHU (signing posts with my callsign now as there seem
>>>>>> to be about three Keiths on here!).
>>>>>> On 30 Jan 2025 at 11:57 +0000, Dirk Koopman via Dxspider-support
>>>>>> <dxspider-support at tobit.co.uk>, wrote:
>>>>>>> Please update in the normal way. This was an error inside the dx
>>>>>>> command
>>>>>>> caused by me changing a naming convention. As always: more
>>>>>>> thought (and
>>>>>>> better testing) required...
>>>>>>>
>>>>>>> You don't need to restart. The fix will be picked up
>>>>>>> automatically when
>>>>>>> you next enter a dx command.
>>>>>>>
>>>>>>> Dirk G1TLH
>>>>>>>
>>>>>>> On 30/01/2025 11:30, Mike G3YPP via Dxspider-support wrote:
>>>>>>>> How do we update the (mn) node command that Kin mentions. My
>>>>>>>> node will not send spots
>>>>>>>>
>>>>>>>> Mike G3YPP
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>>> On 30 Jan 2025, at 10:03, dxspider-support-request at tobit.co.uk
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Re: [Dxspider-support] New version of Mojo
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 77.174.195.163 port 7300
pa4jj-3 77.174.195.163 port 7388
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250130/c316a157/attachment-0001.htm>
More information about the Dxspider-support
mailing list