[Bug]: Library Scan not completing - Socket Closed #2274

Closed
opened 2026-04-25 00:05:40 +02:00 by adam · 4 comments
Owner

Originally created by @sedgbeer on GitHub (Sep 25, 2024).

What happened?

When running a manual or cron scan I am getting a socket closed from the Web App and the log files are presenting an uncaught exception causing the scan to stop.

What did you expect to happen?

expected the library scan to complete

Steps to reproduce the issue

Audiobookshelf version

2.13.4

How are you running audiobookshelf?

Debian/PPA

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

2024-09-24 22:55:28.132

FATAL

[Server] Uncaught exception origin: uncaughtException, error: Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues at assert (node:internal/assert:14:11) at internalConnectMultiple (node:net:1118:3) at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18) at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1510:7) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:130:8) { code: 'ERR_INTERNAL_ASSERTION' }

Additional Notes

attempted to recreate the library. now only have 2 books showing.

Originally created by @sedgbeer on GitHub (Sep 25, 2024). ### What happened? When running a manual or cron scan I am getting a socket closed from the Web App and the log files are presenting an uncaught exception causing the scan to stop. ### What did you expect to happen? expected the library scan to complete ### Steps to reproduce the issue 1. ### Audiobookshelf version 2.13.4 ### How are you running audiobookshelf? Debian/PPA ### 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 2024-09-24 22:55:28.132 FATAL [Server] Uncaught exception origin: uncaughtException, error: Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues at assert (node:internal/assert:14:11) at internalConnectMultiple (node:net:1118:3) at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18) at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1510:7) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:130:8) { code: 'ERR_INTERNAL_ASSERTION' } ``` ### Additional Notes attempted to recreate the library. now only have 2 books showing.
adam added the bug label 2026-04-25 00:05:40 +02:00
adam closed this issue 2026-04-25 00:05:40 +02:00
Author
Owner

@sedgbeer commented on GitHub (Sep 25, 2024):

Update - issue looks to be related to the removal and readdition of books.
Lead up to the issues, I had identified and audio issue with a title I was listening to. faulty content was removed and the books removed from the library.
New content was located and placed back in the dir structure and a scan initiated.
The scan was never completed and the refreshed books also did not get readded.

I have worked round the issue by reverting to a backup of the LXC, and updated the book with a manual scan of the title.
This has also allowed the complete rescanning of the library.

@sedgbeer commented on GitHub (Sep 25, 2024): Update - issue looks to be related to the removal and readdition of books. Lead up to the issues, I had identified and audio issue with a title I was listening to. faulty content was removed and the books removed from the library. New content was located and placed back in the dir structure and a scan initiated. The scan was never completed and the refreshed books also did not get readded. I have worked round the issue by reverting to a backup of the LXC, and updated the book with a manual scan of the title. This has also allowed the complete rescanning of the library.
Author
Owner

@mikiher commented on GitHub (Sep 29, 2024):

It would be good to get more details and clear reproduction instructions:

  • Can you post the the Audiobookshelf log up to the crash? Please include all the log messages since server start.
  • Can you reproduce the crash? If so, can you please:
    • Set Audiobookshelf Log Level to debug
    • Reproduce the crash
    • Post the log containing the debug messages up to the crash?
@mikiher commented on GitHub (Sep 29, 2024): It would be good to get more details and clear reproduction instructions: - Can you post the the Audiobookshelf log up to the crash? Please include all the log messages since server start. - Can you reproduce the crash? If so, can you please: - Set Audiobookshelf Log Level to debug - Reproduce the crash - Post the log containing the debug messages up to the crash?
Author
Owner

@mikiher commented on GitHub (Oct 6, 2024):

@advplyr Since the reporter didn't respond, can you mark this as Unable to reproduce?

@mikiher commented on GitHub (Oct 6, 2024): @advplyr Since the reporter didn't respond, can you mark this as `Unable to reproduce`?
Author
Owner

@sedgbeer commented on GitHub (Oct 6, 2024):

Issues is not reproducible

@sedgbeer commented on GitHub (Oct 6, 2024): Issues is not reproducible
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2274