Where is the log file for warnings and errors of sabnzbd queue?

[abu3safeer]

Hello everyone,

I had some broken files in my queue, and there were some error and warnings, I left them to later.

the next day I wanted to fix them, but looks like it only have the latest 20 warnings, I cannot see anything before, are they stored in log file for warnings?
I cannot see any, or they does not exists?

[safihre]

https://sabnzbd.org/wiki/advanced/directory-setup
The log_dir has your logs.

[abu3safeer]

Thanks

[abu3safeer]

Found them, can I customize a separate file for each log level?

[abu3safeer]

Hmm, I cannot find these messages in the log file

[sander]

Did you check inside sabnzbd.log?

Because when I add a broken .NZB to SAB, SAB does tell it in the GUI and in sabnzbd.log, for example

Code: Select all

2024-04-02 17:44:50,607::WARNING::[nzbstuff:787] Invalid NZB file broken.nzb, skipping (error: not well-formed (invalid token): line 9, column 0)

full logging in sabnzbd.log:

Code: Select all

2024-04-02 17:44:50,604::INFO::[nzbparser:87] Attempting to add broken.nzb
2024-04-02 17:44:50,605::INFO::[filesystem:747] Creating directories: /home/sander/Downloads/incomplete/broken
2024-04-02 17:44:50,606::INFO::[filesystem:747] Creating directories: /home/sander/Downloads/incomplete/broken/__ADMIN__
2024-04-02 17:44:50,606::INFO::[filesystem:1240] Saving /home/sander/Downloads/incomplete/broken/__ADMIN__/broken.nzb.gz
2024-04-02 17:44:50,607::INFO::[notifier:157] Sending notification: Warning - Invalid NZB file broken.nzb, skipping (error: not well-formed (invalid token): line 9, column 0) (type=warning, job_cat=None)
2024-04-02 17:44:50,607::WARNING::[nzbstuff:787] Invalid NZB file broken.nzb, skipping (error: not well-formed (invalid token): line 9, column 0)
2024-04-02 17:44:50,607::INFO::[nzbstuff:788] Traceback: 
Traceback (most recent call last):
  File "/usr/share/sabnzbdplus/sabnzbd/nzbstuff.py", line 784, in __init__
    sabnzbd.nzbparser.nzbfile_parser(full_nzb_path, self)
  File "/usr/share/sabnzbdplus/sabnzbd/nzbparser.py", line 378, in nzbfile_parser
    for _, element in xml.etree.ElementTree.iterparse(nzb_fh):
  File "/usr/lib/python3.10/xml/etree/ElementTree.py", line 1253, in iterator
    yield from pullparser.read_events()
  File "/usr/lib/python3.10/xml/etree/ElementTree.py", line 1324, in read_events
    raise event
  File "/usr/lib/python3.10/xml/etree/ElementTree.py", line 1296, in feed
    self._parser.feed(data)
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 9, column 0
2024-04-02 17:44:50,607::INFO::[nzbstuff:1806] [sabnzbd.nzbstuff.__init__] Purging data for job broken (delete_all_data=True)
2024-04-02 17:44:50,607::DEBUG::[articlecache:152] Purging 0 articles from the cache/disk
2024-04-02 17:44:50,608::DEBUG::[filesystem:986] Removing dir recursively /home/sander/Downloads/incomplete/broken

[abu3safeer]

Yes, I checked, just INFO messages, not warning or error

[abu3safeer]

I had to check them line by line, I was able to find the error messages, but no warning was there, on all the log files.

[sander]

We can spend more and more time on that ... or we can spend time on your original remark:

"the next day I wanted to fix them"

My question to you: how do you want to fix them?