When running "/opt/quest/bin/vastool status" the following messages are seen:
WARNING: 231 Unable to determine QAS daemon's connectivity state. Failed with error: 107.
WARNING: 231 Unable to determine QAS daemon's connectivity state. Failed with error: 76.
Output from ps or vastool daemon status vasd confirms that no vasd processes are running on the system.
With vasd debug 5 enabled, in the syslog for cause 1 you will see the following:
Also doing vastool join -f to rejoin fails.
Cause 1: Permissions on /var directory have been changed and vasd cannot stat up
Cause 2:Product Defect 26534 in earlier versions than 188.8.131.52 and 184.108.40.20685. This problem can be caused by systems going into disconnected mode due to a network or DC interruption. After entering this state a defect causes the vasd processes to segfault about 2 hours after the incident.
Output from linux lab:
2 - If incorect change the permissions:
chmod 755 /var/
3 - Start vasd daemon process
/opt/quest/bin/vastool daemon start vasd
4- Check the health of QAS:
STATUS FOR PRODUCT DEFECTS: Fixed
Please go to https://support.oneidentity.com/authentication-services/download-new-releases to download the latest software.