Steps to run winbindd in debug level 10 mode to make sure the system is joined to the domain

Version 1

    Steps to run winbindd in debug level 10 mode.

    This information applies to the following Product(s):

    - SnapServer 4200

    - SnapServer 4400
    - SnapServer 4500
    - SnapServer 14000
    - SnapServer 15000
    - SnapServer 18000

    This information applies to the following Operating System(s):

    - This information is not Operating System specific


    ---Solution---

    Running winbindd in debug level 10 mode is applicable in the following situations.

    A) System is running the current operating system and domain join is successful but domain users and groups are not being retrieved by the system
    B) System is running the current operating system but the message \?internal fault in PID XXXXX - /bin/winbindd\? is recorded in the system log


    Steps to run winbindd in debug level 10 mode.

    1. make sure system is joined to the domain
    2. point the browser to the /admin/debug.cgi page
    3. run the commands in steps 4 through 8
    4. pidof winbindd (This command checks if winbindd is running. Two numbers should be returned.)
    5. killall winbindd (This command should stop the two winbindd processes.)
    6. pidof winbindd (Run this command to confirm the winbindd processes have stopped. No numbers should display in the output.)
    7. winbindd -i -d10 > /shares/SHARE1/log_winbindd_d10.txt 2>&1& (This command runs winbindd in debug mode and outputs the log file inside SHARE1. This assumes the default SHARE1 still exists on the system. Replace SHARE1 with the name of an existing share if SHARE1 does not exist.)
    8. pidof winbindd (Confirm the winbindd processes are running. Two numbers should be displayed in the output.)

    How long to keep the process running will depend on the situation.

    If domain users and groups are not being populated after joining the domain and waiting for 30 minutes, run the process in debug mode for about 30 minutes.

    If the message \?internal fault in PID XXXXX - /bin/winbindd\? is recorded in the system log while running the latest operating system version, run the process in debug mode until another instance of the message is recorded in the event log. Note the winbindd log file will become very large the longer winbindd runs in debug mode. If the file becomes too large, repeating the steps will overwrite the existing log file.


    To stop running winbindd in debug mode, run the command in step 5 and rejoin the domain from the web administration page. Remember to compress the log file before submitting.