Missing file, but it's definitely there #71

Closed
opened 2026-04-24 22:57:37 +02:00 by adam · 9 comments
Owner

Originally created by @jarrodCoombes on GitHub (Oct 25, 2021).

Note that file 1 is missing in this book entry:

image

But the folder list looks like this:

image

Nothing I seem to do will get the first track to come up in the interface.

Any ideas?

Originally created by @jarrodCoombes on GitHub (Oct 25, 2021). Note that file 1 is missing in this book entry: ![image](https://user-images.githubusercontent.com/58901318/138630101-cae4a365-1184-43c3-bb94-3b011f481fb1.png) But the folder list looks like this: ![image](https://user-images.githubusercontent.com/58901318/138627541-61f4c189-b6c1-4861-9ed7-0b2eeed1ab32.png) Nothing I seem to do will get the first track to come up in the interface. Any ideas?
adam closed this issue 2026-04-24 22:57:37 +02:00
Author
Owner

@advplyr commented on GitHub (Oct 25, 2021):

When you click manage tracks do you see it in there?

If it is not showing in manage tracks you can try moving the file somewhere else. Wait a few seconds for the changes to scan. Then move it back.

@advplyr commented on GitHub (Oct 25, 2021): When you click manage tracks do you see it in there? If it is not showing in manage tracks you can try moving the file somewhere else. Wait a few seconds for the changes to scan. Then move it back.
Author
Owner

@jarrodCoombes commented on GitHub (Oct 25, 2021):

It's not listed in the track management. It was doing this before I wiped my database and restarted yesterday (I was having a ton of other issues). Did not show up after a full scan either.

I'll try the move out and move back in, but I will say I removed the book from the DB, then changed the folder name. The book got re-added but that track was still missing.

@jarrodCoombes commented on GitHub (Oct 25, 2021): It's not listed in the track management. It was doing this before I wiped my database and restarted yesterday (I was having a ton of other issues). Did not show up after a full scan either. I'll try the move out and move back in, but I will say I removed the book from the DB, then changed the folder name. The book got re-added but that track was still missing.
Author
Owner

@advplyr commented on GitHub (Oct 25, 2021):

I wonder if the file is corrupt or the probe is failing.. when you move the file out and back in can you open the unraid logger and see the results of the scan. If ffprobe fails on an audio file it should produce some logs.

@advplyr commented on GitHub (Oct 25, 2021): I wonder if the file is corrupt or the probe is failing.. when you move the file out and back in can you open the unraid logger and see the results of the scan. If ffprobe fails on an audio file it should produce some logs.
Author
Owner

@jarrodCoombes commented on GitHub (Oct 25, 2021):

As near as I can tell the file is not corrupt in so far as it plays just fine, but I did not do any extensive checks on it, and if the id3 tag is bad, that would not affect the playback.

@jarrodCoombes commented on GitHub (Oct 25, 2021): As near as I can tell the file is not corrupt in so far as it plays just fine, but I did not do any extensive checks on it, and if the id3 tag is bad, that would not affect the playback.
Author
Owner

@jarrodCoombes commented on GitHub (Oct 26, 2021):

I moved it out of the folder, waited a few minutes, then moved it back it and waited for a bit again. Still does not show up. Loaded the mp3 into mp3tag, everything looked ok. I added the track number and saved that. Waited some more time, still no show.

Where on unraid can I get to the log you mention? I'd like watch them as I do this to see if anything of note comes up.

@jarrodCoombes commented on GitHub (Oct 26, 2021): I moved it out of the folder, waited a few minutes, then moved it back it and waited for a bit again. Still does not show up. Loaded the mp3 into mp3tag, everything looked ok. I added the track number and saved that. Waited some more time, still no show. Where on unraid can I get to the log you mention? I'd like watch them as I do this to see if anything of note comes up.
Author
Owner

@advplyr commented on GitHub (Oct 27, 2021):

You can watch the docker image logs:
image

There is also a logs page in audiobookshelf, but it is a work in progress. You would need to keep the page open to watch changes, it will only show logs currently happening.

@advplyr commented on GitHub (Oct 27, 2021): You can watch the docker image logs: ![image](https://user-images.githubusercontent.com/67830747/138972683-f9d41f62-93b0-47d3-9520-7681d80855f1.png) There is also a logs page in audiobookshelf, but it is a work in progress. You would need to keep the page open to watch changes, it will only show logs currently happening.
Author
Owner

@jarrodCoombes commented on GitHub (Oct 27, 2021):

Thanks, that was helpful.

Here is what happens in the log in settings (set to debug):

2021-10-27 00:15:46 INFO [Scanner] 1 new audio files were found for audiobook "Dirty Work"
2021-10-27 00:15:46 DEBUG [AudioFileScanner] Scanning audio files
2021-10-27 00:15:46 DEBUG Scanning path "/audiobooks/Woods, Stuart/Stone Barrington/Book 09 - Dirty Work/Dirty Work - 01.mp3"
2021-10-27 00:15:48 DEBUG Notable! file_tag_contentgroup => Stone Barrington
2021-10-27 00:15:48 ERROR [AudioFileScanner] Scan failed for Woods, Stuart/Stone Barrington/Book 09 - Dirty Work/Dirty Work - 01.mp3
2021-10-27 00:15:48 WARN [AudioFileScanner] No Tracks for audiobook kv60xbk1
2021-10-27 00:15:49 DEBUG [DB] Audiobook updated 1
2021-10-27 00:15:49 INFO [Scanner] "Dirty Work" was updated
2021-10-27 00:15:49 DEBUG [Scanner] Finished scanning file changes, results: [object Object]

No indication why the scan failed though. Unraid logs look the same.

@jarrodCoombes commented on GitHub (Oct 27, 2021): Thanks, that was helpful. Here is what happens in the log in settings (set to debug): ``` 2021-10-27 00:15:46 INFO [Scanner] 1 new audio files were found for audiobook "Dirty Work" 2021-10-27 00:15:46 DEBUG [AudioFileScanner] Scanning audio files 2021-10-27 00:15:46 DEBUG Scanning path "/audiobooks/Woods, Stuart/Stone Barrington/Book 09 - Dirty Work/Dirty Work - 01.mp3" 2021-10-27 00:15:48 DEBUG Notable! file_tag_contentgroup => Stone Barrington 2021-10-27 00:15:48 ERROR [AudioFileScanner] Scan failed for Woods, Stuart/Stone Barrington/Book 09 - Dirty Work/Dirty Work - 01.mp3 2021-10-27 00:15:48 WARN [AudioFileScanner] No Tracks for audiobook kv60xbk1 2021-10-27 00:15:49 DEBUG [DB] Audiobook updated 1 2021-10-27 00:15:49 INFO [Scanner] "Dirty Work" was updated 2021-10-27 00:15:49 DEBUG [Scanner] Finished scanning file changes, results: [object Object] ``` No indication why the scan failed though. Unraid logs look the same.
Author
Owner

@jarrodCoombes commented on GitHub (Oct 27, 2021):

Ok, the issue was something broken in the MP3. I loaded it in audacity, then exported it out as a new MP3 (doubled in size, but that's ok). It was ingested just fine.

Would it be possible to add to the error on things like this. Something along the lines of "File in folder appears to be an MP3, but the scan failed on it."

Basically it looks like an MP3, but smells like a 3 dogs standing on each other's shoulders under a very large trench coat, so we dunno what to do with it.

I can send you a copy of the bad MP3 if you want to see if you can work out what happened there.

@jarrodCoombes commented on GitHub (Oct 27, 2021): Ok, the issue was something broken in the MP3. I loaded it in audacity, then exported it out as a new MP3 (doubled in size, but that's ok). It was ingested just fine. Would it be possible to add to the error on things like this. Something along the lines of "File in folder appears to be an MP3, but the scan failed on it." Basically it looks like an MP3, but smells like a 3 dogs standing on each other's shoulders under a very large trench coat, so we dunno what to do with it. I can send you a copy of the bad MP3 if you want to see if you can work out what happened there.
Author
Owner

@advplyr commented on GitHub (Oct 29, 2021):

That is strange, the error thrown by ffmpeg probe must have been empty because it should print out the error log. I think with a scan log you brought up in #152 would help with this even though it wouldn't know about a specific error. At least with a scan log you would be able to see that the probe failed.
Closing this issue as it will be wrapped in with the scan log issue.

@advplyr commented on GitHub (Oct 29, 2021): That is strange, the error thrown by ffmpeg probe must have been empty because it should print out the error log. I think with a scan log you brought up in #152 would help with this even though it wouldn't know about a specific error. At least with a scan log you would be able to see that the probe failed. Closing this issue as it will be wrapped in with the scan log issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#71