<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CRIN Trac: {1} Active Tickets</title>
    <link>https://trac.crin.org/trac/report/1</link>
    <description>Trac Report -  * List all active tickets by priority.
 * Color each row based on priority.
</description>
    <language>en-us</language>
    <image>
      <title>CRIN Trac</title>
      <url>https://trac.crin.org/trac/chrome/site/logo.gif</url>
      <link>https://trac.crin.org/trac/report/1</link>
    </image>
    <generator>Trac v1.0.2</generator>
      <item>
                  <title>#100: crin.org site down</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sat, 18 Feb 2017 11:38:48 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sat, 18 Feb 2017 15:04:54 GMT</pubDate>
                  <description>&lt;p&gt;
Russell, what's up? I'm really sorry I have to go out in 5 mins so I'm not around to help, what has gone wrong?
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/100</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/100</guid>
        <category>Report</category>
      </item><item>
                  <title>#73: CRIN2 ran out of memory</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sun, 01 May 2016 19:16:38 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sun, 15 May 2016 09:21:19 GMT</pubDate>
                  <description>&lt;p&gt;
The site has been down since Sun, 01 May 2016 18:05:44, it is now 8:15. I'm rebooting the server, it ran out of memory.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/73</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/73</guid>
        <category>Report</category>
      </item><item>
                  <title>#94: Ongoing high load caused by a bot</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 15 Dec 2016 19:23:12 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 15 Dec 2016 19:48:49 GMT</pubDate>
                  <description>&lt;p&gt;
Ticket to working out what to do with this issue...
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/94</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/94</guid>
        <category>Report</category>
      </item><item>
                  <title>#104: Problem with CRIN1 and CRIN2 backups</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 21 Mar 2017 09:32:43 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 31 Mar 2017 09:51:18 GMT</pubDate>
                  <description>&lt;p&gt;
Errors from the s3ql backup scripts:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
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.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/104</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/104</guid>
        <category>Report</category>
      </item><item>
                  <title>#119: MySQL Downtime</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 15 Jun 2017 10:31:52 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 15 Jun 2017 11:25:25 GMT</pubDate>
                  <description>&lt;p&gt;
Just after midnight last night MySQL appears to have started having some issues.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/119</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/119</guid>
        <category>Report</category>
      </item><item>
                  <title>#12: ownCloud Synching</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 11 May 2015 15:15:54 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 09 Jun 2015 09:11:36 GMT</pubDate>
                  <description>&lt;p&gt;
Changes are not synching between the desktop app and the browser version.
There is no error message showing up at the desktop app.
&lt;/p&gt;
</description>
                  
        <dc:creator>jonas</dc:creator>

        <link>https://trac.crin.org/trac/ticket/12</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/12</guid>
        <category>Report</category>
      </item><item>
                  <title>#14: Blank CRINmail newsletters being sent out</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sat, 16 May 2015 21:12:30 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 10 Sep 2015 12:10:48 GMT</pubDate>
                  <description>&lt;p&gt;
A newsletter sent via &lt;a class="ext-link" href="https://www.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Drupal&lt;/a&gt; contained no content, Jenny reported:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
We have tried twice today but both times when we send to all it sent out a
blank email, with just the subject line. We have tried sending it to a few
individual addresses and this works. We have sent other listservs out this
week and they have worked as normal.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
This is one of the emails:
&lt;/p&gt;
&lt;pre class="wiki"&gt;From: CRIN [mailto:info@crin.org]
Sent: Friday, May 15, 2015 7:04 AM
To: Gertrud Lenzer
Subject: Children in Court CRINmail 48: Special edition on LGBTQI rights
--
*Child Rights International Network - CRIN*
Unit W125-127, Westminster Business Square
1-45 Durham Street
London SE11 5JH
United Kingdom
T: +44 20 7401 2257
 www.crin.org
@CRINwire &amp;lt;https://twitter.com/CRINwire&amp;gt;
&lt;/pre&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/14</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/14</guid>
        <category>Report</category>
      </item><item>
                  <title>#20: Problem adding Drupal user accounts</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 15 Jun 2015 13:58:06 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 16 Jun 2015 12:27:59 GMT</pubDate>
                  <description>&lt;p&gt;
Jenny has reported:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
We are having trouble adding users (see screenshot - it should just be a save button but has an anti spam message) - this was working last week.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/20</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/20</guid>
        <category>Report</category>
      </item><item>
                  <title>#41: CRINmail multipart email contain CSS in the plain text version</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 10 Sep 2015 10:07:17 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 10 Sep 2015 10:28:46 GMT</pubDate>
                  <description>&lt;p&gt;
CRINmail, which are sent by Drupal, have a HTML and plain text version, the plain text version contains CSS at the top, which takes a while to scroll through and makes it less likely that people with mail user agents set to display the plain text version first will read the newsletter, for example:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Return-Path: &amp;lt;info@crin.org&amp;gt;
Received: from mail.webarch.net ([unix socket])
        by mail.webarch.net (Cyrus v2.3.7-Invoca-RPM-2.3.7-16.el5_11) with LMTPA;
        Thu, 10 Sep 2015 00:19:23 +0100
X-Sieve: CMU Sieve 2.3
Received: from elderberry.rat.burntout.org (mx.webarch.net [81.95.52.71])
        (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
        (Client did not present a certificate)
        by mail.webarch.net (Postfix) with ESMTPS id A7BFB100072
        for &amp;lt;chris@webarchitects.co.uk&amp;gt;; Thu, 10 Sep 2015 00:19:23 +0100 (BST)
Received: from crin2.crin.org ([93.95.228.180])
        by elderberry.rat.burntout.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128)
        (Exim 4.80)
        (envelope-from &amp;lt;info@crin.org&amp;gt;)
        id 1ZZoe5-00056h-Dl
        for chris@webarchitects.co.uk; Thu, 10 Sep 2015 00:19:23 +0100
Received: from www-data by crin2.crin.org with local (Exim 4.84)
        (envelope-from &amp;lt;info@crin.org&amp;gt;)
        id 1ZZoe4-0006TK-78
        for chris@webarchitects.co.uk; Wed, 09 Sep 2015 23:19:16 +0000
To: chris@webarchitects.co.uk
Subject: CRINmail 1445
X-PHP-Originating-Script: 1005:mimemail.module
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8a276e6c6a6f9459ea8c98217bf4e986"
Content-Transfer-Encoding: 8Bit
X-Mailer: Drupal
Sender: CRIN &amp;lt;info@crin.org&amp;gt;
From: CRIN &amp;lt;info@crin.org&amp;gt;
List-Unsubscribe: &amp;lt;http://www.crin.org/en/newsletter/confirm/remove/XXX&amp;gt;
Precedence: bulk
Message-Id: &amp;lt;E1ZZoe4-0006TK-78@crin2.crin.org&amp;gt;
Date: Wed, 09 Sep 2015 23:19:16 +0000
[-- Attachment #1 --]
[-- Type: multipart/alternative, Encoding: 8bit, Size: 73K --]
Content-Type: multipart/alternative;
    boundary="f5f8c71876cf7825d95e748d55f23268"
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
-------- CRINMAIL 1445 -------------------------------------------------------
#nl_wrapper {background-color:#EFEFEF;}#nl_wrapper table,
#nl_wrapper td  {
   font-family:Verdana, Arial, Helvetica;
   line-height:150%;
   font-size:10px;
   margin: 0;
}
#nl_wrapper td img{
   margin: 0;
}
#nl_wrapper .headerTop {
background-color:#FFCC66; border-top:0px solid #000000; border-bottom:1px
solid #FFFFFF; text-align:center;
}
#nl_wrapper .adminText {
font-size:10px; color:#996600; line-height:200%; font-family:Verdana, Arial,
Helvetica; text-decoration:none;
}
#nl_wrapper .headerBar {
background-color:#FFFFFF; border-top:0px solid #333333; border-bottom:10px
solid #FFFFFF;
}
#nl_wrapper .title {
font-size:20px; font-weight:bold; color:#CC6600; font-family:Verdana, Arial,
Helvetica; line-height:150%;
}
#nl_wrapper .subTitle {
font-size:11px; font-weight:normal; color:#666666; font-style:italic;
font-family:arial;
}
#nl_wrapper td {
font-size:11px; color:#000000; line-height:150%; font-family:Verdana, Arial,
Helvetica;
}
#nl_wrapper .sideColumn {
background-color:#FFFFFF; border-left:1px dashed #CCCCCC; text-align:left;
}
#nl_wrapper .sideColumnText {
font-size:11px; font-weight:normal; color:#AAAAAA; font-family:Verdana,
Arial, Helvetica; line-height:150%;
}
#nl_wrapper .sideColumnTitle {
font-size:15px; font-weight:bold; color:#333333; font-family:Verdana, Arial,
Helvetica; line-height:150%;
}
#nl_wrapper .footerRow {
background-color:#FFFFCC; border-top:10px solid #FFFFFF;
}
#nl_wrapper .footerText {
font-size:10px; color:#996600; line-height:100%; font-family:Verdana, Arial,
Helvetica;
}
#nl_wrapper h1,
#nl_wrapper h2  {
   color:#888888;font-size:20px;font-weight:bold;font-family:Arial,
Helvetica;margin:0 0 10px 0; line-height:150%;
}
#nl_wrapper h2  { font-size:15px; margin:23px 0 10px 0; padding-top:8px;
border-top:1px solid #EFEFEF;}
#nl_wrapper p   {margin:10px 0;
font-size:11px;color:#333333;font-family:Verdana, Arial, Helvetica;
line-height:150%;}
#nl_wrapper a,
#nl_wrapper table td p a,
#nl_wrapper #crintable a,
#nl_wrapper #crintable a:visited { color:#1155cc; /* color:#003a6a;*/ }
#nl_wrapper a:hover,
#nl_wrapper table td p a:hover,
#nl_wrapper #crintable a:hover{color:#000;}
#nl_wrapper ul,
#nl_wrapper li,
#nl_wrapper
#crintable ul   {margin:0; padding:0; list-style:none; list-style-image:none;
list-style-type:none}
#nl_wrapper ul li,
#nl_wrapper #crintable ul li,
#nl_wrapper #CMrightcol ul li
{font-size:11px;color:#333333;background-image:url(http://crin.org/i/crinmail/bg_bullet.gif);
background-repeat:no-repeat; background-position:2px
center;font-family:Verdana, Arial, Helvetica;  margin:0; list-style:none;
list-style-type:none; padding:0 0 0 20px; margin:13px 0;}
#nl_wrapper div.FB,                                                                                     #nl_wrapper div.FB p    { margin:10px 0}
#nl_wrapper div.FB h2   {color:#5e768b; font-size:16px; margin:0;}
#nl_wrapper #crintable table td {
vertical-align: top;
}
#nl_wrapper h3.h3image{
   background-repeat: no-repeat;
   background-position: center right;
}
   http://crin.org
09 September 2015
subscribe http://crin.org/node/41907 | subscribe http://crin.org/node/293 |
submit information http://crin.org/en/home/about/contact-us
======== *CRINMAIL 1445* =====================================================
-------- IN THIS ISSUE: ------------------------------------------------------
*The year in children's rights:*
CRIN annual report 2015 #AR
*Latest news and reports* #news
- Discrimination on school grounds #dis
- Criminalising children for sexting #crim
- Access to bathrooms denied #ac
- States leave migrant children unprotected #sta
- Issues neglected by UN committees #iss
- UN calls for submissions #un
- Contribute to evaluation of CRIN’s work #cont
*Access to justice for children in Ireland* #a2j
*Upcoming events* #events
*Employment* #jbs
/Problems viewing this CRINmail? Click here
https://www.crin.org/en/home/what-we-do/crinmail/crinmail-1445. /
*/CRIN announcement/*
/We are aware that some of our readers may be receiving blank CRINmails. This
is due to our website experiencing some technical issues, which we are
working to resolve. Should you receive a blank or incomplete CRINmail, you
can also access the latest edition via our website here
https://www.crin.org/en/home/what-we-do/crinmail. /
&lt;/pre&gt;&lt;p&gt;
Also note that the list unsub header contains a HTTP URL when this would be better as a HTTPS one for privacy reasons:
&lt;/p&gt;
&lt;pre class="wiki"&gt;List-Unsubscribe: &amp;lt;http://www.crin.org/en/newsletter/confirm/remove/XXX&amp;gt;
&lt;/pre&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/41</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/41</guid>
        <category>Report</category>
      </item><item>
                  <title>#49: Frozen emails on crin4</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 05 Nov 2015 19:22:51 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 15 Apr 2016 10:04:50 GMT</pubDate>
                  <description>&lt;p&gt;
Munin is sending alert emails every 5 mins because of the number of &lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin4.crin.org/exim_mailqueue.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;frozen emails&lt;/a&gt; on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org/trac/attachment/ticket/49/exim_mailqueue-day.png"&gt;&lt;img src="https://trac.crin.org/trac/raw-attachment/ticket/49/exim_mailqueue-day.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/49</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/49</guid>
        <category>Report</category>
      </item><item>
                  <title>#53: Blank email: CRINmail 1459</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 17 Dec 2015 13:04:49 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 23 Dec 2015 21:18:55 GMT</pubDate>
                  <description>&lt;p&gt;
I was sent this last night, with no email body:
&lt;/p&gt;
&lt;pre class="wiki"&gt;To: chris@webarchitects.co.uk
Subject: CRINmail 1459
X-PHP-Originating-Script: 1005:mimemail.module
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8Bit
X-Mailer: Drupal
Sender: CRIN &amp;lt;info@crin.org&amp;gt;
From: CRIN &amp;lt;info@crin.org&amp;gt;
List-Unsubscribe: &amp;lt;https://www.crin.org/en/newsletter/confirm/remove/XXXX&amp;gt;
Precedence: bulk
Message-Id: &amp;lt;E1a9N9t-0001cP-Qt@crin2.crin.org&amp;gt;
Date: Thu, 17 Dec 2015 01:15:05 +0000
&lt;/pre&gt;&lt;p&gt;
This looks like another case of the issue previously raised here: &lt;a class="new ticket" href="https://trac.crin.org/trac/ticket/14" title="defect: Blank CRINmail newsletters being sent out (new)"&gt;ticket:14&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/53</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/53</guid>
        <category>Report</category>
      </item><item>
                  <title>#54: 502 Errors</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 22 Dec 2015 11:06:04 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 23 Feb 2016 10:02:15 GMT</pubDate>
                  <description>&lt;p&gt;
Last night the &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/NginxLogWatch"&gt;wiki:NginxLogWatch&lt;/a&gt; script found a lot of 502 errors:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Dec 22     288 502, 0 503 and 0 504 errors from crin2.crin.org
Dec 22    4283 502, 0 503 and 0 504 errors from crin2.crin.org
&lt;/pre&gt;&lt;p&gt;
I'm not sure why yet.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/54</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/54</guid>
        <category>Report</category>
      </item><item>
                  <title>#56: Drupal Caching</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sun, 03 Jan 2016 11:46:35 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 07 Apr 2016 12:37:07 GMT</pubDate>
                  <description>&lt;p&gt;
This is a ticket to discuss and then implement some additional caching for the &lt;a class="ext-link" href="https://www.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/&lt;/a&gt; Drupal site.
&lt;/p&gt;
&lt;p&gt;
Possible options:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Generating static content from Drupal and serving these to non-logged in users, for example using &lt;a class="ext-link" href="https://www.drupal.org/project/boost"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Boost&lt;/a&gt; or something like it.
&lt;/li&gt;&lt;li&gt;Caching PHP generated pages using Nginx.
&lt;/li&gt;&lt;li&gt;Using a caching server such as Varnish.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
My preference would for 1. and 2., I can start doing some research on how best to do 2. I'd rather not do 3. if possible due to the complication it would add: &lt;tt&gt;php5-fpm -&amp;gt; varnish -&amp;gt; nginx&lt;/tt&gt;.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/56</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/56</guid>
        <category>Report</category>
      </item><item>
                  <title>#60: Advania S3 Account</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 04 Feb 2016 11:36:22 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 04 Feb 2016 17:22:32 GMT</pubDate>
                  <description>&lt;p&gt;
This ticket is to track the time spent answering Andrew's questions regarding the Advania S3 account which is used for backups by &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin3"&gt;Crin3&lt;/a&gt;.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/60</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/60</guid>
        <category>Report</category>
      </item><item>
                  <title>#65: Custom 502 and 503 pages for crin.org</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sun, 28 Feb 2016 14:17:03 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 06 May 2016 09:40:28 GMT</pubDate>
                  <description>&lt;p&gt;
It would be more informative if there were custom 502 and 503 error pages for &lt;a class="ext-link" href="https://www.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/&lt;/a&gt; rather than the default Nginx ones.
&lt;/p&gt;
&lt;p&gt;
I will write up some details below on the 502 and 503's we seeing getting, see also &lt;a class="new ticket" href="https://trac.crin.org/trac/ticket/54" title="defect: 502 Errors (new)"&gt;ticket:54&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
I'm happy to create a static 502 and static 503 error page and will look at adding it to the git repo.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/65</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/65</guid>
        <category>Report</category>
      </item><item>
                  <title>#66: Optimise backups, omit some MySQL tables and delete old backups from s3ql</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 08 Mar 2016 10:59:50 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 19 Apr 2016 10:06:24 GMT</pubDate>
                  <description>&lt;p&gt;
Currently the &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/DumpMysqlTables"&gt;DumpMysqlTables&lt;/a&gt; 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:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://drupal.stackexchange.com/questions/22041/which-drupal-tables-are-safe-to-clear"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.stackexchange.com/questions/22041/which-drupal-tables-are-safe-to-clear&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The same will be the case for Piwik and ownCloud and &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
In addition php session files should be deleted.
&lt;/p&gt;
&lt;p&gt;
Also the S3QLBackup script could be improved so it deleted old backups.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/66</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/66</guid>
        <category>Report</category>
      </item><item>
                  <title>#72: exim paniclog on crin3.crin.org</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 19 Apr 2016 09:47:12 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 19 Apr 2016 09:47:12 GMT</pubDate>
                  <description>&lt;p&gt;
I'm getting this email every day:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
exim paniclog /var/log/exim4/paniclog on crin3.crin.org has non-zero size, mail system might be broken. The last 10 lines are quoted below.
&lt;/p&gt;
&lt;p&gt;
2016-03-31 10:00:15 Warning: No server certificate defined; TLS connections will fail.
Suggested action: either install a certificate or change tls_advertise_hosts option
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/72</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/72</guid>
        <category>Report</category>
      </item><item>
                  <title>#76: Google Apps setup for crin.com</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 06 Jul 2016 19:50:38 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 08 Jul 2016 09:39:54 GMT</pubDate>
                  <description>&lt;p&gt;
This ticket is to track the time spent setting up Google Apps for crin.com.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/76</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/76</guid>
        <category>Report</category>
      </item><item>
                  <title>#77: Drupal contrib - Highly Critical - Remote code execution PSA-2016-001</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 13 Jul 2016 09:47:24 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 13 Jul 2016 16:25:03 GMT</pubDate>
                  <description>&lt;p&gt;
At 16:00 UTC (5pm BST) fixes for multiple &lt;em&gt;"highly critical remote code execution vulnerabilities"&lt;/em&gt; in unspecified Drupal 7 modules will be released and it is expected that &lt;em&gt;"exploits are expected to be developed within hours/days"&lt;/em&gt;, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.drupal.org/node/2764899"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2764899&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Peter: do you have this in hand? I notice that the dev site is still not running properly:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://dev.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://dev.crin.org/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
CSS is linked like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;@import url("https:///sites/all/modules/contrib/domain/domain_nav/domain_nav.css?o4jry7");
@import url("https:///modules/field/theme/field.css?o4jry7");
&lt;/pre&gt;&lt;p&gt;
JS is linked like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;&amp;lt;script src="https:///sites/default/files/js/js_zzcIWOou_jnX0ZWAIA4sb6Xy_p5a8FZNA0GySvuWjPU.js"&amp;gt;&amp;lt;/script&amp;gt;
&lt;/pre&gt;&lt;p&gt;
And images are linked like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;&amp;lt;img typeof="foaf:Image" src="https:///sites/default/files/styles/390x387/public/1.1.jpg?itok=p_PWQReL" width="390" height="387" alt="" /&amp;gt;
&lt;/pre&gt;&lt;p&gt;
Is there anything I can do to help?
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/77</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/77</guid>
        <category>Report</category>
      </item><item>
                  <title>#81: crin3 backup issue</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 19 Aug 2016 09:36:01 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 15 Sep 2016 08:47:32 GMT</pubDate>
                  <description>&lt;p&gt;
Munin email alert I'm getting every 5 mins:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Date: Fri, 19 Aug 2016 09:30:16 +0000
From: munin application user &amp;lt;munin@crin1.crin.org&amp;gt;
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.
&lt;/pre&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/81</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/81</guid>
        <category>Report</category>
      </item><item>
                  <title>#89: Broken Links</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 24 Oct 2016 12:11:44 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 24 Oct 2016 12:11:44 GMT</pubDate>
                  <description>&lt;p&gt;
&lt;a class="ext-link" href="https://www.crin.org/en/library/publications/crin-newsletter-15-mainstreaming-child-rights"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/en/library/publications/crin-newsletter-15-mainstreaming-child-rights&lt;/a&gt;
&lt;a class="ext-link" href="https://www.crin.org/en/library/publications/crin-newsletter-16-children-and-young-peoples-participation"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/en/library/publications/crin-newsletter-16-children-and-young-peoples-participation&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
were reported as broken
&lt;/p&gt;
</description>
                  
        <dc:creator>matthew</dc:creator>

        <link>https://trac.crin.org/trac/ticket/89</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/89</guid>
        <category>Report</category>
      </item><item>
                  <title>#97: Debian Stretch</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 30 Jan 2017 10:59:00 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 30 Jan 2017 10:59:01 GMT</pubDate>
                  <description>&lt;p&gt;
Debian Stretch will probably be released in May 2017 or so, we need a plan to migrate to it, specifically:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;PHP 7.0
&lt;/li&gt;&lt;li&gt;MariaDB 10
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This has been raised with Russell on Bitbucket.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/97</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/97</guid>
        <category>Report</category>
      </item><item>
                  <title>#99: Let's Encrypt Cert for CRIN.org</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 30 Jan 2017 14:32:43 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 30 Jan 2017 14:33:49 GMT</pubDate>
                  <description>&lt;p&gt;
The Gandi cert expires in a couple of weeks, in 17th Feb 2017, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=www.crin.org&amp;amp;latest"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.ssllabs.com/ssltest/analyze.html?d=www.crin.org&amp;amp;latest&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
It would make sense to switch to use &lt;a class="ext-link" href="https://letsencrypt.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://letsencrypt.org/&lt;/a&gt; and the client implementation I suggest we use is this one &lt;a class="ext-link" href="https://github.com/Neilpang/acme.sh"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/Neilpang/acme.sh&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/99</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/99</guid>
        <category>Report</category>
      </item><item>
                  <title>#102: Security certificate issue</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 10 Mar 2017 12:30:04 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 23 Aug 2017 16:38:50 GMT</pubDate>
                  <description>&lt;p&gt;
Hi Chris,
&lt;/p&gt;
&lt;p&gt;
I'm having trouble browsing to the stage site today on crin4 - I'm getting:
&lt;/p&gt;
&lt;p&gt;
SEC_ERROR_EXPIRED_CERTIFICATE
&lt;/p&gt;
&lt;p&gt;
.. trying to view stage.crin.org
&lt;/p&gt;
&lt;p&gt;
Are you able to help there?
&lt;/p&gt;
&lt;p&gt;
Many thanks,
Russell
&lt;/p&gt;
</description>
                  
        <dc:creator>russell</dc:creator>

        <link>https://trac.crin.org/trac/ticket/102</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/102</guid>
        <category>Report</category>
      </item><item>
                  <title>#103: Upgrade CRIN4 to 2GB of RAM</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 16 Mar 2017 09:37:21 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 20 Mar 2017 11:30:06 GMT</pubDate>
                  <description>&lt;p&gt;
Ticket to track the upgrading of &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; from 1GB to 2GB of RAM.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/103</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/103</guid>
        <category>Report</category>
      </item><item>
                  <title>#106: MySQL Error</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 27 Mar 2017 13:37:30 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 27 Mar 2017 13:37:30 GMT</pubDate>
                  <description>&lt;p&gt;
On Saturday morning the MySQL database on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; was generating errors which prevented the site for working, this was fixed by running this command on the server:
&lt;/p&gt;
&lt;pre class="wiki"&gt;mysqladmin flush-hosts
&lt;/pre&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/106</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/106</guid>
        <category>Report</category>
      </item><item>
                  <title>#111: Backups to Webarchitects server</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 13 Apr 2017 10:11:54 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 13 Apr 2017 17:28:46 GMT</pubDate>
                  <description>&lt;p&gt;
This is a ticket to setup backups to &lt;tt&gt;store1.webarch.net&lt;/tt&gt; on.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/111</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/111</guid>
        <category>Report</category>
      </item><item>
                  <title>#113: MySQL Performance</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 25 Apr 2017 11:22:11 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 28 Apr 2017 15:19:20 GMT</pubDate>
                  <description>&lt;p&gt;
MySQL is set to use a lot of resources, see the RAM allocation here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin1.crin.org/multips_memory.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://munin.crin.org/munin/crin.org/crin1.crin.org/multips_memory.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
And also a lot of queries are cached via memcache, which also has a lot of RAM allocated, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin2.crin.org/multips_memory.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://munin.crin.org/munin/crin.org/crin2.crin.org/multips_memory.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
What can we do to make it quicker?
&lt;/p&gt;
&lt;p&gt;
See also the work done when the server was setup on &lt;a class="closed ticket" href="https://trac.crin.org/trac/ticket/9" title="task: Monitor and adjust server settings after Crin1 and Crin2 server go live (closed: fixed)"&gt;ticket:9&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/113</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/113</guid>
        <category>Report</category>
      </item><item>
                  <title>#114: Update TLS certs for MySQL</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 05 May 2017 12:20:04 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 05 May 2017 14:03:38 GMT</pubDate>
                  <description>&lt;p&gt;
The TLS certs for MySQL connections between the servers are due to expire on 7th May 2017 so need to be updated.
&lt;/p&gt;
&lt;p&gt;
Peter, Russell, I have added you just so you know this is happening, it'll involve restarting MySQL when the new keys and certs are in place, so there might be a few moments of site downtime, but I'll do this on the dev/staging sever first.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/114</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/114</guid>
        <category>Report</category>
      </item><item>
                  <title>#115: 500 Errors for crin.org</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 16 May 2017 17:00:33 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 16 May 2017 17:00:33 GMT</pubDate>
                  <description>&lt;p&gt;
There have been a lot of 500 errors today and they appear to be related to lines like this in &lt;tt&gt;/var/log/php/error.log&lt;/tt&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[16-May-2017 17:33:08 Europe/London] PHP Fatal error:  Call to undefined function entity_translation_language_load() in /var/www/prod/docroot/includes/menu.inc on line 593
&lt;/pre&gt;&lt;p&gt;
The section on the file in question:
&lt;/p&gt;
&lt;pre class="wiki"&gt; 538
 539 /**
 540  * Loads objects into the map as defined in the $item['load_functions'].
 541  *
 542  * @param $item
 543  *   A menu router or menu link item
 544  * @param $map
 545  *   An array of path arguments; for example, array('node', '5').
 546  *
 547  * @return
 548  *   Returns TRUE for success, FALSE if an object cannot be loaded.
 549  *   Names of object loading functions are placed in $item['load_functions'].
 550  *   Loaded objects are placed in $map[]; keys are the same as keys in the
 551  *   $item['load_functions'] array.
 553  */
 554 function _menu_load_objects(&amp;amp;$item, &amp;amp;$map) {
 555   if ($load_functions = $item['load_functions']) {
 556     // If someone calls this function twice, then unserialize will fail.
 557     if (!is_array($load_functions)) {
 558       $load_functions = unserialize($load_functions);
 559     }
 560     $path_map = $map;
 561     foreach ($load_functions as $index =&amp;gt; $function) {
 562       if ($function) {
 563         $value = isset($path_map[$index]) ? $path_map[$index] : '';
 564         if (is_array($function)) {
 565           // Set up arguments for the load function. These were pulled from
 566           // 'load arguments' in the hook_menu() entry, but they need
 567           // some processing. In this case the $function is the key to the
 568           // load_function array, and the value is the list of arguments.
 569           list($function, $args) = each($function);
 570           $load_functions[$index] = $function;
 571
 572           // Some arguments are placeholders for dynamic items to process.
 573           foreach ($args as $i =&amp;gt; $arg) {
 574             if ($arg === '%index') {
 575               // Pass on argument index to the load function, so multiple
 576               // occurrences of the same placeholder can be identified.
 577               $args[$i] = $index;
 578             }
 579             if ($arg === '%map') {
 580               // Pass on menu map by reference. The accepting function must
 581               // also declare this as a reference if it wants to modify
 582               // the map.
 583               $args[$i] = &amp;amp;$map;
 584             }
 585             if (is_int($arg)) {
 586               $args[$i] = isset($path_map[$arg]) ? $path_map[$arg] : '';
 587             }
 588           }
 589           array_unshift($args, $value);
 590           $return = call_user_func_array($function, $args);
 591         }
 592         else {
 593           $return = $function($value);
 594         }
 595         // If callback returned an error or there is no callback, trigger 404.
 596         if ($return === FALSE) {
 597           $item['access'] = FALSE;
 598           $map = FALSE;
 599           return FALSE;
 600         }
 601         $map[$index] = $return;
 602       }
 603     }
 604     $item['load_functions'] = $load_functions;
 605   }
 606   return TRUE;
 607 }
 608
&lt;/pre&gt;&lt;p&gt;
Peter, is the the cause of the 500 errors or is it a symptom, or is it unrelated? Do you have an idea what is going on here?
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/115</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/115</guid>
        <category>Report</category>
      </item><item>
                  <title>#116: Limit the number of MySQL connections from Crin4 to Crin1</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 17 May 2017 11:44:18 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 23 May 2017 11:29:04 GMT</pubDate>
                  <description>&lt;p&gt;
Both the dev, &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; and live &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;, servers use the MySQL database on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; and we want to limit the resources available to &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; so it reduced the impact on the live site.
&lt;/p&gt;
&lt;p&gt;
Some documentation on this:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://dba.stackexchange.com/a/15427"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://dba.stackexchange.com/a/15427&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://dev.mysql.com/doc/refman/5.7/en/user-resources.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://dev.mysql.com/doc/refman/5.7/en/user-resources.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/116</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/116</guid>
        <category>Report</category>
      </item><item>
                  <title>#117: Install Newrelic on Crin2</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 17 May 2017 11:51:53 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 25 May 2017 10:28:13 GMT</pubDate>
                  <description>&lt;p&gt;
Peter has requested that Newrelic be installed on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Note that last time it was installed we had to remove it due to the resources it was using, see this thread &lt;a class="new ticket" href="https://trac.crin.org/trac/ticket/73#comment:24" title="defect: CRIN2 ran out of memory (new)"&gt;ticket:73#comment:24&lt;/a&gt;, so I'd advise against leaving it on the server all the time.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/117</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/117</guid>
        <category>Report</category>
      </item><item>
                  <title>#118: Piwik 3.0.4 and some setting changes</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 02 Jun 2017 09:58:17 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 02 Jun 2017 11:06:08 GMT</pubDate>
                  <description>&lt;p&gt;
