Closed juanra closed 1 month ago
Feramance
commented
4 months ago Could you kindly send over your config file so I can check please? And also set debug level to trace and run it till you get the error again and attach the full log for the Radarr instance with the error
juanra
commented
4 months ago Thanks for your quick reply @Feramance.
I'm attaching my config file without my credentials here: config.toml.txt I commented the sections that I don't use (i.e. Anime, Radar-4k)
For more context I have qBitrr deployed on a TrueNAS server using TrueCharts, and I followed their recommendations here: TrueCharts.
I will share the log with trace level soon.
Feramance
commented
4 months ago I'll be able to take a better look once I have the logs
juanra
commented
4 months ago Sorry for my delay in responding.
I am attaching the log with the trace enabled here: qbitrr_qbitrr-659d67d78c-994g5_qbitrr.log
Btw, I don't see any error in this log... :/
Feramance
commented
4 months ago Realistically, unless you see the error again, I can't really look for a solution given that error should never even be possible to reach
norimicry
commented
1 month ago Just want to say I'm experiencing the same thing with Custom formats after following the Trash Guides guide on adding custom formats. Seeing the same errors but unable to find them after enabling Trace log levels.
Feramance
commented
1 month ago Just want to say I'm experiencing the same thing with Custom formats after following the Trash Guides guide on adding custom formats. Seeing the same errors but unable to find them after enabling Trace log levels.
Hi, just to clarify. Whether you have custom formats configured or not is irrelevant in this scope as Radarr/sonarr handle those, qBitrr just reads the value for minimum and the value of the final score for the individual file.
To be able to debug this I'll need your logs showing this error occurring please. If you can first make sure you're on the latest version, set logs to trace and then send over the entire logs folder and config file. Thanks
norimicry
commented
1 month ago Stack trace consistently throws in ERROR level immediately upon starting:
STARTING QBITRR
Process Process-1:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/urllib3/response.py", line 737, in _error_catcher
yield
File "/usr/local/lib/python3.10/site-packages/urllib3/response.py", line 1184, in read_chunked
self._update_chunk_length()
File "/usr/local/lib/python3.10/site-packages/urllib3/response.py", line 1116, in _update_chunk_length
raise InvalidChunkLength(self, line) from None
urllib3.exceptions.InvalidChunkLength: InvalidChunkLength(got length b'HTTP/1.1 200 OK\r\n', 0 bytes read)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 816, in generate
yield from self.raw.stream(chunk_size, decode_content=True)
File "/usr/local/lib/python3.10/site-packages/urllib3/response.py", line 1040, in stream
yield from self.read_chunked(amt, decode_content=decode_content)
File "/usr/local/lib/python3.10/site-packages/urllib3/response.py", line 1172, in read_chunked
with self._error_catcher():
File "/usr/local/lib/python3.10/contextlib.py", line 153, in __exit__
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.10/site-packages/urllib3/response.py", line 764, in _error_catcher
raise ProtocolError(f"Connection broken: {e!r}", e) from e
urllib3.exceptions.ProtocolError: ("Connection broken: InvalidChunkLength(got length b'HTTP/1.1 200 OK\\r\\n', 0 bytes read)", InvalidChunkLength(got length b'HTTP/1.1 200 OK\r\n', 0 bytes read))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/multiprocess/process.py", line 314, in _bootstrap
self.run()
File "/usr/local/lib/python3.10/site-packages/multiprocess/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.10/site-packages/qBitrr/arss.py", line 4447, in run_search_loop
years, years_count = self.get_year_search()
File "/usr/local/lib/python3.10/site-packages/qBitrr/arss.py", line 4399, in get_year_search
episodes = self.client.get_episode(s["id"], True)
File "/usr/local/lib/python3.10/site-packages/pyarr/sonarr.py", line 86, in get_episode
return self._get(
File "/usr/local/lib/python3.10/site-packages/pyarr/request_handler.py", line 81, in _get
res = self.session.get(
File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 602, in get
return self.request("GET", url, **kwargs)
File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 747, in send
r.content
File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 899, in content
self._content = b"".join(self.iter_content(CONTENT_CHUNK_SIZE)) or b""
File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 818, in generate
raise ChunkedEncodingError(e)
requests.exceptions.ChunkedEncodingError: ("Connection broken: InvalidChunkLength(got length b'HTTP/1.1 200 OK\\r\\n', 0 bytes read)", InvalidChunkLength(got length b'HTTP/1.1 200 OK\r\n', 0 bytes read))I understand custom formats are irrelevant but error only started appearing after adding custom formats. Stack trace indicates an issue with Sonarr.
Feramance
commented
1 month ago I see, this is an indication of an issue in the communication between sonarr and qBitrr. The error is a chunk encoding error which is a result of a bad response from sonarr
norimicry
commented
1 month ago Correct. I am seeing several
[2024-05-15 18:29:28] [pid: 8][tid:139816677288832] WARNING : qBitrr.Sonarr-TV : Could not connect to http://sonarr.ix-sonarr.svc.cluster.local:8989
[2024-05-15 18:29:28] [pid: 8][tid:139816677288832] ERROR : qBitrr.Sonarr-TV : Could not connect to http://sonarr.ix-sonarr.svc.cluster.local:8989
[2024-05-15 18:29:28] [pid: 8][tid:139816677288832] CRITICAL: qBitrr.Sonarr-TV : Failed to connected to the Arr instance, sleeping for 0:05:00errors though my configuration for Sonarr is correct, set up the same as Radarr, and has not changed in qBitrr. Is this a Sonarr problem then?
Feramance
commented
1 month ago Could be network, Url or apikey. I'd suggest first making 100% sure your URL and apikey are correct, then proceeding to ensure everything is running well in the network
norimicry
commented
1 month ago Reinstalled both, got a few more errors, restarted qbitrr a few times, and then it seemed to pick up the connection. Not sure why qbitrr was struggling to pick up a connection to Sonarr. Both are hosted on the same machine and connection through internal DNS names via the k8s network. Seems to be processing Sonarr releases for now.
Feramance
commented
1 month ago Good to hear, don't hesitate to reopen or open another ticket if any other issues crop up
Hey, thanks for this amazing script.
I'm trying to understand what's wrong with the configuration I made, because I'm getting the following error...
I understand that at the beginning it is related to a connection. And then there is an issue with the customFormat variable.
Could you guide me to correct what I need to correct?