the website is slow for me, so I tried pinging libre-soc.org: jacob@jacob-desktop:~$ ping libre-soc.org PING libre-soc.org(libre-riscv.org (2a00:1098:82:f::1)) 56 data bytes 64 bytes from libre-riscv.org (2a00:1098:82:f::1): icmp_seq=1 ttl=43 time=171 ms 64 bytes from libre-riscv.org (2a00:1098:82:f::1): icmp_seq=2 ttl=43 time=170 ms 64 bytes from libre-riscv.org (2a00:1098:82:f::1): icmp_seq=3 ttl=43 time=168 ms Seeing no issue there, I tried pinging using IPv4: jacob@jacob-desktop:~$ ping -4 libre-soc.org PING libre-soc.org (46.235.227.77) 56(84) bytes of data. ^C --- libre-soc.org ping statistics --- 16 packets transmitted, 0 received, 100% packet loss, time 15359ms I got the same failure pinging through a different network.
(In reply to Jacob Lifshay from comment #0) > the website is slow for me, i've enabled cgroups to bring CPU usage down after a simple clone of the soclayout repo (120 mb download) was discovered to take CPU load well over 1.7. anything running under fastcgi is now only permitted 40% CPU, which approximately multiplies the completion time of any requests by 2.5
(In reply to Luke Kenneth Casson Leighton from comment #1) > (In reply to Jacob Lifshay from comment #0) > > the website is slow for me, > > i've enabled cgroups to bring CPU usage down after a simple clone of > the soclayout repo (120 mb download) was discovered to take CPU load > well over 1.7. > > anything running under fastcgi is now only permitted 40% CPU, > which approximately multiplies the completion time of any requests > by 2.5 Ok, it's still not accessible over IPv4 though...if that's intentional (I hope not, lots of people still can't use IPv6) please remove the IPv4 address from DNS. Otherwise, please fix the IPv4 accessibility problem.
(In reply to Jacob Lifshay from comment #2) > Ok, it's still not accessible over IPv4 though... that is incorrect. http://46.235.227.77 $ traceroute -n 46.235.227.77 ... 13 46.235.227.77 61.752 ms 68.095 ms 68.081 ms > if that's intentional (I > hope not, lots of people still can't use IPv6) please remove the IPv4 > address from DNS. there is no problem with either HTTP or HTTPS, so that is misleading. $ telnet 46.235.227.77 80 Trying 46.235.227.77... Connected to 46.235.227.77. Escape character is '^]'. HEAD /index.html HTTP/1.1 HTTP/1.1 400 Bad Request it responded, therefore is functional. > Otherwise, please fix the IPv4 accessibility problem. there is no IPv4 accessibility problem. not a high enough priority to warrant investigating the ping packets. traceroute is fine. closing permanently.
(In reply to Luke Kenneth Casson Leighton from comment #3) > (In reply to Jacob Lifshay from comment #2) > > > Ok, it's still not accessible over IPv4 though... > > that is incorrect. Ok, good!