The latest &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-0-4/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik is 3.0.4&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/118</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/118</guid>
        <category>Report</category>
      </item><item>
                  <title>#121: [webarch-mail] Planned migration of the email services at	mail.webarch.net</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 19 Jun 2017 09:30:05 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 19 Jun 2017 09:30:05 GMT</pubDate>
                  <description>&lt;pre class="wiki"&gt;Hi
You are being sent this email because you have a email account on
mail.webarch.net, if you don't believe this to be the case please let us know.
Soon we will be migrating your email account to a new Webarchitects mail server
running Mailcow, https://mailcow.email/
The new server will be available at https://webarch.email/ and it will provide
a lot of new features.
We haven't yet got a date for when all the email domains will be migrated but
we are moving the first few on the evening of Friday 23rd June from 8pm
onward.
To ensure that no email is lost when we do the migration we will have to stop
the mail.webarch.net and webarch.email servers for a little while, no emails
will be lost but some might be delayed while the servers are unavailable.
We will post an update to https://www.webarch.info/ when we start the migration
on Friday 23rd June and also when it has been completed.
If you have any questions please don't hesitate to get in touch via
support@webarchitects.coop.
All the best
Chris
--
Webarchitects Co-operative
http://webarchitects.coop/
+44 114 276 9709
@webarchcoop
_______________________________________________
webarch-mail mailing list
webarch-mail@lists.webarch.co.uk
https://lists.webarch.co.uk/mailman/listinfo/webarch-mail
&lt;/pre&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/121</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/121</guid>
        <category>Report</category>
      </item><item>
                  <title>#122: DB sync failed</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 23 Jun 2017 14:38:12 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 23 Jun 2017 14:51:34 GMT</pubDate>
                  <description>&lt;p&gt;
