Your message dated Tue, 30 Dec 2008 10:32:30 +0100
with message-id <[email protected]>
and subject line Re: gkrellmd: Unable to monitor a server correctly if it has
16Gb of RAM
has caused the Debian Bug report #475408,
regarding gkrellmd: Unable to monitor a server correctly if it has 16Gb of RAM
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 [email protected]
immediately.)
--
475408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475408
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gkrellmd
Version: 2.3.1-1
Severity: important
I've recently upgraded the RAM of a couple of servers from 8 to 16Gb of RAM and
I'm unable to use gkrellm any more on them.
Gkrellms flashes and gives some info maybe once every 10 seconds, rendering it
completely useless.
Of course the OS on the server is 64bit.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'stable'), (50, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.21-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages gkrellmd depends on:
ii adduser 3.107 add and remove users and groups
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libglib2.0-0 2.16.1-2 The GLib library of C routines
gkrellmd recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.3.2-2
Hello Alessandro,
On Tue, Dec 30, 2008 at 09:11, Alessandro Polverini <[email protected]> wrote:
> Hello Sandro, and thank for your inquiry.
> Latest version of gkrellmd seems ok
Given that this bug is solved, I'm closing this report.
> but now the problem is that the process
> uses around 60/70% of cpu, being by far the most cpu intensive task on the
> server.
Could you please file another report with the debug and log options
enabled? if you could run a strace might be helpful.
Regards,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
