Solaris Cluster 3.x HA-Samba resource fails to start due to pid file errors (Doc ID 1585714.1)

Last updated on SEPTEMBER 21, 2013

Applies to:

Solaris Cluster - Version 3.3 to OSC 3.3 3/13 [Release 3.3]
Solaris Cluster Geographic Edition - Version 3.3 to OSC 3.3 3/13 [Release 3.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)


The samba daemon processes (eg. winbind and smbd and nmbd) do use some well known files and record their own pid (process id) within these files to track when they are running. The location and names of these files have been changing in various versions of samba. Such files shall get cleaned up by samba daemons themselves when they quit gracefully. When system crash or samba daemons do not quit gracefully for whatever reason, the HA-Samba agent shall cleanup these pid files upon failover. When the HA-Samba agent do not cleanup the pid files, the subsequent start of samba might fail with errors like

[2012/10/12 15:16:54.207066,  0] lib/pidfile.c:154(pidfile_create) ERROR: can't open /samba-mountpoint/var/locks/ Error was File exists

Similar errors can occur with winbind or  smbd  or nmbd.



 The location and names of pid files have been changing in various versions of samba.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms