All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: vishalfaldu <vishal@servarica.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen-ringwatch generating many alerts
Date: Thu, 8 Jan 2015 10:25:04 +0000	[thread overview]
Message-ID: <1420712704.19787.1.camel@citrix.com> (raw)
In-Reply-To: <1420696474396-5725675.post@n5.nabble.com>

On Wed, 2015-01-07 at 22:54 -0700, vishalfaldu wrote:
> Hi ,
> 
> We have xen-ringwatch which is sending below alert frequently, Any one can
> help ?
> 
> Subject: Cron <root@DOM0> xen-ringwatch check -T3 --kick | logger -p
> daemon.crit -t RINGWATCH-ALERT
> To: root
> 
> 
> 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

It seems like there is a bug in the  error handling at line 240, repr(s)
ought to be repr(line), I think. If you fix that (and please do send a
patch if you do, see [0]) then I expect you'll get a more useful error
message.

Ian.

[0] http://wiki.xen.org/wiki/Submitting_Xen_Patches

      reply	other threads:[~2015-01-08 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  5:54 Xen-ringwatch generating many alerts vishalfaldu
2015-01-08 10:25 ` Ian Campbell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1420712704.19787.1.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=vishal@servarica.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.