Solaris Cluster 3.3 HA-Samba Resource Fails to Start due to pid File Errors After Upgrade or Patching of Samba to Version 3.6.x
Last updated on OCTOBER 24, 2017
Applies to:Solaris Cluster - Version 3.3 to 3.3 U2 [Release 3.3]
Solaris Cluster Geographic Edition - Version 3.3 to 3.3 U2 [Release 3.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-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
The location and names of pid files have been changing in various versions of samba.
Especially starting with Samba 3.6 patches
<SunPatch 119757-22> SunOS 5.10: Samba patch
<SunPatch 119757-22> SunOS 5.10_x86: Samba patch
which upgrade the Samba version.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms