Migration from NS7 to NS8

Denis_Pollini · March 21, 2024, 11:17am

I follow this documentation: NethServer 7 migration — NS8 documentation
I start the sync but is still al 0%

This is the log of /var/log/ns8-migration.log:

Any toughts?

oneitonitram · March 21, 2024, 12:01pm

Hello @Denis_Pollini we would love to assist and help you troubleshoot your situation,

however there is a lot of grey area in your support request.

Equally, logs from both destination and source i believe would be a great start, and is possible avoid sharing screenshot of logs, just copy the text, and enclose it in code.

Could you kindly share more information about your setup, intended migration, apps being migrated local or remote, basically your setup to provide a possible resolution?

Denis_Pollini · March 22, 2024, 10:48am

Hi
This morning i click to “sync data” and it goes fine without any errors.
After that i click on “finish migration” but something goes wrong now i can’t open Nextcloud, this is the log of instance “Nextcloud1” on NS8

2024-03-22T11:47:16+01:00 [1:nextcloud1:agent@nextcloud1] parse error: Invalid numeric literal at line 1, column 3
2024-03-22T11:47:16+01:00 [1:nextcloud1:podman] 2024-03-22 11:47:16.372535989 +0100 CET m=+0.056227062 container exec_died 317b946589fd713677cdcf1f55f458d214490cd7212a28c1fef086b00e58ad20 (image=ghcr.io/nethserver/nextcloud-app:1.1.5, name=nextcloud-app, PODMAN_SYSTEMD_UNIT=nextcloud-app.service, io.buildah.version=1.23.1)
2024-03-22T11:47:16+01:00 [1:nextcloud1:podman] 2024-03-22 11:47:16.379982435 +0100 CET m=+0.272873480 container exec_died 317b946589fd713677cdcf1f55f458d214490cd7212a28c1fef086b00e58ad20 (image=ghcr.io/nethserver/nextcloud-app:1.1.5, name=nextcloud-app, io.buildah.version=1.23.1, PODMAN_SYSTEMD_UNIT=nextcloud-app.service)
2024-03-22T11:47:16+01:00 [1:nextcloud1:agent@nextcloud1] parse error: Invalid numeric literal at line 1, column 3
2024-03-22T11:47:16+01:00 [1:nextcloud1:agent@nextcloud1] parse error: Invalid numeric literal at line 1, column 3
2024-03-22T11:47:16+01:00 [1:nextcloud1:podman] 2024-03-22 11:47:16.688405906 +0100 CET m=+0.045629571 container exec_died 317b946589fd713677cdcf1f55f458d214490cd7212a28c1fef086b00e58ad20 (image=ghcr.io/nethserver/nextcloud-app:1.1.5, name=nextcloud-app, PODMAN_SYSTEMD_UNIT=nextcloud-app.service, io.buildah.version=1.23.1)
2024-03-22T11:47:17+01:00 [1:nextcloud1:agent@nextcloud1] parse error: Invalid numeric literal at line 1, column 3
2024-03-22T11:47:17+01:00 [1:nextcloud1:podman] 2024-03-22 11:47:17.074692861 +0100 CET m=+0.255980370 container exec_died 317b946589fd713677cdcf1f55f458d214490cd7212a28c1fef086b00e58ad20 (image=ghcr.io/nethserver/nextcloud-app:1.1.5, name=nextcloud-app, PODMAN_SYSTEMD_UNIT=nextcloud-app.service, io.buildah.version=1.23.1)
2024-03-22T11:47:17+01:00 [1:nextcloud1:agent@nextcloud1] parse error: Invalid numeric literal at line 1, column 3
2024-03-22T11:47:17+01:00 [1:nextcloud1:podman] 2024-03-22 11:47:17.322891554 +0100 CET m=+0.241623306 container exec_died 317b946589fd713677cdcf1f55f458d214490cd7212a28c1fef086b00e58ad20 (image=ghcr.io/nethserver/nextcloud-app:1.1.5, name=nextcloud-app, io.buildah.version=1.23.1, PODMAN_SYSTEMD_UNIT=nextcloud-app.service)
2024-03-22T11:47:17+01:00 [1:nextcloud1:agent@nextcloud1] parse error: Invalid numeric literal at line 1, column 3
2024-03-22T11:47:17+01:00 [1:nextcloud1:podman] 2024-03-22 11:47:17.60044965 +0100 CET m=+0.060072043 container exec_died 317b946589fd713677cdcf1f55f458d214490cd7212a28c1fef086b00e58ad20 (image=ghcr.io/nethserver/nextcloud-app:1.1.5, name=nextcloud-app, io.buildah.version=1.23.1, PODMAN_SYSTEMD_UNIT=nextcloud-app.service)

In NS7 if i click Sync data i get this error

nethserver-ns8-migration/migration/update

And this is the output:

