sabnzbd / sabnzbd

SABnzbd - The automated Usenet download tool

Home Page:http://sabnzbd.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

wait_for_dfolder should add log entry prior to execution.

irctrakz opened this issue · comments

Description

With this latest release (4.2.0) the docker image would hang. Tracked it down to having the flag wait_for_dfolder set to true and the folder no longer existing. Would be a wonderful addition if sabnzbd could write a log message prior to checking these folders exist (I know you do highlight the potential for a hang in the docs):

2024-01-04 11:09:08,772::INFO::[SABnzbd:1145] --------------------------------
2024-01-04 11:09:08,773::INFO::[SABnzbd:1146] SABnzbd.py-4.2.0
2024-01-04 11:09:08,773::INFO::[SABnzbd:1156] Commit = 4e7e44e25fed1f71eba3cd2e93bd3107fab912a4
2024-01-04 11:09:08,775::INFO::[SABnzbd:1158] Full executable path = /app/sabnzbd/SABnzbd.py
2024-01-04 11:09:08,775::INFO::[SABnzbd:1159] Arguments = "/app/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "::"
2024-01-04 11:09:08,775::INFO::[SABnzbd:1160] Python-version = 3.11.6 (main, Oct 13 2023, 15:52:55) [GCC 13.1.1 20230722]
2024-01-04 11:09:08,776::INFO::[SABnzbd:1161] Dockerized = True
2024-01-04 11:09:08,776::INFO::[SABnzbd:1162] CPU architecture = x86_64
2024-01-04 11:09:08,782::INFO::[SABnzbd:1165] Platform = posix - Linux-4.14.22-x86_64-with
2024-01-04 11:09:08,783::INFO::[SABnzbd:1171] Preferred encoding = UTF-8
2024-01-04 11:09:08,783::INFO::[SABnzbd:1193] SSL version = OpenSSL 3.1.4 24 Oct 2023
2024-01-04 11:09:08,786::INFO::[SABnzbd:1202] Certifi version = 2023.11.17
2024-01-04 11:09:08,787::INFO::[SABnzbd:1203] Loaded additional certificates from /lsiopy/lib/python3.11/site-packages/certifi/cacert.pem
2024-01-04 11:09:08,787::INFO::[SABnzbd:1213] Using INI file /config/sabnzbd.ini

set your sab logging to debug, click wrench > logging level

Can't do that if the container is in a hung state!

Set it then restart, or stop and change it in .ini.

Right, but I guess my ask here is, for a potentially breaking configuration it would seem to make sense to have that log message at a higher log level (or whatever log level the default is)?

Sure, we can change it to Info level.