Your message dated Wed, 30 Mar 2016 19:02:00 +0300
with message-id <[email protected]>
and subject line Re: Bug#819250: minidlna: Poor handling of inotify limits
has caused the Debian Bug report #819250,
regarding minidlna: Poor handling of inotify limits
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
819250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819250
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: minidlna
Version: 1.1.2+dfsg-1.1+b3
Severity: important
On startup on my system minidlna exits with the following log message:
[2016/03/25 15:04:04] inotify.c:198: warn: WARNING: Inotify max_user_watches
[16382] is low or close to the number of used watches [1887] and I do not have
permission to increase this limit. Please do so manually by writing a higher
value into /proc/sys/fs/inotify/max_user_watches.
There are several problems with this. One is that this message is
marked as a warning and it is therefore very surprising to find it
treated as a fatal error. This is especially the case since the message
says that the number of used watches is about an order of magnitude
lower than the limit which doesn't suggest that the limit has actually
been hit.
The other is that since the program appears to have support for
non-inotify operation (there's a configuration option to control inotify
use) I'd expect it to fall back to that.
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages minidlna depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii libavformat56 6:11.6-1~deb8u1
ii libavutil54 6:11.6-1~deb8u1
ii libc6 2.19-18+deb8u3
ii libexif12 0.6.21-2
ii libflac8 1.3.0-3
ii libid3tag0 0.15.1b-11
ii libjpeg62-turbo 1:1.3.1-12
ii libogg0 1.3.2-1
ii libsqlite3-0 3.8.7.1-1+deb8u1
ii libvorbis0a 1.3.4-2
ii lsb-base 4.1+Debian13+nmu1
minidlna recommends no packages.
minidlna suggests no packages.
-- Configuration Files:
/etc/minidlna.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Mark,
On Wed, 30 Mar 2016 08:42:49 -0700
Mark Brown <[email protected]> wrote:
> On Wed, Mar 30, 2016 at 12:12:39PM +0300, Alexander Gerasiov wrote:
> > Mark Brown <[email protected]> wrote:
>
> > > > 2. I believe the problem is fixed in current testing version.
> > > > Please try 1.1.5 from testing or backports and report if crash
> > > > persists.
>
> > > Are you sure this isn't serious enough to be fixed in stable? The
> > > number of directories it's failing on is relatively low...
>
> > Debian release policy only allows to fix bugs in stable which are
> > 1. security flows
> > or
> > 2. makes software totally (or really highly) unusable.
>
> > Other fixes should go normal way through unstable and could be
> > delivered to users of stable distribution via backports.
>
> I'd argue that this is going towards the second case, my music
> collection is not *that* big.
Yes, but no, that's not enough =)
And once again: the problem is not from inotify limit. I think it
crashes on parsing some files. So I'm closing this bug, feel free to
reopen if you reproduce in with version from backports.
--
Best regards,
Alexander Gerasiov
Contacts:
e-mail: [email protected] Homepage: http://gerasiov.net Skype: gerasiov
PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
pgpnMqyJijjpR.pgp
Description: OpenPGP digital signature
--- End Message ---
