[Bug]: Crash during scan #914

Closed
opened 2026-04-24 23:25:54 +02:00 by adam · 5 comments
Owner

Originally created by @EardyMaen on GitHub (Jan 26, 2023).

Describe the issue

I installed it on my raspberry pi 3 B+ via Docker.
When I try to initially scan my library the whole container crashes

audiobookshelf@2.2.12 start
node index.js

Config /config /metadata
[2023-01-26 11:43:39] INFO: === Starting Server ===
[2023-01-26 11:43:39] INFO: [Server] Init v2.2.12
[2023-01-26 11:43:39] INFO: [DB] 0 Collections Loaded
[2023-01-26 11:43:39] INFO: [DB] 0 Playlists Loaded
[2023-01-26 11:43:39] INFO: [DB] 0 Series Loaded
[2023-01-26 11:43:40] INFO: [DB] 1 Users Loaded
[2023-01-26 11:43:40] INFO: [DB] 1 Libraries Loaded
[2023-01-26 11:43:40] INFO: [DB] 14 Authors Loaded
[2023-01-26 11:43:41] INFO: [DB] 64 Library Items Loaded
[2023-01-26 11:43:41] INFO: [BackupManager] 0 Backups Found
[2023-01-26 11:43:41] INFO: [BackupManager] Auto Backups are disabled
[2023-01-26 11:43:41] INFO: [LogManager] Init current daily log filename: 2023-01-26.txt
[2023-01-26 11:43:41] INFO: [Watcher] Initializing watcher for "Audiobooks".
[2023-01-26 11:43:41] INFO: Listening on port :80
[2023-01-26 11:43:45] INFO: [Server] Socket Connected Ja1SRbrv7q2MQO2cAAAB
[2023-01-26 11:43:57] INFO: [Watcher] "Audiobooks" Ready
[2023-01-26 11:44:03] INFO: [Scanner] Starting library scan lscan_3non0t84yd99zrjom7 for Audiobooks
/server/libs/njodb/index.js:103
throw error;
^

Error: read ENOTCONN
at tryReadStart (node:net:662:20)
at Socket._read (node:net:673:5)
at Socket.Readable.read (node:internal/streams/readable:487:10)
at Socket.read (node:net:729:39)
at new Socket (node:net:449:12)
at Object.Socket (node:net:318:41)
at createSocket (node:internal/child_process:335:14)
at ChildProcess.spawn (node:internal/child_process:452:23)
at spawn (node:child_process:733:9)
at /server/libs/nodeFfprobe/index.js:11:18
Emitted 'error' event on Socket instance at:
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -107,
code: 'ENOTCONN',
syscall: 'read'
}

docker-compose.yml
version: "3.5"
services:
audiobookshelf:
container_name: audiobookshelf
image: ghcr.io/advplyr/audiobookshelf:latest
environment:
- AUDIOBOOKSHELF_UID=99
- AUDIOBOOKSHELF_GID=100
ports:
- 13378:80
volumes:
- /media/eardy/NAS/Audiobooks:/audiobooks
- /media/eardy/NAS/data/audiobookshelf/config:/config
- /media/eardy/NAS/data/audiobookshelf/metadata:/metadata

Steps to reproduce the issue

  1. Start container
  2. Login
  3. Start library scan

Audiobookshelf version

2.2.12

How are you running audiobookshelf?

Docker

