SMB logs

The SMB services write the most important messages to syslog.

The SMB service in IBM Storage Scale writes its log message into the syslog of the CES nodes. Thus, it needs a working syslog daemon and configuration. An SMB snap expects syslog on CES nodes to be found in a file in the distribution's default paths. If syslog gets redirected to another location, the customer should provide the logs in case of support.

With the standard syslog configuration, you can search for the terms such as ctdbd or smbd in the /var/log/messages file to see the relevant logs. For example:

grep ctdbd /var/log/messages

The system displays output similar to the following example:
May 31 09:11:23 prt002st001 ctdbd: Updated hot key database=locking.tdb key=0x2795c3b1 id=0 hop_count=1
May 31 09:27:33 prt002st001 ctdbd: Updated hot key database=smbXsrv_open_global.tdb key=0x0d0d4abe id=0 hop_count=1
May 31 09:37:17 prt002st001 ctdbd: Updated hot key database=brlock.tdb key=0xc37fe57c id=0 hop_count=1
grep smbd /var/log/messages
The system displays output similar to the following example:
May 31 09:40:58 prt002st001 smbd[19614]: [2015/05/31 09:40:58.357418,  0] ../source3
/lib/dbwrap/dbwrap_ctdb.c:962(db_ctdb_record_destr)
May 31 09:40:58 prt002st001 smbd[19614]: tdb_chainunlock on db /var/lib/ctdb/locking.tdb.2, 
key FF5B87B2A3FF862E96EFB400000000000000000000000000 took 5.261000 milliseconds
May 31 09:55:26 prt002st001 smbd[1431]: [2015/05/31 09:55:26.703422,  0] ../source3
/lib/dbwrap/dbwrap_ctdb.c:962(db_ctdb_record_destr)
May 31 09:55:26 prt002st001 smbd[1431]: tdb_chainunlock on db /var/lib/ctdb/locking.tdb.2, 
key FF5B87B2A3FF862EE5073801000000000000000000000000 took 17.844000 milliseconds
Additional SMB service logs are available in following folders:
  • /var/adm/ras/log.smbd
  • /var/adm/ras/log.smbd.old

When the size of the log.smbd file becomes 100 MB, the system changes the file as log.smbd.old. To capture more detailed traces for problem determination, use the mmprotocoltrace command.

Some of the issues with SMB services are related to winbind service also. For more information about winbind tracing, see Winbind logs.