Hi Chris,
&lt;/p&gt;
&lt;p&gt;
Our dev. site (&lt;a class="ext-link" href="https://dev.crin.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://dev.crin.org&lt;/a&gt;) looked like it got rebuilt from a very old backup.
&lt;/p&gt;
&lt;p&gt;
I've just tried to resync dev. from live, and the DB sync has failed:
&lt;/p&gt;
&lt;p&gt;
crin4:/var/www/dev/docroot/drush sql-sync @crin.prodbox-prod @crin.dev
&lt;/p&gt;
&lt;p&gt;
.. with error 'Query failed'
&lt;/p&gt;
&lt;p&gt;
This has always worked until today.
&lt;/p&gt;
&lt;p&gt;
Any idea what's gone wrong?
&lt;/p&gt;
&lt;p&gt;
Thanks,
Russell
&lt;/p&gt;
</description>
                  
        <dc:creator>russell</dc:creator>

        <link>https://trac.crin.org/trac/ticket/122</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/122</guid>
        <category>Report</category>
      </item><item>
                  <title>#125: Piwik 3.1.1</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 21 Sep 2017 08:01:47 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 21 Sep 2017 08:06:13 GMT</pubDate>
                  <description>&lt;p&gt;
See the changelog &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-1-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-1-1/&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/125</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/125</guid>
        <category>Report</category>
      </item><item>
                  <title>#127: 1984.is Server Rebuild</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 21 Nov 2017 19:26:16 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 27 Nov 2017 14:54:50 GMT</pubDate>
                  <description>&lt;p&gt;
Due to critical hardware failure at 1984.is all three servers needed rebuilding from scratch.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/127</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/127</guid>
        <category>Report</category>
      </item><item>
                  <title>#129: Problem with image uploads</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 11 Dec 2017 18:09:39 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 11 Dec 2017 18:21:24 GMT</pubDate>
                  <description>&lt;blockquote class="citation"&gt;
&lt;p&gt;
unable to upload new documents and images to the website.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/129</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/129</guid>
        <category>Report</category>
      </item><item>
                  <title>#131: Let's Encrypt Certificates</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 20 Feb 2018 21:17:52 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 20 Feb 2018 21:17:52 GMT</pubDate>
                  <description>&lt;p&gt;
I have installed a new script for getting HTTPS certs on both servers:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://github.com/Neilpang/acme.sh"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/Neilpang/acme.sh&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
And there are now new certs for these domains:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=crin.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.ssllabs.com/ssltest/analyze.html?d=crin.org&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=crin.com"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.ssllabs.com/ssltest/analyze.html?d=crin.com&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=trac.crin.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.ssllabs.com/ssltest/analyze.html?d=trac.crin.org&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The Trac cert on this server is also used for, wiki.crin.org, phpmyadmin.crin.org, munin.crin.org and stats.crin.org.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/131</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/131</guid>
        <category>Report</category>
      </item><item>
                  <title>#132: Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 28 Mar 2018 20:06:22 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 28 Mar 2018 20:09:33 GMT</pubDate>
                  <description>&lt;p&gt;
&lt;a class="ext-link" href="https://www.drupal.org/sa-core-2018-002"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/sa-core-2018-002&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/132</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/132</guid>
        <category>Report</category>
      </item><item>
                  <title>#19: PHP Parser Error - node--country.tpl.php</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 15 Jun 2015 10:21:19 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 03 Aug 2015 10:41:36 GMT</pubDate>
                  <description>&lt;p&gt;
The php-fpm error log at &lt;tt&gt;/var/log/fpm-php.www.log&lt;/tt&gt; contains lots of entries like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[15-Jun-2015 11:17:32 Europe/London] PHP Parse error:  syntax error, unexpected end of file in /var/www/drupal/sites/default/themes/crin/templates/node--country.tpl.php on line 522
&lt;/pre&gt;&lt;p&gt;
Line 522 is the last line of the file, it simply contains a closing &lt;tt&gt;}&lt;/tt&gt; bracket, this is the last part of the file:
&lt;/p&gt;
&lt;pre class="wiki"&gt;
    &amp;lt;?php
  }
  ?&amp;gt;
  &amp;lt;?php // print render($content['links']); ?&amp;gt;
  &amp;lt;?php // print render($content['comments']); ?&amp;gt;
&amp;lt;?php
  // 'Albania' = 441;
  //$node_load(441);
  /*
  global $user;
  if($user-&amp;gt;uid == 1 ){
    if($node-&amp;gt;nid == 441){
      //update_country_from_wiki($node);
    }
  }
  */
?&amp;gt;
&amp;lt;/article&amp;gt;
&amp;lt;?php
}
&lt;/pre&gt;&lt;p&gt;
This is an issue for the Drupal developers to look at.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/19</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/19</guid>
        <category>Report</category>
      </item><item>
                  <title>#57: RSS requests from MediaWiki site to Drupal site</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 07 Jan 2016 13:05:37 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 07 Jan 2016 13:05:37 GMT</pubDate>
                  <description>&lt;p&gt;
The &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; site requests RSS URL's which are 404's at such a high rate that it is blocked, see &lt;a class="new ticket" href="https://trac.crin.org/trac/ticket/54#comment:6" title="defect: 502 Errors (new)"&gt;ticket:54#comment:6&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/57</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/57</guid>
        <category>Report</category>
      </item><item>
                  <title>#82: Attempted DDOS?</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sat, 24 Sep 2016 09:20:39 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Sat, 24 Sep 2016 10:12:50 GMT</pubDate>
                  <description>&lt;p&gt;
Yesterday evening there 1k 502 errors caused by one user agent from multiple IP addresses. This isn't an uncommon event, I usually don't write them  up, but I thought it might be useful for Mathew if I do with this one.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/82</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/82</guid>
        <category>Report</category>
      </item><item>
                  <title>#92: dev.crin.org needs /en appending the the URL for CSS to load</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 08 Nov 2016 12:35:59 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 08 Nov 2016 13:06:32 GMT</pubDate>
                  <description>&lt;p&gt;
This came up on &lt;a class="new ticket" href="https://trac.crin.org/trac/ticket/77#comment:10" title="defect: Drupal contrib - Highly Critical - Remote code execution PSA-2016-001 (new)"&gt;ticket:77#comment:10&lt;/a&gt; and it would be good to find the cause and also to solve it.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://dev.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://dev.crin.org/&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://dev.crin.org/en"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://dev.crin.org/en&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/92</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/92</guid>
        <category>Report</category>
      </item><item>
                  <title>#93: Piwik 2.17.1</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 02 Dec 2016 14:11:51 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 14 Dec 2016 11:59:56 GMT</pubDate>
                  <description>&lt;p&gt;
Not urgent, no security updates, see &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-17-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-2-17-1/&lt;/a&gt;
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/93</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/93</guid>
        <category>Report</category>
      </item><item>
                  <title>#120: crin2 mail queue</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 15 Jun 2017 18:36:04 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 22 Jun 2017 14:29:57 GMT</pubDate>
                  <description>&lt;p&gt;
There is a mail queue on Crin2, we haven't had one of these for ages, Munin reports:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
crin.org :: crin2.crin.org :: Exim Mailqueue
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
WARNINGs: frozen mails is 171.00 (outside range 100).
OKs: queued mails is 230.00.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Graph here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin2.crin.org/exim_mailqueue.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://munin.crin.org/munin/crin.org/crin2.crin.org/exim_mailqueue.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Anyone know if this is something to be concerned about?
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/120</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/120</guid>
        <category>Report</category>
      </item><item>
                  <title>#42: How CRINmail deals with email addresses that no longer work</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 10 Sep 2015 10:42:07 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 10 Sep 2015 10:42:07 GMT</pubDate>
                  <description>&lt;p&gt;
When the CRINmail newsletter is sent out via Drupal it has the following from envelope:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Return-Path: &amp;lt;info@crin.org&amp;gt;
&lt;/pre&gt;&lt;p&gt;
This results in emails that are returned as undeliverable going to that address and the Drupal site doesn't know when a recipient address no longer works so is unable to stop sending emails to address that bounce email back.
&lt;/p&gt;
&lt;p&gt;
One symptom of this problem are the forozen emails that build up after each CRINmail run, see the blue on Munin graphs here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin2.crin.org/exim_mailqueue.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://munin.crin.org/munin/crin.org/crin2.crin.org/exim_mailqueue.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
What should happen is that the from envelope (this is different from the From: header users see, that can remain as it is) should be an address that Drupal can check (probably via IMAP but we could set up one of the servers to accept SMPT email if needs be) and then do some thing sensible with the bounces.
&lt;/p&gt;
&lt;p&gt;
See for example the discussion here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://stackoverflow.com/q/1011714"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stackoverflow.com/q/1011714&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/42</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/42</guid>
        <category>Report</category>
      </item><item>
                  <title>#17: Debian System Updates</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 09 Jun 2015 18:42:00 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 30 Nov 2017 16:00:24 GMT</pubDate>
                  <description>&lt;p&gt;
