Hi Timo, Thanks for your response.
I had spotted the Samba schema issue shortly after and took it out of the configuration already, but still had the same problem. Only by creating the symlink I mentioned this problem became resolved. Does it matter that this system was an in-place upgrade from Buster? (Its original installation was Jessie and has been upgraded throughout releases.) * Adam Reece * Sven Co-op team * Email: a...@svencoop.com <mailto:a...@svencoop.com> * Web: www.svencoop.com <http://www.svencoop.com> On 31/08/2021 17:47, Timo Aaltonen wrote:
On 22.8.2021 15.15, Adam Reece wrote:Aug 22 14:13:38 amun ns-slapd[14030]: [22/Aug/2021:14:13:38.279004946 +0200] - ERR - dse_read_one_file - The entry cn=schema in file /etc/dirsrv/slapd-amun.service/schema/60samba3.ldif (lineno: 1) is invalid, error code 20 (Type or value exists) - object class sambaConfig: The name does not match the OID "1.3.6.1.4.1.7165.1.2.2.10". Another object class is already using the name or OID. Aug 22 14:13:38 amun ns-slapd[14030]: [22/Aug/2021:14:13:38.280495362 +0200] - ERR - setup_internal_backends - Please edit the file to correct the reported problems and then restart the server.That's your error. The 389 packages didn't change since -2 and things work just fine on ci.debian.net and salsa (meaning the daemon starts), so I don't know how 389 could be to blame here. the libjemalloc thing is just noise, it's not a hard requirement AIUI.
OpenPGP_0x772BA858CF9CD88D.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
