Article ID: 123851, created on Dec 9, 2014, last review on Dec 9, 2014

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux 4.7
  • Virtuozzo hypervisor
  • Virtual Automation 6.0

Symptom

Even though container was in stopped state, PVA shows traffic statistics for container.

Cause

In PVA Agent cached data was not removed automatically.

The issue will be fixed permanently in scope of PVA-34101

Resolution

There are two workarounds available

1. Remove perfdata cache of PVA Agent for the container on the virtualization node:

  • Check the EID of container in question, e.g:

    ~# cat /vz/private/CT_ID/.vza/eid.conf
    e962770e-a9e7-8f4e-a69b-28ee73bea65b
    

    replace CT_ID with actual ID

  • Remove the cached data from /var/opt/pva/agent/tmp/perfdata/$EID, e.g.:

    ~# rm /var/opt/pva/agent/tmp/perfdata/e962770e-a9e7-8f4e-a69b-28ee73bea65b
    

2. Restart PVA Agent:

    ~# pvaagent restart

Search Words

traffic statistics

CT

PVA-34101

traffic

stopped

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 319940068c5fa20655215d590b7be29b 0dd5b9380c7d4884d77587f3eb0fa8ef 0c05f0c76fec3dd785e9feafce1099a9 0889ab60fa6494de107aa7338c3c38b6 c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF