Your message dated Fri, 02 Oct 2009 19:06:21 +0200
with message-id <4ac6330d.4080...@debian.org>
and subject line Re: Bug#518930: gmetad: Wrong filename/path creation for rrd
tool.
has caused the Debian Bug report #518930,
regarding gmetad: Wrong filename/path creation for rrd tool.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
518930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmetad
Version: 2.5.7-3.1etch1
Severity: grave
Justification: causes non-serious data loss
I have a gmetad setup collecting data from 5 cluster. Sometimes gmetad dies
with the following entry in /var/log/messages:
Mar 3 04:25:39 lamp /usr/sbin/gmetad[23507]: RRD_create: creating
'/var/li.rrd': Permission denied
Mar 7 11:16:45 lamp /usr/sbin/gmetad[9578]: RRD_create: creating
'/var/lib/ga.rrd': Permission denied
The gmetad's on the other clusters continue to work without any error. To me
it seems the path for the output rrd's is concatenated incorrectly. Gmetad
stores it's rrd in /var/lib/ganglia/...., so /var/lib/ga.rrd seem to me like
a concatenation if incomplete cluster names used for path creation.
Regards,
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages gmetad depends on:
ii adduser 3.102 Add and remove users and groups
ii libc6 2.3.6.ds1-13etch9+b1 GNU C Library: Shared libraries
ii librrd2 1.2.15-0.3 Time-series data storage and displ
gmetad recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Simon Kainz wrote:
> Luk Claes wrote:
>> Hi
>>
>> Does this also happen with version 3.1.2-2 (the one in unstable and
>> testing)?
> no, unstable is fine. But it seems to me this was a very rare CPU bug
> on my machine (apache webserver, medium load), as i couldn't make ssh
> backups (corrputed mac on input)
>
> i tracked this down to a faulty cpu after changing _every_ other
> replaceable port in my machine.
Ok, closing this bug.
Cheers
Luk
--- End Message ---