[root@srv01 ~]#  echo '{"app":"nethserver-nextcloud","action":"sync"}' | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/nethserver-ns8-migration/migration/update | jq
{
  "progress": "0.00",
  "time": "0.0",
  "exit": 0,
  "event": "migration-sync",
  "state": "running",
  "step": 0,
  "pid": 0,
  "action": ""
}
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
rsync: failed to connect to 10.5.4.1 (10.5.4.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]
{
  "pid": 0,
  "status": "failed",
  "event": "migration-sync"
}
{
  "id": "1711104250",
  "type": "ApiFailed",
  "message": "sync nethserver-nextcloud failed"
}

danb35 · March 22, 2024, 12:13pm

Are any errors showing in NS8?

Denis_Pollini · March 22, 2024, 5:02pm

Hi yes if you see the post above the top one is the log of “nextcloud” instance.

Denis_Pollini · March 22, 2024, 5:26pm

Hi everyone in this case the final migration not goes fine, and now i can’t use nextcloud, is possibile to restart the service on the original nethserver 7 was before i click on the button “final migration”?
Because if i start manually the httpd service and go to cloud.mydomain.tld i see this webpage:

dnutan · March 22, 2024, 5:50pm

Please note that some migrated applications may also add some custom templates. To list such template fragments use:
grep -lR ns8migration /etc/e-smith/templates-custom/
It is possible to manually re-enable the services with the following commands.

Nextcloud
rm -rf /etc/e-smith/templates-custom/etc/httpd/conf.d/zz_nextcloud.conf
rm -f /etc/e-smith/templates-custom/etc/httpd/conf.d/default->virtualhost.inc/40nextcloud
signal-event nethserver-nextcloud-update

(source)

dnutan · March 22, 2024, 6:13pm

If I understood correctly, Nextcloud migration from NS7 to NS8 succeeded from the point of view of NS7 side but something on NS8 is preventing Nextcloud from being operational (so migration failed or got stuck)?

Denis_Pollini · March 22, 2024, 6:43pm

Hi @dnutan
I do this command:

rm -rf /etc/e-smith/templates-custom/etc/httpd/conf.d/zz_nextcloud.conf
rm -f /etc/e-smith/templates-custom/etc/httpd/conf.d/default->virtualhost.inc/40nextcloud
signal-event nethserver-nextcloud-update

And now i’m still able to have nextcloud up and running again on ns7

The procedure was this:
I install the migration tool on NS7 and add the NS8 using the FQDN with no errors, after that i start to sync data with no errors, this morning i change the dhcp ip for ns8 to static one and on webpage of migration tool on NS7 he give me some errors and i can’t see the application for migrate anymore, so i reconfigure the ns8 machine with the ip address has before and then the migration tool on ns7 show me again the application, so i click the button “finish migration” is start but a certain point he give some error, like i post on the 1st reply.

Denis_Pollini · March 27, 2024, 1:57pm

Update
So i create VM on Proxmox customer and restore the config and the data from backup restic, so now i have the same NS7 but not anymore on bare metal but on a VM, so i can try things without worry too much because i can create snapshot very quicly and restore if something goes wrong.

So in my case now i have this on NS8 Migration tool on NS7:

What step i need to do uninstall this tool and reinstall?
And on NS8 Side Remove the container and to it from scratch?

stephdl · March 27, 2024, 2:14pm

webbrowser console or the content of the migration log (/var/log/*) should explain a bit more

Denis_Pollini · March 27, 2024, 2:19pm

Hi @stephdl
Don’t have any entries on the logs of NS8 Migration Tools as you can see:

And in the terminal under /var/log the ns8-migration.log doesn’t exists.

Denis_Pollini · March 29, 2024, 4:00pm

UPDATE:
Hi guys i remove the database of ns8 migration tool remove the package and reinstall, reconfigure the ns8 but we back at start situation.
This is what i think is related to this problem on /var/log/messages:

stephdl · March 29, 2024, 4:28pm

does the fqdn you used is resolved both by the NS7 and the NS8, do they share the same DNS server ?

can u try with IP too

Denis_Pollini · April 2, 2024, 7:27am

Hi
Ping from NS7 to NS8:

Ping from NS8 to NS7:

I notice if i ping trought wireguard not work this is the interface on NS7:

This on NS8:

If from ns7 ping ns8 not reply:

From NS8 to NS7:

is in italian but it says:
ping: sendmsg: The required key is not available

stephdl · April 2, 2024, 7:46am

try to remove everything related to ns8-migration and also wiregard and reinstall again, if you cannot ping the endpoint of vpn, this is probably the root cause

BTW what is the version of migration you installed, we released a new one recently

Denis_Pollini · April 2, 2024, 7:50am

stephdl · April 2, 2024, 7:50am

yes it is good, this is the last

Denis_Pollini · April 2, 2024, 7:51am

Ok What command should i run on NS7 to remove everything related to ns8 migration e wireguard?
Update:
I remove the package from NS7 GUI Applications and the remove ns8 migration tools, but wireguard i see still there:

i remove it just with yum remove? but the configuration of wireguard does remove too with yum remove?

stephdl · April 2, 2024, 8:10am

yum install mlocate
updatedb
locate wg0