Your message dated Mon, 17 Nov 2014 18:18:35 +0100
with message-id <[email protected]>
and subject line Re: [Packaging] Bug#717287:
has caused the Debian Bug report #717287,
regarding munin-plugins-core: cpuspeed plugin doesn't work with kernel 3.10
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.)
--
717287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717287
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: munin-plugins-core
Version: 2.0.16-3
Severity: minor
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On the server side I noticed:
2013/07/18 23:38:46 [WARNING] Service cpuspeed on $host/$ip:4949 returned no
data for label cpu1
2013/07/18 23:38:46 [WARNING] Service cpuspeed on $host/$ip:4949 returned no
data for label cpu2
2013/07/18 23:38:46 [WARNING] Service cpuspeed on $host/$ip:4949 returned no
data for label cpu0
2013/07/18 23:38:46 [WARNING] Service cpuspeed on $host/$ip:4949 returned no
data for label cpu3
On $host I checked:
# MUNIN_LIBDIR=/usr/share/munin/ /etc/munin/plugins/cpuspeed
awk: fatal: cannot open file
`/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state' for reading (No such
file or directory)
awk: fatal: cannot open file
`/sys/devices/system/cpu/cpu1/cpufreq/stats/time_in_state' for reading (No such
file or directory)
awk: fatal: cannot open file
`/sys/devices/system/cpu/cpu2/cpufreq/stats/time_in_state' for reading (No such
file or directory)
awk: fatal: cannot open file
`/sys/devices/system/cpu/cpu3/cpufreq/stats/time_in_state' for reading (No such
file or directory)
# echo $?
2
and
# find /sys/devices/system/cpu/cpu0/cpufreq
/sys/devices/system/cpu/cpu0/cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
/sys/devices/system/cpu/cpu0/cpufreq/related_cpus
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
No idea where the stats directory went ...
Cheers,
gregor
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500,
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages munin-plugins-core depends on:
ii munin-common 2.0.16-3
ii perl 5.14.2-21
Versions of packages munin-plugins-core recommends:
ii libnet-snmp-perl 6.0.1-2
Versions of packages munin-plugins-core suggests:
pn conntrack <none>
pn libnet-netmask-perl <none>
pn libnet-telnet-perl <none>
ii libxml-parser-perl 2.41-1+b1
ii python 2.7.5-2
ii ruby 1:1.9.3
ii ruby1.8 [ruby-interpreter] 1.8.7.358-7.1
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-8.1+b1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJR6GIgAAoJELs6aAGGSaoGfA4P/1Fp+zF2ErXPQYLIlJLtQrmz
ZECn9wUVV3GlsPtgXJorwOWAfl5TZpKcQPyCZmva9HXZLcNNVp0LWTiehxODpsur
skj/0bMj264+U/Vlm8cCSL3mFkUMGMq/ddBL1na+BY/ah2uir1nY4JOZF/dsm+EE
t01j1EjhsUmHehHbOQztXKaQkWvngMPD669BAhJDVaIgOew7fp0iMpC7SX3x5QyW
X9qa2Bmc9fsy4SYxLcgWsmFHL3yhAXS1pSPwyI7HtGd2akrvBiEGStYtydMjW2CJ
IImGbPs03oWO7IK5/5XZNZIuQnIeEM8sLYilz5nrJsMzSSOPyoWUY8XhRjlPzlaw
tPtBbaVHw2P2LA28eWOpMHLLNWCD/S7p6ViZegx+UbsPLqv9tsyHH6I8p4NcNMhs
lrwrdT+OPxEUwh4gXMJFUgoOmiqMyr4xyVST9W0nChy9kSLd7GxN0THCpsJGCCFp
Wl3v6QrdZCbsV7VZqhKxugTNw5lOXS8amn95TSRWz4ZYXzVYB+veI55juRMzSrbL
hTmsBS+uF42NcNX4e0M+/y65Cf/AYQGv2QzeeKm6o4VdNCVY+bqZq2vNjh+ZHDwn
kpjSnWt5JjZXzSRg4yZmoPnpahKgoNpYSJsq3MFFKfMxw+kDWiAySJG58BWXKxhY
swBwe6ctgupWx/Vk6oIC
=JbLD
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Reiner Herrmann <[email protected]> writes:
> Package: munin-plugins-core
>
> With linux-image-3.16.0-4-amd64, which is currently the default kernel
> in jessie, the files
> /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state are available
> (again). (At least when cpufreq_stats is loaded, which was the case.)
>
> "munin-run cpuspeed" is also running without any error.
>
> So I think this bug can be closed?
It certainly sounds that way. Thank you for testing.
--
Stig Sandbeck Mathisen
signature.asc
Description: PGP signature
--- End Message ---
