Migration fail without a real error message

Support
,
1

NethServer Version: 7.9 to 8.5
Module: migration tool NS7 to NS8
i did everything how it is wrote in the Documentation but if i start the Migration, first with Emails i got an red error sign again…
Fehler

Synchronization failed

Der folgende Befehl ist gescheitert:
nethserver-ns8-migration/migration/update
Leider konnten wir den exakten Fehler nicht finden. Wenn Sie helfen wollen, clicken Sie bitte auf den Button unten, um den fehlerhaften Befehl zu kopieren und im Terminal einzufügen, damit Sie den Befehl an die Entwickler weiterleiten können…
any advice? its stop after it move the imapsynch and mail app

== Join cluster Thu, 17 Apr 2025 18:16:45 +0200
ns8-join: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:877)>
=========== Join cluster Thu, 17 Apr 2025 18:16:50 +0200
Joined to cluster leader NS8.wt-sonnenberg.de
----------- start nethserver-mail Thu, 17 Apr 2025 18:17:37 +0200
mkdir: created directory ‘/var/lib/nethserver/nethserver-ns8-migration/nethserver-sogo’
mkdir: created directory ‘/var/lib/nethserver/nethserver-ns8-migration/nethserver-mail-getmail’
Assertion failed
File “/var/lib/nethserver/cluster/actions/import-module/50import”, line 50, in
agent.assert_exp(add_module_result[‘exit_code’] == 0) # add-module is successful
[INFO] Created remote module instance imapsync1
[INFO] App nethserver-mail-getmail is bound to rsync://imapsync1@10.5.4.1:20003, waiting for task module/imapsync1/task/ee4d0759-52db-493e-82d8-25a0ff063497
[INFO] Created remote module instance mail1
[INFO] App nethserver-mail is bound to rsync://mail1@10.5.4.1:20004, waiting for task module/mail1/task/3d028183-1f18-4085-a565-375446efe646
do i have to install mail app and sogo first? not sure about that step

Updates are suspended
ON NS8 this is written
There is an ongoing NS7 migration. Updates will resume once the migration is complete.

mkdir: created directory ‘/var/lib/nethserver/nethserver-ns8-migration/nethserver-sogo’
mkdir: created directory ‘/var/lib/nethserver/nethserver-ns8-migration/nethserver-mail-getmail’
Assertion failed
File “/var/lib/nethserver/cluster/actions/import-module/50import”, line 50, in
agent.assert_exp(add_module_result[‘exit_code’] == 0) # add-module is successful
[INFO] Created remote module instance imapsync1
[INFO] App nethserver-mail-getmail is bound to rsync://imapsync1@10.5.4.1:20003, waiting for task module/imapsync1/task/ee4d0759-52db-493e-82d8-25a0ff063497
[INFO] Created remote module instance mail1
[INFO] App nethserver-mail is bound to rsync://mail1@10.5.4.1:20004, waiting for task module/mail1/task/3d028183-1f18-4085-a565-375446efe646
----------- sync nethserver-mail Thu, 17 Apr 2025 18:26:14 +0200
----------- sync nethserver-mail Thu, 17 Apr 2025 18:38:31 +0200
----------- abort nethserver-mail Thu, 17 Apr 2025 18:38:52 +0200
----------- sync nethserver-mail Thu, 17 Apr 2025 18:40:38 +0200
----------- sync nethserver-mail Thu, 17 Apr 2025 18:41:58 +0200
----------- sync nethserver-mail Thu, 17 Apr 2025 18:45:50 +0200

echo ‘{“app”:“nethserver-mail”,“action”:“sync”}’ | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/nethserver-ns8-migration/migration/update | jq

Okay, got everything working.

2

After checking the new server no user from Active directory was migrated… is there a general Prob?

{“context”:{“action”:“list-domain-groups”,“data”:{“domain”:“ad.xx-sonnenberg.de”},“extra”:{“eventId”:“71e3bdec-85e4-4506-b56d-82e8cc114a93”,“isNotificationHidden”:true,“title”:“Domänen-Gruppen auflisten”},“id”:“18b31fc3-5076-4227-bd2d-2b290fed72b5”,“parent”:“”,“queue”:“cluster/tasks”,“timestamp”:“2025-04-17T19:07:18.35424799Z”,“user”:“admin”},“status”:“aborted”,“progress”:0,“subTasks”:,“validated”:false,“result”:{“error”:“Traceback (most recent call last):\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/strategy/sync.py", line 89, in receiving\n data = self.connection.socket.recv(self.socket_size)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nConnectionResetError: [Errno 104] Connection reset by peer\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File "/var/lib/nethserver/cluster/actions/list-domain-groups/50list_groups", line 33, in \n groups = Ldapclient.factory(**domain).list_groups()\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pypkg/agent/ldapclient/init.py", line 29, in factory\n return LdapclientAd(**kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pypkg/agent/ldapclient/base.py", line 37, in init\n self.ldapconn = ldap3.Connection(self.ldapsrv,\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/core/connection.py", line 363, in init\n self._do_auto_bind()\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/core/connection.py", line 389, in _do_auto_bind\n self.bind(read_server_info=True)\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/core/connection.py", line 607, in bind\n response = self.post_send_single_response(self.send(‘bindRequest’, request, controls))\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/strategy/sync.py", line 160, in post_send_single_response\n responses, result = self.get_response(message_id)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/strategy/base.py", line 355, in get_response\n responses = self._get_response(message_id, timeout)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/strategy/sync.py", line 196, in _get_response\n responses = self.receiving()\n ^^^^^^^^^^^^^^^^\n File "/usr/local/agent/pyenv/lib64/python3.11/site-packages/ldap3/strategy/sync.py", line 99, in receiving\n raise communication_exception_factory(LDAPSocketReceiveError, type(e)(str(e)))(self.connection.last_error)\nldap3.core.exceptions.LDAPSocketReceiveError: error receiving data: [Errno 104] Connection reset by peer\n”,“exit_code”:1,“file”:“task/cluster/18b31fc3-5076-4227-bd2d-2b290fed72b5”,“output”:“”}}

3

It seems samba cannot be reached.

Is it running?

runagent -m samba1 podman ps

Let’s check if the users are there:

runagent -m samba1 podman exec samba-dc samba-tool user list

Maybe the samba IP is not the same as the host IP?

To check the samba IP:

runagent -m samba1 grep IPADDRESS environment
4

i did an error, at the end of the migration it ask about the ip for the domain controller, i choose the ip of the formerly but at this time the ns8 had a different ip, guess i have to do it once again… or is there a chance to get it run?

5

Yes, you can set the samba IP, see also NethServer 7 migration — NS8 documentation

api-cli run module/samba1/set-ipaddress --data '{"ipaddress":"192.168.1.123"}'
1 Like
6

grafik
grafik2322×448 49.5 KB

something went wrong

7

got it, thank you, will see if it works :smiley:

1 Like