LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 10-11-2019, 11:06 AM   #1
ddenial
Member
 
Registered: Dec 2016
Distribution: CentOS, Fedora, Ubuntu
Posts: 359

Rep: Reputation: 56
Getting kernel error every second. Please help


Hello

OS: Fedora 30 Gnome

I'm getting this error every second. "Oops! We're sorry, it looks like a problem occurred. If you'd like to help..."

Code:
# journalctl -f
Oct 11 21:25:50 svr.itcore.in abrt-notification[9071]: System encountered a non-fatal error in ??()
Oct 11 21:25:50 svr.itcore.in abrt-dump-journal-oops[1546]: abrt-dump-journal-oops: Found oopses: 5
Oct 11 21:25:50 svr.itcore.in abrt-dump-journal-oops[1546]: abrt-dump-journal-oops: Creating problem directories
Oct 11 21:25:50 svr.itcore.in abrt-server[9073]: Deleting problem directory oops-2019-10-11-21:25:50-1546-0 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:25:50 svr.itcore.in abrt-notification[9080]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:25:51 svr.itcore.in abrt-server[9084]: Deleting problem directory oops-2019-10-11-21:25:50-1546-1 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:25:51 svr.itcore.in abrt-notification[9092]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:25:52 svr.itcore.in abrt-server[9095]: Can't find a meaningful backtrace for hashing in '.'
Oct 11 21:25:52 svr.itcore.in abrt-server[9095]: Option 'DropNotReportableOopses' is not configured
Oct 11 21:25:52 svr.itcore.in abrt-server[9095]: Preserving oops '.' because DropNotReportableOopses is 'no'
Oct 11 21:25:53 svr.itcore.in abrt-notification[9112]: System encountered a non-fatal error in ??()
Oct 11 21:25:53 svr.itcore.in abrt-server[9114]: Deleting problem directory oops-2019-10-11-21:25:50-1546-3 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:25:53 svr.itcore.in abrt-notification[9121]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:25:54 svr.itcore.in abrt-dump-journal-oops[1546]: Reported 5 kernel oopses to Abrt
Oct 11 21:25:54 svr.itcore.in abrt-server[9123]: Can't find a meaningful backtrace for hashing in '.'
Oct 11 21:25:54 svr.itcore.in abrt-server[9123]: Option 'DropNotReportableOopses' is not configured
Oct 11 21:25:54 svr.itcore.in abrt-server[9123]: Preserving oops '.' because DropNotReportableOopses is 'no'
Oct 11 21:25:55 svr.itcore.in abrt-notification[9140]: System encountered a non-fatal error in ??()
Oct 11 21:25:55 svr.itcore.in abrt-dump-journal-oops[1546]: abrt-dump-journal-oops: Found oopses: 5
Oct 11 21:25:55 svr.itcore.in abrt-dump-journal-oops[1546]: abrt-dump-journal-oops: Creating problem directories
Oct 11 21:25:55 svr.itcore.in abrt-server[9142]: Deleting problem directory oops-2019-10-11-21:25:55-1546-0 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:25:55 svr.itcore.in abrt-notification[9149]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:25:56 svr.itcore.in abrt-server[9152]: Deleting problem directory oops-2019-10-11-21:25:55-1546-1 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:25:56 svr.itcore.in abrt-notification[9159]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:25:57 svr.itcore.in abrt-server[9162]: Can't find a meaningful backtrace for hashing in '.'
Oct 11 21:25:57 svr.itcore.in abrt-server[9162]: Option 'DropNotReportableOopses' is not configured
Oct 11 21:25:57 svr.itcore.in abrt-server[9162]: Preserving oops '.' because DropNotReportableOopses is 'no'
Oct 11 21:25:58 svr.itcore.in abrt-notification[9179]: System encountered a non-fatal error in ??()
Oct 11 21:25:58 svr.itcore.in abrt-server[9181]: Deleting problem directory oops-2019-10-11-21:25:55-1546-3 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:25:58 svr.itcore.in abrt-notification[9188]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:25:59 svr.itcore.in abrt-dump-journal-oops[1546]: Reported 5 kernel oopses to Abrt
Oct 11 21:25:59 svr.itcore.in abrt-server[9190]: Can't find a meaningful backtrace for hashing in '.'
Oct 11 21:25:59 svr.itcore.in abrt-server[9190]: Option 'DropNotReportableOopses' is not configured
Oct 11 21:25:59 svr.itcore.in abrt-server[9190]: Preserving oops '.' because DropNotReportableOopses is 'no'
Oct 11 21:26:00 svr.itcore.in abrt-notification[9207]: System encountered a non-fatal error in ??()
Oct 11 21:26:00 svr.itcore.in abrt-dump-journal-oops[1546]: abrt-dump-journal-oops: Found oopses: 5
Oct 11 21:26:00 svr.itcore.in abrt-dump-journal-oops[1546]: abrt-dump-journal-oops: Creating problem directories
Oct 11 21:26:00 svr.itcore.in abrt-server[9209]: Deleting problem directory oops-2019-10-11-21:26:00-1546-0 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:26:00 svr.itcore.in abrt-notification[9216]: System encountered a non-fatal error in __check_object_size()
Oct 11 21:26:01 svr.itcore.in abrt-server[9218]: Deleting problem directory oops-2019-10-11-21:26:00-1546-1 (dup of oops-2019-10-11-21:25:35-1546-0)
Oct 11 21:26:01 svr.itcore.in abrt-notification[9225]: System encountered a non-fatal error in __check_object_size()
My abrt directory is flooded with thousands of folders:
Code:
# ls -1 /var/spool/abrt/oops-2019-10-11-21*/ | wc -l
6536
What do I do? How do I stop this?
Attached Thumbnails
Click image for larger version

