Gerbera 2.0 error: Failed to read /home/user/.mpdascache: No such file or directory about gerbera

[KarlStraussberger]

To me this looks like a broken link. You may also try to get rid of the message with hidden-files="no" for the directory.

[efermi]

1. I've added hidden-files="no" to the directory entries
2. found no related broken links with $ find ~/. -xtype l

The error message is still there. What else can I do?

[KarlStraussberger]

Where does the error message show up. Syslog or gerbera.log.

Can you run gerbera with --debug command line option.

[efermi]

In the syslog. When running it with --debug option the related output is as follows:

2024-02-26 18:58:29.040  trace: [autoscan_inotify.cc:179] threadProc(): inotify event: 210 mask=0x8 name=.mpdascache
2024-02-26 18:58:29.040  error: [autoscan_inotify.cc:203] threadProc(): Failed to read /home/user/.mpdascache: No such file or directory
2024-02-26 18:58:29.040  trace: [autoscan_inotify.cc:210] threadProc(): autoscan not found in watches? (210, watchAs:true, adir:true, /home/user/.mpdascache)

[KarlStraussberger]

Can you give a bit more of the log context, so that I can anticipate the logical flow (call history) that leads to the error.

[efermi]

It'll take some time to redact personal info out. Could be it that the database contains an outdated list of files to watch and it could be enough to rebuild it from scratch?

[KarlStraussberger]

It is highly recommended to rebuild it from scratch, because there are many new features that come with import. Be aware that 2.0 has some issues with importing playlists (already fixed in HEAD).

[efermi]

I've deleted the database and temporarily left an empty directory in the home dir as a single library location. The issue still persists, here is the full log:
gerbera-output.log
EDIT: I've switched to the gerbera-git from AUR, the error is still there.

[efermi]

I've setup a watch for the ~/.mpdascache file like that:

inotifywait -m -e create,delete --include '\.mpdascache' /home/user |
while read path action file; do
    echo "The file '$file' $action in '$path' at $(date)"
done

and it is indeed being created and deleted multiple times per second indefinitely while the mpdas.service is running as can also be seen here https://github.com/hrkfdn/mpdas/blob/c81c480a6081af104c70c3574fb71319ff1521b7/cache.cpp#L5 IIUIC. While there is probably a better way to do it, is it possible to make gerbera ignore these events which happen outside of specified library locations?

[KarlStraussberger]

Now I understand the problem: we monitor all parent dirs of autoscan entries to see when they go any (e.g. unmount). This monitoring has to handle the parent dirs differently.

[KarlStraussberger]

Finally, I've found some time to test this in current head. We detect the file which is already gone when we try to analyse it further in your case.
We can suppress the message if we're outside an autoscan dir.

[efermi]

Sounds good to me.