This ticket is document system updates done to the servers.
&lt;/p&gt;
&lt;p&gt;
Sources for further information:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://lists.debian.org/debian-security-announce/recent"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Recent Debian security announcements&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://mailman.owncloud.org/pipermail/announcements/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;ownCloud announcements&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
These updates are generally done using the &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/AptitudeUpdateScript"&gt;wiki:AptitudeUpdateScript&lt;/a&gt; and this records all the changes in the &lt;tt&gt;/root/Changelog&lt;/tt&gt; and then the contents of the Changelog are pasted into the ticket to document the upgrade.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/17</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/17</guid>
        <category>Report</category>
      </item><item>
                  <title>#45: MediaWiki 1.23.11</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 16 Oct 2015 08:44:21 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 16 Oct 2015 08:44:21 GMT</pubDate>
                  <description>&lt;p&gt;
Email on &lt;a class="ext-link" href="https://lists.wikimedia.org/pipermail/mediawiki-announce/2015-October/000180.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;the announcements list&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Tomorrow we will be issuing a security release to all supported
branches of MediaWiki.
The new releases will be:
1.25.3
1.24.4
1.23.11
Fixes will be available in these respective release branches, the
unreleased 1.26.x branch, and master. Tarballs will be available
for the above mentioned point releases as well.
This security release will encompass core only, no bundled extensions
are affected.
&lt;/pre&gt;</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/45</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/45</guid>
        <category>Report</category>
      </item><item>
                  <title>#64: Let's Encrypt HTTPS Certs</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Fri, 26 Feb 2016 11:30:54 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 03 Oct 2016 09:43:34 GMT</pubDate>
                  <description>&lt;p&gt;
These certs, on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt;, are due to expire soon:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://cloud.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://cloud.crin.org/&lt;/a&gt; 13/03/16
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://stats.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stats.crin.org/&lt;/a&gt; 13/03/16
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://trac.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.crin.org/&lt;/a&gt;  29/04/16
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://wiki.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://wiki.crin.org/&lt;/a&gt;  03/05/16
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The one on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; has a while to run:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/&lt;/a&gt; 17/02/18
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
To save money I suggest that the certs on &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; are replaced with &lt;a class="ext-link" href="https://letsencrypt.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Let's Encrypt&lt;/a&gt; ones, for the above domains and in addition these sites which use &lt;a class="ext-link" href="http://www.cacert.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;CAcert&lt;/a&gt;:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://munin.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://munin.crin.org/&lt;/a&gt; 07/05/17
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://phpmyadmin.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phpmyadmin.crin.org/&lt;/a&gt; 07/05/17
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
I suggest we still use CACert for the MySQL certs as these are valid for two years and Let's Encrypt ones are only valid for 3 months and it would be complicated to automate the renewal and deployment for these certs.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/64</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/64</guid>
        <category>Report</category>
      </item><item>
                  <title>#79: Create accounts for Matthew</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 21 Jul 2016 10:15:23 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Mon, 09 Jan 2017 16:11:52 GMT</pubDate>
                  <description>&lt;p&gt;
Create &lt;a class="wiki" href="https://trac.crin.org/trac/wiki/Trac"&gt;Trac&lt;/a&gt; and other accounts for Matthew.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/79</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/79</guid>
        <category>Report</category>
      </item><item>
                  <title>#85: Trac is run on a different IP</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 04 Oct 2016 15:07:07 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 04 Oct 2016 15:50:47 GMT</pubDate>
                  <description></description>
                  
        <dc:creator>matthew</dc:creator>

        <link>https://trac.crin.org/trac/ticket/85</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/85</guid>
        <category>Report</category>
      </item><item>
                  <title>#86: Discussion</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Wed, 05 Oct 2016 12:14:15 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 08 Nov 2016 12:43:29 GMT</pubDate>
                  <description>&lt;p&gt;
This ticket is to keep track of time spent discussing issues with Matthew via email and IRC.
&lt;/p&gt;
</description>
                  
        <dc:creator>chris</dc:creator>

        <link>https://trac.crin.org/trac/ticket/86</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/86</guid>
        <category>Report</category>
      </item><item>
                  <title>#88: enoch website is deactivated</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 11 Oct 2016 10:13:17 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 11 Oct 2016 10:13:17 GMT</pubDate>
                  <description></description>
                  
        <dc:creator>matthew</dc:creator>

        <link>https://trac.crin.org/trac/ticket/88</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/88</guid>
        <category>Report</category>
      </item><item>
                  <title>#90: Cost of backup is estimated</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 25 Oct 2016 07:06:20 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Thu, 27 Oct 2016 13:36:10 GMT</pubDate>
                  <description>&lt;p&gt;
It would be useful to estimate the expected cost of back up, by estimated the size and correlating this with the advertised price page.
&lt;/p&gt;
</description>
                  
        <dc:creator>matthew</dc:creator>

        <link>https://trac.crin.org/trac/ticket/90</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/90</guid>
        <category>Report</category>
      </item><item>
                  <title>#108: Go live</title>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 04 Apr 2017 16:01:05 GMT</pubDate>
                  <!-- FIXME: we end up with multiple pubDate -->
                  <pubDate>Tue, 04 Apr 2017 17:42:21 GMT</pubDate>
                  <description>&lt;p&gt;
Hi Chris,
&lt;/p&gt;
&lt;p&gt;
I've got a round of work ready to go onto Crin live. All tested and signed off on stage. The code element is very light. I don't expect any problems, but just letting you know. I'm planning to get into this as the working day is finishing today.
&lt;/p&gt;
&lt;p&gt;
Best,
Russell
&lt;/p&gt;
</description>
                  
        <dc:creator>russell</dc:creator>

        <link>https://trac.crin.org/trac/ticket/108</link>
        <guid isPermaLink="false">https://trac.crin.org/trac/ticket/108</guid>
        <category>Report</category>
      </item>
  </channel>
</rss>