starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: 2.8.1 (Docker) Library Scan Fails Getting Repeated "alert number 12" in log file #1836

New Issue
Closed
opened 2026-04-24 23:59:28 +02:00 by adam · 9 comments
adam commented 2026-04-24 23:59:28 +02:00
Owner
Copy Link
Copy Source

Originally created by @freddyyeddy on GitHub (Mar 22, 2024).

Describe the issue

When triggering library scan (using NFS so I cant trust auto scans) It throws The Errors Below. Im gonna let it take forever and see if it finally finishes and detects the one New audiobook. After Looking at Debug log it looks like more work than dont (Second Image). So I suspect this could be a red herring.
image
image

Steps to reproduce the issue

  1. Manually Trigger Library Scan And Watch.

Audiobookshelf version

1.8.2

How are you running audiobookshelf?

Docker

Originally created by @freddyyeddy on GitHub (Mar 22, 2024). ### Describe the issue When triggering library scan (using NFS so I cant trust auto scans) It throws The Errors Below. Im gonna let it take forever and see if it finally finishes and detects the one New audiobook. After Looking at Debug log it looks like more work than dont (Second Image). So I suspect this could be a red herring. ![image](https://github.com/advplyr/audiobookshelf/assets/26309499/43ea4e05-f0ed-4ed9-8e4e-23f7a972f6c0) ![image](https://github.com/advplyr/audiobookshelf/assets/26309499/e9dcf276-3576-42f4-9206-4f7f4cff57c0) ### Steps to reproduce the issue 1. Manually Trigger Library Scan And Watch. ### Audiobookshelf version 1.8.2 ### How are you running audiobookshelf? Docker
adam added the bugconfig-issue labels 2026-04-24 23:59:28 +02:00
adam closed this issue 2026-04-24 23:59:28 +02:00
adam commented 2026-04-24 23:59:29 +02:00
Author
Owner
Copy Link
Copy Source

@freddyyeddy commented on GitHub (Mar 22, 2024):

Update With It finished (First Image) and picked up the new Book. But it seems needlessly long for a simple single book find. Has there been a change to the scan methodology that affects if pre-existing books are re-checked after updating. The second scan seems more reasonable (Second Image). So I assume It has to do with how the update process (re-pull/build container for latest version). If Im right might be worth updating the Change notes for clarity. Im closing this ticket myself as seems problem did not persist.
image
image

@freddyyeddy commented on GitHub (Mar 22, 2024): Update With It finished (First Image) and picked up the new Book. But it seems needlessly long for a simple single book find. Has there been a change to the scan methodology that affects if pre-existing books are re-checked after updating. The second scan seems more reasonable (Second Image). So I assume It has to do with how the update process (re-pull/build container for latest version). If Im right might be worth updating the Change notes for clarity. Im closing this ticket myself as seems problem did not persist. ![image](https://github.com/advplyr/audiobookshelf/assets/26309499/7bce7f82-8209-458a-8352-5c0e46f22473) ![image](https://github.com/advplyr/audiobookshelf/assets/26309499/be6ea68f-5566-4019-8bbd-fd31c1be8389)
adam commented 2026-04-24 23:59:29 +02:00
Author
Owner
Copy Link
Copy Source

@freddyyeddy commented on GitHub (Apr 6, 2024):

I seems this is still happening and I can no longer search Audible For Meta data either. I added another batch of audiobooks and the search seemed to do a full scan and take forever and threw the alert 112's

@freddyyeddy commented on GitHub (Apr 6, 2024): I seems this is still happening and I can no longer search Audible For Meta data either. I added another batch of audiobooks and the search seemed to do a full scan and take forever and threw the alert 112's
adam commented 2026-04-24 23:59:30 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Apr 6, 2024):

Looks like TLS error 112 is something specific to your setup, or an issue with Audnexus?

https://stackoverflow.com/questions/5671000/what-does-this-tls-alert-mean

@nichwall commented on GitHub (Apr 6, 2024): Looks like TLS error 112 is something specific to your setup, or an issue with Audnexus? https://stackoverflow.com/questions/5671000/what-does-this-tls-alert-mean
adam commented 2026-04-24 23:59:30 +02:00
Author
Owner
Copy Link
Copy Source

@freddyyeddy commented on GitHub (Apr 6, 2024):

I cant Seem to find any real reason for this to happen. All I did was update docker image to new version. Then it started happening. Got any tips for where to look. I basically turned off the firewall for the server. So I dont think its bocking there. I recently moved to using ngix proxy manager. But the reverse proxy has been fine there too. This happens when I attempt to search for a match.
image

@freddyyeddy commented on GitHub (Apr 6, 2024): I cant Seem to find any real reason for this to happen. All I did was update docker image to new version. Then it started happening. Got any tips for where to look. I basically turned off the firewall for the server. So I dont think its bocking there. I recently moved to using ngix proxy manager. But the reverse proxy has been fine there too. This happens when I attempt to search for a match. ![image](https://github.com/advplyr/audiobookshelf/assets/26309499/f5740a30-d852-4a25-abb8-58637fb8e2b3)
adam commented 2026-04-24 23:59:30 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Apr 7, 2024):

Are you getting this error using a local ip address?

