-
Notifications
You must be signed in to change notification settings - Fork 442
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]: Uncaught Exception stops server, and cannot be restarted without quitting tray and restarting. #2998
Comments
This probably belongs in https://github.com/mikiher/audiobookshelf-windows, I don't recognize that folder path. @mikiher any thoughts on this one? |
I have not encountered a crash like this. |
I can upload the full log tomorrow evening when I return from travel.
…On Thu, May 23, 2024, 16:29 mikiher ***@***.***> wrote:
I have not encountered a crash like this.
It seems weird that this happens randomly while the server is idle. Can
you please share the full log file?
It is usually located at %LOCALAPPDATA%\AudiobookshelfTray\logfile.txt
—
Reply to this email directly, view it on GitHub
<#2998 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGJGS5TGXMBMKQZ3LRUOMDZDZGTDAVCNFSM6AAAAABIER6UXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXHE3DMNJRHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Logfile attached |
OK, it looks like you have a periodic podcast check running every hour, but it didn't seem to have been running while the crash happened (the last check ended 3 minutes before the crash), so it doesn't seem likely that it's connected to it. This crash happened internally in the pkg code (pkg is the component that bundles Node and the server into a windows executable and is responsible for loading and running it), and unfortunately it is hard to understand from the exception what happened, except that it was trying to access its temp directory and it didn't exist. You said this happens periodically, however I only found one uncaught exception in the log. |
I believe it has happened three times since installation, which was about a
month or so ago. I can look through the previous logs and see if there are
more instances.
…On Tue, May 28, 2024, 06:07 mikiher ***@***.***> wrote:
OK, it looks like you have a periodic podcast check running every hour,
but it didn't seem to have been running while the crash happened (the last
check ended 3 minutes before the crash), so it doesn't seem likely that
it's connected to it.
This crash happened internally in the pkg code (pkg is the component that
bundles Node and the server into a windows executable and is responsible
for loading and running it), and unfortunately it is hard to understand
from the exception what happened, except that it was trying to access its
temp directory and it didn't exist.
You said this happens periodically, however I only found one uncaught
exception in the log.
Did the server have additional crashes during the period covered by the
log? How often does this happen?
—
Reply to this email directly, view it on GitHub
<#2998 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGJGS3QKZLSUTDGGBJTZD3ZERJO3AVCNFSM6AAAAABIER6UXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUHAZTMNJWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Any update on this? |
Thanks for the reminder. I just looked through the logs, and have found the following other instances:
Please let me know if you need anything else. It has not happened again at this point. |
I have also seen this a few times, here is the latest one, it happened when I stopped a playback in the web player.
|
If either of you have gathered any more information about this issue please follow up. I'm not sure what to do with this one. |
I have not had this happen again lately, but we have also had a few complete software updates, so it hasn't run for that long without restarting anyway. You can close this if no one has any other opinions. |
I switch to running from source on windows and have not seen this happen again. |
Thanks for the reminder. Let's keep this bug open a little more. I'd like to bring this up with the Yao-pkg maintainer. |
What happened?
Periodically, my server will stop and cannot be started again unless the tray application is exited and restarted. I checked the corresponding AudioBookShelf log, and there were no entries for the time specified, as well as three minutes before the incident.
What did you expect to happen?
Basically, I expected the system to not crash when it was idle. I don't know why it was looking for a file in the APPDATA\Temp directory.
Steps to reproduce the issue
Audiobookshelf version
2.9.0
How are you running audiobookshelf?
Windows Tray App
What OS is your Audiobookshelf server hosted from?
Windows
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
The text was updated successfully, but these errors were encountered: