Bug 343437

Summary: Do not Index NFS
Product: [Frameworks and Libraries] frameworks-baloo Reporter: J <jojo>
Component: generalAssignee: Pinak Ahuja <pinak.ahuja>
Status: RESOLVED FIXED    
Severity: normal CC: aspotashev, jojo, null, pinak.ahuja, stefan.bruens
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description J 2015-01-28 08:00:46 UTC 
Classical setup for companies, firms, enterprises is to mount /home from an NFS Server.
Also classical is that User and Groups are administrated central.
There is no way to disable Baloo centrally for all users and stop users to reactivate.

Reproducible: Always

Steps to Reproduce:
1. Setup NFS Server for /home
2. Connect 5, 10, 20, 50 Clients mounting /home
3. Wait for Work Start, ie. 9:00 Morning
4. Users Log in nearly synchronous
5. ballo starts/runs in plenty machines synchronously
6. NFS Server load raises 5, 10, 50, 99, ... infinite until it crashes
7. No one can work anymore - DDOS Completet Argh !


Actual Results:  
Server down

Expected Results:  
Baloo disabled and not activating by it self on NFS-Setups. Only an sysadmin should be able to aktivate baloo on nfs setups.

Completely disable by default if $HOME is on NFS 
Also the Baloo Index Files shoul never be stored on NFS Filesystems.
Comment 1 Vishesh Handa 2015-01-28 12:37:10 UTC 
Could you please provide some version information?

I remember adding some code related to never indexing network shares in 5.1.
Comment 2 Vishesh Handa 2015-02-02 19:38:11 UTC 
Ping?
Comment 3 J 2015-02-16 12:02:23 UTC 
Pong
Problem exist @ Arch Linux Rolling Release.
This BUG is CRITICAL because it damages other server in Company Environments.
Comment 4 J 2015-02-16 12:05:18 UTC 
Exact Version Information:
kdebase-runtime 14.12.2-2 [Installiert]
extra/kdebase-workspace 4.11.16-1 (kde kdebase) [Installiert]
Comment 5 Vishesh Handa 2015-02-16 12:45:52 UTC 
Could you please provide the Baloo version number?
Comment 6 J 2015-02-16 14:36:30 UTC 
I presume, this should give an hint:
[jojo@pc7 ~]$ pacman -Qo /usr/bin/balooctl 
/usr/bin/balooctl ist in baloo-frameworks 5.6.0-1 enthalten

We have a current problem, during "Desktop Search" is enabled-checked after each package upgrade, even $HOME redides on an NFS Server.

The only Way to protect the Server from DDOS by its clients is chmod -x /usr/bin/baloo* (and btw. also chmod -x /usr/bin/akonadi*) on each client. Our Admins made an systemd target for doing this.

This is an "ouch" problem.
Comment 7 J 2015-02-16 14:39:02 UTC 
ahh, here is the Link for the current package:
https://www.archlinux.org/packages/extra/x86_64/baloo-frameworks/
Comment 8 Vishesh Handa 2015-02-16 15:41:36 UTC 
I'm a little confused about what we should be doing -
* We're not maintaining configuration between 4 and 5. 
* Baloo can easily be disabled via the KCM or via `$ balooctl disable`.

I guess you want Baloo to be disabled/not index NFS media. Marking as CONFIRMED.

Though I have to say -
> Classical setup for companies, firms, enterprises is to mount /home from an NFS Server.

As an individual user without access to NFS systems, it's harder for me to test these things out. Given that you're in a company using KDE, it would be great if you could invest some time and provide patches.
Comment 9 J 2021-02-16 14:23:31 UTC 
Ok, bu as "individual" User you should ever have in mind, that Unix ans alike Systems (like Linux, *BSD) are mostly ever used in Network environments.

On architecture design, avoid *any* things, or switch them completely off by default, if such a beast may be harmful to others, especially like the balloo  behavior in 2015!

And a balloctl comand may not help at all, if it was running and crashing the servers.
Comment 10 Stefan Brüns 2024-05-14 14:40:26 UTC 
Network shares are excluded in current versions (i.e. for the last ~5 years).