Bug 1155697 - process journalctl became abnormal high CPU load.
Summary: process journalctl became abnormal high CPU load.
Keywords:
Status: CLOSED DUPLICATE of bug 1324663
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-22 16:14 UTC by Mikhail
Modified: 2016-05-17 06:55 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-17 06:55:32 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
screenshot of htop (276.32 KB, image/png)
2014-10-22 16:14 UTC, Mikhail 		no flags Details
screenshot of htop 2 (271.92 KB, image/png)
2014-10-22 16:15 UTC, Mikhail 		no flags Details
strace of journalctl (1.54 MB, application/x-gzip)
2014-10-22 16:18 UTC, Mikhail 		no flags Details
dmesg (122.79 KB, text/plain)
2014-10-22 16:19 UTC, Mikhail 		no flags Details
View All

Description Mikhail 2014-10-22 16:14:46 UTC 
Created attachment 949477 [details]
screenshot of htop

Description of problem:
process journalctl became abnormal high CPU load.
Comment 1 Mikhail 2014-10-22 16:15:16 UTC 
Created attachment 949478 [details]
screenshot of htop 2
Comment 2 Mikhail 2014-10-22 16:15:38 UTC 
$ rpm -q systemd
systemd-216-5.fc21.x86_64
Comment 3 Mikhail 2014-10-22 16:18:59 UTC 
Created attachment 949479 [details]
strace of journalctl
Comment 4 Mikhail 2014-10-22 16:19:42 UTC 
Created attachment 949480 [details]
dmesg
Comment 5 Jaroslav Reznik 2015-03-03 16:23:36 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 6 Susant Sahani 2016-05-17 06:55:32 UTC 

*** This bug has been marked as a duplicate of bug 1324663 ***
Note You need to log in before you can comment on or make changes to this bug.