[Bug]: Crash during scan - Error: read ENOTCONN #2958

Closed
opened 2026-04-25 00:12:18 +02:00 by adam · 2 comments
Owner

Originally created by @NathanTheGr8 on GitHub (Aug 18, 2025).

What happened?

Hello, I updated my sever to Debian 13 recently and I encountered an issue scanning my library. I have deleted and redeployed ABS via docker from scratch and still encountered the issue on a "clean build" were I deleted my config and metadata volumes. This is similar to issue 1443, so I assume it is something about my files? I tried removing the 2 most recent books I added but it didn't help. The file system is backed by zfs so I don't believe the files corrupted.

Version 2.28.0

Docker Deploy String
docker run -d \ -p 13378:80 \ --restart unless-stopped \ -v /storage/docker/abs/config:/config \ -v /storage/docker/abs/metadata:/metadata \ -v /storage/share/AudioBooks:/audiobooks \ -v /storage/share/podcasts:/podcasts \ --name audiobookshelf \ ghcr.io/advplyr/audiobookshelf

What did you expect to happen?

For the library to scan

Steps to reproduce the issue

  1. Install ABS with the docker command above. Create a new library and try to scan it.

Audiobookshelf version

2.28.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

[2025-08-18 02:15:03.175] INFO: [Server] Initializing new server

[2025-08-18 02:15:08.893] INFO: [LocalAuth] User "root" logged in from ip ::ffff:192.168.3.1

[2025-08-18 02:15:09.137] INFO: [SocketAuthority] Socket Connected to /audiobookshelf/socket.io 4vwAGFu1rBh9mQKMAAAD

[2025-08-18 02:15:58.044] INFO: [Watcher] Initializing watcher for "Audio Books".

[2025-08-18 02:15:58.333] INFO: [Watcher] "Audio Books" Ready

[2025-08-18 02:16:01.724] INFO: [LibraryScanner] Library metadata precedence changed since last scan. From [Unset] to [folderStructure,audioMetatags,nfoFile,txtFiles,opfFile,absMetadata]

[2025-08-18 02:16:01.724] INFO: [LibraryScanner] Starting (forced) library scan e81e4260-3cdb-4805-936a-b4bbacfda418 for Audio Books

[2025-08-18 02:16:02.354] FATAL: [Server] Uncaught exception origin: uncaughtException, error: Error: read ENOTCONN

    at tryReadStart (node:net:707:20)

    at Socket._read (node:net:722:5)

    at Readable.read (node:internal/streams/readable:739:12)

    at Socket.read (node:net:777:39)

    at new Socket (node:net:491:12)

    at Object.Socket (node:net:360:41)

    at createSocket (node:internal/child_process:335:14)

    at ChildProcess.spawn (node:internal/child_process:450:23)

    at spawn (node:child_process:762:9)

    at /app/server/libs/nodeFfprobe/index.js:11:18 {

  errno: -107,

  code: 'ENOTCONN',

  syscall: 'read'

}

node:events:502

      throw er; // Unhandled 'error' event

      ^

Error: read ENOTCONN

    at tryReadStart (node:net:707:20)

    at Socket._read (node:net:722:5)

    at Readable.read (node:internal/streams/readable:739:12)

    at Socket.read (node:net:777:39)

    at new Socket (node:net:491:12)

    at Object.Socket (node:net:360:41)

    at createSocket (node:internal/child_process:335:14)

    at ChildProcess.spawn (node:internal/child_process:450:23)

    at spawn (node:child_process:762:9)

    at /app/server/libs/nodeFfprobe/index.js:11:18

Emitted 'error' event on Socket instance at:

    at emitErrorNT (node:internal/streams/destroy:169:8)

    at emitErrorCloseNT (node:internal/streams/destroy:128:3)

    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {

  errno: -107,

  code: 'ENOTCONN',

  syscall: 'read'

}

Node.js v20.19.4

Running in production mode.

Options: CONFIG_PATH=/config, METADATA_PATH=/metadata, PORT=80, HOST=undefined, SOURCE=docker, ROUTER_BASE_PATH=/audiobookshelf

[2025-08-18 02:16:05.715] INFO: === Starting Server ===

Additional Notes

No response

