I use my own home grown monitoring tools on my servers and they picked up something interesting. One of the checks my tools run is to look for processes that are growing in memory size, or are using more memory than I would expect.<\/p>\n
They identified a couple of programs, baloo_file and tracker-store. A ps on processes containing tracker gave tracker-store, tracker-miner-fs and tracker-miner apps, so I thought I would see what they were.<\/p>\n
Guess what, they are both file indexer programs. Why Gnome under F29 comes with two seperate file indexers I do not know, but it seems like a waste of CPU resources, and as I detected them when their running memory footprints raised warnings in my monitoring toolkit a waste of memory usage as well.<\/p>\n
There documentation available for tracker at https:\/\/wiki.gnome.org\/Projects\/Tracker and it indicates that it is tightly tied to the gnome desktop so I have decided to leave that alone for now as it also had the smaller memory footprint.
\nThe baloo documentation is at https:\/\/community.kde.org\/Baloo and indicates it is used by the KDE plasma desktop.<\/p>\n
I have both desktops installed and available via the logon session switcher menu as it took me a while to find a desktop that worked correctly with synergy so had to try quite a few. That may explain why both are installed, but annoyingly it means that reguardless of what desktop I chose both of them start running at user login.<\/p>\n
I also do not know how usefull they are, as they are apparently used by applications that hook into them and have no direct command line interface to search (that I can see anyway) so a simple grep and my PDF text search utility are still more usefull to me than these indexers. They may be usefull to users that use file managers and are afraid of the command line however.<\/p>\n
As baloo_file had the larger (by far) memory footprint that is the one I decided to get rid of, as I am not using the plasma desktop but the KDE fallback one. The result of that exercise is that you cannot get rid of it as it is tied to the installed plasma desktop. It is theoretically possible to disable it (although I have not rebooted to see if it stays disabled) using the following steps… on a per user basis<\/b> as baloo is provided to index files under the users home directory and each user has there own configuration file. Fortunately on my machines I am the only user.<\/p>\n
(1) vi $HOME\/.config\/baloofilerc and add to the end of the file the line
\nIndexing-Enabled=false<\/p>\n
(2) stop and disable the baloo process using the balooctl commands as below<\/p>\n
\r\n[mark@vmhost3 ~]$ balooctl status\r\nBaloo File Indexer is running\r\nIndexer state: Idle\r\nIndexed 273 \/ 273 files\r\nCurrent size of index is 32.33 MiB\r\n[mark@vmhost3 ~]$ balooctl stop<\/b>\r\n[mark@vmhost3 ~]$ balooctl disable<\/b>\r\nDisabling the File Indexer\r\n[mark@vmhost3 ~]$ balooctl status\r\nBaloo is currently disabled. To enable, please run balooctl enable\r\n[mark@vmhost3 ~]$\r\n<\/pre>\nIt is not possible to remove the baloo packages themselves as they are tied to the plasma desktop <\/p>\n
\r\n[root@vmhost3 jobdata]# rpm -qa | grep -i baloo\r\nkf5-baloo-5.52.0-2.fc29.x86_64\r\nkf5-baloo-file-5.52.0-2.fc29.x86_64\r\nkf5-baloo-libs-5.52.0-2.fc29.x86_64\r\nbaloo-widgets-18.08.1-1.fc29.x86_64\r\nbaloo-libs-4.14.3-21.fc29.x86_64\r\n[root@vmhost3 jobdata]# rpm -e kf5-baloo-5.52.0-2.fc29.x86_64 \\\r\n kf5-baloo-file-5.52.0-2.fc29.x86_64 \\\r\n kf5-baloo-libs-5.52.0-2.fc29.x86_64 \\\r\n baloo-widgets-18.08.1-1.fc29.x86_64 \\\r\n baloo-libs-4.14.3-21.fc29.x86_64\r\nerror: Failed dependencies:\r\n\tkf5-baloo is needed by (installed) plasma-workspace-5.13.5-1.fc29.x86_64\r\n\tlibKF5Baloo.so.5()(64bit) is needed by (installed) gwenview-1:18.04.3-1.fc29.x86_64\r\n\tlibKF5Baloo.so.5()(64bit) is needed by (installed) gwenview-libs-1:18.04.3-1.fc29.x86_64\r\n\tlibKF5Baloo.so.5()(64bit) is needed by (installed) dolphin-libs-18.08.1-1.fc29.x86_64\r\n\tlibKF5Baloo.so.5()(64bit) is needed by (installed) dolphin-18.08.1-1.fc29.x86_64\r\n\tlibKF5Baloo.so.5()(64bit) is needed by (installed) plasma-workspace-5.13.5-1.fc29.x86_64\r\n\tlibKF5Baloo.so.5()(64bit) is needed by (installed) plasma-desktop-5.13.5-1.fc29.x86_64\r\n\tlibKF5BalooWidgets.so.5()(64bit) is needed by (installed) dolphin-libs-18.08.1-1.fc29.x86_64\r\n\tlibKF5BalooWidgets.so.5()(64bit) is needed by (installed) dolphin-18.08.1-1.fc29.x86_64\r\n\tlibbaloopim.so.4()(64bit) is needed by (installed) knode-libs-4.14.10-38.fc29.x86_64\r\n<\/pre>\nThe tracker one I have left running for now as its memory footprint while enough to exceed my alerting threshold was tiny compared to baloo. So at some point I can get around to seeing if it is usefull, for now tracker-store has just been threshold adjusted up and added to my track memory growth monitoring to see if it is actually growing or is fairly static.<\/p>\n
Update 18 June 2019, how to disable the tracker processes<\/b>
\nTo stop Tracker running on F30 (a list of services can be found with ‘ls \/usr\/lib\/systemd\/user\/tracker*’)
\nLogged on as your own userid<\/p>\n\r\ncd ~\/.config\/autostart\r\ncp \/etc\/xdg\/autostart\/tracker*desktop .\r\nfor FILE in $(ls tracker*); do echo \"Hidden=true\" >> $FILE; done\r\nsystemctl --user disable tracker-store.service\r\nsystemctl --user disable tracker-miner-fs.service\r\nsystemctl --user stop tracker-miner-fs.service\r\nsystemctl --user disable tracker-extract.service\r\nsystemctl --user disable tracker-miner-rss.service\r\nsystemctl --user disable tracker-writeback.service\r\n<\/pre>\nreboot to confirm they are all stopped; ‘tracker reset -r’ to delete all existing indexes; check all are disabled<\/p>\n
\r\n[mark@phoenix posts]$ tracker status\r\nCurrently indexed: 0 files, 0 folders\r\nRemaining space on database partition: 44.1?GB (56.42%)\r\nAll data miners are idle, indexing complete\r\n\r\n[mark@phoenix posts]$ tracker daemon\r\nStore:\r\n18 Jun 2019, 09:27:05: 0% Store - Idle \r\n\r\nMiners:\r\n18 Jun 2019, 09:27:05: ? RSS\/ATOM Feeds - Not running or is a disabled plugin\r\n18 Jun 2019, 09:27:05: ? File System - Not running or is a disabled plugin\r\n18 Jun 2019, 09:27:05: ? Extractor - Not running or is a disabled plugin\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"I use my own home grown monitoring tools on my servers and they picked up something interesting. One of the checks my tools run is to look for processes that are growing in memory size, or are using more memory … Continue reading