Hi,
here is a report on patchbot migration.
Previous state:
- minor OS-related issues (apparently specific to CentOS):
- Readahead for the filesystem hosting the db was set to 4096KB by
default, while mongodb recommends at most 256KB. This was temporarly
fixed by blockdev, until the migration (will disapear on reboot).
- The setup of selinux was too restrictive to allow mongodb to
recreate an instance from an empty dir (which was needed to work
locally on a fresh basis). Was fixed by asking selinux to be more
permissive.
- mongodb-related issues:
- it is impossible to list all the docbuild logs (which is the largest
part of the db).
- it was not possible to dump the db (errors after 3% of the dump).
- asking mongo to repair the db did not change anything.
- one reason was that some logs were inconsistent (two kinds of errors
depending on the log: InvalidDocument or OperationFailure)
- the trick was to reach the logs one by one by iterating over the
ticket reports and remove the broken ones (63 such logs were
inconsistent, hence destroyed), and recreate a db from there.
- This results in a db two times smaller (16GB of data instead of 32B,
effectively 20GB instead of 40GB on the hard disk). One hypothesis
is that there was also some spam in the remaining part of the db,
but i guess that most of it was actually made of "pending builds"
logs, that were not removed when the corresponding report is
removed. I modified the source code of the patchbot to also remove
pending logs when the pending reports are pruned, so that the db
only contains reachable information, and remains slim.
So, after dealing with that stuff, i could get a healthy install at my
lab, now using the same technology as asksage (ubuntu, nginx, uwsgi,...)
and no special tweaks (e.g. custom mongodb port), so that the admins do
not have to learn some new softwares to help there. Everything is fully
documented in /root/admin, so that it is trivial to redeploy without
additional archelolgy.
Then, Frederic Chapoton (who currently maintains the patchbot) got a
dedicated VM at his university, and we moved the stuff there. Everything
seems fine, please tell whether you discover some issue.
Regarding ssl certificates, i am not sure about registration thresholds
for LetsEncrypt so i just copied the current certificate, without
installing any renewal stuff. It is valid until september 8th, so we have
time to do it consistently.
Ciao,
Thierry
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
