[Dxspider-support] Migrate DXspider to other VM (PS)

[Dirk Koopman]

PS I should have added:

Although, now in the distant past, the underlying Berkeley DB was rather 
flaky - it seems that it now takes version upgrades well and I have not 
had a problem here for quite a while. Having said that, if the users.v3 
file is really old (or maybe generated on an other architecture), then 
the current BDB would refuse to read it. I think this was version 2 of 
BDB and below, we are now on version 9. so I don't suppose there are 
many of these installations left. However, of late, I have been getting 
a number of reports about issues with the Storable module (a standard 
part of perl) and had some trouble myself with it. That seems to be the 
more likely failure mode.

But, happily 99.8% of upgrades of this sort go smoothly. But I try to 
provide "easy to use" alternatives for 0.2%.

One of the goals I have with the 'mojo' branch was to remove the 
Storable module and replace it with something else. This has now been 
done and we are now using JSON as the serialiser for the users and 
(dx)qsl files. And it works 2.5 times faster too!

73 Dirk G1TLH

On 13/07/2020 15:44, Dirk Koopman via Dxspider-support wrote:
> You don't need to worry if it working. But had it not worked because 
> of a users file error, then you could recover by:
>
> stopping the node.
> cd /spider/data
> perl user_asc
> start the node.
>
> Dirk
>
> On 13/07/2020 15:10, Erwin Fiten wrote:
>> @Dirk Koopman <mailto:djk at tobit.co.uk>  What do you mean with : ' , 
>> rebuild the users file from the user_asc you generated (perl user_asc) '
>>
>> alll the rest is already done now. looks good
>>
>>
>> Op ma 13 jul. 2020 om 12:16 schreef Dirk Koopman via Dxspider-support 
>> <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>:
>>
>>     Erwin
>>
>>     You do precisely that. But I suggest that you do an 'export_user'
>>     in a console, then stop the node BEFORE you copy. Do the update
>>     on the new machine. You may have issues with the user and qsl
>>     file, if that happens, rebuild the users file from the user_asc
>>     you generated (perl user_asc) and the qsl file with
>>     /spider/perl/create_qsl.pl <http://create_qsl.pl> and, when it's
>>     finished, run 'load/qsl' in a console.
>>
>>     73 Dirk G1TLH
>>
>>     On 13/07/2020 09:46, Erwin Fiten via Dxspider-support wrote:
>>>     I'm now (still) running DXspider V1.55 build 0.198 under Debian
>>>     9. It's running on a shared VM, and I want to migrate & update
>>>     it to a new separate VM. What's the best way to do this ?
>>>     because I want to keep my settings, connection profiles, etc...
>>>
>>>     Copy the complete SPIDER folder, and then do an update via GIT?
>>>     how ?
>>>
>>>
>>>     Erwin de ON8AR, sysop of ON0NOL cluster
>>>
>>>
>>>     _______________________________________________
>>>     Dxspider-support mailing list
>>>     Dxspider-support at tobit.co.uk  <mailto: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 <mailto: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/20200713/668b03a7/attachment.htm>