Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-2237: Unable to see Samba shares; smbd hangs

Centrify DirectControl ,   Centrify DirectControl Plugins ,  

12 April,16 at 11:47 AM

Applies to: All versions of Centrify-enabled Samba.
 
Problem:
We are unable to view Centrify-enabled shares from Windows or Unix. The Samba (smbd)  daemon does not start or stop gracefully. The Centrify-enabled Samba server has been rebooted and Centrify adbindproxy.pl has been run too. Its not possible to get debug logs either as level-10 debug logs require restart of Centrify-enabled Samba which is failing.
 
Cause:
This can happen if printer definitions fail to load. Each section in the smb.conf file represents either a share or a meta-service on the Samba server. The section [global] is special, since it contains settings that apply to the whole Samba server. Samba supports a number of meta-services, each of which serves its own purpose.. The [printers] share is a meta-service that establishes print queue support and that specifies the location of the intermediate spool directory into which print jobs are received from Windows clients prior to being dispatched to the UNIX/Linux print spooler. 
 
Workaround:
Please follow these steps:
 
1) As root, please stop all Centrify-enabled Samba daemons by running 
#/etc/init.d/centrifydc-samba stop.
 
2) Confirm the same by doing a ps -ef|grep centrify*
If you see any of the below processes, please do a pkill or kill -9 of these processes.
 
 root  1031     1   0 21:57:39 ?           0:00 /opt/centrify/samba/sbin/smbd    
 root   992     1   0 21:57:36 ?           0:00 /opt/centrify/samba/sbin/nmbd    
root  1017     1   0 21:57:38 ?           0:01 /usr/share/centrifydc/sbin/adbindd
root  1004     1   0 21:57:37 ?           0:00 /opt/centrify/samba/sbin/winbindd -s /etc/centrifydc/smb2.conf
 
3) Run smbd as follows
#/usr/sbin/smbd -F -d 10 -i where F is foreground, d is debug, 10 is level and i is info
 
4) If it hangs as shown below, then it could be a printer issue.
"lp_servicenumber: couldn't find printers reloading printcap cache reloading sysv printcap 
cache"
 
5) If customer is not using Centrify-enabled Samba server as a print server, they can disable 
printing as follows:
 
a) Navigate to /etc/samba and open smb.conf.
 
Under the global section (and just before the share definitions), add the following lines
 
        load printers = no
        printing = bsd
        printcap name = /dev/null
        show add printer wizard = no
        disable spoolss = yes
 
b) Run testparm command to check for syntax errors (if any).
 
6) Stop all Samba processes as mentioned above. Re-run "#/usr/sbin/smbd -F -d 10 -i" where 'F' is foreground, 'd' is debug, '10' is level and 'i' is interactive
 
7) If the last line shows "waiting for a connection", then Centrify-enabled Samba is accepting 
connections.
 
8)Verify by browsing to Samba shares from Windows machines.
 
9) Stop Centrify-enabled Samba running in foreground by pressing cotntrol C and restart the 
same from /etc/init.d.
 
Resolution:
None as this issue can exist in stock Samba too.
 
 
 
 
 
 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.