CRIN Trac: Ticket Query

#79: Create accounts for Matthew

chris — Thu, 21 Jul 2016 10:15:23 GMT

Create Trac and other accounts for Matthew.

#85: Trac is run on a different IP

matthew — Tue, 04 Oct 2016 15:07:07 GMT

#90: Cost of backup is estimated

matthew — Tue, 25 Oct 2016 07:06:20 GMT

It would be useful to estimate the expected cost of back up, by estimated the size and correlating this with the advertised price page.

#60: Advania S3 Account

chris — Thu, 04 Feb 2016 11:36:22 GMT

This ticket is to track the time spent answering Andrew's questions regarding the Advania S3 account which is used for backups by Crin3.

#66: Optimise backups, omit some MySQL tables and delete old backups from s3ql

chris — Tue, 08 Mar 2016 10:59:50 GMT

Currently the DumpMysqlTables script doesn't omit or truncate any tables so the backups contain unneeded data, such as cache tables, Drupal tables which can be truncated, see:

https://drupal.stackexchange.com/questions/22041/which-drupal-tables-are-safe-to-clear

The same will be the case for Piwik and ownCloud and MediaWiki.

In addition php session files should be deleted.

Also the S3QLBackup script could be improved so it deleted old backups.

#81: crin3 backup issue

chris — Fri, 19 Aug 2016 09:36:01 GMT

Munin email alert I'm getting every 5 mins:

Date: Fri, 19 Aug 2016 09:30:16 +0000
From: munin application user <munin@crin1.crin.org>
Subject: crin3.crin.org Munin Alert
crin.org :: crin3.crin.org :: Disk usage in percent
        WARNINGs: / is 97.35 (outside range [:92]).
        OKs: /run is 10.40, /dev/shm is 0.00, /boot is 87.07, /run/lock is 0.00, /sys/fs/cgroup is 0.00, /run/user/1000 is 0.00.

#89: Broken Links

matthew — Mon, 24 Oct 2016 12:11:44 GMT

https://www.crin.org/en/library/publications/crin-newsletter-15-mainstreaming-child-rights https://www.crin.org/en/library/publications/crin-newsletter-16-children-and-young-peoples-participation

were reported as broken

#104: Problem with CRIN1 and CRIN2 backups

chris — Tue, 21 Mar 2017 09:32:43 GMT

Errors from the s3ql backup scripts:

Backend reports that file system is still mounted elsewhere. Either the file system has not been unmounted cleanly or the data has not yet propagated through the backend. In the later case, waiting for a while should fix the problem, in the former case you should try to run fsck on the computer where the file system has been mounted most recently. You may also continue and use whatever metadata is available in the backend. However, in that case YOU MAY LOOSE ALL DATA THAT HAS BEEN UPLOADED OR MODIFIED SINCE THE LAST SUCCESSFULL METADATA UPLOAD. Moreover, files and directories that you have deleted since then MAY REAPPEAR WITH SOME OF THEIR CONTENT LOST.

#111: Backups to Webarchitects server

chris — Thu, 13 Apr 2017 10:11:54 GMT

This is a ticket to setup backups to store1.webarch.net on.