Name:	abrt.png
Views:	47
Size:	109.2 KB
ID:	31501  
 
Old 10-11-2019, 12:21 PM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
It looks like your logging level is set way too high, and it's whining continually.

I would delete those directories and try to reduce your logging level. google that, i.e. google 'Fedora set log level'
 
Old 10-11-2019, 12:31 PM   #3
ddenial
Member
 
Registered: Dec 2016
Distribution: CentOS, Fedora, Ubuntu
Posts: 359

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by business_kid View Post
It looks like your logging level is set way too high, and it's whining continually.

I would delete those directories and try to reduce your logging level. google that, i.e. google 'Fedora set log level'
Everything was fine. I took a snapshot of the root filesystem, installed qbittorrent, didn't like it, so reverted back the snapshot to the previous state. From then on, the problem started.
 
Old 10-11-2019, 12:37 PM   #4
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
Quote:
Originally Posted by ddenial View Post
Everything was fine. I took a snapshot of the root filesystem, installed qbittorrent, didn't like it, so reverted back the snapshot to the previous state. From then on, the problem started.
My guess is you screwed something in that process. How do you do snapshots? Have you reverted successfully before? It may be better to revert to a clean partition.
 
Old 10-11-2019, 12:46 PM   #5
ddenial
Member
 
Registered: Dec 2016
Distribution: CentOS, Fedora, Ubuntu
Posts: 359

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by business_kid View Post
My guess is you screwed something in that process. How do you do snapshots? Have you reverted successfully before? It may be better to revert to a clean partition.
I used following commands to take/revert snapshot. Everything went fine except this oops error.
Code:
# df -h /
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/vgh-rfs   98G   12G   82G  13% /

# lvcreate -n snap -s -L5G vgh/rfs
# dnf install qbittorrent
# lvconvert --merge vgh/snap
# reboot
 
Old 10-12-2019, 06:18 AM   #6
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
Not familiar with those commands at all. I did that search I suggested you do...

Code:
cat /proc/sys/kernel/printk
gets your current kernel log level
Code:
echo 4 > /proc/sys/kernel/printk
puts a sane log level there. You can also use lower numbers, but I wouldn't go below 3. Higher numbers can give log spam, like you're attracting.
 
1 members found this post helpful.
Old 10-12-2019, 06:59 AM   #7
ddenial
Member
 
Registered: Dec 2016
Distribution: CentOS, Fedora, Ubuntu
Posts: 359

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by business_kid View Post
Not familiar with those commands at all. I did that search I suggested you do...

Code:
cat /proc/sys/kernel/printk
gets your current kernel log level
Code:
echo 4 > /proc/sys/kernel/printk
puts a sane log level there. You can also use lower numbers, but I wouldn't go below 3. Higher numbers can give log spam, like you're attracting.
The output for /proc/sys/kernel/printk was '4 4 1 7'. The Oops message was so intense that it flooded hundreds of messages in minutes, which made me unable to do any work on my PC. I got so irked by that, I reinstalled the whole OS and other packages from the beginning.

Thanks anyway.
 
Old 10-12-2019, 11:54 AM   #8
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
Grand. Mark this solved. If you're starting linux, Fedora is an awkward one IMO. They have bleeding edge stuff in there, and odd ways of doing things so I often felt like a crash tester for RHEL. The trouble with the bleeding edge is that blood flows - usually yours .
 
Old 10-13-2019, 04:27 AM   #9
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
Quote:
Originally Posted by ddenial View Post
The output for /proc/sys/kernel/printk was '4 4 1 7'.
On my systems it was
Code:
4	4	1	4
and
Code:
1	4	1	3
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Every app segfaults, every liveCD/DVD kernel panics. I dunno what to do. Exospaciac Linux - General 3 01-23-2011 02:44 AM
How to set up a Cron Job to run every other week or every three months etc. kckabobus Linux - Newbie 3 04-03-2008 01:36 PM
every movie in every player has no visual Geminias Linux - Newbie 10 12-11-2007 12:12 AM
Gnome panel shows every open window in taskbar on every workspace polemon Linux - Desktop 3 11-20-2006 03:27 AM
Getting error message after installing AIM, please please help. TWTony Linux - Software 1 11-24-2004 08:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 06:25 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration