[Xen-devel] xen-ringwatch issues

[moftah moftah <mofta7y@xxxxxxxxx>]

Hi All,

We are using Xenserver 6.2 with latest patches installed and we just enabled email sending on the pool (the pool has been running for long time with no major issues)

now 3 hosts out of 4 hosts in the pool are flooding us with xen-ringwatch exceptions

like this

Traceback (most recent call last):
 File "/usr/sbin/xen-ringwatch", line 593, in ?
  watches.update()
 File "/usr/sbin/xen-ringwatch", line 414, in update
  entry = RingWatch.new(ring)
 File "/usr/sbin/xen-ringwatch", line 357, in new
  state = ring.read()
 File "/usr/sbin/xen-ringwatch", line 136, in read
  state = RingState.from_sysfs(self.path())
 File "/usr/sbin/xen-ringwatch", line 223, in from_sysfs
  req = cls.Req.from_sysfs(_req, size=nr_ents)
 File "/usr/sbin/xen-ringwatch", line 240, in from_sysfs
  raise Exception, "Malformed %s input: %s" % \
NameError: global name 's' is not defined

so after searching around we changed the file xen-ringwatch in order to see the real issue

the changes are

--- /usr/sbin/xen-ringwatch     2013-07-22 13:52:19.000000000 +0200
+++ /usr/sbin/xen-ringwatch     2013-07-22 13:52:30.000000000 +0200
@@ -238,7 +238,7 @@
             match = cls._pattern.search(line)
             if not match:
                 raise Exception, "Malformed %s input: %s" % \
-                    (cls.__name__, repr(s))
+                    (cls.__name__, repr(line))
 
             i = iter(match.groups())
             for k in i:

now the issue we see is like this

Exception: Malformed Req input: 'req prod 3412900880 cons -882066416 event 3412900881'
Exception: Malformed Req input: 'req prod 3412902034 cons -882065262 event 3412902035''
and it is flooding us with this for every host every 2 minutes
and in each email the numbers changes


I have been trying to read the original article where this script was introduced here
http://comments.gmane.org/gmane.comp.emulators.xen.devel/106601

but i am not sure whats wrong with the script
and why we have negative number here

if any one can help in fixing the script or at least inform us if it is still in use as it seems it was done for specific version of the kernel

Any help will be appreciated

Thanks

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel