Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RSS Feeds fail to update #11327

Closed
rspierenburg opened this issue Oct 3, 2019 · 17 comments
Closed

RSS Feeds fail to update #11327

rspierenburg opened this issue Oct 3, 2019 · 17 comments
Labels
RSS RSS-related issues/changes

Comments

@rspierenburg
Copy link

rspierenburg commented Oct 3, 2019

Please provide the following information

qBittorrent version and Operating System

Qbitorrent v4.1.8 - Windows 10

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

RSS Feed fails to update

What is the expected behavior

RSS Feed updates after a period of time, and filtered content gets downloaded.

Steps to reproduce

Setup RSS feed, update will work the first time but will not work again.

Extra info(if any)

It seems more like the RSS feed hangs on update. I've tried two separate RSS feeds and both have the same result. The only way to re-update the feed is to completely shutdown Qbitorrent and restart it which allows the feeds to be updated and downloads begin.

Cannot find a log with reference to RSS feeds.

@topernicus
Copy link

I'm having a similar issue. The RSS feeds will update as per the Feeds Refresh Interval setting, but after a few hours of continuous uptime, the feeds stop updating.

I'll try to capture some logs next time it happens, but all that really shows in the Execution Log is the expected periodic 'RSS feed at 'xxx' updated. Added n new articles.' when it's working, then nothing when it stops. Other events continue to be logged normally, so it's like the thread handling the RSS Feed Updates just dies.

I've tried manually updating the feeds when this happens and they don't update via that method either. The only solution once the RSS feeds stop updating is to close and restart the app, which is much less than ideal.

I'm currently running Windows 10 Pro version 1903 build 18362.418 and qBittorrent v4.1.9.1.

@topernicus
Copy link

Here's a copy of my execution log. Hopefully it's helpful, but due to lack of info being logged I'm not sure how it would be. My current config has a 20 minute refresh set for the RSS feeds.

Hopefully this is the best place to provide this info. Perhaps @glassez can comment?

11/14/2019 5:04 AM - qBittorrent v4.1.9.1 started
11/14/2019 5:04 AM - qBittorrent is trying to listen on any interface port: 8999
11/14/2019 5:04 AM - Peer ID: -qB4191-
11/14/2019 5:04 AM - HTTP User-Agent is 'qBittorrent/4.1.9.1'
11/14/2019 5:04 AM - DHT support [OFF]
11/14/2019 5:04 AM - Local Peer Discovery support [OFF]
11/14/2019 5:04 AM - PeX support [OFF]
11/14/2019 5:04 AM - Anonymous mode [ON]
11/14/2019 5:04 AM - Encryption support [FORCED]
11/14/2019 5:04 AM - Embedded Tracker [OFF]
11/14/2019 5:04 AM - UPnP / NAT-PMP support [ON]
11/14/2019 5:04 AM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Wed Nov 6 05:56:32 2019.
11/14/2019 5:04 AM - Options were saved successfully.
11/14/2019 5:04 AM - qBittorrent is successfully listening on interface :: port: TCP/8999
11/14/2019 5:04 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/8999
11/14/2019 5:04 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/8999
11/14/2019 5:04 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 5:04 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999
11/14/2019 5:04 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: TCP/8999
11/14/2019 5:04 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: UDP/8999
11/14/2019 5:04 AM - RSS feed at '[redacted]' updated. Added 0 new articles.
11/14/2019 5:04 AM - RSS feed at '[redacted]' updated. Added 0 new articles.
11/14/2019 5:24 AM - RSS feed at '[redacted]' updated. Added 7 new articles.
11/14/2019 5:24 AM - RSS feed at '[redacted]' updated. Added 0 new articles.
11/14/2019 5:46 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 5:46 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999
11/14/2019 6:04 AM - RSS feed at '[redacted]' updated. Added 8 new articles.
11/14/2019 6:05 AM - RSS feed at '[redacted]' updated. Added 0 new articles.
11/14/2019 6:24 AM - RSS feed at '[redacted]' updated. Added 1 new articles.
11/14/2019 6:24 AM - RSS feed at '[redacted]' updated. Added 0 new articles.
11/14/2019 6:28 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 6:28 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999
11/14/2019 6:44 AM - RSS feed at '[redacted]' updated. Added 0 new articles.
11/14/2019 7:10 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 7:10 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999
11/14/2019 7:52 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 7:52 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999
11/14/2019 8:34 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 8:34 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999
11/14/2019 9:16 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: TCP/8999
11/14/2019 9:16 AM - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: UDP/8999

@glassez
Copy link
Member

glassez commented Nov 15, 2019

I've tried manually updating the feeds when this happens and they don't update via that method either.

What exactly does happen? How feed icons look when it stops working and when you try to refresh it manually? Please provide some screenshots.

@topernicus
Copy link

I remember it stuck as the
image icons before I press the update all button or right-click->update on the individual feed. Pressing the button or using the context menu to update appears to have no effect.

Next time my RSS feed updates stop responding, I'll verify and provide screenshots.

@glassez
Copy link
Member

glassez commented Nov 15, 2019

Next time my RSS feed updates stop responding, I'll verify and provide screenshots.

Also please try to access your feeds using different software (e.g. web browser) when it stops updating next time.

@glassez glassez added the RSS RSS-related issues/changes label Nov 15, 2019
@glassez
Copy link
Member

glassez commented Nov 15, 2019

@topernicus, I suppose your RSS feeds are secret/private and you can't send me their URLs for testing, isn't it?

@topernicus
Copy link

@glassez Just trying to retain some anonymity. I'll send you the RSS urls privately if you'd like.

RSS feeds stopped updating at 6:50a this morning.
image

The appearance of the feeds in the RSS tab when in this state.
image

Attempting to update the feeds has no visual impact in the UI, nor does it update the Execution Log.
I can copy the feed urls via the context menu, paste them into my browser, and they load normally in the browser.

@glassez
Copy link
Member

glassez commented Nov 24, 2019

It's really weird. Seems like network requests never finished (neither successfully nor erroneously). Or maybe it hangs on parsing step?
This would be easy to understand if I managed to reproduce this problem on my computer.
Or maybe I need to add some intermediate logging?.. Won't these additional messages be annoying?

@glassez
Copy link
Member

glassez commented Nov 24, 2019

@topernicus, can you test your feeds on another machine (e.g. your friend computer)?

@topernicus
Copy link

Additional logging could assist with fixing issues, but I agree that it could be annoying for regular use. I was a little surprised that there isn't a 'verbose logging' option for qBittorrent that would enable additional logging.

I do have one more computer that I could attempt to test the feeds on. I'll let you know when I have information regarding that.

@topernicus
Copy link

I haven't had a chance to attempt to reproduce this issue on a 2nd computer, but I have had some success in finding an interim solution on my main PC.

I'm currently using a SOCKS5 proxy, which is configured on the Connection tab inside the Settings/Options. By checking the "Use proxy only for torrents" option, it has eliminated the issue with RSS feeds freezing up.

With this configuration, I will randomly have some torrents not connect to trackers immediately, sometimes requiring an app restart, but nowhere near the level of what I was experiencing with the RSS feeds.

Perhaps the actual issue is related to qBittorrent's proxy implementation or my proxy service provider. Unfortunately, I won't be able to share any of the proxy details other than what I have already shared above.

@rspierenburg
Copy link
Author

rspierenburg commented Dec 3, 2019 via email

@Metzlmane
Copy link

I have the same error.. after closing and restarting qbittorrent the ned downloads appear in the queue

@microka
Copy link

microka commented Oct 3, 2020

Same here. #11168

@Thadah
Copy link

Thadah commented Feb 15, 2021

Issue still happens in qBittorrent 4.3.1, the only way of solving it is restarting the service completely

Screenshot_20210215_105627

@glassez
Copy link
Member

glassez commented Feb 15, 2021

Issue still happens in qBittorrent 4.3.1, the only way of solving it is restarting the service completely

Please provide corresponding log messages.

@ghost
Copy link

ghost commented Jul 25, 2022

This issue has been closed for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

@ghost ghost closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RSS RSS-related issues/changes
Projects
None yet
Development

No branches or pull requests

6 participants