Originally created by @EardyMaen on GitHub (Jan 26, 2023). ### Describe the issue I installed it on my raspberry pi 3 B+ via Docker. When I try to initially scan my library the whole container crashes > audiobookshelf@2.2.12 start > node index.js Config /config /metadata [2023-01-26 11:43:39] INFO: === Starting Server === [2023-01-26 11:43:39] INFO: [Server] Init v2.2.12 [2023-01-26 11:43:39] INFO: [DB] 0 Collections Loaded [2023-01-26 11:43:39] INFO: [DB] 0 Playlists Loaded [2023-01-26 11:43:39] INFO: [DB] 0 Series Loaded [2023-01-26 11:43:40] INFO: [DB] 1 Users Loaded [2023-01-26 11:43:40] INFO: [DB] 1 Libraries Loaded [2023-01-26 11:43:40] INFO: [DB] 14 Authors Loaded [2023-01-26 11:43:41] INFO: [DB] 64 Library Items Loaded [2023-01-26 11:43:41] INFO: [BackupManager] 0 Backups Found [2023-01-26 11:43:41] INFO: [BackupManager] Auto Backups are disabled [2023-01-26 11:43:41] INFO: [LogManager] Init current daily log filename: 2023-01-26.txt [2023-01-26 11:43:41] INFO: [Watcher] Initializing watcher for "Audiobooks". [2023-01-26 11:43:41] INFO: Listening on port :80 [2023-01-26 11:43:45] INFO: [Server] Socket Connected Ja1SRbrv7q2MQO2cAAAB [2023-01-26 11:43:57] INFO: [Watcher] "Audiobooks" Ready [2023-01-26 11:44:03] INFO: [Scanner] Starting library scan lscan_3non0t84yd99zrjom7 for Audiobooks /server/libs/njodb/index.js:103 throw error; ^ Error: read ENOTCONN at tryReadStart (node:net:662:20) at Socket._read (node:net:673:5) at Socket.Readable.read (node:internal/streams/readable:487:10) at Socket.read (node:net:729:39) at new Socket (node:net:449:12) at Object.Socket (node:net:318:41) at createSocket (node:internal/child_process:335:14) at ChildProcess.spawn (node:internal/child_process:452:23) at spawn (node:child_process:733:9) at /server/libs/nodeFfprobe/index.js:11:18 Emitted 'error' event on Socket instance at: at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { errno: -107, code: 'ENOTCONN', syscall: 'read' } docker-compose.yml version: "3.5" services: audiobookshelf: container_name: audiobookshelf image: ghcr.io/advplyr/audiobookshelf:latest environment: - AUDIOBOOKSHELF_UID=99 - AUDIOBOOKSHELF_GID=100 ports: - 13378:80 volumes: - /media/eardy/NAS/Audiobooks:/audiobooks - /media/eardy/NAS/data/audiobookshelf/config:/config - /media/eardy/NAS/data/audiobookshelf/metadata:/metadata ### Steps to reproduce the issue 1. Start container 2. Login 3. Start library scan ### Audiobookshelf version 2.2.12 ### How are you running audiobookshelf? Docker
adam added the bug label 2026-04-24 23:25:54 +02:00
adam closed this issue 2026-04-24 23:25:55 +02:00
Author
Owner

@HubGon commented on GitHub (Feb 4, 2023):

I have this problem too. Dont know if it is a coincidence, but i observed it always with audiobooks that have more than 50 audiofiles.

Used version: 2.2.14 with ppa installation

@HubGon commented on GitHub (Feb 4, 2023): I have this problem too. Dont know if it is a coincidence, but i observed it always with audiobooks that have more than 50 audiofiles. Used version: 2.2.14 with ppa installation
Author
Owner

@HubGon commented on GitHub (Feb 6, 2023):

Have found a Workaround. Upload the audiobook via FTP (Filezilla etc.), but only 50 audiofiles. Let audiobookshelf scan your libary (partial-scan is sufficient). Then upload the next 50 files. etc

@HubGon commented on GitHub (Feb 6, 2023): Have found a Workaround. Upload the audiobook via FTP (Filezilla etc.), but only 50 audiofiles. Let audiobookshelf scan your libary (partial-scan is sufficient). Then upload the next 50 files. etc
Author
Owner

@advplyr commented on GitHub (Feb 11, 2023):

I think this is related to #1498 and will be fixed in the next release from PR #1484

@advplyr commented on GitHub (Feb 11, 2023): I think this is related to #1498 and will be fixed in the next release from PR #1484
Author
Owner

@advplyr commented on GitHub (Feb 12, 2023):

Hopefully fixed in v2.2.15

.. but let me know!

@advplyr commented on GitHub (Feb 12, 2023): *Hopefully* fixed in [v2.2.15](https://github.com/advplyr/audiobookshelf/releases/tag/v2.2.15) .. but let me know!
Author
Owner

@EardyMaen commented on GitHub (Feb 13, 2023):

yep, that fixed it. thanks

@EardyMaen commented on GitHub (Feb 13, 2023): yep, that fixed it. thanks
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#914