Closed
Bug 1164517
Opened 9 years ago
Closed 5 years ago
Clean out old and un-used feeds to prevent errors
Categories
(developer.mozilla.org Graveyard :: Code Cleanup, defect)
developer.mozilla.org Graveyard
Code Cleanup
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: groovecoder, Unassigned)
Details
The only feed items we display on the site are from Hacks. We can remove all the other bundles and feeds. Especially now that many are causing errors ... Old and un-used: Unable to fetch https://developer.mozilla.org/@api/deki/site/feed Removed/missing blog.mozilla.org feeds (failing since the move of blog.mozilla.org to WPEngine): Unable to fetch http://planet.firefox.com/mobile/rss20.xml Unable to fetch https://blog.mozilla.org/addons/feed/ Unable to fetch http://blog.mozilla.org/about_mozilla/feed/atom/
Reporter | ||
Comment 1•9 years ago
|
||
Hmm ... All of these feeds work except for the MDN one, which I deleted from the stage and prod servers. :cyliang - can you see any reason why the stage & prod cron hosts wouldn't be able to reach those planet.firefox.com and blog.mozilla.org urls? Maybe a netflow needs to be open or something? I'm still fine removing them, would just like to know why they're failing.
Flags: needinfo?(cliang)
Comment 2•9 years ago
|
||
I’m not sure why the feed links are failing. A quick test shows that they should, for the most part, work when invoked from the developer web heads. [1] Some questions: * How are the feed links being parsed? Is there some regular job that grabs new feeds? (I’m trying to see if I should be testing feed access from the celery nodes or some other part of the MDN infra.) * Do you know what user agent string you are emitting? (I can try running a wget that spoofs that agent.) In https://bugzilla.mozilla.org/show_bug.cgi?id=1160609#c16, we discovered that wp-engine apparently filters out UA strings it considers “harmful”. >_< planet.mozilla.org updated their code to emit a different user agent string. [1] When I attempt to grab the feeds via wget from the developer webheads, I succeed for the http feeds but not the https ones. That, I think, has to do with a bug in the version of wget running on those servers. (I can successfully grab the HTTPS feed from developeradm, which is running a newer version of wget.)
Flags: needinfo?(cliang)
Reporter | ||
Comment 3•9 years ago
|
||
* There's an 'update_feeds' cron job, which I think runs on the admin node? * Our feedparser package uses urllib2, which uses "Python-urllib/2.6" by default [1] as the user agent. I updated all the stage feeds [2] to https if possible. planet.firefox.com/mobile/rss20.xml does not respond on https. I deleted all the twitter feeds, as they're not available anymore. I'll keep an eye on the update_feeds emails to see if these changes fix the errors. [1] https://docs.python.org/2/library/urllib2.html#urllib2.Request [2] https://developer.allizom.org/admin/feeder/feed/
Reporter | ||
Comment 4•9 years ago
|
||
The error was down to only the http planet.firefox.com so I removed that from stage too.
Reporter | ||
Comment 5•9 years ago
|
||
Since I removed the planet feed, we're not getting so many errors. Still getting this one intermittently: http_app_kuma: 2015-05-14 08:30:15,858 kuma.feeder:ERROR Unable to fetch https://forums.addons.mozilla.org/feed.php Exception: <urlopen error The read operation timed out>: /data/developer/www/developer.mozilla.org/kuma/kuma/feeder/management/commands/update_feeds.py:176
Comment 6•5 years ago
|
||
I removed these feeds from production:
- tw-planetmozilla - http://twitter.com/statuses/user_timeline/39292665.rss
- amo-blog-comments - https://blog.mozilla.org/addons/comments/feed/
- tw-mozamo - http://twitter.com/statuses/user_timeline/15383463.rss
- tw-mozillaqa - http://twitter.com/statuses/user_timeline/24752152.rss
- tw-mozmobile - http://twitter.com/statuses/user_timeline/67033966.rss
- tw-mozillaweb - http://twitter.com/statuses/user_timeline/38209403.rss
- tw-mozhacks - http://twitter.com/statuses/user_timeline/45496942.rss
- moz-hacks-comments - https://hacks.mozilla.org/comments/feed/
I also removed feed bundles:
- twitter-addons
- twitter-apps
- twitter-mobile
- twitter-mozilla
- twitter-web
- updates-addons
- updates-mobile
- updates-mozilla
- updates-web
This just leaves the feed and bundle used on the Homepage:
- Feed moz-hacks - https://hacks.mozilla.org/feed/
- Bundle updates-moz-hacks - just moz-hacks
There is more cleanup to drop the Bundle abstraction and simplify the kuma/feeder app, but that's a different bug.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•