-
Title
vasd(Temporary IPC) (PID ) exiting seen in the syslog messages -
Description
vasd(Temporary IPC) (PID ) exiting seen in the syslog messages -
Resolution
The vasd(Temporary IPC) (PID ) exiting is normal behaviour to see in the logs and can be safely ignored.
The older 3.x and 4.0 worked very differently than the 4.1.x or 4.2 version of the product. In the past, version 3.5 days, semaphores were used in the NSS module to handle threaded requests, but that is no longer the case. IPC is a legacy name for them, they don’t actually use anything from ipcs. Authentication Services internally uses a UNIX domain socket for communication. QAS has also changed the amount of processes in the version 4.1.x and up. There are a minimum of 6 and a maximum of 9 vasd processes. The processes are the Parent, a Dispatcher, a DB Handler, an auth handler, two permanent LDAP Handlers and up to three temporary LDAP Handlers as needed which will start and stop.
We keep two Perm IPC processes going all the time, but if both are busy we will spin up a Temp IPC process to handle any potential additional load. There is a little bit of work to start one up, so we want it ready for quick response if more requests come in before everything else is done. Then if they haven't been used in 2 minutes, we shut them down to release their resources. So something as simple as a cron job from a QAS user, or a log, might kick it off if it also happens during normal vasd parent process housekeeping. I've seen some setups that will trigger it without any user's logging in at all. We parallelize a few of our updates, and depending on the size could trigger it by itself.To see the process you can use the command: /opt/quest/bin/vastool info processes.