Return
-
Title
The vasproxy startup has a delay before it is listening, which may break services that attempt to use it within the first few moments. -
Description
Vasproxy may refuse connections immediately after the init script completes. The expected behavior would be that the vasproxyd service is ready to accept connections immediately after the init script completes. -
Cause
With systemd, the vasproxyd service startup may complete before the child listener process(es) are listening. This may causes issues during system startup as services that start immediately after vasproxyd may fail as the service is not yet listening. -
Resolution
WORKAROUND: None.
STATUS: Defect ID # 271082 has been created to address this issue; the corrective action in this instance will have the vasproxyd processes wait (up to 10 seconds) until the child process(es) are fully listening on the configured port before continuing.
-
Change Request
271082