details also T153930

@Reception123 I appreciate that you made this a ticket rather than IRC ping. Yesterday i looked briefly and the source of the custom domain list, https://meta.miraheze.org/wstats/miraheze.txt was not available due to maintenance on the miraheze side and that was the root cause of it. I see that it is back now. Theoretically this should just work again, but this is just started by cron once per week. Also i can probably improve the update script so that if the source URL isn't available temporarily it does not result in all of them disappearing from the table. Currently it relies on that too much, first dumps the current content and then tries to import new content.

@Dzahn Thank you for the reply. We migrated our database yesterday so that was probably the reason of the downtime of the list. Hopefully it will work next time the cron runs

@Reception123 P.S. "Labs-project-Wikistats" is the right tag, but the "Analytics" tags are not. The Analytics "Wikistats" is something completely different and completely different people get notfied. It's just for historic reasons that both share this name.

OK. I'll note that down for next time.

I have manually started the script that cron should start to debug this. It found 1137 wikis, is then updating 1109 wikis. Is that the difference and the number of custom wikis? No, there are 44 custom wikis in https://meta.miraheze.org/wstats/custom.txt...

Is it possible that there was a change on your side that means now custom wikis are reported in BOTH, the regular list AND the custom list? It seems like that is the root cause when looking at the result of my import script.

Change 340618 had a related patch set uploaded (by Dzahn):
[operations/debs/wikistats] miraheze auto import: change order, custom domains first

https://gerrit.wikimedia.org/r/340618

Change 340618 merged by Dzahn:
[operations/debs/wikistats] miraheze auto import: change order, custom domains first

https://gerrit.wikimedia.org/r/340618