<html><head></head><body><div class="ydp4ff0d37cyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">I see so that's the reason why my IPv6 only box didn't got an update and to solve it temporary i added an IPv4 address</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">So now I will remove that IPv4 address and see what happens</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Cheers,</div><div dir="ltr" data-setdir="false">Biton</div><div><br></div>
</div><div id="ydp8e69439eyahoo_quoted_7869148680" class="ydp8e69439eyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, 7 December 2020, 08:31:52 GMT, Michael Stauber <mstauber@blueonyx.it> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Darren,<br clear="none"><br clear="none">By the way: Let me follow up on that previous mirror problem while I'm<br clear="none">at it:<br clear="none"><br clear="none">> The index.php on updates.blueonyx.it <<a shape="rect" href="http://updates.blueonyx.it" rel="nofollow" target="_blank">http://updates.blueonyx.it</a>> makes<br clear="none">> a callback to our<br clear="none">> Matomo/Piwik instance on stats.blueonyx.it <<a shape="rect" href="http://stats.blueonyx.it" rel="nofollow" target="_blank">http://stats.blueonyx.it</a>> to<br clear="none">> count the mirror access by<br clear="none">> platform and general geographical origin. Sadly something seems to have<br clear="none">> changed in Matomo and this tiny transaction now causes frequent<br clear="none">> timeouts. Especially when a lot of YUM updates happen simultaneously.<br clear="none">> <br clear="none">> It's a bitch to troubleshoot and for the last couple of weeks I try to<br clear="none">> be around whenever a tsunami of update requests from Japan comes in so<br clear="none">> that I can apply some tweaks and see if that helps.<br clear="none"><br clear="none">That issue was eventually fixed back in the middle of August this year.<br clear="none"><br clear="none">That was a really interesting problem, by the way.<br clear="none"><br clear="none">Like said: The index.php on each updates.blueonyx.it makes calls to<br clear="none">stats.blueonyx.it and also to another database server where we store<br clear="none">which URL parameter resolves to what repository.<br clear="none"><br clear="none">The updates.blueonyx.it VPS's (both of them) have IPv4 and IPv6 IPs. And<br clear="none">stats.blueonyx.it also *had* both IPv4 and IPv6. However: That<br clear="none">stats.blueonyx.it VPS had been moved from one virtualization node to<br clear="none">another. And stupidly I had forgotten to assign that new node an IPv6<br clear="none">IP. It only had IPv4 configured.<br clear="none"><br clear="none">So whenever an updates.blueonyx.it/index.php was called up, the outgoing<br clear="none">request would be attempted via IPv6, as the remote host it was calling<br clear="none">(stats.blueonyx.it) supposedly was IPv6 capable and had an IPv6 IP. But<br clear="none">the one hop before that (the virtualization node) had no IPv6 enabled or<br clear="none">configured.<br clear="none"><br clear="none">The fun part?<br clear="none"><br clear="none">The IPv6 connection *still* completed. But only after a 10-15 second<br clear="none">delay. As a result the index.php with the mirror-list always loaded so<br clear="none">damn slow that any other delaying factor (like higher than usual load)<br clear="none">would cause a time-out.<br clear="none"><br clear="none">Once the node finally got it's IPv6 IP (that it should have had from the<br clear="none">start) things went back to normal speeds.<br clear="none"><br clear="none">And I'm ashamed to admit how long it took me to find that. But hey: It<br clear="none">had some good side effects: While troubleshooting the issue I removed a<br clear="none">lot of legacy code from the mirroring stuff to make that part faster and<br clear="none">more robust as well. \o/<div class="ydp8e69439eyqt7646142311" id="ydp8e69439eyqtfd12966"><br clear="none"><br clear="none">-- <br clear="none">With best regards<br clear="none"><br clear="none">Michael Stauber<br clear="none">_______________________________________________<br clear="none">Blueonyx mailing list<br clear="none"><a shape="rect" href="mailto:Blueonyx@mail.blueonyx.it" rel="nofollow" target="_blank">Blueonyx@mail.blueonyx.it</a><br clear="none"><a shape="rect" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx" rel="nofollow" target="_blank">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a><br clear="none"></div></div></div>
</div>
</div></body></html>