[Dxspider-support] Help regarding node upgrade...

[Dirk Koopman]

On 23/02/2023 16:49, Martin Davies G0HDB via Dxspider-support wrote:
> Hello all, I'm part-way through upgrading the GB7DXC-5 node, which currently runs
> DXSpider 'Master' v1.55 build 249, to 'Mojo' v1.57 build 499.
>
> I've installed the Lite version of 32-bit Rasbian 'Bullseye' (Debian 11) on a Raspberry Pi 3B
> and have migrated the root filesystem to a USB-connected hard disk, and I've run the
> SV5FRI script (thanks Yiannis!) to install the latest Mojo version of DXSpider onto the Pi.
> The Pi is headless so everything is done using SSH access.  The only problem that I seemed
> to encounter during the DXSpider install was that for some reason the script didn't add the
> sysop user to the 'sudoers' list so I had to do this manually later - I can now use sudo when
> logged in as sysop.
>
> As far as I can tell everything seems to be working as expected - the node, which I've
> temporarily named GB7DXC-7 - appears to be running, I can log into it from a sysop console,
> and when I (temporarily) connect the new node to my existing GB7DXC-5 node I can see the
> DX spots coming through.  So far so good!
>
> However, there's a few aspects for which I need some help...
>
> 1.  The node appears to start successfully whenever the Pi is rebooted - the SV5FRI
>      script seems to have created a file called dxspider.service in /usr/lib/systemd/system
>      but I'm unclear about whether anything else is needed to enable cluster.pl to be
>      restarted automatically after a crash or whatever.  I'll be grateful for any clarification
>      on this aspect although I see that the dxspider.service file does include the statement
>      of 'Restart=always'.  Is anything else needed?

No.

>
> 2.  I'll want to migrate as many user-related and other relevant files as possible from the
>      existing GB7DXC-5 node running 'Master' v1.55 build 249 over to the new node
>      running 'Mojo' v1.57 build 499.  Which are the essential files that I'll need to copy
>      across from the old node to the new node?

Hmm... I probably need to have a look at that script. My standard 
recommendation for UPGRADING to mojo from master is to start from an 
existing installation and that means having started with your step 3 
first. But, using the power of git, all is not lost.

Firstly do a 'systemctl stop dxspider' or 'service dxspider stop' the 
first will work on buster and the second should work (otherwise you may 
need to install a package 'apt install init-system-helpers').

cd /spider/local; cp DXVars.pm /tmp/DXVars.pm.dxc7
rm -rf /spider/local_data/*

Do your step 3. After which you will have a copy of the complete tree 
from your old machine on your new one.

cd /spider/local_cmd; mv crontab crontab.save

cd /spider
git reset --hard
git branch

check to see that there is an '*' in front of the mojo branch name.//If 
not then do a 'git checkout mojo'.

At this point, you have a choice: you can just expect it to 'work' 
(minus crontab stuff) or you can test it again with DXC-7 if you want to 
do that (I wouldn't bother) then do these steps:

cd local; mv DXVars.pm DXVars.pm.dxc
cp /tmp/DXVars.pm.save DXVars.pm
/spider/perl/update_sysop.pl

This command, as a side effect, will do the users file conversion.

You will now have a working DXC-7 node to test. Run it manually first as 
below. When you are happy that it is working as desired you will need to 
shutdown the node (either 'shut' in a console.pl or just <ctrl-c> it in 
the shell). To now run as DXC(not-7) then:

cd /spider/local; cp DXVars.pm.dxc7 DXVars.pm

And, assuming you have removed all the extraneous stuff as recommended 
in UPGRADE.mojo, just change $mycall to 'GB7DXC' and $myalias to your taste.

/spider/perl/update_sysop.pl

Run it manually first:

cd /spider/perl/; ./cluster.pl

Check that it all works. This is the point at which you stop BOTH nodes, 
do any IP address changes you require, and (on the new node) restart the 
whole machine. The cluster.pl should be running.

If it is, then:

Start watchdbg in another shell and:

cd /spider/local_cmd; mv crontab.save crontab

You should see all your node connects all spring into life over the next 
few minutes.

Do not switch your old machine back on :-)

> 3.  I assume I'll need to use rsync to copy the relevant files across from the old node to
>      the new node; I'm largely unfamiliar with using rsync for this purpose so any guidance
>      on the syntax to use will be much appreciated!  I find the documentation for rsync to
>      be rather confusing for my limited Linux skills and experience!

on your new machine: 'rsync -avz sysop@<oldmachinename>:/spider/* 
/spider --exclude .git'

NOTE: you may need to install the rsync package on one or both machines 
if you have not used them before.

>
> Many thanks in advance for any help and suggestions that might be offered.
>
> 73
> ---
> Martin, G0HDB
>
>
> _______________________________________________
> 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/20230223/7be2e1eb/attachment.htm>