Environment
Open Enterprise Server 2018 (OES 2018) Linux
Situation
CIFS will not start and reported as inactive/dead.
In the /var/log/cifs/cifs.log, the following messages are reported when attempting to start CIFS:
cifsd[20228]: ERROR: ENTRY: Resolve Name failed with error code -626
cifsd[20228]: message repeated 5 times: [ ERROR: ENTRY: Resolve Name failed with error code -626]
cifsd[20228]: ERROR: ENTRY: CIFSNDSResolveName failed with error = -626
cifsd[20228]: ERROR: ENTRY: Schema not extended. Errorcode = -626
cifsd[20228]: ERROR: ENTRY: Failed to start CIFS service, shutdown flags: 0x28
cifsd[20228]: EVENT: ENTRY: Shutdown, process going down
In the /var/log/cifs/cifs.log, the following messages are reported when attempting to start CIFS:
cifsd[20228]: ERROR: ENTRY: Resolve Name failed with error code -626
cifsd[20228]: message repeated 5 times: [ ERROR: ENTRY: Resolve Name failed with error code -626]
cifsd[20228]: ERROR: ENTRY: CIFSNDSResolveName failed with error = -626
cifsd[20228]: ERROR: ENTRY: Schema not extended. Errorcode = -626
cifsd[20228]: ERROR: ENTRY: Failed to start CIFS service, shutdown flags: 0x28
cifsd[20228]: EVENT: ENTRY: Shutdown, process going down
Resolution
The file /etc/opt/novell/eDirectory/conf/nds.conf, was missing the entry that states the server context.
For example: n4u.nds.server-context=OU=Servers.O=ACME
Restart ndsd: systemctl restart ndsd.service
Restart cifsd: systemctl restart novell-cifs.service
The setting can be checked with: ndsconfig get n4u.nds.server-context
For example: n4u.nds.server-context=OU=Servers.O=ACME
Append this missing line to nds.conf with the correct context for the server.
Restart cifsd: systemctl restart novell-cifs.service
The setting can be checked with: ndsconfig get n4u.nds.server-context