Knowledge Base

Advanced troubleshooting steps

1. On the vDR appliance, log into the console as root and check the /var/log/messages file for any CIFS-related messages by running the command:
   
   # grep CIFS /var/log/messages
   
   Nov 30 09:46:27 localhost kernel:  CIFS VFS: No response for cmd 50 mid 34376
   Nov 30 09:46:27 localhost kernel:  CIFS VFS: No response for cmd 50 mid 34375
   Nov 30 09:46:48 localhost kernel:  CIFS VFS: server not responding
   Nov 30 09:46:48 localhost kernel:  CIFS VFS: No response for cmd 114 mid 34377
   
   
2. Check the state of the mounted CIFS shares by running the command:
   
   # cat /proc/fs/cifs/DebugData
   
   Display Internal CIFS Data Structures for Debugging
   ---------------------------------------------------
   CIFS Version 1.60RH
   Active VFS Requests: 0
   Servers:
   1) Name: 10.16.224.189  Domain: WORKGROUP Uses: 1 OS: Windows 7 Ultimate 7601 Service Pack 1
         NOS: Windows 7 Ultimate 6.1     Capability: 0x1e3fc
         SMB session status: 1   TCP status: 1
         Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0
         Shares:
         1) \\10.16.224.189\share Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0xc700ff
   PathComponentMax: 255 Status: 0x1 type: DISK
         MIDs:
   
   
3. Verify that the vDR appliance can successfully connect to the Windows server providing the CIFS share by running the command:
   
   # smbclient -d 7 -L //SMB_HOST_OR_IP -W WorkGroup -U user%password
   
   Note: The -d parameter specifies the output verbosity. The value is configurable from 0 (the default) to 7 (most verbose).
   
   Example usage:
   
   # smbclient -d 7 -L //10.0.0.1 -W MyWorkGroup -U MyUser%MyPassword
   
   Note: If you see the session setup failed: SUCCESS - 0 error, you must uninstall all Windows Live Essentials applications from the Windows 7 machine hosting the CIFS share. For more information, see Samba bug 7577.

Debug Troubleshooting

1. Log into a console or SSH session as root on the vDR appliance.
2. Verify whether all kernel messages are being logged to /var/log/kernel.log by running the command:
   
   # grep kern /etc/syslog.conf
   
   If all kernel messages are being logged, output is similar to:
   
   kern.*                      /var/log/kernel.log
   
   
3. If all kernel messages are not being logged, enable them by running:
   
   # echo "kern.*             /var/log/kernel.log" >> /etc/syslog.conf
   
   Note: Verify that the content of the /etc/syslog.conf file is similar to this example by running the command:
   
   # cat /etc/syslog.conf
   
   Example content:
   
   kern.*                                       /var/log/kernel.log
   *.info;mail.none;authpriv.none;cron.none     /var/log/messages
   authpriv.*                                   /var/log/secure
   mail.*                                       -/var/log/maillog
   cron.*                                       /var/log/cron
   *.emerg                                      *
   uucp,news.crit                               /var/log/spooler
   local7.*                                     /var/log/boot.log
   
   
4. To apply the changes, restart the syslog service on the vDR appliance by running the command:
   
   # service syslog restart

1. Log into a console or SSH session as root on the vDR appliance.
2. Enable increased CIFS logging by running the command:
   
   # echo 3 > /proc/fs/cifs/cifsFYI
   
   
3. Verify the value in cifsFYI by running:
   
   # cat /proc/fs/cifs/cifsFYI
   3
   
   Note: The value is configurable from 0 (the default) to 7 (most verbose).

Troubleshooting network connectivity between vDR and the CIFS server

1. Log into the console of the vDR appliance as the root user.
2. Install tcpdump on the vDR appliance by running the command:
   
   # yum install tcpdump
   
   
3. The installer prompts you to confirm installing the package. Answer yes to install tcpdump.
4. When complete, you see a message similar to:
   
   Installed:
    tcpdump.x86_64 14:3.9.4-15.el5
   Complete!