[Dxspider-support] Nodes disconnecting after upgrade

Kin ea3cv at cronux.net
Mon Feb 6 15:49:00 GMT 2023


The upgrade script is run as root but the installation of dxspider is done
as sysop (sudo su - sysop).

The script is intended for those who have no experience and are afraid of
losing everything, so it incorporates a backup, but there are a lot of
settings ... unorthodox configurations that can lead to problems.

It is normal that you lost the node type because it was probably not defined
in any file (ie startup). 

 

But it's easy, if you follow Dirk's instructions in his UPGRADE file:

git reset --hard

git pull --all

 

Kin

 

 

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
Kelly Leavitt via Dxspider-support
Enviado el: lunes, 6 de febrero de 2023 16:17
Para: dxspider-support at tobit.co.uk
CC: Kelly Leavitt <kelly at catcorner.org>
Asunto: Re: [Dxspider-support] Nodes disconnecting after upgrade

 

  IT9FTP-6 DXSP  6-Feb-2023 1459Z      11m 11s   0.12   2    300    90
Y    151.52.199.150 

      N2KI DXSP  6-Feb-2023 1505Z       6m 10s   0.09   2    300    90
162.191.245.209

   N2WLS-5 DXSP  6-Feb-2023 1505Z       6m 10s   0.04   2    300    90
69.207.20.244

      W1NR DXSP  6-Feb-2023 1503Z       8m 10s   0.01   2    300   270
173.255.232.93

 

I know they're not. I do development for a living. However, you can see
above, the nodes are not staying connected now.

 

Ran the "upgrade" script update_dxspider.sh as sysop user. I got a lot of
"permission denied" message for directories and files already owned by
sysop.

 

However, the nodes are all disconnecting and reconnecting regularly. All
node settings were lost during the upgrade too. I had to re-run set/spider
for each one.

 

Might just try a clean install.

 

 

  _____  

From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> on behalf of
Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk>
Sent: Monday, February 6, 2023 10:01 AM
To: dxspider-support at tobit.co.uk <dxspider-support at tobit.co.uk>
Cc: Dirk Koopman <djk at tobit.co.uk>
Subject: Re: [Dxspider-support] Nodes disconnecting after upgrade 

 

This email trail (and some similar ones like it) fills me with a certain 
amount of disquiet. This is because I cannot reproduce the errors on my 
test node, nor on the four (large) nodes that I have oversight of. It 
leaves me feeling somewhat powerless to make suggestions and/or to fix 
it. Programs are not supposed to have minds of their own...

Dirk G1TLH

On 06/02/2023 13:49, Mike McCarthy, W1NR via Dxspider-support wrote:
> Do a 'set/spider w1nr' and see if it works.
>
> Mike, W1NR
>
> On 2/6/2023 6:25 AM, Kelly Leavitt via Dxspider-support wrote:
>> Just checked through the logs. No mention of permission denied. Any 
>> other thoughts? It seems like the cron is ignoring the 'unless 
>> connected', forcing a disconnect and then reconnecting.
>> ------------------------------------------------------------------------
>> *From:* Dxspider-support <dxspider-support-bounces at tobit.co.uk> on 
>> behalf of gu6efb--- via Dxspider-support <dxspider-support at tobit.co.uk>
>> *Sent:* Sunday, February 5, 2023 3:16 PM
>> *To:* 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
>> *Cc:* gu6efb at cwgsy.net <gu6efb at cwgsy.net>
>> *Subject:* Re: [Dxspider-support] Nodes disconnecting after upgrade
>>
>> Hi Kelly
>>
>> Have a look in your debug log and see if you have any entries with 
>> permission denied, as after my upgrade I had a very similar issue and 
>> this was
>>
>> Due to some files not having the right permissions after the upgrade.
>>
>> It maybe something completely in your case but it's someware to start.
>>
>> 73 Keith GU6EFB
>>
>> *From:*Dxspider-support <dxspider-support-bounces at tobit.co.uk> *On 
>> Behalf Of *Kelly Leavitt via Dxspider-support
>> *Sent:* 05 February 2023 19:41
>> *To:* Dxspider-support at tobit.co.uk
>> *Cc:* Kelly Leavitt <kelly at catcorner.org>
>> *Subject:* [Dxspider-support] Nodes disconnecting after upgrade
>>
>> I have a cron job set up that is like this:
>>
>> 3,8,13,18,23,28,33,38,43,48,53,57 * * * * start_connect('w1nr') 
>> unless connected('w1nr')
>>
>> At every time in the cron job, w1nr is disconnected and re-connected. 
>> I don't recall it working like this.
>>
>> As it stands now, I never have more than 2 nodes connected at any 
>> time. What is best practice?
>>
>> Thanks and 73 de Kelly, KE2L
>>
>>
>> _______________________________________________
>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230206/5dd07ab1/attachment.htm>


More information about the Dxspider-support mailing list