Cron jobs stop running for all users after upgrading QAS. You may receive errors in the syslog similar to the ones shown below.
<service> : fatal: relocation error: file /opt/quest/lib/security/pam_vas3.so: symbol libvascache_check_pam_skip_local_users: referenced symbol not found
cron: fatal: relocation error: file /opt/quest/lib/security/pam_vas3.so: symbol libvascache_check_pam_skip_local_users: referenced symbol not found
/usr/sbin/cron: PAM unable to dlopen(/lib64/security/pam_vas3.so)
/usr/sbin/cron: PAM [error: /lib64/security/pam_vas3.so: undefined symbol: vascache_pm_get]
/usr/sbin/cron: PAM adding faulty module: /lib64/security/pam_vas3.so
/usr/sbin/cron: Module is unknown
This is caused by cron keeping one of the QAS libraries in memory during the upgrade.
Restart the crond daemon. This same issue can happen with sshd, dtlogin, svc.startd or any daemons that may have the pam_vas3 libraries open at the time of the upgrade. Restarting the service that is erroring will correct the problem.
Any service that could have an open library to QAS should be restarted. So if an application is compiled with PAM and using QAS for authentication, it shoud be restarted. The best way to ensure that no service are missed is to reboot the server on off hours after an upgrade