search

advplyr / audiobookshelf

Self-hosted audiobook and podcast server
https://audiobookshelf.org
GNU General Public License v3.0
6.17k stars 431 forks source link

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

Open freddyyeddy opened 5 months ago

freddyyeddy commented 5 months ago

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

freddyyeddy commented 5 months ago

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 5 months ago

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

nichwall commented 5 months ago

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

freddyyeddy commented 5 months ago

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

advplyr commented 4 months ago

Are you getting this error using a local ip address?

freddyyeddy commented 4 months ago

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

freddyyeddy commented 4 months ago

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