mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: No start after update from 2.3.1 to 2.3.2 of audiobookshelf with linux directly (without docker or simmilar) #1259
Reference in New Issue
Block a user
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 @Hallo951 on GitHub (Jul 18, 2023).
Describe the issue
Hi,
oh man, my problems don't stop after the update from 2.2.23 with abs. I use abs with linux ubuntu without docker. In the version 2.2.23 abs ran with me without problems. I updated abs first from version 2.2.23 to version 2.3.0 with the known problem that my database was not migrated. An update to version 2.3.1 unfortunately did not bring my data back, because the file olddb.zip was missing under linux ubuntu for whatever reason. But in the version 2.3.1 it ran then first again, after I have read all my data again.
Just now I have updated from version 2.3.1 to version 2.3.2. Now abs does not work at all, or is in an infinite loop when starting. My little mini computer is now always running at high speed because it tries to start abs all the time but it doesn't work. I have now turned off the computer from abs. The abs update went through without any problems. I have attached the linux log file to identify the error.
How do I get abs to run again without losing all my data? @advplyr can you help me?
Logfiles:
syslog.log
apport.log
Steps to reproduce the issue
Audiobookshelf version
2.3.2
How are you running audiobookshelf?
Debian/PPA
@kaiminator commented on GitHub (Jul 18, 2023):
got the same with docker/docker-compose
Attaching to Audiobookshelf\ Audiobookshelf | \ Audiobookshelf | <--- Last few GCs ---> Audiobookshelf | Audiobookshelf | Audiobookshelf | <--- JS stacktrace ---> Audiobookshelf | Audiobookshelf | Audiobookshelf | # Audiobookshelf | # Fatal javascript OOM in GC during deserialization Audiobookshelf | # Audiobookshelf | Audiobookshelf exited with code 133@Maxklos commented on GitHub (Jul 18, 2023):
I got the Error:
[Error: SQLITE_CONSTRAINT: FOREIGN KEY constraint failed]but i think it is a similar ProblemIn the Changenotes is a hint for the solution -> v2.3.2
I renamed my
config/absdatabase.sqlitefile toabsdatabase.sqlite.oldand restarted the Docker Container.Now my ABD Server is running again.
@kaiminator commented on GitHub (Jul 18, 2023):
tried it before - does not work for me
Attaching to Audiobookshelf
Audiobookshelf |
Audiobookshelf | <--- Last few GCs --->
Audiobookshelf |
Audiobookshelf |
Audiobookshelf | <--- JS stacktrace --->
Audiobookshelf |
Audiobookshelf |
Audiobookshelf | #
Audiobookshelf | # Fatal javascript OOM in GC during deserialization
Audiobookshelf | #
Audiobookshelf |
Audiobookshelf exited with code 133
@Hallo951 commented on GitHub (Jul 18, 2023):
Unfortunately, that didn't work for me either. The error remains the same... @advplyr do you have another idea?
@derkington commented on GitHub (Jul 18, 2023):
Same problem for me on Linux (not a container). My logs show the same as what has been reported in the syslog file attached by Hallo951. I have stopped the audiobookshelf service for now.
@CoryM commented on GitHub (Jul 19, 2023):
In 2.3.2 added NODE_OPTIONS=--max-old-space-size=8096 to the Dockerfile. this causes node to grab 8 gigs of ram and then release it on startup.
Add this to your docker-compose.yaml file
If your using "docker run" then add bellow to work around the issue.
-e "NODE_OPTIONS=--max-old-space-size=1024"-- EDIT --
I run mine on a 2G Raspberry Pi 4 and could not run it, had to find out why.
@cdmatter commented on GitHub (Jul 19, 2023):
I was getting the same errors as @kaiminator with my docker instance of audiobookshelf. Applying the environment edit to my docker compose file as suggested by @CoryM fixed my issue and now my audiobookshlef container is running again! I am running Armbian with OMV6 installed (using the openmediavault-compose plugin for docker) on an ODROID HC2 (similar to an XU4). Thanks!
@Hallo951 commented on GitHub (Jul 19, 2023):
Hmm, nice if this works under Docker but how do I solve the problem directly under Linux Ubuntu?
@kaiminator commented on GitHub (Jul 19, 2023):
Can confirm this works under raspbian/arm/pi 4
@Hallo951 commented on GitHub (Jul 19, 2023):
I don't know if it helps but here I found a post about setting a node option on Linux. I'm not a computer expert on Linux directley, so I can't do much with it, but maybe the link helps to solve the problem.
Link: https://stackoverflow.com/questions/56982005/where-do-i-set-node-options-max-old-space-size-2048
Edit: Can it be that one can enter here in the line ExecStart that somehow?
Edit2: Or alternatively directly in the Environmental File? Can you just write the command -e "NODE_OPTIONS=--max-old-space-size=1024" in there and it works?
@Hallo951 commented on GitHub (Jul 19, 2023):
Ha, I solved it. Adudiobookshelf (Abs) is now running again under Linux directly (without docker or ....). Jeppi :)
My procedure and solution was as follows:
For a better overview here is a screenshot of my environment file:

With this I was able to fix the error. And the great thing is, I don't know how he did it, but my complete progress is back too. Great!!!
@advplyr For future versions, could you make it so that this NODE_OPTIONS is automatically set in the environment file?
@advplyr commented on GitHub (Nov 10, 2023):
We don't want to require users to have 8GB of available space in order to install Abs