Shut up a kernel error or avoid it by configuring Prometheus Node Exporter
Let me start by giving the output which I get to see in /var/log/syslog and with dmesg:
[559151.898586] ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170831/exfield-427)
[559151.911578] No Local Variables are initialized for Method [_PMM]
[559151.911580] No Arguments are initialized for method [_PMM]
[559151.911584] ACPI Error: Method parse/execution failed _SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170831/psparse-550)
[559151.916648] ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170831/power_meter-338)
Clearly the Prometheus Node Exporter is triggering the error, although it doesn't seem to be the cause for the error that gets logged.
Now what I want to achieve is - preferably - to tell the Prometheus Node Exporter to stop querying for whatever information it's attempting to query. Failing that, I'd like to silence these messages so they don't spam my log files.
How would I go about either of these options? ... or perhaps there are other options I haven't considered ...
This is happening on Ubuntu 18.04 with the packaged prometheus-node-exporter (it also happened with the 0.16 and 0.17 versions of prometheus-node-exporter which could be installed via stretch-backports - yes, on Ubuntu).
ubuntu prometheus-exporter
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
add a comment |
Let me start by giving the output which I get to see in /var/log/syslog and with dmesg:
[559151.898586] ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170831/exfield-427)
[559151.911578] No Local Variables are initialized for Method [_PMM]
[559151.911580] No Arguments are initialized for method [_PMM]
[559151.911584] ACPI Error: Method parse/execution failed _SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170831/psparse-550)
[559151.916648] ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170831/power_meter-338)
Clearly the Prometheus Node Exporter is triggering the error, although it doesn't seem to be the cause for the error that gets logged.
Now what I want to achieve is - preferably - to tell the Prometheus Node Exporter to stop querying for whatever information it's attempting to query. Failing that, I'd like to silence these messages so they don't spam my log files.
How would I go about either of these options? ... or perhaps there are other options I haven't considered ...
This is happening on Ubuntu 18.04 with the packaged prometheus-node-exporter (it also happened with the 0.16 and 0.17 versions of prometheus-node-exporter which could be installed via stretch-backports - yes, on Ubuntu).
ubuntu prometheus-exporter
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
add a comment |
Let me start by giving the output which I get to see in /var/log/syslog and with dmesg:
[559151.898586] ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170831/exfield-427)
[559151.911578] No Local Variables are initialized for Method [_PMM]
[559151.911580] No Arguments are initialized for method [_PMM]
[559151.911584] ACPI Error: Method parse/execution failed _SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170831/psparse-550)
[559151.916648] ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170831/power_meter-338)
Clearly the Prometheus Node Exporter is triggering the error, although it doesn't seem to be the cause for the error that gets logged.
Now what I want to achieve is - preferably - to tell the Prometheus Node Exporter to stop querying for whatever information it's attempting to query. Failing that, I'd like to silence these messages so they don't spam my log files.
How would I go about either of these options? ... or perhaps there are other options I haven't considered ...
This is happening on Ubuntu 18.04 with the packaged prometheus-node-exporter (it also happened with the 0.16 and 0.17 versions of prometheus-node-exporter which could be installed via stretch-backports - yes, on Ubuntu).
ubuntu prometheus-exporter
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
Let me start by giving the output which I get to see in /var/log/syslog and with dmesg:
[559151.898586] ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170831/exfield-427)
[559151.911578] No Local Variables are initialized for Method [_PMM]
[559151.911580] No Arguments are initialized for method [_PMM]
[559151.911584] ACPI Error: Method parse/execution failed _SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170831/psparse-550)
[559151.916648] ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170831/power_meter-338)
Clearly the Prometheus Node Exporter is triggering the error, although it doesn't seem to be the cause for the error that gets logged.
Now what I want to achieve is - preferably - to tell the Prometheus Node Exporter to stop querying for whatever information it's attempting to query. Failing that, I'd like to silence these messages so they don't spam my log files.
How would I go about either of these options? ... or perhaps there are other options I haven't considered ...
This is happening on Ubuntu 18.04 with the packaged prometheus-node-exporter (it also happened with the 0.16 and 0.17 versions of prometheus-node-exporter which could be installed via stretch-backports - yes, on Ubuntu).
ubuntu prometheus-exporter
ubuntu prometheus-exporter
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
edited Jan 23 at 19:42
0xC0000022L
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
asked Nov 8 '18 at 21:13
0xC0000022L0xC0000022L
7,4661564118
7,4661564118
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I had these [_PMM] type log messages in a new openvz container (so the messages were outside of my control).
With rsyslog you can create a property filter in /etc/rsyslog.d/discard.conf (files in this directory are sourced before all other configuration is applied):
:msg, contains, "[_PMM]" ~
For a syslog without filters (e.g inetutils-syslogd) - a simple fix is to create /etc/cron.hourly/pmmlog & make it executable:
#!/bin/sh
# remove annoying logs
# Nov 29 12:55:29 vzbackup vmunix: [161167.516267] No Arguments are initialized for method [_PMM]
# Nov 29 12:56:29 vzbackup vmunix: [161227.527169] No Local Variables are initialized for Method [_PMM]
sed -i '/.*[_PMM]/d' /var/log/messages
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
At the very least on my Ubuntu machine I cannot find any cron job containingpmmor named this way ... also no other files in/var/spooland/etccontaining that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.
– 0xC0000022L
Nov 29 '18 at 16:32
you could also runcrontab -easroot& just add thesedline above to therootcrontab - or you create the cron file as shown above.
– Stuart Cardall
Nov 29 '18 at 17:15
add a comment |
Apparently the best method is to blacklist the kernel module named acpi_power_meter by adding a line as follows into /etc/modprobe.d/blacklist.conf (or a newly created file in that same folder):
blacklist acpi_power_meter
On a running system one should also run rmmod acpi_power_meter as super user in order to unload the module. I already tested it and this works perfectly fine on all the HP servers I am taking care of. Cause of the error is allegedly a BIOS defect on said HP hardware.
This seems the only viable method and I found it via this comment on the Prometheus node_exporter project.
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f480643%2fshut-up-a-kernel-error-or-avoid-it-by-configuring-prometheus-node-exporter%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had these [_PMM] type log messages in a new openvz container (so the messages were outside of my control).
With rsyslog you can create a property filter in /etc/rsyslog.d/discard.conf (files in this directory are sourced before all other configuration is applied):
:msg, contains, "[_PMM]" ~
For a syslog without filters (e.g inetutils-syslogd) - a simple fix is to create /etc/cron.hourly/pmmlog & make it executable:
#!/bin/sh
# remove annoying logs
# Nov 29 12:55:29 vzbackup vmunix: [161167.516267] No Arguments are initialized for method [_PMM]
# Nov 29 12:56:29 vzbackup vmunix: [161227.527169] No Local Variables are initialized for Method [_PMM]
sed -i '/.*[_PMM]/d' /var/log/messages
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
At the very least on my Ubuntu machine I cannot find any cron job containingpmmor named this way ... also no other files in/var/spooland/etccontaining that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.
– 0xC0000022L
Nov 29 '18 at 16:32
you could also runcrontab -easroot& just add thesedline above to therootcrontab - or you create the cron file as shown above.
– Stuart Cardall
Nov 29 '18 at 17:15
add a comment |
I had these [_PMM] type log messages in a new openvz container (so the messages were outside of my control).
With rsyslog you can create a property filter in /etc/rsyslog.d/discard.conf (files in this directory are sourced before all other configuration is applied):
:msg, contains, "[_PMM]" ~
For a syslog without filters (e.g inetutils-syslogd) - a simple fix is to create /etc/cron.hourly/pmmlog & make it executable:
#!/bin/sh
# remove annoying logs
# Nov 29 12:55:29 vzbackup vmunix: [161167.516267] No Arguments are initialized for method [_PMM]
# Nov 29 12:56:29 vzbackup vmunix: [161227.527169] No Local Variables are initialized for Method [_PMM]
sed -i '/.*[_PMM]/d' /var/log/messages
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
At the very least on my Ubuntu machine I cannot find any cron job containingpmmor named this way ... also no other files in/var/spooland/etccontaining that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.
– 0xC0000022L
Nov 29 '18 at 16:32
you could also runcrontab -easroot& just add thesedline above to therootcrontab - or you create the cron file as shown above.
– Stuart Cardall
Nov 29 '18 at 17:15
add a comment |
I had these [_PMM] type log messages in a new openvz container (so the messages were outside of my control).
With rsyslog you can create a property filter in /etc/rsyslog.d/discard.conf (files in this directory are sourced before all other configuration is applied):
:msg, contains, "[_PMM]" ~
For a syslog without filters (e.g inetutils-syslogd) - a simple fix is to create /etc/cron.hourly/pmmlog & make it executable:
#!/bin/sh
# remove annoying logs
# Nov 29 12:55:29 vzbackup vmunix: [161167.516267] No Arguments are initialized for method [_PMM]
# Nov 29 12:56:29 vzbackup vmunix: [161227.527169] No Local Variables are initialized for Method [_PMM]
sed -i '/.*[_PMM]/d' /var/log/messages
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
I had these [_PMM] type log messages in a new openvz container (so the messages were outside of my control).
With rsyslog you can create a property filter in /etc/rsyslog.d/discard.conf (files in this directory are sourced before all other configuration is applied):
:msg, contains, "[_PMM]" ~
For a syslog without filters (e.g inetutils-syslogd) - a simple fix is to create /etc/cron.hourly/pmmlog & make it executable:
#!/bin/sh
# remove annoying logs
# Nov 29 12:55:29 vzbackup vmunix: [161167.516267] No Arguments are initialized for method [_PMM]
# Nov 29 12:56:29 vzbackup vmunix: [161227.527169] No Local Variables are initialized for Method [_PMM]
sed -i '/.*[_PMM]/d' /var/log/messages
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
edited Dec 1 '18 at 19:34
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
answered Nov 29 '18 at 13:15
Stuart CardallStuart Cardall
861610
861610
At the very least on my Ubuntu machine I cannot find any cron job containingpmmor named this way ... also no other files in/var/spooland/etccontaining that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.
– 0xC0000022L
Nov 29 '18 at 16:32
you could also runcrontab -easroot& just add thesedline above to therootcrontab - or you create the cron file as shown above.
– Stuart Cardall
Nov 29 '18 at 17:15
add a comment |
At the very least on my Ubuntu machine I cannot find any cron job containingpmmor named this way ... also no other files in/var/spooland/etccontaining that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.
– 0xC0000022L
Nov 29 '18 at 16:32
you could also runcrontab -easroot& just add thesedline above to therootcrontab - or you create the cron file as shown above.
– Stuart Cardall
Nov 29 '18 at 17:15
At the very least on my Ubuntu machine I cannot find any cron job containing
pmm or named this way ... also no other files in /var/spool and /etc containing that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.– 0xC0000022L
Nov 29 '18 at 16:32
At the very least on my Ubuntu machine I cannot find any cron job containing
pmm or named this way ... also no other files in /var/spool and /etc containing that string. So apparently that is not the solution to my problem. Still, thank you for taking the time to answer. Perhaps it helps someone else.– 0xC0000022L
Nov 29 '18 at 16:32
you could also run
crontab -e as root & just add the sed line above to the root crontab - or you create the cron file as shown above.– Stuart Cardall
Nov 29 '18 at 17:15
you could also run
crontab -e as root & just add the sed line above to the root crontab - or you create the cron file as shown above.– Stuart Cardall
Nov 29 '18 at 17:15
add a comment |
Apparently the best method is to blacklist the kernel module named acpi_power_meter by adding a line as follows into /etc/modprobe.d/blacklist.conf (or a newly created file in that same folder):
blacklist acpi_power_meter
On a running system one should also run rmmod acpi_power_meter as super user in order to unload the module. I already tested it and this works perfectly fine on all the HP servers I am taking care of. Cause of the error is allegedly a BIOS defect on said HP hardware.
This seems the only viable method and I found it via this comment on the Prometheus node_exporter project.
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
add a comment |
Apparently the best method is to blacklist the kernel module named acpi_power_meter by adding a line as follows into /etc/modprobe.d/blacklist.conf (or a newly created file in that same folder):
blacklist acpi_power_meter
On a running system one should also run rmmod acpi_power_meter as super user in order to unload the module. I already tested it and this works perfectly fine on all the HP servers I am taking care of. Cause of the error is allegedly a BIOS defect on said HP hardware.
This seems the only viable method and I found it via this comment on the Prometheus node_exporter project.
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
add a comment |
Apparently the best method is to blacklist the kernel module named acpi_power_meter by adding a line as follows into /etc/modprobe.d/blacklist.conf (or a newly created file in that same folder):
blacklist acpi_power_meter
On a running system one should also run rmmod acpi_power_meter as super user in order to unload the module. I already tested it and this works perfectly fine on all the HP servers I am taking care of. Cause of the error is allegedly a BIOS defect on said HP hardware.
This seems the only viable method and I found it via this comment on the Prometheus node_exporter project.
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
Apparently the best method is to blacklist the kernel module named acpi_power_meter by adding a line as follows into /etc/modprobe.d/blacklist.conf (or a newly created file in that same folder):
blacklist acpi_power_meter
On a running system one should also run rmmod acpi_power_meter as super user in order to unload the module. I already tested it and this works perfectly fine on all the HP servers I am taking care of. Cause of the error is allegedly a BIOS defect on said HP hardware.
This seems the only viable method and I found it via this comment on the Prometheus node_exporter project.
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
edited Jan 23 at 19:52
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
answered Jan 23 at 19:40
0xC0000022L0xC0000022L
7,4661564118
7,4661564118
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f480643%2fshut-up-a-kernel-error-or-avoid-it-by-configuring-prometheus-node-exporter%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
