mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-03-02 22:46:55 -05:00
[Bug]: new issues since 2.3.0 #1248
Labels
No labels
authentication
awaiting release
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/audiobookshelf-advplyr#1248
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rweatherly on GitHub (Jul 16, 2023).
Describe the issue
A number of issues started showing up since upgrading to 2.3.0 via docker using docker compose
1.) meta data is now missing author and series info (rest is still there)
2.) on android app, for a series that I repopulated (after bug 1), the series page shows a 404 time error in the mobile app
3.) all settings reset to default
4.) all user sessions and listening history gone
Steps to reproduce the issue
Variety of issues, but are after simple docker compose down / pull / up
Audiobookshelf version
2.3.0
How are you running audiobookshelf?
Docker
@SilentStray commented on GitHub (Jul 16, 2023):
From this listed items, I can concur that I am experiencing issue #2 only.
Below is the log file incident when i try to view a series on mobile app.
[2023-07-16 09:05:10] INFO: [Watcher] "Main" Ready [2023-07-16 09:05:12] INFO: [Server] Socket Connected E89TongIHyHYrmCiAAAD [2023-07-16 09:05:54] INFO: [Server] Socket Connected EUVMH0uQultCiefvAAAF TypeError: Cannot read properties of undefined (reading 'checkCanAccessLibrary') at checkCanAccessLibraryItem (/server/objects/user/User.js:361:15) at Array.filter (<anonymous>) at ApiRouter.middleware (/server/controllers/SeriesController.js:73:49) at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5) at next (/node_modules/express/lib/router/route.js:144:13) at Route.dispatch (/node_modules/express/lib/router/route.js:114:3) at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5) at /node_modules/express/lib/router/index.js:284:15 at param (/node_modules/express/lib/router/index.js:365:14) at param (/node_modules/express/lib/router/index.js:376:14)@advplyr commented on GitHub (Jul 16, 2023):
@rweatherly Did you happen to get the server logs when the container started up? This is the only way for me to see what happened for your migration
@rweatherly commented on GitHub (Jul 16, 2023):
i stopped the container (backup the folder now), cause I was going to try and revert to the previous version. I'm not sure if the container logs are still there, do they persist after stopping ?
@advplyr commented on GitHub (Jul 16, 2023):
@rweatherly I think it depends on whether you removed the container or not. And how you are using docker. In the terminal you would do
docker ps -athen get the ID of the container. Thendocker logs <container id>@advplyr commented on GitHub (Jul 16, 2023):
You may want to wait until I put out a patch because I did identify a few things to fix. I'm going to try to get the patch out today
@advplyr commented on GitHub (Jul 16, 2023):
If you want to revert to the previous version you will need to extract the old database files in
/config/oldDb.zipand delete the/config/absdatabase.sqlitefile. That will put you right back to where you were until the patch@rweatherly commented on GitHub (Jul 16, 2023):
i use docker-compose, and that removed the container so docker ps -a doesn't list anything.
ok thanks, i was worried about the DB thing cause i saw something about a new one, i was thinking about going to my duplicati backup from the previous night, but that would make it easier..
i have a couple of other people looking to listen to books this morning so i want to try and get something that is working for them. i will make sure to save logs if i run through the upgrade process again
@advplyr commented on GitHub (Jul 16, 2023):
@SilentStray Your issue was reported in #1914 and I just fixed it for the upcoming patch
@BDaddyG commented on GitHub (Jul 16, 2023):
I also have issues after the upgrade. Mine are related to issue #1 meta data. "Series", "Collections", and "Authors" are all missing.
I was able to get the following partial logs (attached file)
AudioBookShelf_v2.3.0_upgrade_errors_redacted.txt
Docker running on unRAID
@captainnapalm commented on GitHub (Jul 16, 2023):
these are my errors. app won't start:
@Gauva1n commented on GitHub (Jul 16, 2023):
Running into the same issue after upgrading to v2.3.0 with the "JavaScript heap out of memory" error when the container is trying to start. Running Ubuntu Server 22.04.2 LTS, Docker version 20.10.21. Near identical logs.
@rweatherly commented on GitHub (Jul 16, 2023):
mine started, just had those listed issues.. here are my versions, for reference
OS: Raspberry Pi OS / Debian 11 (latest version all patches applied)
Docker version: 24.0.4, build 3713ee1
Compose version: 1.29.2
I did successfully roll back to the previous version (via backups)
If it would be helpful, I can do the update again to capture more data, just let me know what would be helpful
@Gauva1n commented on GitHub (Jul 16, 2023):
Tried rolling back to the backup I took of the latest version, and it started at least. But looks like the db is borked. Totally blank collections and getting the following from the application logs:
Edit: Meh, actually I cat'd out the database and I can see everything OK in there. App's just not connecting to it anymore.
@Hallo951 commented on GitHub (Jul 16, 2023):
I am running Abs without docker on Ubuntu Linux 22.04.2 and have just updated to the latest version. I also had everything reset to default and my audiobook library no longer exists. I have now started to re-read everything :(
@Gauva1n commented on GitHub (Jul 16, 2023):
Okay, got everything back again running v2.2.23. Read the release notes and saw there was a database upgrade in this version. After restoring the backup I took with
docker loadand updating my docker-compose file to use the local backup image, I found in an oldDb.zip archive in my /config folder. Moved all of the following folders in /config to a junk folder of /new-db-broken:authors
collections
feeds
libraries
libraryItems
playlists
series
sessions
settings
users
Made sure to stop the container, unzipped the oldDb.zip folder into the /config folder, restarted the container and now we're good back at v2.2.23 at least with all my items.
@rweatherly commented on GitHub (Jul 16, 2023):
if you were using the build in backup/restore, I believe you have to manually restore the old db, as this version introduced a new SQLlite db.. it should have been backed up to oldDb.zip..
I couldn't find it and used a duplicate restore, but advplyr mentioned a few posts back that it should have been backed up and stored
@Gauva1n commented on GitHub (Jul 16, 2023):
Yep, think I posted my last comment about the same time you did. Manual database restore worked for me, going to keep it at v2.2.23 for now.
@Hallo951 commented on GitHub (Jul 16, 2023):
Where can I find this oldDb.zip file for restoring the old library under Linux Ubuntu? I found the config and metadata folders under /usr/share/audiobookshelf but the oldDb.zip file is not there.... Can you help me?
@advplyr commented on GitHub (Jul 16, 2023):
I would suggest waiting for the patch I'm releasing shortly where I will put in instructions on what to do. Trying to revert and messing with other config files may cause more problems.
@Hallo951 commented on GitHub (Jul 16, 2023):
Ok, then I'll wait. My current situation is that I have updated to version 2.3.0 and everything has been reset to standard. I thought that I would now restore the old state and then wait for your patch, but if you have a better solution, I'd rather wait...
@advplyr commented on GitHub (Jul 16, 2023):
The patch notes will include instructions for you to restore to your old state. No data was lost for you, it just didn't go into the new database properly.
@advplyr commented on GitHub (Jul 16, 2023):
The patch is released with instructions on the fix: https://github.com/advplyr/audiobookshelf/releases/tag/v2.3.1
Basically you want to update, then stop the container, delete the
absdatabase.sqlitefile, then start the container. The database will be recreated from your old database.@captainnapalm commented on GitHub (Jul 16, 2023):
I followed your instructions, and I'm still getting the JavaScript heap out of memory. Here's the end of the logs:
Edit: took the container down again, and tried restarting to no avail:
@advplyr commented on GitHub (Jul 16, 2023):
@captainnapalm What is the size of the sqlite file?
@captainnapalm commented on GitHub (Jul 16, 2023):
@advplyr commented on GitHub (Jul 16, 2023):
What are you running Abs on? That shouldn't be very much memory to load that in.
To migrate back to v2.2.23 you can just unzip the
oldDb.zip. For those whereoldDb.zipisn't there you can just revert back. When upgrading in the future from v2.2.23 you will want to make sure/config/absdatabase.sqliteis deleted so it can be re-created.I'll be looking into reducing the memory usage further tomorrow
@captainnapalm commented on GitHub (Jul 16, 2023):
Running in Ubuntu server 22.04, Docker 24.0.4, docker-compose 1.29.2, with 128GB RAM, Ryzen 9 5950X, etc.
@captainnapalm commented on GitHub (Jul 16, 2023):
Is this how
/config/should look after unzipping theoldDB.zip?@Gauva1n commented on GitHub (Jul 16, 2023):
Confirming that v2.3.1 is still failing for me as well with the same heap allocation limit error. Tried deleting the absdatabase.sqlite file as per instructions after updating but before launching.
Successfully rolled back to v2.2.23 once more, the manual database reversion method is still working. Not sure if it's worth mentioning, but this time around after upgrading, all the directories and files in /config were deleted but nothing was recreated except for the new absdatabase.sqlite file. With v2.3.0 it at least recreated the contents of those files/folders.
My instance of ABS is running on a small headless server, only 8GB of RAM but 5GB currently free. Ubuntu 22.04, Docker Compose version v2.19.1, Docker 20.10.21. My working absdatabase.sqlite file is 3.9 MB.
@roadkingvrod commented on GitHub (Jul 16, 2023):
It appears that after 2.3, it broke using a cifs share for the config folder....
@freakadings commented on GitHub (Jul 17, 2023):
From the above on my instance only 2.) occured, the patched fixed it for me. Thank you very much!
@Hallo951 commented on GitHub (Jul 17, 2023):
I have now updated to the new version under Linux Ubuntu and followed your instructions, but I do not have this oldDb.zip file (see screenshot). What else can I do?
@warwolf commented on GitHub (Jul 17, 2023):
Im also experiencing bug 2, everything works fine in web interface tho but not on android app.
This is Docker log when trying to access series:
TypeError: Cannot read properties of undefined (reading 'checkCanAccessLibrary') at checkCanAccessLibraryItem (/server/objects/user/User.js:361:15) at Array.filter (<anonymous>) at ApiRouter.middleware (/server/controllers/SeriesController.js:73:49) at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5) at next (/node_modules/express/lib/router/route.js:144:13) at Route.dispatch (/node_modules/express/lib/router/route.js:114:3) at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5) at /node_modules/express/lib/router/index.js:284:15 at param (/node_modules/express/lib/router/index.js:365:14) at param (/node_modules/express/lib/router/index.js:376:14)@skyzuma commented on GitHub (Jul 17, 2023):
try the latest server version / patch ... 2.3.1 ... its fixed ...
@warwolf commented on GitHub (Jul 17, 2023):
Yea sry about that, i was sure i did pull the new image but for some reason it was still 2.3.0.
Can confirm it works fine in 2.3.1
@Hallo951 commented on GitHub (Jul 17, 2023):
Is it possible that this olddb.zip file is located in a different path under Linux ubuntu than in the Audiobookshelf folder? for me it simply does not exist....
@trixor commented on GitHub (Jul 17, 2023):
Found this thread, and I'm experiencing the same challenge waiting to pull in 2.3.1
Seems to provide me with 2.3.0 when I force-recreate it.
find . -name "*.zip"yields no results :(@JakobTischler commented on GitHub (Jul 17, 2023):
FWIW, I still get the heap limit bug with 2.3.1 (docker on Synology).
@advplyr commented on GitHub (Jul 17, 2023):
Memory crash should be fixed in v2.3.2
Let me know how it goes
@captainnapalm commented on GitHub (Jul 19, 2023):
Can confirm, upgraded from 2.2.23 to 2.3.3 and all seems to be working as expected. Thanks @advplyr!
@captainnapalm commented on GitHub (Jul 20, 2023):
Nope, I spoke too soon. I am able to get a few hours of running, but I still run into the
Javascript heap out of memoryerror. Container restarts withunless-stoppedand it will run again for a few hours and then hit this same issue.@advplyr commented on GitHub (Jul 20, 2023):
@captainnapalm I was sent 2 databases that had this issue which helped me to recreate the OOM crash and push up fixes for it. I'm not able to reproduce any crashes now on 2.3.3. If you or anyone on here still having that issue wants to send me a copy of your DB I'll see if I can reproduce it. Or if you can find some pattern for when the crash happens that would be helpful also.
@mattj415 commented on GitHub (Jul 20, 2023):
I had the OOM error with 2.3.1 and rolled back. Didn't get a chance to try 2.3.2 but 2.3.3 fixes the issue for me!
Thanks so much for this awesome project!
@roadkingvrod commented on GitHub (Jul 20, 2023):
In my case, I was running the config on a CIFS external share. 2.3.0 broke that with the DB error. 2.3.3 it seems to work great.
From: advplyr @.>
Sent: Thursday, July 20, 2023 3:07 PM
To: advplyr/audiobookshelf @.>
Cc: roadkingvrod @.>; Comment @.>
Subject: Re: [advplyr/audiobookshelf] [Bug]: new issues since 2.3.0 (Issue #1913)
@captainnapalm https://github.com/captainnapalm I was sent 2 databases that had this issue which helped me to recreate the OOM crash and push up fixes for it. I'm not able to reproduce any crashes now on 2.3.3. If you or anyone on here still having that issue wants to send me a copy of your DB I'll see if I can reproduce it. Or if you can find some pattern for when the crash happens that would be helpful also.
—
Reply to this email directly, view it on GitHub https://github.com/advplyr/audiobookshelf/issues/1913#issuecomment-1644675666 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL553RC4DS54GIVY422QX53XRGTW5ANCNFSM6AAAAAA2L5UO7M .
You are receiving this because you commented. https://github.com/notifications/beacon/AL553RGZWPMCJSNB4VJYDITXRGTW5A5CNFSM6AAAAAA2L5UO7OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCA7BFE.gif Message ID: @.*** @.***> >
@captainnapalm commented on GitHub (Jul 21, 2023):
Where can I send my db? To your email dev@advplyr.com? I'm basically seeing the OOM error every 4 hours right now.
@advplyr commented on GitHub (Jul 21, 2023):
@captainnapalm Yeah you can send to that email or you can DM me in the Discord server. If you zip the sqlite file it should reduce the file size a lot.