Idle vCops sessions

[dmoroney]

The vCops 5.0.x collector user is spawning connections and leaving the status "Idle for" forever in the vSphere client Sessions view. Why is vCops not cleaning up its connections that are no longer in use?

[SatyS]

Occasionally, vCenter Operations Standard creates new sessions to the vCenter Server without closing the old sessions it opened. This way, old sessions become idle or stale sessions that never time out or log out. This might cause performance issues in vCenter Server. When the per-user session limit is exceeded, vCenter Operations might stop working properly. The vCenter Server might deny service to the user that vCenter Operations uses to connect to vCenter Server. Workaround: Restart the vCenter Operations service to clear old sessions.

On the vCenter Operations Standard virtual appliance settings page, click the Appliance Administration tab.

Type the root user password above the Restart button and click Restart.

The Restart successful message appears when the restart operation completes.

-SatyS

[gradinka]

Also, which vcops version do you have?
I *think* there were some improvements in that area in 5.7.x version...