<div dir="ltr">Hi Sam,<div><br></div><div>I would go for the 2nd approach. Apparently it all fit correctly and we can continue moving our services to docker containers.</div><div><br></div><div>Best regards,</div><div><br></div><div>Samuel C.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 6, 2016 at 6:56 AM, Sam Parkinson <span dir="ltr"><<a href="mailto:sam.parkinson3@gmail.com" target="_blank">sam.parkinson3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>On Sun, Mar 6, 2016 at 5:47 PM, Cron Daemon <<a href="mailto:root@sugarlabs.org" target="_blank">root@sugarlabs.org</a>> wrote:<br>
<blockquote type="cite"><div style="white-space:pre-wrap">/etc/cron.weekly/mirrorbrain:
bash: asn_import: command not found</div></blockquote><div><br></div><div>This cron error message hides that mirrorbrain isn't running at all now. See this in</div><div><br></div><div>1) appending ".mirrorlist" to a <a href="http://download.sugarlabs.org" target="_blank">download.sugarlabs.org</a> URL now gives a 404 (should show a list of mirrors and file metadata)</div><div>2) our MirrorMon [1] (which uses data from mirrorbrain) now shows that there are no mirrors. This is a lie, arrnet's still mirroring us [2]</div><div><br></div><div>Upon further investigation, it doesn't seem to be even set up properly:</div><div><br></div><div>1) "sudo -u mirrorbrain mb" (mb is mirrorbrain config tool) -> "sudo: mb: command not found"</div><div>2) from apt.sources.list "#bernie: mirrorbrain no longer supported on trusty :-("</div><div><br></div><div>So, any preferences for a plan of action? So far, I can think of:</div><div><br></div><div>1) Compile it from source. MirrorBrain moves slowly, so my old tut about this is still up to date [3]. But this feels so dirty and bad.</div><div>2) Use a Debian 8 docker container. The mirror brain repos [4] include packages for it, so it is just a package manager install in that respect. We can base it off the official docker apache images[5], which use debian jessie.</div><div><br></div><div>Thanks,</div><div>Sam</div><div><br></div><div>[1] <a href="https://mirrors.sugarlabs.org/" target="_blank">https://mirrors.sugarlabs.org/</a></div><div>[2] <a href="http://mirror.aarnet.edu.au/pub/sugarlabs/" target="_blank">http://mirror.aarnet.edu.au/pub/sugarlabs/</a></div><div>[3] <a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-a-mirror-director-with-mirrorbrain-on-ubuntu-14-04" target="_blank">https://www.digitalocean.com/community/tutorials/how-to-set-up-a-mirror-director-with-mirrorbrain-on-ubuntu-14-04</a></div>[4] <a href="http://download.opensuse.org/repositories/Apache:/MirrorBrain/" target="_blank">http://download.opensuse.org/repositories/Apache:/MirrorBrain/</a><div>[5] <a href="https://github.com/docker-library/httpd/blob/master/2.4/Dockerfile" target="_blank">https://github.com/docker-library/httpd/blob/master/2.4/Dockerfile</a><br><blockquote type="cite"><div style="white-space:pre-wrap">
_______________________________________________
Systems-logs mailing list
<a href="mailto:Systems-logs@lists.sugarlabs.org" target="_blank">Systems-logs@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/systems-logs" target="_blank">http://lists.sugarlabs.org/listinfo/systems-logs</a>
</div></blockquote></div><br>_______________________________________________<br>
Systems mailing list<br>
<a href="mailto:Systems@lists.sugarlabs.org">Systems@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/systems" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/systems</a><br>
<br></blockquote></div><br></div>