Shut up a kernel error or avoid it by configuring Prometheus Node Exporter
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
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
.
ubuntu prometheus-exporter
add a comment |Â
up vote
0
down vote
favorite
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
.
ubuntu prometheus-exporter
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
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
.
ubuntu prometheus-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
.
ubuntu prometheus-exporter
ubuntu prometheus-exporter
asked 18 mins ago
0xC0000022L
7,2161364112
7,2161364112
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
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
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
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
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