The user doesn’t want to restart winbind or samba to increase the log levels. The user needs increased logging while a problem is occurring but increasing the log level through the smb.conf requires a restart of the services which can temporarily fix an issue and requires the user to wait for another occurrence to get the logs needed. How can we increase the log levels without restarting the services?
Increasing the log level of winbind or samba without restarting the services
Increasing the logs while a problem is occurring can help reduce the impact of high log levels over an extended period such as disk usage and system performance. Setting the logs without restarting the daemon is also useful for cases when restarting the service temporarily fixes the problem for a period of time. The drawback is that increasing logs after a problem has occurred may result in missing information but this isn’t needed in cases when a reproducer is known. Follow the steps below to increase the log levels without restarting the services.
1. Set runtime samba and winbind log levels with the following two commands, respectively.
# smbcontrol smbd debug 10 # smbcontrol winbindd debug 10
2. You can output the log level of winbindd like this:
# smbcontrol winbind debuglevel PID 16873: all:10 tdb:10 printdrivers:10 lanman:10 smb:10 rpc_parse:10 rpc_srv:10 rpc_cli:10 passdb:10 sam:10 auth:10 winbind:10 vfs:10 idmap:10 quota:10 acls:10 locking:10 msdfs:10 dmapi:10 registry:10
3. You can also set the log level for a specific process:
# smbcontrol [pid] debug 10
4. And output the level with this command:
# smbcontrol [pid] debuglevel