[SOLVED] Laggy system / high CPU load after upgrade

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] Laggy system / high CPU load after upgrade

Postby Gelsenbury » Jul 31st, '19, 20:38

I just upgraded Mageia on my HP laptop. Generally speaking, the upgrade from Mageia 6.1 to 7.1 (using the installer DVD) went well. All applications seem to be working so far, the desktop looks just as before, the network connection is fine, even Virtualbox works.

My only problem is that a couple of processes seem to put a high load on the CPU from the moment I log into my user account. This causes the laptop fan to make a lot of noise because it's always on full speed, and the system to be slower than usual. I also suspect that the battery will run down faster once I unplug.

It seems as if systemd-journald and baloo_file_extractor were the two processes with significant CPU usage according to the top command. I'm not competent enough to know what these are doing. But I've left the system to run for a couple of hours now, so I don't think the issue will just go away.

When I log into another user account (which is basically blank because I only use it for testing), these processes don't create such a high load, the fan stays quiet, and the system works as expected. So the problem only seems to happen in my user account, which is unchanged from Mageia 6.1 and was working normally before the upgrade.

Who can give me an idea about how to solve this issue?
Last edited by Gelsenbury on Aug 5th, '19, 14:51, edited 1 time in total.
User avatar
Gelsenbury
 
Posts: 113
Joined: Jun 1st, '11, 21:00

Re: Laggy system / high CPU load after upgrade

Postby ITA84 » Aug 1st, '19, 09:58

Those processes are known to misbehave on several systems (although I haven't heard about journald issues in a while), without a definitive fix for every user case; baloo_file_extractor sometimes does it when it has to index a large amount of files all at once, and the common workarounds are to clear the Baloo index and restart it, or just disable Baloo file search altogether (if you don't need full text file search you might as well do that).

To disable Baloo file search you can open System Settings -> Workspace -> Search, and uncheck the two options there (optionally, you can leave it enabled but exclude some directories from search).

To clear the Baloo file index you can open a terminal and use the following commands

Code: Select all
balooctl disable
balooctl enable


If this doesn't work, after balooctl disable you should look for the .local/share/baloo in your home folder (.local is a hidden folder) and remove it, then run balooctl enable.

As for journald, the journal might have become corrupted, but any fix I suggest now could be obsolete. I'll let you know if I find anything. Just to make sure, though, see if by running journalctl -f on a terminal when there's high CPU usage for journald you see a lot of log messages being output, in case the issue is not corruption but just some process filling up the logs
ITA84
 
Posts: 199
Joined: Mar 5th, '13, 18:15

Re: Laggy system / high CPU load after upgrade

Postby doktor5000 » Aug 2nd, '19, 16:55

Regarding journalctl, can you please post the output as root of
Code: Select all
journalctl --verify
journalctl --disk-usage

Although it looks like something is spamming the journal quite hard, I'd also suggest to run journalctl -f and watch the log to see if there are any obvious repeated offenders, you can post it here if in doubt ...
See also https://askubuntu.com/questions/906251/ ... -cpu-usage
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17630
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Laggy system / high CPU load after upgrade

Postby Gelsenbury » Aug 3rd, '19, 14:41

Thank you both for your help. The command "balooctl disable" doesn't seem to be doing much. The baloo_file_extractor continues to run and take up an unchanged amount of CPU load. I have deleted ~/.local/share/baloo, also to no effect.

