Return
-
Title
Post install or upgrade of Safeguard Authentication Services (SAS) version 5.1.0.15600 the vasd daemon is disabled on Red Hat 7 and 8 and variants.. -
Description
With version 5.1.0.15600 on Redhat versions 7 & 8 and variants including Alma, CentOS, OEL, RHEL, Rocky, Fedora, and SLES 12 & 15 systems, when upgrading, or newly installing and joining to a domain, the vasd process is left running but the vasd.service is marked disabled. If the system is then rebooted, without explicitly enabling the vasd.service, the service is not automatically restarted on system startup.
This can be seen by running: systemctl status vasd.
vasd.service - Safeguard Authentication Services
Loaded: loaded (/usr/lib/systemd/system/vasd.service; disabled; vendor preset: disabled)
Active: active (running)
Note that the "vendor preset: disabled" is expected.
The "vasd.service; disabled" should be enabled by default however it is not.
-
Cause
Product defect: 368125 -
Resolution
Product defect ID 368125 has been raised to fix this issue in a future version (5.1.1) with the highest priority set.
Workaround:
Enable the vasd.service daemon with the following command.
systemctl enable vasd
The systemctl status vasd output should look like this:
vasd.service - Safeguard Authentication Services
Loaded: loaded (/usr/lib/systemd/system/vasd.service; enabled; vendor preset: disabled)
Active: active (running)
Note that the "vendor preset: disabled" is expected.
Once enabled the vasd daemon will start as expected on future system starts. -
Change Request
368125