Hi, it seems that the Gentoo Planet is not even trying to index any posts from my blog feed. I can't see any HTTP request from Gentoo infra for a long time. Settings seems to be correct in the planet git repo. Can you please check? Thanks! Reproducible: Always
I can't see any errors in the planet/universe cron email, CCIng infra for someone to check further in the backend.
some time ago I got bug 569570, that was exactly the opposite of this bug: there where errors in the logs, but everything was fine from my side. maybe they are somewhat related?
I recall seeing that error in the mailed log, however that's no longer present. I don't have access to any other logs beyond the fetch log that's mailed to me and it doesn't include any errors for your blog, so we need to wait for someone from infra to look further.
I ran venus with the planet settings from git, only changing paths, and it indexed my blog properly.
Also, I spent some time investigating this yesterday, and found out that the OPML feed still lists the old feed URL: https://planet.gentoo.org/opml.xml
We need to wait for infra to investigate. The configuration looks correct (https://gitweb.gentoo.org/sites/planet.git/plain/configs/planet/rafaelmartins) and only infra has access to the box to check what is going on.
(In reply to Michael Palimaka (kensington) from comment #6) > We need to wait for infra to investigate. The configuration looks correct > (https://gitweb.gentoo.org/sites/planet.git/plain/configs/planet/ > rafaelmartins) and only infra has access to the box to check what is going > on. yeah, according to my testing the configs are all fine, and seems to be an infra problem. thanks for looking at it
I fixed this last night with help from jmbsvicetto. I'll explain the issue here for the record: The current URL in my planet configs used to be an S3 bucket, redirecting to another S3 bucket. At some point I moved it all to a personal server, removing the redirect, but venus was still hitting the old url (that still happened to be valid, I do not deleted the old S3 bugs), despite the planet configs. It happened because Amazon S3 redirects are HTTP 301, that means permanent redirects, and venus cached that info. I fixed the issue by making the old S3 bucket redirect back to the new URL, with 301, and now it works, even after I removed the redirects. And as the configured URLs and the final redirect URLs are the same, I think that things should work as expected now. A venus cache clean could still be useful, though.
