Can't migrate to NS8 (Error connecting to NS8 and retrieving apps)

[pnemenz]

I also have problems to migrate to NS8.
after puting the correct data into the migration Form I’ll get

On NS7 in the Log I found:

Apr 22 12:51:23 home2 systemd: Reloading.
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/netdata.service:9] Unknown lvalue 'LogNamespace' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:17] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:18] Unknown lvalue 'LockPersonality' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:19] Unknown lvalue 'ProtectControlGroups' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:20] Unknown lvalue 'ProtectKernelModules' in section 'Service'
Apr 22 12:51:23 home2 systemd: Reloading The Apache HTTP Server.
Apr 22 12:51:23 home2 httpd: [Mon Apr 22 12:51:23.886229 2024] [so:warn] [pid 10821] AH01574: module php5_module is already loaded, skipping
Apr 22 12:51:23 home2 systemd: Reloaded The Apache HTTP Server.
Apr 22 12:51:23 home2 systemd: Reloading.
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/netdata.service:9] Unknown lvalue 'LogNamespace' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:17] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:18] Unknown lvalue 'LockPersonality' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:19] Unknown lvalue 'ProtectControlGroups' in section 'Service'
Apr 22 12:51:23 home2 systemd: [/usr/lib/systemd/system/suricata.service:20] Unknown lvalue 'ProtectKernelModules' in section 'Service'
Apr 22 12:51:24 home2 systemd: Starting WireGuard via wg-quick(8) for ns8...
Apr 22 12:51:24 home2 wg-quick: [#] ip link add ns8 type wireguard
Apr 22 12:51:24 home2 wg-quick: [#] wg setconf ns8 /dev/fd/63
Apr 22 12:51:24 home2 wg-quick: [#] ip -4 address add 10.5.4.16 dev ns8
Apr 22 12:51:24 home2 wg-quick: [#] ip link set mtu 1420 up dev ns8
Apr 22 12:51:24 home2 wg-quick: [#] ip -4 route add 10.5.4.0/24 dev ns8
Apr 22 12:51:24 home2 wg-quick: RTNETLINK answers: File exists
Apr 22 12:51:24 home2 wg-quick: [#] ip link delete dev ns8
Apr 22 12:51:24 home2 systemd: wg-quick@ns8.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 22 12:51:24 home2 systemd: Failed to start WireGuard via wg-quick(8) for ns8.
Apr 22 12:51:24 home2 systemd: Unit wg-quick@ns8.service entered failed state.
Apr 22 12:51:24 home2 systemd: wg-quick@ns8.service failed.
Apr 22 12:51:24 home2 systemd: Starting WireGuard via wg-quick(8) for ns8...
Apr 22 12:51:24 home2 wg-quick: [#] ip link add ns8 type wireguard
Apr 22 12:51:24 home2 wg-quick: [#] wg setconf ns8 /dev/fd/63
Apr 22 12:51:24 home2 wg-quick: [#] ip -4 address add 10.5.4.16 dev ns8
Apr 22 12:51:24 home2 wg-quick: [#] ip link set mtu 1420 up dev ns8
Apr 22 12:51:24 home2 wg-quick: [#] ip -4 route add 10.5.4.0/24 dev ns8
Apr 22 12:51:24 home2 wg-quick: RTNETLINK answers: File exists
Apr 22 12:51:24 home2 wg-quick: [#] ip link delete dev ns8
Apr 22 12:51:24 home2 systemd: wg-quick@ns8.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 22 12:51:24 home2 systemd: Failed to start WireGuard via wg-quick(8) for ns8.
Apr 22 12:51:24 home2 systemd: Unit wg-quick@ns8.service entered failed state.
Apr 22 12:51:24 home2 systemd: wg-quick@ns8.service failed.
Apr 22 12:51:24 home2 cockpit-bridge: Traceback (most recent call last):
Apr 22 12:51:24 home2 cockpit-bridge: File "/usr/sbin/ns8-join", line 169, in <module>
Apr 22 12:51:24 home2 cockpit-bridge: subprocess.run(['/sbin/e-smith/signal-event', '-j', 'nethserver-ns8-migration-save'], check=True)
Apr 22 12:51:24 home2 cockpit-bridge: File "/usr/lib64/python3.6/subprocess.py", line 438, in run
Apr 22 12:51:24 home2 cockpit-bridge: output=stdout, stderr=stderr)
Apr 22 12:51:24 home2 cockpit-bridge: subprocess.CalledProcessError: Command '['/sbin/e-smith/signal-event', '-j', 'nethserver-ns8-migration-save']' returned non-zero exit status 1.

I can’t post the logs of ns8, since I cant access per ssh, the only way is over the proxmox console and there I cant copy

it’s a little pain right now, I need to change the keyboard layout becouse i Do not have an english keyboard… anybody know how to set this thing to german?

[dnutan (Marc)]

@pnemenz

change the keyboard layout

One way, if locales are installed:

localectl
localectl list-keymaps |grep de

# to change keymap probably is:
localectl set-keymap de

[Andy_Wismer (André Wismer)]

Adapt Language & TimeZone for Debian…

export LANG=de_DE.UTF-8

dpkg-reconfigure locales

nano /etc/default/locale

Insert the following entries:

LC_TIME=“de_DE.UTF-8”
LC_PAPER=“de_DE.UTF-8”
LC_MEASUREMENT=“de_DE.UTF-8”

Use CTRL-x to quit, y to save.

dpkg-reconfigure tzdata

reboot

This is for german german, swiss german would be de_CH

My 2 cents
Andy

[pnemenz]

Thank you all, dpkg is not found but @dnutan way worked.

Back to the initial Problem:

How can I migrate to NS8?

I want to migrate only the Active directory and the mailserver. other things I will built from scatch.
Any sugestions?

[dnutan (Marc)]

Failed to start WireGuard via wg-quick(8) for ns8.

Don’t know if this applies to your case (expand it or follow link for full details):

NS7 to NS8 migration tool fails to connect

After a lot of help from @davidep I got my NS7 node to connect to the new NS8 cluster. It looks like putting a “|” in the password really messed up the configuration for migration. However, resetting the NS7 config isn’t enough to fix it; the incorrect connection attempt from NS7 also left my NS8 node in a non-connectable state. Here’s what I did that worked: NS7 - Uninstalled Migration tool NS7 - Ran the config clean commands mentioned by Davide: config delete ns8 config delete wg-quick@wg…

NS8 migration: wireguard does not install on NS7

The 2017 build (ancient) ns7 server was missing the required secure boot keys from the ELrepo to load the kernel module for wireguard. these elrepo wiki post has all the needed steps to fix the problem.

[mrmarkuz (Markus Neuberger)]

Maybe relevant:

Failed even to start migration... any ideas?

OK newer news. I started from scratch, from fresh NS8 VM, where I set the VPN related FQDN (or the leader node?) correctly from scratch, from the setup wizard. This allowed migration in NS7 to query installed apps properly. I don’t know if the migration will work but the issue of this thread is resolved. So, I don’t know if the issue was that this FQDN was not set correctly from the beginning, or something else. I do know that going to leader node and clicking to change FQDN FAILS the whole…

[pnemenz]

the first dosn’t applies, there is no | in my password.

the 2nd dosn’t work

as said on your link:

 mokutil --import /etc/pki/elrepo/SECURE-BOOT-KEY-elrepo.org.der
-bash: mokutil: Command not found

[dnutan (Marc)]

@pnemenz

the first dosn’t applies, there is no | in my password.

@mrmarkuz , do you think it makes sense or can help to recreate the WG VPN?

@NS7 to NS8 migration tool fails to connect

• NS7 - Ran the config clean commands mentioned by Davide:

config delete ns8
config delete wg-quick@wg0
config delete agent

• NS7 - Re-installed Migration Tool

[mrmarkuz (Markus Neuberger)]

Yes, I think it’s worth a try.

[pnemenz]

Didn’t help a thing. Maybe I should try to install on debian instad using the proxmox image?

[dnutan (Marc)]

Maybe a leftover from the wg tunnel remains… (or wg it’s still active)

RTNETLINK answers: File exists

About trying with Debian beware of this recent case:

Clean install of NS8 on Debian12, Fails with Redis

Hi After installing a very current Debian from a downloaded ISO Image on Proxmox, updating and making sure the FQDN & static IP are correctly set on Debian 12, the install of NS8 according to the instructions here fail: https://docs.nethserver.org/projects/ns8/en/latest/install.html#install-linux-section Actually, all seem to run through just fine, until this section of code while running ths bash installer: Created symlink /etc/systemd/system/default.target.wants/redis.service → /etc/system…