Here is the output requested, first for journalctl --verify:
Code: Select all
[root@manchot03 baloo]# journalctl --verify
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000009050ef-00058f34e6ea3b4e.journal
7ffff08: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000008c5ccd-00058f34c64e3e23.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000009597c0-00058f35058cd08b.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000091f817-00058f34f0148e43.journal
7ffff38: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000990b09-00058f351adb599b.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000008e7653-00058f34d2c52a7f.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000086d861-00058efef06afc5b.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000006f7d69-00058efdaac7f01a.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000832a79-00058efec74960a4.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000086bf0d-00058efeeeaacaae.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000008351da-00058efec911aee3.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1001@1f18c9c3433d45b99906ae5a4aa18022-0000000000765add-00058efdffe33fac.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000091d66a-00058f34eff3d46d.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000093e58d-00058f34fb0ca89f.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000074e2c9-00058efde7cddf56.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000009ebd4d-00058f353cc20450.journal
7fffdd0: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000007a3287-00058efe636178c0.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000007c1e3f-00058efe796fac9c.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000076b050-00058efe3ca03206.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1001@c1c0b5a6b7ba4deaa748668398041630-000000000089b953-00058eff90d2e851.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-0000000000a08a58-00058f35477cd7a8.journal
7fffd98: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000730a77-00058efdd232c673.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system.journal                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-0000000000a4323d-00058f356e380816.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000009b2304-00058f35274cd89b.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000008acac0-00058f34bd4e8932.journal
7ffff38: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000009ca502-00058f35304e30ed.journal
7ffff38: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000009ad818-00058f352591ad94.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000081602d-00058efeb1b7ba74.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000081657c-00058efeb36b1380.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000007f95e1-00058efe9e0778d7.journal
7fffeb8: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000008a9001-00058f34bd12e112.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000007ddfaa-00058efe8c141f1c.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000073250f-00058efdd3f2da0d.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-0000000000889b36-00058eff0417bf2c.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000007a3321-00058efe63f9b176.journal
7ffff20: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000a03ed6-00058f3545c18c3e.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000007fa241-00058efe9fbfab9c.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000008514fb-00058efedcbe718e.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-0000000000a25f2e-00058f3564962bce.journal
7ffff38: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000009570dd-00058f35056b12a6.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000713fdb-00058efdbe7d4659.journal
7fffdd0: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000008e2994-00058f34d10992bc.journal
7fffed8: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000769dfd-00058efe3ae57726.journal
7fffef0: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000a21e73-00058f3562e1d457.journal
7fffd98: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000078683e-00058efe4e976f6c.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000084f4c3-00058efedafa2a2b.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000009950a2-00058f351c91f017.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000007dcb97-00058efe8a5c6eb7.journal
7ffff38: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000009e71ee-00058f353b06d780.journal
7fffee0: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000.journal               
7f99148: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-00000000007bfcd1-00058efe77aabf1a.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000007871ad-00058efe504d2df3.journal
7fffed8: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000093a3e8-00058f34fab7f70d.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000008caa15-00058f34c809dbda.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000071659d-00058efdc042dfb4.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000888977-00058eff025c9389.journal
7ffff10: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000090096c-00058f34e5311314.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-000000000097831d-00058f3511d746d0.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000a3eb52-00058f356d987cf5.journal
7ffff38: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-0000000000973e21-00058f351020fc11.journal
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/system@64641b84001c4cc29e1fa0ab9247f0c8-00000000009cf017-00058f3532076e7b.journal
7fffe08: Unused data (entry_offset==0)                                                 
PASS: /var/log/journal/ca2add224b9946f2ae226e372536f775/user-1000@7d35e117ff724c45b8103de9384bf5fa-000000000074d511-00058efde6108473.journal


And then for journalctl --disk-usage:
Code: Select all
[root@manchot03 share]# journalctl --disk-usage
Archived and active journals take up 3.9G in the file system.


I can't quite make sense of the journalctl -f output, but it does seem to be indicating a problem:
Code: Select all
Aug 03 13:37:21 manchot03 baloo_file_extractor[19564]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Aug 03 13:37:21 manchot03 baloo_file_extractor[19564]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Aug 03 13:37:21 manchot03 baloo_file_extractor[19564]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid


I get many lines of that, and then repeated lines specifying two file names. One of them is an interview transcript from work, which I've tried to neutralise by opening it, saving it in a different format, and deleting the original. The other is the virtual harddisc image of my Virtualbox Windows machine, so I'll just tell the file indexer to skip that directory for indexing (no need for it anyway).

I'll now reboot and see what happens.
User avatar
Gelsenbury
 
Posts: 113
Joined: Jun 1st, '11, 21:00

Re: Laggy system / high CPU load after upgrade

Postby doktor5000 » Aug 4th, '19, 15:10

Gelsenbury wrote:The baloo_file_extractor continues to run and take up an unchanged amount of CPU load. I have deleted ~/.local/share/baloo, also to no effect.


balooctl disable only enables/disables it for autostart, it does not end all running processes from what I understood.
If the process is still running, you have to kill it first before you delete the files/folders it's trying to write to. So disable baloo, as you already did, and then reboot, then check again with balooctl status.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17630
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Laggy system / high CPU load after upgrade

Postby Gelsenbury » Aug 5th, '19, 14:50

Thank you, that seems to have worked. The journal isn't causing problems any more either. Perhaps the problem with the file indexer caused the problem with the journal?

Incidentally, baloo is now running again. The problem seems to have been solved by stopping it, deleting the index, and starting again.
User avatar
Gelsenbury
 
Posts: 113
Joined: Jun 1st, '11, 21:00


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron