<p><fontstyle='background-color:red; color:black'>EXPERIMENTAL CODE - double check all results you see here, and read the logs if it's important.</font></p>
<p>The full list of Devuan package mirrors is available at the URL: <ahref='https://pkgmaster.devuan.org/mirror_list.txt'>https://pkgmaster.devuan.org/mirror_list.txt</a></p>
<p>Due to the nature of the tests, some errors or warnings will be counted several times. The links in the table and DNS list go to the detailed testing logs.</p>
<p><bclass="TTitem"title="This is a tooltip with an explanation in it.">Tooltips</b> are things that have an explanation tooltip, hover over them.</p>
<p><fontcolor='red'><b>FAILED</b></font> or <fontcolor='lime'><b>OK</b></font> means the tested thing is supported for that mirror.</p>
<p><fontcolor='darkred'><b>FAILED*</b></font> or <fontcolor='darkgreen'><b>OK*</b></font> means the tested thing is unsupported for that mirror, but might have been tested anyway.</p>
<p><fontcolor='aqua'><b>timeout</b></font> or <fontcolor='blue'><b>timeout</b></font> means the mirror had some timeouts, and tests where not yet aborted. The darker colour means unsupported by the mirror, but tested anyway.</p>
<p><fontcolor='aqua'><b>TIMEOUT</b></font> or <fontcolor='blue'><b>TIMEOUT</b></font> means the mirror had too many timeouts, and tests where aborted, so there is no result for this test.</p>
<p>NOTE: timeouts may be due to a problem on the testing computer, it might be busy with other things, or be having it's own network problems.</p>
<p>NOTE: the speed of the server this checking script is running on might be wildly exaggerated, it doesn't have to go through the Internet to download from itself.</p>
<p>The DNS round robin (DNS-RR) column shows the IPs for that mirror, or <fontcolor='grey'><b>no</b></font> if it isn't part of the DNS-RR. The IPs link to the testing log for that IP accessed via the DNS-RR. deb.devuan.org is the DNS-RR itself, so it doesn't get tested directly.</p>
<p>The time in the Updated column is how often the mirror updates itself.</p>
<p>Mirrors with a <fontstyle='background-color:dimgrey'>grey background</font> are not active (though may be usable as part of the DNS-RR).</p>
<p><fontcolor='grey'><b>skip</b></font> means that the test hasn't been written yet.</p>
<p>There are two styles of HTTP tests - actual HTTP downloads and HTTP HEAD tests.
Actual downloads happen when other tests need the files to be downloaded.
HEAD tests are where apt-panopticon probes things in detail.
For each mirror (including the DNS round robin domain), and for each IP of that mirror -
</p>
<ul>
<li>Chose a small collection of package files to test, and the Release files for each release.</li>
<li>Send a HTTP HEAD request for each of those files.</li>
<li>Carefully inspect and log the response.</li>
<li>Retry the request if needed, and log that.</li>
<li>If the mirror replies with a redirect to the same mirror, then try that and keep checking.</li>
<li>If the mirror replies with a redirect to a different server, then probe that mirror the same way.</li>
<li>If a redirect loop is detected, log that and give up.</li>
</ul>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
HTTPS
<divid="hoverShow0">
<h1>HTTPS tests</h1>
<p>The HTTPS tests are very similar to the HTTP tests detailed above, though obviously they are tried with HTTPS requests instead of HTTP requests.
The validity of the HTTPS certificate for each server is tested as well.
</p>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
RSYNC
<divid="hoverShow0">
<h1>RSYNC tests</h1>
<p>The RSYNC tests have not been written yet.</p>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
DNS round robin
<divid="hoverShow0">
<h1>DNS round robin</h1>
<p>The "DNS round robin" column lists the IP addresses for each mirror that is part of the DNS round robin, or DNS-RR.
The IPs are linked to the log for that specific IP when used via the DNS round robin, and is followed by the number of ERRORs, WARNINGs, or TIMEOUTs if any.
</p>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
Protocol
<divid="hoverShow0">
<h1>Protocol tests</h1>
<p>The Protocol test will give a warning if the protocol is changed during a redirect, HTTP -> HTTPS for example.
While apt HTTPS transport is now the default in Beowulf / Buster, not everyone with an older release will have that installed,
so redirecting HTTP to HTTPS will break apt for those people.
An ERROR is given instead if that happens for mirrors in the DNS round robin.
Servers in the DNS round robin will not have the HTTPS certificate for the round robin domain, so redirecting to HTTPS for that is an ERROR.
</p>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
Redirects
<divid="hoverShow0">
<h1>Redirect tests</h1>
<p>Mirrors that redirect /DEVUAN/ back out to deb.devuan.org is an ERROR.
/DEBIAN-SECURITY/ packages must be redirected to a Debian mirror, specifically a mirror hosting Debian security updates.
However, some Devuan mirrors might also be Debian mirrors, so this is just a WARNING.
</p>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
URL sanity
<divid="hoverShow0">
<h1>URL sanity tests</h1>
<p>The URL sanity test replaces "/" in URLS with "///", to see if the mirror can cope with that.
This might happen due to a minor mis-configuration by the apt user, but decent web servers should cope with that.
The result for a mirror that does not cope is a failed download for that user, so this is an ERROR.
</p>
</div>
</div>
</th>
<thclass="TTitem">
<divclass="hoverWrapper0">
Integrity
<divid="hoverShow0">
<h1>Integrity tests</h1>
<p>Actually download files, then check things like PGP keys, SHA256 check sums, and file size.
For packages, pick the smallest one that has been recently updated.
</p>
</div>
</div>
</th>
<thclass="TTitem"colspan='2'>
<divclass="hoverWrapper0">
Updated
<divid="hoverShow0">
<h1>Updated tests</h1>
<p>Make sure the Release files are up to date by checking their internal "Date" field.
If they are up to date, download and check updated Packages.xz files, and actual packages.
For actual packages, pick the smallest one that has been recently updated.
</p>
<p>Also shown is the mirrors scheduled time between updates, with "m" meaning minutes and "h" meaning hours.
If this is showing a WARNING, it's likely that the mirror hasn't updated yet, but is due to update after this test was run.
</p>
</div>
</div>
</th>
<thclass="TTitem"colspan='2'>
<divclass="hoverWrapper0">
Speed range
<divid="hoverShow0">
<h1>Speed range</h1>
<p>The speed test tries to guess at a minimum and maximum speed range for each mirror.
It does this by measuring the reported speeds from the curl commands that actually download files.
Since apt-panopticon is trying hard to download everything from all mirrors all at the same time, this guess will be low.
Also, the computer running the apt-panopticon might have a network connection that is busy with other things.
Not to mention that obviously if the computer this is running on is one of the mirrors, it might get a wildly exaggerated speed,
not having to go through the rest of the Internet tends to help.
Finally, the tested mirror may have a bigger network connection than the computer running the test, so wont show it's true maximum.
So take this speed measurement with a grain of salt, it's more of an indication, the <ahref="../apt-panopticon_cgp/index.php">full graphs</a> might be more useful.
</p>
</div>
</div>
</th>
<thclass="TTitem"colspan='2'>
<divclass="hoverWrapper0">
Weekly statistics
<divid="hoverShow0">
<h1>Weekly statistics</h1>
<p>This is the percentage of time, over the last week, that the mirror was up, and the percentage of time the mirror was up to date.
Note that if the mirror has a low uptime, then there wasn't much chance to check if it was up to date.
"<h1>Welcome to the apt-panopticon results page.</h1>\n"..
"<p>Here the apt-panopticon system probes into every nook and cranny of the Devuan apt package mirror system, trying to live up to it's name.</p>"..
"<p>This is the status of the mirror servers in the Devuan package mirror network.</p>\n")
copyHTMLbit(web,"Report-web_1.html")
if0<tonumber(APT.options.refresh.value)then
web:write('<p>This page will refresh every '..(APT.options.refresh.value/60)..' minutes.</p>')
end
web:write("<p><font style='background-color:red; color:black'>EXPERIMENTAL CODE - double check all results you see here, and read the logs if it's important.</font></p>"..
"<p>The full list of Devuan package mirrors is available at the URL: "..
"<p>Due to the nature of the tests, some errors or warnings will be counted several times. "..
"The links in the table and DNS list go to the detailed testing logs.</p>\n\n"..
"<hr>\n<h2>==== package mirror status "..os.date("!%F %H:%M").." GMT ====</h2>\n"..
"<p><font color='red'><b>FAILED</b></font> or <font color='lime'><b>OK</b></font>"..
" means the tested thing is supported for that mirror.</p>\n"..
"<p><font color='darkred'><b>FAILED*</b></font> or <font color='darkgreen'><b>OK*</b></font>"..
" means the tested thing is unsupported for that mirror, but might have been tested anyway.</p>\n"..
"<p><font color='aqua'><b>timeout</b></font> or <font color='blue'><b>timeout</b></font>"..
" means the mirror had some timeouts, and tests where not yet aborted. The darker colour means unsupported by the mirror, but tested anyway.</p>"..
"<p><font color='aqua'><b>TIMEOUT</b></font> or <font color='blue'><b>TIMEOUT</b></font>"..
" means the mirror had too many timeouts, and tests where aborted, so there is no result for this test.</p>"..
"<p>NOTE: timeouts may be due to a problem on the testing computer, it might be busy with other things, or be having it's own network problems..</p>"..
"<p>NOTE: the speed of the server this checking script is running on might be wildly exaggerated, it doesn't have to go through the Internet to download from itself.</p>"..
"<p>The DNS round robin (DNS-RR) column shows the IPs for that mirror, or <font color='grey'><b>no</b></font> if it isn't part of the DNS-RR. "..
"The IPs link to the testing log for that IP accessed via the DNS-RR. "..
APT.options.roundRobin.value.." is the DNS-RR itself, so it doesn't get tested directly.</p>\n"..
"<p>The time in the Updated column is how often the mirror updates itself.</p>"..
"<p>Mirrors with a <font style='background-color:dimgrey'>grey background</font> are not active (though may be usable as part of the DNS-RR).</p>\n"..
"<p><font color='grey'><b>skip</b></font> means that the test hasn't been written yet.</p>\n"
)
copyHTMLbit(web,"Report-web_2.html")
web:write("\n<h2>==== package mirror status "..os.date("!%F %H:%M").." GMT ====</h2>\n")
web:write("<br>\n<br>\n<h2>==== DNS, graphs <a href='explanations.html#Graphs'>*</a>, and logs: ====</h2>\n")
web:write("<br>\n<br>\n<h2>==== DNS, links to graphs, and links to logs: ====</h2>\n")
m=makeIPlist(APT.mirrors)
web:write("<p>This lists each mirror, and the DNS entries for that mirror. "..
"The links point to the testing log files ("..logCount("apt-panopticon")..") for each domain name / IP combination that was tested. "..
"The IP links point to the testing log files (the overall log is "..logCount("apt-panopticon")..") for each domain name / IP combination that was tested. "..
"If a mirror has a CNAME, that CNAME is listed along with that CNAMEs DNS entries. "..
APT.options.roundRobin.value.." is the DNS round robin, which points to the mirrors that are part of the DNS-RR. "..
"If an IP is part of the DNS-RR, it is marked with '<font color='purple'><b>DNS-RR</b></font>' "..
APT.options.referenceSite.value.." is the master mirror, all the others sync to it. "..
APT.options.referenceSite.value.." is the master mirror, all the others copy files from it. "..
"</p>\n"
)
web:write(APT.dumpTableHTML(m,""))
@ -524,7 +505,7 @@ if nil == web then C("opening mirrors file - " .. e) else
)
makeTable(web,APT.debians)
web:write("<br>\n<br>\n<h2>==== Debian DNS, graphs <a href='explanations.html#Graphs'>*</a>, and logs: ====</h2>\n")
web:write("<br>\n<br>\n<h2>==== Debian DNS, links to graphs, and links to logs: ====</h2>\n")
</head><bodybgcolor="black"text="white"><h1>Welcome to the apt-panopticon explanations page.</h1>
<p>The purpose of this page is to try to explain everything shown on <ahref="Report-web.html">the results page</a>,
so that the results page can link to the various parts for the curious.<p>
<hr><h1id="IPv4">IPV4 tests</h1>
<p>Tests are tested over IPv4 if the mirror has IPv4 addresses.</p>
<hr><h1id="IPv6">IPv6</h1>
<p>Tests are tested over IPv6 if the mirror has IPv6 addresses.</p>
<hr><h1id="FTP">FTP tests</h1>
<p>The FTP tests have not been written yet.</p>
<hr><h1id="HTTP">HTTP tests</h1>
<p>There are two styles of HTTP tests - actual HTTP downloads and HTTP HEAD tests.
Actual downloads happen when other tests need the files to be downloaded.
HEAD tests are where apt-panopticon probes things in detail.
For each mirror (including the DNS round robin domain), and for each IP of that mirror -
</p>
<ul>
<li>Chose a small collection of package files to test, and the Release files for each release.</li>
<li>Send a HTTP HEAD request for each of those files.</li>
<li>Carefully inspect and log the response.</li>
<li>Retry the request if needed, and log that.</li>
<li>If a redirect loop is detected, log that and give up.</li>
<li>If the mirror replies with a redirect to the same mirror, then try that and keep checking.</li>
<li>If the mirror replies with a redirect to a different server, then probe that mirror the same way.</li>
</ul>
<hr><h1id="HTTPS">HTTPS tests</h1>
<p>The HTTPS tests are very similar to the HTTP tests detailed above, though obviously they are tried with HTTPS requests intead of HTTP requests.
The validity of the HTTPS certificate for each server is tested as well.
</p>
<hr><h1id="RSYNC">rsync tests</h1>
<p>The RSYNC tests have not been written yet.</p>
<hr><h1id="DNS-RR">DNS round robin tests</h1>
<p>The "DNS round robin" column lists the IP addresses for each mirror that is part of the DNS round robin, or DNS-RR.
The IPs are linked to the log for that specific IP when used via the DNS round robin, and is followed by the number of errors, warnings, or timeouts of any.
</p>
<hr><h1id="Redirects">Redirect tests</h1>
<p>Mirrors that redirect /DEVUAN/ back out to deb.devuan.org is an ERROR.
/DEBIAN-SECURITY/ packages must be redirected to a Debian mirror, specifically a mirror hosting Debian security updates.
However, some Devuan mirrors might also be Debian mirrors, so this is just a WARNING.
</p>
<hr><h1id="Protocol">Protocol tests</h1>
<p>The Protocol test will give a warning if the protocol is changed during a redirect, HTTP -> HTTPS for example.
While apt HTTPS transport is now the default in Beowulf / Buster, not everyone with an older release will have that installed,
so redirecting HTTP to HTTPS will break apt for those people.
An error is given instead if that happens for mirrors in the DNS round robin.
Servers in the DNS round robin will not have the HTTPS certificate for the round robin domain, so redirecting to HTTPS for that is a mistake.
</p>
<hr><h1id="URL-Sanity">URL sanity tests</h1>
<p>The URL sanity test replaces "/" in URLS with "///", to see if the mirror can cope with that.
This might happen due to a minor mis-configuration by the apt user, but decent web servers should cope with that.
The result for a mirror that does not cope is a failed download for that use, so this is an error.
</p>
<hr><h1id="Integrity">Integrity tests</h1>
<p>Actually download files, then check things like PGP keys, SHA256 check sums, and file size.
For actual packages, pick the smallest one that has been recently updated.
</p>
<hr><h1id="Updated">Updated tests</h1>
<p>Make sure the Release files are up to date by checking their internal "Date" field.
If they are up to date, download and check updated Packages.xz files, and actual packages.
For actual packages, pick the smallest one that has been recently updated.
</p>
<p>Also shown is the mirrors scheduled time between updates, with "m" meaning minutes and "h" meaning hours.
</p>
<hr><h1id="Speed">Speed test</h1>
<p>The speed test tries to guess at a minimum and maximum speed range for each mirror.
It does this by measuring the reported speeds from the curl commands that actually download files.
Since apt-panopticon is trying hard to download everything from all mirrors all at the same time, this guess will be low.
Also, the computer running the apt-panopticon might have a network connection that is busy with other things.
Not to mention that obviously if the computer this is running on is one of the mirrors, it might get a wildly exaggerated speed,
not haaving to go through the rest of the Internet tends to help.
Finally, the tested mirror may have a bigger network connection than the computer running the test, so wont show it's true maximum.
So take this speed measurement with a grain of salt, it's more of an indication, the <ahref="../apt-panopticon_cgp/index.php">full graphs</a> might be useful.
</p>
<hr><h1id="Weekly">Weekly averages</h1>
<p>This is the percentage of time the mirror was up, and the percentage of time the mirror was up to date.
Note that if the mirror has a low uptime, then there wasn't much chance to check if it was up to date.