SMB error events

This topic describes how to verify and resolve SMB errors.

CTDB process is not running (ctdb_down)

Cause

CTDB process is not running.

Determination

Check /var/log/messages for CTDB error messages or crashes.

Solution

Fix any obvious issues and run this command:
mmces service stop SMB
mmces service start SMB

CTDB recovery detected (ctdb_recovery)

Cause

CTDB status is stuck in Recovery mode for an extended amount of time.

Determination

If the service status is Degraded for a while, there is an issue. The service status should be Transient. Check the logs for a possible issue.

Solution

Run:
mmces service stop SMB && mmces service start SMB
If still not fixed, run:
gpfs.snap
and contact IBM® support.

CTDB state is not healthy (ctdb_state_down)

Determination

  1. Check /var/log/messages for errors and correct any that you find.
  2. Check CTDB status by running the ctdb status command.
  3. Check the network connectivity.

Solution

After the error is resolved, the CTDB node should recover. If you have not resolved the error, restart SMB by running this command:
mmces service stop SMB && mmces service start SMB

SMBD process not running

Determination

  1. Check /var/log/messages and /var/adm/ras/log.smbd for errors and correct if found.
  2. Restart by running this command:
    mmces service stop SMB && mmces services start SMB

SMB port (?) is not active (smbport_down_)

Cause

The SMB port (?) is not listening for connections.

Determination

Check the network connectivity.

Solution

Restart by running:
mmces service stop SMB && mmces services start SMB