[Users] Excessive syslog logging from vdsm/sampling.py

[Sander Grendelman]

Any ideas on this one?

On Mon, Dec 16, 2013 at 11:31 AM, Sander Grendelman
<sander at grendelman.com> wrote:
> The syslog on my ovirt nodes is constantly logging errors from sampling.py:
>
> Dec 16 11:22:47 gnkvm01 vdsm vm.Vm ERROR
> vmId=`66aa5555-2299-4d93-931d-b7a2e421b7e9`::Stats function failed:
> <AdvancedStatsFunction _highWrite at 0x1733dc0>#012Traceback (most
> recent call last):#012  File "/usr/share/vdsm/sampling.py", line 351,
> in collect#012    statsFunction()#012  File
> "/usr/share/vdsm/sampling.py", line 226, in __call__#012    retValue =
> self._function(*args, **kwargs)#012  File "/usr/share/vdsm/vm.py",
> line 509, in _highWrite#012    if not vmDrive.blockDev or
> vmDrive.format != 'cow':#012AttributeError: 'Drive' object has no
> attribute 'format'
> Dec 16 11:22:47 gnkvm01 vdsm vm.Vm ERROR
> vmId=`22654002-cbef-454d-b001-7823da5f592f`::Stats function failed:
> <AdvancedStatsFunction _highWrite at 0x1733dc0>#012Traceback (most
> recent call last):#012  File "/usr/share/vdsm/sampling.py", line 351,
> in collect#012    statsFunction()#012  File
> "/usr/share/vdsm/sampling.py", line 226, in __call__#012    retValue =
> self._function(*args, **kwargs)#012  File "/usr/share/vdsm/vm.py",
> line 509, in _highWrite#012    if not vmDrive.blockDev or
> vmDrive.format != 'cow':#012AttributeError: 'Drive' object has no
> attribute 'format'
> Dec 16 11:22:48 gnkvm01 vdsm vm.Vm ERROR
> vmId=`d3dae626-279b-4bcf-afc4-7a3c198a3035`::Stats function failed:
> <AdvancedStatsFunction _highWrite at 0x1733dc0>#012Traceback (most
> recent call last):#012  File "/usr/share/vdsm/sampling.py", line 351,
> in collect#012    statsFunction()#012  File
> "/usr/share/vdsm/sampling.py", line 226, in __call__#012    retValue =
> self._function(*args, **kwargs)#012  File "/usr/share/vdsm/vm.py",
> line 513, in _highWrite#012    self._vm._dom.blockInfo(vmDrive.path,
> 0)#012  File "/usr/share/vdsm/vm.py", line 835, in f#012    ret =
> attr(*args, **kwargs)#012  File
> "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line
> 76, in wrapper#012    ret = f(*args, **kwargs)#012  File
> "/usr/lib64/python2.6/site-packages/libvirt.py", line 1797, in
> blockInfo#012    if ret is None: raise libvirtError
> ('virDomainGetBlockInfo() failed', dom=self)#012libvirtError: invalid
> argument: invalid path
> /rhev/data-center/mnt/blockSD/b526b148-b810-47c6-9bdd-4fd8d8226855/images/347f2238-c018-4370-94df-bd1e81f8b854/9e5dad95-73ea-4e5c-aa13-522efd9bad11
> not assigned to domain
> Dec 16 11:22:48 gnkvm01 vdsm vm.Vm ERROR
> vmId=`c6f56584-1ccd-4c02-be94-897a4e747d34`::Stats function failed:
> <AdvancedStatsFunction _highWrite at 0x1733dc0>#012Traceback (most
> recent call last):#012  File "/usr/share/vdsm/sampling.py", line 351,
> in collect#012    statsFunction()#012  File
> "/usr/share/vdsm/sampling.py", line 226, in __call__#012    retValue =
> self._function(*args, **kwargs)#012  File "/usr/share/vdsm/vm.py",
> line 509, in _highWrite#012    if not vmDrive.blockDev or
> vmDrive.format != 'cow':#012AttributeError: 'Drive' object has no
> attribute 'format'
> Dec 16 11:22:48 gnkvm01 vdsm vm.Vm ERROR
> vmId=`0ae3a3d7-ead9-4c0d-9df0-3901b6e6859c`::Stats function failed:
> <AdvancedStatsFunction _highWrite at 0x1733dc0>#012Traceback (most
> recent call last):#012  File "/usr/share/vdsm/sampling.py", line 351,
> in collect#012    statsFunction()#012  File
> "/usr/share/vdsm/sampling.py", line 226, in __call__#012    retValue =
> self._function(*args, **kwargs)#012  File "/usr/share/vdsm/vm.py",
> line 509, in _highWrite#012    if not vmDrive.blockDev or
> vmDrive.format != 'cow':#012AttributeError: 'Drive' object has no
> attribute 'format'
>
> These messages might have something to do with reading
> information/statistics through the API.
> But I've stopped all my (monitoring) processes using the API.
>
> Restarting ovirt-engine and vdsm did not resolve the issue.
>
> Both nodes and engine server are running oVirt 3.3.1 on CentOS 6.4
>
> This may be a red herring but the values  of disk statistics read
> through the API are "static"/unchanging.
>
> Any clues on whether these messages are serious and any ideas on how
> to stop them
> spamming my system logs?