-
Title
When running custom script getting errors from vastool commands -
Description
When running custom script getting errors from vastool commands
-
Cause
The script was stopping and starting vasd after the join and then immediately doing a vastool flush. VASD was not fully started when the flush was done and causing the error.
In QAS 4.X behavior, it is NOT acceptable to restart vasd via script unless absolutly needed.
-
Resolution
RESOULTION 1:
1 - Edit the custom script and remove
VASD stop and start lines and any vastool flush commands
RESOLUTION 2:
1 - Put sleep 60 seconds after the vasd restart or vasd start lines
RESOLUTION 3:
1 - If it is a join script, it is better to provide join option such as -u and -g on the join line rather than doing a vastool flush after setting the settings in the vas.conf. Please see the command output of /opt/quest/bin/vastool join -h for information on the join options that can be set.