[Dxspider-support] dx command actions + announce problems + links + who commands

[Stephen Carroll]

su - sysop
cd /spider
git reset --hard
git pull
Samsung Galaxy S22+ on Verizon

On Fri, Jan 31, 2025, 11:05 AM Luigi Carlotto IK5ZUK via Dxspider-support <
dxspider-support at tobit.co.uk> wrote:

> Hi Dirk,
>
> I'm trying to update one of the node that I manage, but when using GIT I
> have the following:
>
> sysop at HAM-Srv02:~$ cd /spider/
> sysop at HAM-Srv02:/spider$ git pull
> fatal: unable to connect to scm.dxcluster.org:
> scm.dxcluster.org[0: 2001:bc8:3b8c:200::2]: errno=Connection timed out
> scm.dxcluster.org[1: 163.172.11.79]: errno=Connection timed out
>
> sysop at HAM-Srv02:/spider$ git pull
> fatal: unable to connect to scm.dxcluster.org:
> scm.dxcluster.org[0: 2001:bc8:3b8c:200::2]: errno=Connection timed out
> scm.dxcluster.org[1: 163.172.11.79]: errno=Connection timed out
>
> sysop at HAM-Srv02:/spider$
>
> Please, could you tell me what I can do?
>
> 73 Luigi IK5ZUK
>
>
>
>
> Il 31/01/2025 15:16, Dirk Koopman via Dxspider-support ha scritto:
>
> Normal service is a bit tardy as I had a late night rescuing my other half
> from a broken down car and did not get to bed until 3am.
>
> I have looked a number of versions from 536 to 561. And I remain confused.
>
> Firstly 536 stores the spot and also sends it back to a telnet console:
>
> dx 3505 g1brn test 4
> DX de G1TLH:      3505.0  G1BRN        test 4                         1248Z
>
> On 561 the same is true
>
> dx 7013 g1brn test 5
> DX de G1TLH:      7013.0  G1BRN        test 5                         1252Z
> G1TLH de GB7TLH 31-Jan-2025 1252Z dxspider >
>
> These spots have also been sent out to other nodes and should be
> searchable with a sh/dx 2 g1brn.
>
> The line that sent the spot back to the user in user format had been
> removed and has now been put back again, but will be moved slightly in the
> next release (soon today). But it clearly was a bodge that was not
> necessary in (waves hand randomly) earlier versions. This will be fixed
> after this weekend.
>
> As for announcements - as well a few other things - this was a consequence
> of me not thinking through (mainly because it seemed too difficult to test)
> the defences I added  to prevent nodes that had not fully initialised (e.g.
> the ungodly attempting fraud  but also CC Cluster instances [nominally
> godly]) passing traffic. This is now fixed.
>
> I cannot reproduce errors viz: CCCluster connection on the 'links' command:
>
> link
>                                                   Ave  Obs  Ping
> Next      Filters
>   Callsign Type Started                 Uptime    RTT Count Int.  Ping
> Iso? In  Out PC92? Address
>     GB7DJK DXSP 31-Jan-2025 1347Z        6m 1s   0.03   2    300
> 92               Y    163.172.11.79
>    VE7CC-1 CCCL 31-Jan-2025 1353Z           3s 999.00   2    300
> 296               Y    207.216.236.158
>
> I have added an extra field to the 'who' command to indicate the 'state'
> of that connection.
>
> who
>   Callsign Type      State    Started           Name     Ave RTT Link
>    G1TLH-2 USER LOCL prompt   31-Jan-2025 1346Z Dirk             127.0.0.1
>     GB7DJK NODE DXSP normal   31-Jan-2025 1347Z Dirk        0.03
> 163.172.11.79
>     GB7TLH NODE DXSP indiffer 31-Jan-2025 1346Z Dirk
>    VE7CC-1 NODE CCCL normal   31-Jan-2025 1353Z Node        0.16
> 207.216.236.158
>
> This version is now available from git.
>
> You will need to do a restart.
>
> 73 Dirk G1TLH
>
>
> _______________________________________________
> Dxspider-support mailing listDxspider-support at tobit.co.ukhttps://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/20250131/8bbe6b09/attachment.htm>