Users cannot authenticate. This could be due to database locking. To check if database locking is occurring:
/opt/quest/libexec/vas/sqlite3 /var/opt/quest/vas/vasd/vas_ident.vdb "SELECT * FROM domain_sids"
SQL error: "database is locked"
When an application makes getgrent() or getpwent() calls, it will create a temporary lock on the cache files vasd owns. This normally does not cause any problems, as the locks are released quickly when the application calls endgrent() or endpwent(). However, some applications do not always call the endXXent() functions, which creates an undesired effect of keeping the lock for the life of the application
Set the getent-use-memory-cache setting to true in the /etc/opt/quest/vas/vas.conf file. You can do this by running the following command:
/opt/quest/bin/vastool configure vas nss_vas getent-use-memory-cache true
To investigate what application is causing the lock. Please gather the following information and Contact Support
1) fuser /var/opt/quest/vas/vasd/* 2>&1 | tee /tmp/fuser
2) stop vasd (using the init script)
3) /opt/quest/sbin/vasd -d1 -g5 -x u 2>&1 | tee /tmp/vasd_debug
To clear the database lock please refer to Knowledge Article 27393