Timeout accessing the database

[gedl]

Hi,

My local scan crashed and I took the chance to try what it could index. However I keep getting the following on mopidy log:

2017-02-12 18:35:51,871 DEBUG [735:HttpServer] mopidy.http.handlers: Received WebSocket message from 192.168.37.253: u'{"method":"core.playback.get_current_tl_track","jsonrpc":"2.0","id":34}'
2017-02-12 18:35:51,882 DEBUG [735:HttpServer] mopidy.http.handlers: Received WebSocket message from 192.168.37.253: u'{"method":"core.tracklist.add","params":{"uri":"file:///var/lib/mopidy/local-sqlite/library.db"},"jsonrpc":"2.0","id":35}'
2017-02-12 18:35:51,886 DEBUG [735:FileBackend-6] mopidy.file.library: Looking up file URI: file:///var/lib/mopidy/local-sqlite/library.db
2017-02-12 18:35:52,904 WARNING [735:FileBackend-6] mopidy.file.library: Failed looking up file:///var/lib/mopidy/local-sqlite/library.db: Timeout after 1000ms

I am using Mopidy 2.1.0-1 and Mopidy Mobile 1.7.5

It looks strange that the client app shows "library.db" as a track, so maybe I am doing something else wrong.

This is the sql-lite section of my mopidy.conf:

[local-sqlite]
enabled = true
timeout = 10

[tkem]

From the log it looks like you're trying to access the SQLite database file using the file backend. In Mopidy Mobile, you should see two top-level library directories: "Files" and "Local media". "Files" is for simple, direct access to local files, without any local scan or indexing. "Local media" is where Mopidy-Local-SQLite (if configured correctly) comes into play.

[gedl]

Yes, that was exactly it.

I had the feeling I was doing something dumb.

Thanks.