Bug 256269 - sysutils/kf5-baloo: Opens 19+k files and causes 'Too many open files' error
Summary: sysutils/kf5-baloo: Opens 19+k files and causes 'Too many open files' error
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-kde (group)
URL: https://bugs.kde.org/show_bug.cgi?id=...
Keywords: needs-patch, needs-qa, performance
: 273669 (view as bug list)
Depends on:
Blocks: 230726 281479
  Show dependency treegraph
 
Reported: 2021-05-30 18:25 UTC by Yuri Victorovich
Modified: 2024-09-27 11:41 UTC (History)
8 users (show)

See Also:
bugzilla: maintainer-feedback? (kde)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer freebsd_triage 2021-05-30 18:25:46 UTC
I have kf5-baloo-5.82.0, plasma5-plasma-5.21.5, kde5-5.21.5.21.04.1 installed.

/usr/local/bin/startplasma-x11 runs baloo_file and it opens 19+k files and kde5 fails to start because many processes fail with 'Too many open files' error.
Comment 1 Tobias C. Berner freebsd_committer freebsd_triage 2021-06-16 18:55:44 UTC
Moin moin Yuri

Sorry for not responding here earlier. Yes, that is a very bad behaviour that is caused by files being required to be opened to be monitored.

We cannot really disable baloo by default, as having such a huge home directory is probably not too common, and it would disable functionality out of the box. 

I think we need to work on the documentation be it pkg-message or handbook to get people some information on how to handle this issue (`balooctl disable` or restricting the folders to be monitored, or increasing the number of file handles).

And of course, find some time to make baloo behave properly with FreeBSD's file monitoring capabilities.


mfg Tobias
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2021-09-05 17:05:33 UTC
FYI bug 258010
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2022-10-23 03:53:36 UTC
Documentation
=============


(In reply to Tobias C. Berner from comment #1)

> … need to work on the documentation be it pkg-message or handbook …
> how to handle this issue (`balooctl disable` or restricting the 
> folders to be monitored, or increasing the number of file handles). …

+1

For kern.maxvnodes we have <https://docs.freebsd.org/en/books/handbook/config/#_kern_maxvnodes> (currently 12.11.3.1), however this subsection is not referenced from any troubleshooting section of any chapter. 


Absence of a package message
----------------------------

<https://www.freshports.org/sysutils/kf5-baloo/> ▶ <https://www.freshports.org/sysutils/kf5-baloo/#message>

This might be prioritised. 

* Add a messsage

* mention vfs.numvnodes and kern.maxvnodes

* refer to the virtual memory subsection of the FreeBSD Handbook

* do not yet refer to tuning(7) 
  <https://www.freebsd.org/cgi/man.cgi?query=tuning&sektion=7&manpath=FreeBSD>, 
  because there's no relevant mention of kern.maxvnodes.


The manual page for tuning(7), and answers to frequently asked questions (FAQ)
------------------------------------------------------------------------------

Bug 218538 might improve the man page, by making an example of vfs.numvnodes and kern.maxvnodes in a situation such as this. 

Bug 266111 comment 2, carlavilla@ mentions his template for a new FAQ for FreeBSD. Whilst I have not seen the template for an /en/ edition, I imagine a (plain English) mention of system performance; plus maybe a (semi-technical) phrase such as virtual memory vnode limit; then either the answer, or reference to the FreeBSD Handbook. 

218538 and 266111 in parallel. Realistically, the new FAQ might happen first.
Comment 4 Graham Perrin 2023-09-11 00:59:42 UTC
(In reply to Tobias C. Berner from comment #1)

> … documentation be it pkg-message or handbook …

Would you like me to draft a package message, with you as reviewer?
Comment 5 lexusaside 2024-03-05 08:49:59 UTC
MARKED AS SPAM
Comment 6 Gleb Popov freebsd_committer freebsd_triage 2024-03-30 09:50:19 UTC
*** Bug 273669 has been marked as a duplicate of this bug. ***