Hi,
I am trying to migrate my domain from Zentyal 6.0 to UCS 4.4-3 errata413. It detects users and groups, however it freezes later on. Log shows that it is unable to synchronize users:
27.12.2019 22:05:09.191 LDAP (PROCESS): sync to ucs: Resync rejected dn: CN=xxx ,CN=Users,DC=xxx,DC=home
27.12.2019 22:05:09.196 LDAP (PROCESS): sync to ucs: [ user] [ add] u'uid=xxx,CN=Users,dc=xxx,dc=home'
27.12.2019 22:05:09.463 LDAP (ERROR ): InvalidSyntax: Unix home directory: Not an absolute path! (u'uid=xxx,CN=Users,dc=xxx,dc=home')
(user name & domain replaced with xxx)
The error repeats for every user. I have no clue what is the reason of this “Unix home directory: Not an absolute path! error”
The domain itself on Zentyal works well, this is small home network. I have few linux, windows and Freenas machines joined and bunch of users.
I’d appreciate if someone could help me.
Best Regards
Marcin
OK, so I moved I a bit forward… I looked into Attribute Editor in user properties in RSAT; UnixHomeDirectory attribute was . For every user I’ve changed it to /home/user and the error with “Unix home directory: Not an absolute path!" is gone. However, there are still two other problems:
- univention-s4-connector is crashing and I have to restart it manually with /etc/init.d/univention-s4-connector restart to have the takeover process moving
- users are not still getting synced, but now I am getting another error:
27.12.2019 23:44:36.792 LDAP (PROCESS): sync to ucs: Resync rejected dn: CN=xxx,CN=Users,DC=xxx,DC=home
27.12.2019 23:44:36.798 LDAP (PROCESS): sync to ucs: [ user] [ add] u'uid=xxx,CN=Users,dc=xxx,dc=home'
27.12.2019 23:44:37.134 LDAP (ERROR ): Value may not change: key=gidNumber old=None new=2513 (u'uid=xxx,CN=Users,dc=rogozch,dc=home')
2513 is indeed correct gidNumber (checked again with RSAT), but what does “new” and “old” mean here?
Just to continue my monologue: I spun off fresh VM and tried again, with same result. Connector is crashing and nothing happens (except for progress bar in the web interface which goes until 98% and then freezes for ever). After restarting univention-s4-connector manually it successfully imports DNS zones, but fails with already mentioned error to import users. Nevertheless web interface shows: all Windows domain accounts have been successfully transferred…
I managed to solve the issue - I had to remove gidNumbers from attributes of every user (I had just four of them so it was not that bad) and afterwards all users have been imported. Just in case someone will be in same situation: before clearing gidNumbers from users one needs to clear gidNumber from the respective group as well, otherwise users’ gidNUmbers get automatically recreated.
However I had to start again manually s4-connector because it failed to start automatically during take over process:
root@ucsad:/var/log/univention# /etc/init.d/univention-s4-connector status
● univention-s4-connector.service - LSB: Univention S4 Connector
Loaded: loaded (/etc/init.d/univention-s4-connector; generated; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2019-12-28 12:06:10 CET; 3min 30s ago
Docs: man:systemd-sysv-generator(8)
Process: 7355 ExecStop=/etc/init.d/univention-s4-connector stop (code=exited, status=0/SUCCESS)
Process: 7333 ExecStart=/etc/init.d/univention-s4-connector start (code=exited, status=0/SUCCESS)
Main PID: 7348 (code=killed, signal=TERM)
CPU: 726ms
Dec 28 12:06:10 ucsad systemd[1]: univention-s4-connector.service: PID file /var/run/univention-s4-connector not readable (yet?) after start: No …or directory
Dec 28 12:06:10 ucsad systemd[1]: univention-s4-connector.service: Supervising process 7348 which is not our child. We'll most likely not notice …en it exits.
Dec 28 12:06:10 ucsad systemd[1]: Started LSB: Univention S4 Connector.
Dec 28 12:06:10 ucsad systemd[1]: Stopping LSB: Univention S4 Connector...
Dec 28 12:06:10 ucsad univention-s4-connector[7355]: Stopping Univention S4 Connector: univention-s4-connector.
Dec 28 12:06:10 ucsad systemd[1]: Stopped LSB: Univention S4 Connector.
Dec 28 12:06:10 ucsad systemd[1]: univention-s4-connector.service: Start request repeated too quickly.
Dec 28 12:06:10 ucsad systemd[1]: Failed to start LSB: Univention S4 Connector.
Dec 28 12:06:10 ucsad systemd[1]: univention-s4-connector.service: Unit entered failed state.
Dec 28 12:06:10 ucsad systemd[1]: univention-s4-connector.service: Failed with result 'start-limit-hit'.
Hint: Some lines were ellipsized, use -l to show in full.