-
Notifications
You must be signed in to change notification settings - Fork 20
Releases being reported multiple times #11
Comments
That is indeed strange. I will take a look to see if its anything obvious, haven't encountered this get myself though. If possible could you check the status.log created in same folder as the py file and paste a couple of the socket error full logs. |
The logs are gigantic (several megabytes for just a day). I wasn't aware, but evidently it was sitting there constantly reconnecting for the better part of 24 hours. I'm surprised I didn't get a g:line. Here is a paste of about 10 minutes worth of logs. For what its worth, I also have autodl-irssi set up on the same box connecting to different servers and it was solid the entire day. |
the logs should only do 5*5 mb log files. Thanks for the log file, will try and figure out whats going on here. PS. You should likely change your torrent pass on those sites as that information is visible in those log files. |
Arg I scrubbed IP and nicks, totally forgot about torrent passes. Let me know if you need anything else. |
Any progress on this? I have the same issue with some trackers, and if I leave it running a few hours eventually every release gets sent to sonarr a bunch of times. I have set up a cronjob to restart the service every few hours as a workaround. |
I'm having an issue with released being reported multiple times. Here is an example
http://i.imgur.com/FUEBo7y.png
You can see that they are in fact being reported to Sonarr multiple times as well:
http://i.imgur.com/ctKS2NC.png
I'm not sure if this is related or not, but I'm also receiving socket errors multiple times per hours:
http://i.imgur.com/pWEuolz.png
The text was updated successfully, but these errors were encountered: