I've found that incorrect container's traffic is shown in Odin Business Automation Standard (OBAS). Traffic statistics shown in OBAS
- PVA Agent (VZAgent) version 4.6 or older is installed on the Virtuozzo node where the container resides.
Container's traffic is collected correctly by VZAgent 6.0 on the Virtuozzo node. OBAS shows overlapped net counters data because of frequent reconnections to nodes from the vzcoll service.
OBAS connects to the VZ nodes every 500 seconds (this value is hardcoded) in order to collect information. Under certain conditions - 1) slow ping from one of the nodes or 2) a large number of nodes - OBAS may re-connect to the VZ node before the previous cycle is finished, causing duplicate values to be recorded.
Traffic calculation date was changed. Every time a Subscription is upgraded to the Latest Version of the Same Hosting Plan, OBAS starts to calculate resources usage from the upgrade date. That is done because in the latest Hosting Plan version fees and rules for traffic calculation can be different from those in the older version.
Such behavior is not described clearly in OBAS documentation. Documentation request PBAS-30075 was submitted to the OBAS Maintenance Team.
Upgrade VZAgent to version 6.0 or higher.
Increase the "RECONNECT_PERIOD" parameter to a value more than 500 (seconds) in
/etc/hspc/vzcoll.confon the OBAS node (the default value is 60). For example, to set the limit to 560 seconds (9 minutes):
[root@obas ~]# grep RECONNECT_PERIOD /etc/hspc/vzcoll.conf RECONNECT_PERIOD = 560 [root@obas ~]#
Remember to restart the vzcoll service to apply the changes:
[root@obas ~]# /etc/init.d/vzcoll restart
Additional: We recommend that you upgrade OBAS to the latest available version.