File not found when attempting to stream
Posted: Wed Mar 10, 2021 11:34 am
Twonky Server version 8.5.2-3 on a Western Digital ‘My Cloud Mirror’ NAS running firmware version 5.10.122.
I’ve been using Twonky with three different DLNA clients to stream music from my WD NAS ‘forever’ and it has worked faultlessly — until recently… Now, although I can navigate my music repository without problem, when I select a track to play, the client tells me it failed. I turned on some logging and here’s what I see.
When I use a DLNA client to browse my music on the NAS, Twonky returns details of the individual tracks in XML format and specifies file names of the form:
/disk/DLNA-PNMP3-OP01-FLAGS01700000/O0$1$8I9729.mp3
(The pathname for this file on the NAS is actually /Public/Shared Music/Al Stewart/Past, Present And Future/01.Old Admirals.mp3)
When I tell my DLNA client to play this particular track, the client requests the filename that Twonky gave it, but Twonky logs a "File not found" error and appears to return an HTTP 404 to the DLNA client.
AFAICT Twonky is giving the client a handle for an MP3 file, but when it is subsequently asked to stream that file, Twonky cannot resolve the handle.
FWIW, I have tried uninstalling/reinstalling Twonky on the NAS, which should have caused it to rebuild its index of music files, so I don't think the problem is that Twonky's index is out-of-sync with the NAS content.
Does anyone have any ideas why I might be seeing File not found errors? Is the file name encoding /disk/DLNA-PNMP3-OP01-FLAGS01700000/O0$1$8I9729.mp3 a Twonky-internal representation? If so, what could cause Twonky to fail to map that to the file’s actual path name on the NAS?
I can’t be certain when this issue first started, though I suspect it was after a WD firmware update that got applied automatically. I certainly didn’t change anything myself. I have a case open with WD support, but although Twonky is supplied by WD as an optional app for the NAS, they (not unreasonably) don’t have the expertise to analyse Twonky logs.
TIA.
I’ve been using Twonky with three different DLNA clients to stream music from my WD NAS ‘forever’ and it has worked faultlessly — until recently… Now, although I can navigate my music repository without problem, when I select a track to play, the client tells me it failed. I turned on some logging and here’s what I see.
When I use a DLNA client to browse my music on the NAS, Twonky returns details of the individual tracks in XML format and specifies file names of the form:
/disk/DLNA-PNMP3-OP01-FLAGS01700000/O0$1$8I9729.mp3
(The pathname for this file on the NAS is actually /Public/Shared Music/Al Stewart/Past, Present And Future/01.Old Admirals.mp3)
When I tell my DLNA client to play this particular track, the client requests the filename that Twonky gave it, but Twonky logs a "File not found" error and appears to return an HTTP 404 to the DLNA client.
AFAICT Twonky is giving the client a handle for an MP3 file, but when it is subsequently asked to stream that file, Twonky cannot resolve the handle.
FWIW, I have tried uninstalling/reinstalling Twonky on the NAS, which should have caused it to rebuild its index of music files, so I don't think the problem is that Twonky's index is out-of-sync with the NAS content.
Does anyone have any ideas why I might be seeing File not found errors? Is the file name encoding /disk/DLNA-PNMP3-OP01-FLAGS01700000/O0$1$8I9729.mp3 a Twonky-internal representation? If so, what could cause Twonky to fail to map that to the file’s actual path name on the NAS?
I can’t be certain when this issue first started, though I suspect it was after a WD firmware update that got applied automatically. I certainly didn’t change anything myself. I have a case open with WD support, but although Twonky is supplied by WD as an optional app for the NAS, they (not unreasonably) don’t have the expertise to analyse Twonky logs.
TIA.