Bug 12383 – SC crashes "Unable to start Inotify watcher"

Bug 12383 - SC crashes "Unable to start Inotify watcher"

Summary:

SC crashes "Unable to start Inotify watcher"

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Scanner
Version:	7.4.0
Platform:	PC RedHat Linux

Importance:	-- major (vote)
Target Milestone:	7.4.0
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-06-15 00:30 UTC by Michael Herger
Modified:	2009-10-05 14:34 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Herger 2009-06-15 00:30:18 UTC

On my box I no longer can start SC. It crashes with the following error (which is not logged in the server.log file?):

[09-06-15 09:26:38.1826] Slim::Utils::AutoRescan::Linux::watch (71) Warning: Unable to start Inotify watcher at /usr/local/Squeezebox/Slim/Utils/AutoRescan/Linux.pm line 71.

Comment 1 Michael Herger 2009-06-15 00:42:03 UTC

INotify's error message is "Function not implemented".

Documentation says: "This module implements an interface to the Linux 2.6.13 and later Inotify file/directory change notification sytem."

My uname -r: 2.6.9-78.0.22.EL

Comment 2 Andy Grundman 2009-06-15 05:11:12 UTC

Try change 27074.

Comment 3 Michael Herger 2009-06-15 06:14:18 UTC

Looking good, thanks!

Comment 4 James Richardson 2009-10-05 14:34:53 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.