-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: #1971
Comments
I have set the logging level to debug to see if I can capture a future crash. |
Can you capture the logs from the container instead of using the ones from Abs? There is an uncaught exception that isn't going to show up in Abs logs, we need to get the container logs to see it. |
I use unraid, and it looks like it is not persisting the logs past a container restart. I will investigate more. |
I took another look and I found the issue. There is media progress on your mobile device that is trying to sync with the server but the linked library item no longer exists. The next server release will fix this, otherwise you can try finding the downloaded item on your device that is the problem and removing it. |
ok. I had some books but they had issues, so I removed and readded them, so that might be the issue. I have had some issues previously where I click the remove from continue listening and it will remove, but next login it will be back, if that tries to sync that might exacerbate the issue. Thanks for the quick response. |
this happened again, and I was able to find the issue in the docker file: I thought that it could have been based on a library item that isn't existing, but reading through it seems to be syncing while playing a file, unless that is a red herring and the app is syncing some items that aren't currently in progress at some point. {"log":"[2023-08-02 17:58:16] DEBUG: [PlaybackSessionManager] Updating progress for "The Dresden Files 05.0 - Death Masks" with current time 25608.999470000002 (previously 25609.575439620003) (PlaybackSessionManager.js:165)\n","stream":"stdout","time":"2023-08-02T17:58:16.939926514Z"} |
I've been having crashes with a very similar error, which seems to be caused by two of my users' apps uploading progress. Log Dump
Specifically, I think these lines probably point to the problem:
It looks like maybe a race condition in the check for an existing session when multiple |
Fixed in v2.4.0 Although the latest server version is now 2.4.1. This is for the original issue you can let me know if it is still causing issues on 2.4.1 |
Describe the issue
Server crashed. restarted docker and worked fine so far. I will try to find how to increase logging levels
Steps to reproduce the issue
here are the logs before and after crash:
{"timestamp":"2023-07-26 11:19:08","source":"Logger.js:114","message":"[Watcher] Initializing watcher for "AudioBooks".","levelName":"INFO","level":2}
{"timestamp":"2023-07-26 11:19:08","source":"Logger.js:114","message":"Listening on port :80","levelName":"INFO","level":2}
{"timestamp":"2023-07-26 11:19:22","source":"Logger.js:114","message":"[Watcher] "AudioBooks" Ready","levelName":"INFO","level":2}
{"timestamp":"2023-07-26 12:27:14","source":"Logger.js:114","message":"[Server] Socket Connected NuM9CpJnNyIQ9npMAAAB","levelName":"INFO","level":2}
{"timestamp":"2023-07-26 12:27:14","source":"Logger.js:126","message":"[MeController] syncLocalMediaProgress invalid local media progress object no library item [object Object]","levelName":"ERROR","level":4}
{"timestamp":"2023-07-26 21:24:36","source":"Logger.js:114","message":"=== Starting Server ===","levelName":"INFO","level":2}
{"timestamp":"2023-07-26 21:24:36","source":"Logger.js:114","message":"[Server] Init v2.3.3","levelName":"INFO","level":2}
Audiobookshelf version
2.3.3
How are you running audiobookshelf?
Docker
The text was updated successfully, but these errors were encountered: