[Dxspider-support] New mojo version

[Keith Maton]

Hi Dirk,

I’ve just installed this on G6NHU-2 and I’ve gone from 270 users down to about 50.  Most of my users are HamClock users and I’m just seeing repeated connect/disconnect entries in the log from them as per below.

Has anything changed regarding the logon process in 547 that could have caused this?  I’ve also dropped the author of HamClock a note as this is a little concerning. 

Thanks,

73 Keith G6NHU


1726753457^(connect) connect 26: G0MBA-13
1726753457^(state) G0MBA-13 channel func  state 0 -> prompt
1726753457^(DXCommand) G0MBA-13 connected from 78.32.158.54 cols 80
1726753457^(progress) CMD: 'show/cluster ' by G0MBA-13 ip: 78.32.158.54 0mS
1726753457^(DXCommand) G0MBA-13 disconnected
1726753472^(connect) connect 225: G0MBA-13
1726753472^(state) G0MBA-13 channel func  state 0 -> prompt
1726753472^(DXCommand) G0MBA-13 connected from 78.32.158.54 cols 80
1726753472^(progress) CMD: 'show/cluster ' by G0MBA-13 ip: 78.32.158.54 0mS
1726753472^(DXCommand) G0MBA-13 disconnected

1726754044^(connect) connect 779: N2JOB
1726754044^(state) N2JOB channel func  state 0 -> prompt
1726754044^(DXCommand) N2JOB connected from 69.117.35.69 cols 80
1726754044^(progress) CMD: 'show/cluster ' by N2JOB ip: 69.117.35.69 0mS
1726754044^(DXCommand) N2JOB disconnected
1726754059^(connect) connect 787: N2JOB
1726754059^(state) N2JOB channel func  state 0 -> prompt
1726754059^(DXCommand) N2JOB connected from 69.117.35.69 cols 80
1726754059^(progress) CMD: 'show/cluster ' by N2JOB ip: 69.117.35.69 1mS
1726754059^(DXCommand) N2JOB disconnected
1726754074^(connect) connect 794: N2JOB
1726754074^(state) N2JOB channel func  state 0 -> prompt
1726754074^(DXCommand) N2JOB connected from 69.117.35.69 cols 80
1726754074^(progress) CMD: 'show/cluster ' by N2JOB ip: 69.117.35.69 0mS
1726754074^(DXCommand) N2JOB disconnected



> On 19 Sep 2024, at 14:24, Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> There is a new mojo version which has been under test by a few brave sysops and they have determined that it is stable. Please look at the Changes file for the list of issues dealt with.
> 
> One of the issues that has become apparent is the random lock status (historically) granted to new nodes that appear on the network. For some reason they defaulting to "unlocked". I don't understand why this has suddenly become a problem AGAIN, but it does seem to affect longer running nodes more than newer ones. 
> 
> This release is an attempt to fix this. It will lock all nodes that are not specifically unlocked via explicit unset/lock or set/spider type commands. Unfortunately, previous attempts to deal with this may have got this all confused and it *MAY* (and I stress this) mean that a (very) few of your older node partners *MIGHT* get locked out. If this happens then simply unset/lock or set/spider any of these nodes manually.
> 
> There is new spot deduping code which seems to reduce the number of dupes, but since I have not been able to reproduce this further than making sure that nodes that issue multiple dupe spots with the same sequence number don't cause dupes.
> 
> 73 Dirk G1TLH
> _______________________________________________
> 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/20240919/670882fc/attachment-0002.htm>