Originally created by @NathanTheGr8 on GitHub (Aug 18, 2025). ### What happened? Hello, I updated my sever to Debian 13 recently and I encountered an issue scanning my library. I have deleted and redeployed ABS via docker from scratch and still encountered the issue on a "clean build" were I deleted my config and metadata volumes. This is similar to issue [1443](https://github.com/advplyr/audiobookshelf/issues/1443), so I assume it is something about my files? I tried removing the 2 most recent books I added but it didn't help. The file system is backed by zfs so I don't believe the files corrupted. Version 2.28.0 Docker Deploy String ` docker run -d \ -p 13378:80 \ --restart unless-stopped \ -v /storage/docker/abs/config:/config \ -v /storage/docker/abs/metadata:/metadata \ -v /storage/share/AudioBooks:/audiobooks \ -v /storage/share/podcasts:/podcasts \ --name audiobookshelf \ ghcr.io/advplyr/audiobookshelf ` ### What did you expect to happen? For the library to scan ### Steps to reproduce the issue 1. Install ABS with the docker command above. Create a new library and try to scan it. ### Audiobookshelf version 2.28.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 [2025-08-18 02:15:03.175] INFO: [Server] Initializing new server [2025-08-18 02:15:08.893] INFO: [LocalAuth] User "root" logged in from ip ::ffff:192.168.3.1 [2025-08-18 02:15:09.137] INFO: [SocketAuthority] Socket Connected to /audiobookshelf/socket.io 4vwAGFu1rBh9mQKMAAAD [2025-08-18 02:15:58.044] INFO: [Watcher] Initializing watcher for "Audio Books". [2025-08-18 02:15:58.333] INFO: [Watcher] "Audio Books" Ready [2025-08-18 02:16:01.724] INFO: [LibraryScanner] Library metadata precedence changed since last scan. From [Unset] to [folderStructure,audioMetatags,nfoFile,txtFiles,opfFile,absMetadata] [2025-08-18 02:16:01.724] INFO: [LibraryScanner] Starting (forced) library scan e81e4260-3cdb-4805-936a-b4bbacfda418 for Audio Books [2025-08-18 02:16:02.354] FATAL: [Server] Uncaught exception origin: uncaughtException, error: Error: read ENOTCONN at tryReadStart (node:net:707:20) at Socket._read (node:net:722:5) at Readable.read (node:internal/streams/readable:739:12) at Socket.read (node:net:777:39) at new Socket (node:net:491:12) at Object.Socket (node:net:360:41) at createSocket (node:internal/child_process:335:14) at ChildProcess.spawn (node:internal/child_process:450:23) at spawn (node:child_process:762:9) at /app/server/libs/nodeFfprobe/index.js:11:18 { errno: -107, code: 'ENOTCONN', syscall: 'read' } node:events:502 throw er; // Unhandled 'error' event ^ Error: read ENOTCONN at tryReadStart (node:net:707:20) at Socket._read (node:net:722:5) at Readable.read (node:internal/streams/readable:739:12) at Socket.read (node:net:777:39) at new Socket (node:net:491:12) at Object.Socket (node:net:360:41) at createSocket (node:internal/child_process:335:14) at ChildProcess.spawn (node:internal/child_process:450:23) at spawn (node:child_process:762:9) at /app/server/libs/nodeFfprobe/index.js:11:18 Emitted 'error' event on Socket instance at: at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { errno: -107, code: 'ENOTCONN', syscall: 'read' } Node.js v20.19.4 Running in production mode. Options: CONFIG_PATH=/config, METADATA_PATH=/metadata, PORT=80, HOST=undefined, SOURCE=docker, ROUTER_BASE_PATH=/audiobookshelf [2025-08-18 02:16:05.715] INFO: === Starting Server === ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:12:18 +02:00
adam closed this issue 2026-04-25 00:12:18 +02:00
Author
Owner

@NathanTheGr8 commented on GitHub (Aug 21, 2025):

I found that removing two books recently added fixed the issue crashing issue. These were two books ripped from my Audible library with Libation. The are owned by the user running ABS. I added the --user 33 \ to my docker command above. It may be that any new book I add will crash the server and there is nothing special about these two. I found the crash log and will attach it.

crash_logs.txt

root@pve2:/storage/share# ls -lG Knife\ of\ Dreams\ \[B002V0K6BA\]/ total 896645 -rw-r--r-- 1 www-data 2587 Aug 15 09:54 'Knife of Dreams: Book Eleven of The Wheel of Time [B002V0K6BA].cue' -rw-r--r-- 1 www-data 924618776 Aug 15 09:54 'Knife of Dreams: Book Eleven of The Wheel of Time [B002V0K6BA].m4b' root@pve2:/storage/share# ls -lG The\ Gathering\ Storm\ \[B002UZN0PA\]/ total 914995 -rw-r--r-- 1 www-data 4147 Aug 15 11:03 'The Gathering Storm: Book Twelve of the Wheel of Time [B002UZN0PA].cue' -rw-r--r-- 1 www-data 944245500 Aug 15 11:08 'The Gathering Storm: Book Twelve of the Wheel of Time [B002UZN0PA].m4b' root@pve2:/storage/share#

@NathanTheGr8 commented on GitHub (Aug 21, 2025): I found that removing two books recently added fixed the issue crashing issue. These were two books ripped from my Audible library with Libation. The are owned by the user running ABS. I added the `--user 33 \` to my docker command above. It may be that any new book I add will crash the server and there is nothing special about these two. I found the crash log and will attach it. [crash_logs.txt](https://github.com/user-attachments/files/21909242/crash_logs.txt) `root@pve2:/storage/share# ls -lG Knife\ of\ Dreams\ \[B002V0K6BA\]/ total 896645 -rw-r--r-- 1 www-data 2587 Aug 15 09:54 'Knife of Dreams: Book Eleven of The Wheel of Time [B002V0K6BA].cue' -rw-r--r-- 1 www-data 924618776 Aug 15 09:54 'Knife of Dreams: Book Eleven of The Wheel of Time [B002V0K6BA].m4b' root@pve2:/storage/share# ls -lG The\ Gathering\ Storm\ \[B002UZN0PA\]/ total 914995 -rw-r--r-- 1 www-data 4147 Aug 15 11:03 'The Gathering Storm: Book Twelve of the Wheel of Time [B002UZN0PA].cue' -rw-r--r-- 1 www-data 944245500 Aug 15 11:08 'The Gathering Storm: Book Twelve of the Wheel of Time [B002UZN0PA].m4b' root@pve2:/storage/share# `
Author
Owner

@NathanTheGr8 commented on GitHub (Aug 21, 2025):

The issue seems to have been apparmor. Proxmox 9 / Debian Trixie had it enabled by default and was causign my issues. Adding this to my run command fixed my issue. I assume this means it isn't an issue with the app and will close the issue.

--security-opt apparmor:unconfined \

@NathanTheGr8 commented on GitHub (Aug 21, 2025): The issue seems to have been apparmor. Proxmox 9 / Debian Trixie had it enabled by default and was causign my issues. Adding this to my run command fixed my issue. I assume this means it isn't an issue with the app and will close the issue. --security-opt apparmor:unconfined \
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2958