CAUSE 1: System is busy
This warning can be seen from time to time and is expected to be transient and not persistent. The message indicates that vasd was 'busy' processing and unable to respond to the IPC ping.If the check is run while the process is doing something else it reports this warning.
If the message is persistent however then the process could locked or extremely busy.
WORKAROUND 1:
If you run /opt/quest/bin/vastool status again and it no longer reports this warning then it is safe to assume QAS is in a healthy state.
WORKAROUND 2:
In environments where large amounts of users and groups are enabled or system resources are low it can help to turn on workstation-mode:
1 - To set workstation mode you would do the following command on the client:
/opt/quest/bin/vastool configure vas vasd workstation-mode true
RESOLUTION:
1 - If the warning persists everytime /opt/quest/bin/vastool status is run, please restart vasd
Solaris - svcadm restart svc/vasd
Linux - /etc/init.d/vasd restart
HP - /sbin/init.d/vasd restart
AIX - /etc/rc.d/init.d/vasd
Mac OSX - sudo /bin/launchctl stop com.quest.vasd
2 - Monitor the system to see if the warning returns
/opt/quest/bin/vastool status
If the warning returns open up a Service Request with Support and include the snapshot data. To collect a snapshot please run the following script:
/opt/quest/libexec/vas/scripts/vas_snapshot.sh
This will create a tar.gz in /tmp that can be included with the Service Request.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center