Solaris BESClient fails to start

I have a group of Solaris 10 servers that I patch with BigFix monthly. The problem I’m having is the BESClient randomly fails to start after a reboot. svcs shows BESClient is in maintenance mode and and svcadm clear brings it right up with no problem. Checking the logs it appears that some filesystem is not available when BESClient is trying to start.

So, is there a way to delay this agent startup by 5 or 10 minutes under SMF? I’m assuming I’m not the only one seeing this.

In besclient.xml file I see a dependency on svc:/service/filesystem/minimal and I wonder if that can be changed to something that will assure all the filesystems are mounted before it tries to start BESClient. I’ve been having trouble finding info on what values are available for this dependency and I was hoping someone here might know.

What version of the client do you have? There were some improvements made for specific environmental differences that can cause this

The client version is 9.2.6.94
I don’t see any newer versions relevant.

The 9.2.5 release changed the SMF file to include an autofs system optional requirement so you should have that as well.

Are the volumes in use by the agent not the normal set? (/opt, /var, /etc)