search

BetterStackHQ / Hello_there

About Better Stack
9 stars 0 forks source link

Syslog flooded #1

Open Aqua1ung opened 1 year ago

Aqua1ung commented 1 year ago

[Apologies for posting this issue here, but I just couldn't find a proper board for my question.]

You guys seem to know a thing or two about Ubuntu logging, so here goes: my Kinetic syslog gets flooded with these error messages (see code excerpt below), one every two seconds, which renders the syslog pretty much unusable. As I've been told that these are harmless errors, my question is: how can I prevent these from flooding the syslog? I tried the loglevel=3 trick, but that didn't help.

Many thanks!

Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583569] 
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583570] 
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583570] Initialized Local Variables for Method [_TMP]:
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583570]   Local0: 0000000099fc2ba8 <Obj>           Integer 0000000000000038
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583574] 
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583575] No Arguments are initialized for method [_TMP]
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583575] 
Dec 19 23:43:09 DadsLGGram kernel: [ 1102.583576] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
Dec 19 23:43:13 DadsLGGram kernel: [ 1106.590603] ACPI Error: No handler for Region [XIN1] (0000000030431499) [UserDefinedRegion] (20220331/evregion-130)
Dec 19 23:43:13 DadsLGGram kernel: [ 1106.590612] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20220331/exfldio-261)
kms0219kms commented 8 months ago

Use hello[at]betterstack.com instead