Receiving err 22 and vastool status report WARNING: 707 vasd did not respond to an IPC ping (4295991)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Receiving err 22 and vastool status report WARNING: 707 vasd did not respond to an IPC ping
Description

Authentication slows and then eventually login begins to fail. Systems are regularly reporting /opt/quest/bin/vastool status WARNING: 707 vasd did not respond to an IPC ping, could be busy
Cause

Product Defect 327931
* vasd: Fix situation where vasd fails to start up properly ( IPC ping fails )
if it starts while the system is very busy making it miss some child messages.

Fixed in 4.0.3.227 and up
Resolution

STATUS:

Fixed in QAS 4.0.3 Maintenance Release

WORKAROUND:

Restart vasd

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title