[Bug]: Audiobookshelf doesn't work after reboot until manually shutting down and starting up container again #382

New issue

Open

opened 2025-10-14 16:21:53 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:21:53 -06:00

Owner

Originally created by @syriaz on 5/18/2025

What happened?

Installed audiobookshelf via docker compose. Then visited the URL at localhost:13378/audiobookshelf and set up the user and libraries. It worked fine.

Now after I reboot the raspberry pi 4b+ (arm64) with headless ubuntu 24.04, the container shows to be running. but for some reason the web UI loads endlessly and is not accessible.

The files are on an attached hard drive. Only if I do "docker compose down; docker compose up -d" it starts working again.

What did you expect to happen?

I expected audiobookshelf to actually work even after I reboot the raspberry pi 4b+ running headless ubuntu 24.04.

Steps to reproduce the issue

Reboot the raspberry pi 4b+ running headless ubuntu 24.04

Audiobookshelf version

2.23.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Chrome

Logs

Running in production mode.
Options: CONFIG_PATH=/config, METADATA_PATH=/metadata, PORT=80, HOST=0.0.0.0, SOURCE=docker, ROUTER_BASE_PATH=/audiobookshelf
[2025-05-18 17:31:44.885] INFO: === Starting Server ===
[2025-05-18 17:31:44.917] INFO: [Server] Init v2.23.0
[2025-05-18 17:31:44.918] INFO: [Server] Node.js Version: v20.19.2
[2025-05-18 17:31:44.920] INFO: [Server] Platform: linux
[2025-05-18 17:31:44.921] INFO: [Server] Arch: arm64
[2025-05-18 17:31:44.964] INFO: [Database] Initializing db at "/config/absdatabase.sqlite"
[2025-05-18 17:31:45.212] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-05-18 17:31:45.224] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-05-18 17:31:45.225] INFO: [Database] Db supports unaccent and unicode foldings
[2025-05-18 17:31:45.228] INFO: [Database] Db connection was successful
[2025-05-18 17:31:45.299] INFO: [MigrationManager] Database is already up to date.
[2025-05-18 17:31:46.085] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare
[2025-05-18 17:31:46.278] INFO: [Database] running ANALYZE
[2025-05-18 17:31:46.294] INFO: [Database] ANALYZE completed
[2025-05-18 17:31:46.310] INFO: [LogManager] Init current daily log filename: 2025-05-18.txt
[2025-05-18 17:31:46.363] INFO: [BackupManager] 0 Backups Found
[2025-05-18 17:31:46.366] INFO: [BackupManager] Auto Backups are disabled
[2025-05-18 17:31:46.459] INFO: [Watcher] Initializing watcher for "Audiobooks".
[2025-05-18 17:31:46.513] INFO: Listening on http://0.0.0.0:80
[2025-05-18 17:31:46.716] INFO: [Watcher] "Audiobooks" Ready

Additional Notes

I have tried delaying the docker containers start up in multiple ways, because I thought my attached hard drive wasn't ready when the container starts but that didn't fix the problem.

*Originally created by @syriaz on 5/18/2025* ### What happened? Installed audiobookshelf via docker compose. Then visited the URL at localhost:13378/audiobookshelf and set up the user and libraries. It worked fine. Now after I reboot the raspberry pi 4b+ (arm64) with headless ubuntu 24.04, the container shows to be running. but for some reason the web UI loads endlessly and is not accessible. The files are on an attached hard drive. Only if I do "docker compose down; docker compose up -d" it starts working again. ### What did you expect to happen? I expected audiobookshelf to actually work even after I reboot the raspberry pi 4b+ running headless ubuntu 24.04. ### Steps to reproduce the issue 1. Reboot the raspberry pi 4b+ running headless ubuntu 24.04 ### Audiobookshelf version 2.23.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Chrome ### Logs ```shell Running in production mode. Options: CONFIG_PATH=/config, METADATA_PATH=/metadata, PORT=80, HOST=0.0.0.0, SOURCE=docker, ROUTER_BASE_PATH=/audiobookshelf [2025-05-18 17:31:44.885] INFO: === Starting Server === [2025-05-18 17:31:44.917] INFO: [Server] Init v2.23.0 [2025-05-18 17:31:44.918] INFO: [Server] Node.js Version: v20.19.2 [2025-05-18 17:31:44.920] INFO: [Server] Platform: linux [2025-05-18 17:31:44.921] INFO: [Server] Arch: arm64 [2025-05-18 17:31:44.964] INFO: [Database] Initializing db at "/config/absdatabase.sqlite" [2025-05-18 17:31:45.212] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so [2025-05-18 17:31:45.224] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so [2025-05-18 17:31:45.225] INFO: [Database] Db supports unaccent and unicode foldings [2025-05-18 17:31:45.228] INFO: [Database] Db connection was successful [2025-05-18 17:31:45.299] INFO: [MigrationManager] Database is already up to date. [2025-05-18 17:31:46.085] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare [2025-05-18 17:31:46.278] INFO: [Database] running ANALYZE [2025-05-18 17:31:46.294] INFO: [Database] ANALYZE completed [2025-05-18 17:31:46.310] INFO: [LogManager] Init current daily log filename: 2025-05-18.txt [2025-05-18 17:31:46.363] INFO: [BackupManager] 0 Backups Found [2025-05-18 17:31:46.366] INFO: [BackupManager] Auto Backups are disabled [2025-05-18 17:31:46.459] INFO: [Watcher] Initializing watcher for "Audiobooks". [2025-05-18 17:31:46.513] INFO: Listening on http://0.0.0.0:80 [2025-05-18 17:31:46.716] INFO: [Watcher] "Audiobooks" Ready ``` ### Additional Notes I have tried delaying the docker containers start up in multiple ways, because I thought my attached hard drive wasn't ready when the container starts but that didn't fix the problem.