@advplyr commented on GitHub (Apr 7, 2024): Are you getting this error using a local ip address?
adam commented 2026-04-24 23:59:31 +02:00
Author
Owner
Copy Link
Copy Source

@freddyyeddy commented on GitHub (Apr 7, 2024):

No I'm using a DNS to access the instance via reverse proxy (web socket
enabled).

@freddyyeddy commented on GitHub (Apr 7, 2024): No I'm using a DNS to access the instance via reverse proxy (web socket enabled).
adam commented 2026-04-24 23:59:31 +02:00
Author
Owner
Copy Link
Copy Source

@freddyyeddy commented on GitHub (Apr 7, 2024):

Checking Via Local IP:Port and still same same (Searched different book this time)
image

@freddyyeddy commented on GitHub (Apr 7, 2024): Checking Via Local IP:Port and still same same (Searched different book this time) ![image](https://github.com/advplyr/audiobookshelf/assets/26309499/9f1c9640-b5df-41c6-9319-3eb8bc90c5d3)
adam commented 2026-04-24 23:59:32 +02:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Sep 11, 2024):

After reviewing this issue, this appears to be a problem with your setup and not Audiobookshelf. This issue is being closed to keep the issue tracker focused on Audiobookshelf itself. Please reach out on the Audiobookshelf Discord for community support.
Some common search terms to help you find the solution to your problem:

  • Reverse proxy
  • Enabling websockets
  • SSL (https vs http)
  • Configuring a static IP
  • localhost versus IP address
  • hairpin NAT
  • VPN
  • firewall ports
  • public versus private network
  • bridge versus host mode
  • Docker networking
  • DNS (such as EAI_AGAIN errors)

After you have followed these steps, please post the solution or steps you followed to fix the problem to help others in the future, or show that it is a problem with Audiobookshelf so we can reopen the issue.

@github-actions[bot] commented on GitHub (Sep 11, 2024): After reviewing this issue, this appears to be a problem with your setup and not Audiobookshelf. This issue is being closed to keep the issue tracker focused on Audiobookshelf itself. Please reach out on the Audiobookshelf Discord for community support. Some common search terms to help you find the solution to your problem: - Reverse proxy - Enabling websockets - SSL (https vs http) - Configuring a static IP - `localhost` versus IP address - hairpin NAT - VPN - firewall ports - public versus private network - bridge versus host mode - Docker networking - DNS (such as EAI_AGAIN errors) After you have followed these steps, please post the solution or steps you followed to fix the problem to help others in the future, or show that it is a problem with Audiobookshelf so we can reopen the issue.
adam commented 2026-04-24 23:59:32 +02:00
Author
Owner
Copy Link
Copy Source

@freddyyeddy commented on GitHub (Sep 11, 2024):

No problem. I am unsure what directly was causing the issue but Its been
resolved. Thanks for the help and support. Sorry I left this go stale and
never followed up.

On Wed, Sep 11, 2024, 5:45 AM github-actions[bot] @.***>
wrote:

After reviewing this issue, this appears to be a problem with your setup
and not Audiobookshelf. This issue is being closed to keep the issue
tracker focused on Audiobookshelf itself. Please reach out on the
Audiobookshelf Discord for community support.
Some common search terms to help you find the solution to your problem:

  • Reverse proxy
  • Enabling websockets
  • SSL (https vs http)
  • Configuring a static IP
  • localhost versus IP address
  • hairpin NAT
  • VPN
  • firewall ports
  • public versus private network
  • bridge versus host mode
  • Docker networking
  • DNS (such as EAI_AGAIN errors)

After you have followed these steps, please post the solution or steps you
followed to fix the problem to help others in the future, or show that it
is a problem with Audiobookshelf so we can reopen the issue.

—
Reply to this email directly, view it on GitHub
https://github.com/advplyr/audiobookshelf/issues/2782#issuecomment-2343720320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGIXG6YSXWB7YEKERQO7ZVTZWBCOVAVCNFSM6AAAAABFCSELBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBTG4ZDAMZSGA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

@freddyyeddy commented on GitHub (Sep 11, 2024): No problem. I am unsure what directly was causing the issue but Its been resolved. Thanks for the help and support. Sorry I left this go stale and never followed up. On Wed, Sep 11, 2024, 5:45 AM github-actions[bot] ***@***.***> wrote: > After reviewing this issue, this appears to be a problem with your setup > and not Audiobookshelf. This issue is being closed to keep the issue > tracker focused on Audiobookshelf itself. Please reach out on the > Audiobookshelf Discord for community support. > Some common search terms to help you find the solution to your problem: > > - Reverse proxy > - Enabling websockets > - SSL (https vs http) > - Configuring a static IP > - localhost versus IP address > - hairpin NAT > - VPN > - firewall ports > - public versus private network > - bridge versus host mode > - Docker networking > - DNS (such as EAI_AGAIN errors) > > After you have followed these steps, please post the solution or steps you > followed to fix the problem to help others in the future, or show that it > is a problem with Audiobookshelf so we can reopen the issue. > > — > Reply to this email directly, view it on GitHub > <https://github.com/advplyr/audiobookshelf/issues/2782#issuecomment-2343720320>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGIXG6YSXWB7YEKERQO7ZVTZWBCOVAVCNFSM6AAAAABFCSELBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBTG4ZDAMZSGA> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> >
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug config-issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#1836
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?