Storage Foundation 5.0 MP3 RP4 (Solaris) includes an additional license fix surrounding a file descriptor leak for vxesd (event source daemon)

Article:TECH135422  |  Created: 2010-01-05  |  Updated: 2011-01-18  |  Article URL
Article Type
Technical Solution




Storage Foundation 5.0 MP3 RP4 (Solaris) includes an additional license fix surrounding a file descriptor leak for vxesd (event source daemon)


VxVM vxdctl ERROR V-5-1-1589 enable failed: License has expired or is not available for operation


In addition to the issue described in technote "328959",  VM engineering identified a new file descriptor leak related to the vxesd daemon. This has been addressed in 5.0 MP3 RP4.


The Event Source Daemon (ESD aka vxesd) is a Volume Manager (VxVM) component process, first introduced in 4.0 on Solaris. In 5.0 and later, vxesd was included in all Unix/Linux platforms.

vxesd is a 'helper' process that receives notifications of device related events which are used to take appropriate actions. The benefits of vxesd include:

   * SAN Fabric event monitoring & pro-active error detection (SAN event)
   * DMP event logging (DMP event)
   * Automated device discovery (OS event)
   * iSCSI topology discovery


Disable the eventsource daemon (vxesd) to prevent the license key from expiring.

# vxddladm stop eventsource

Disable vxesd across a reboot on "Solaris 8 & 9"

To prevent the vxesd daemon from starting on boot-up, comment-out the "vxddladm start eventsource" line from the /etc/rcS.d/S85vxvm-startup2

Disable vxesd across a reboot on "Solaris 10"

To prevent the vxesd damon from starting at boot-time, comment out the if statement surrounding the "vxddladm start eventsource" command in /etc/init.d/vxvm-startup2 file:

## Start Event Source Daemon, to enable dynamic device discovery
##Empty the lock file before starting the daemon
> /etc/vx/.vxesd.lock

if [ -x /usr/sbin/vxddladm ]
/usr/sbin/vxddladm start eventsource

Add a "#" to each of the above four lines of the startup script.

Symantec Support Evidence Collection

If the above workaround does not fix the issue, please collect the following content:

# ps -ef | grep vxconfigd
root 60 1 1 Mar 01 ? 4:45 vxconfigd -x syslog -m boot
root 18097 18064 0 12:41:43 pts/1 0:00 grep vxconfigd

In this instance the vxconfigd process id is "60".

# pfiles 60


Please run VRTSExplorer and upload the output to our FTP site. The entire updated Veritas toolset, including the latest VRTSExplorer can be download form here:

Solaris x64:

truss output

# truss -af -d -v open -t open -o /var/tmp/vxconfigd.out -p <vxconfigd PID>  

5.1 RP1

The fix is also included in Veritas Volume Manager 5.1 RP1.

Supplemental Materials


vxconfigd lose license information, vxesd leaking File descriptors

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices