<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CRIN Trac: Ticket Query</title>
    <link>https://trac.crin.org.archived.website/trac/query?id=&amp;desc=1&amp;order=summary</link>
    <description>Trac project for CRIN website and servers.</description>
    <language>en-US</language>
    <image>
      <title>CRIN Trac</title>
      <url>https://trac.crin.org.archived.website/trac/chrome/site/logo.gif</url>
      <link>https://trac.crin.org.archived.website/trac/query?id=&amp;desc=1&amp;order=summary</link>
    </image>
    <generator>Trac 1.0.2</generator>
    <item>
        <link>https://trac.crin.org.archived.website/trac/ticket/68</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/68</guid>
        <title>#68: {Spam?} Best watches.</title>
        <pubDate>Mon, 14 Mar 2016 00:35:03 GMT</pubDate>
        
        <dc:creator>Alasteir@…</dc:creator>

        <description>&lt;pre class="wiki"&gt; Order watches here-
... spam removed...
&lt;/pre&gt;&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/68/slid.jpg"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/chrome/common/attachment.png" alt="No image &amp;#34;slid.jpg&amp;#34; attached to Ticket #68" title="No image &amp;#34;slid.jpg&amp;#34; attached to Ticket #68" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/68#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/63</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/63</guid>
        <title>#63: {Spam?} Best watches in the world&gt;&gt;</title>
        <pubDate>Wed, 24 Feb 2016 10:20:04 GMT</pubDate>
        
        <dc:creator>info@…</dc:creator>

        <description>&lt;p&gt;
I need to sort out some spam filters, but not that the mailserver did detect this as spem and altered the subject line to add &lt;tt&gt;{Spam?} &lt;/tt&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/63#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/70</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/70</guid>
        <title>#70: s3ql backup error</title>
        <pubDate>Mon, 11 Apr 2016 10:08:41 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin3"&gt;Crin3&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Starting fsck of s3c://s.qstack.advania.com:443/crin4/
Using cached metadata.
WARNING: Remote metadata is outdated.
ERROR: File system revision too old, please run `s3qladm upgrade` first.
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/70#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/69</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/69</guid>
        <title>#69: procmail, email2trac and TLS cert</title>
        <pubDate>Thu, 07 Apr 2016 11:08:08 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;p&gt;
Each year the fingerpint of the server the Trac email accounts collects email from using fetchmail needs changing when the cert if updated,
&lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Trac#email2trac"&gt;wiki:Trac#email2trac&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/69#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/112</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/112</guid>
        <title>#112: phpMyAdmin HTTP Authentication</title>
        <pubDate>Tue, 25 Apr 2017 10:51:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There is a problem with the HTTP Authentication at &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;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/112#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/12</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/12</guid>
        <title>#12: ownCloud Synching</title>
        <pubDate>Mon, 11 May 2015 15:15:54 GMT</pubDate>
        
        <dc:creator>jonas</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/12#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/47</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/47</guid>
        <title>#47: ownCloud 8.1.4.2</title>
        <pubDate>Tue, 20 Oct 2015 13:58:02 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the &lt;a class="ext-link" href="http://mailman.owncloud.org/mailman/listinfo/announcements"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;email list&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Dear ownCloud users!
&lt;/p&gt;
&lt;p&gt;
We're proud to make available the latest ownCloud Server 8.2, which delivers
user interface improvements and significant new features for system
administrators. This release is deemed stable for home users and small
servers. Enterprise users are encouraged to wait for the release of the
ownCloud Enterprise subscriptions before upgrading.
&lt;/p&gt;
&lt;p&gt;
A blog post with instructions on upgrading will appear tomorrow on
&lt;a class="ext-link" href="https://owncloud.org/news"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://owncloud.org/news&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Get the latest version on &lt;a class="ext-link" href="https://owncloud.org/install"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://owncloud.org/install&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
You can find links and installation instructions on
&lt;a class="ext-link" href="https://owncloud.org/release-channels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://owncloud.org/release-channels&lt;/a&gt; and see what's new on
&lt;a class="ext-link" href="https://owncloud.org/changelog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://owncloud.org/changelog&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Note that if you use packages from the release channels, it is your
responsibility to change your package repositories to a newer version before a
release is no longer supported. If you still use ownCloud 6, you are strongly
urged to upgrade to the stable 7 series or newer as soon as possible.
&lt;/p&gt;
&lt;p&gt;
They all have received critical stability and security updates and it is
highly recommended to upgrade.
&lt;/p&gt;
&lt;p&gt;
Enjoy the latest ownCloud releases!
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/47#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/43</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/43</guid>
        <title>#43: ownCloud 8.1.3-13.1</title>
        <pubDate>Thu, 17 Sep 2015 11:52:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Subject: 4 Debian package update(s) for crin1
apticron report [Thu, 17 Sep 2015 11:40:12 +0000]
========================================================================
apticron has detected that some packages need upgrading on:
        crin1
        [ 93.95.228.179 ]
The following packages are currently pending an upgrade:
        owncloud 8.1.3-13.1
        owncloud-config-apache 8.1.3-13.1
        owncloud-server 8.1.3-13.1
        php5-ldap 5.6.13+dfsg-0+deb8u1
========================================================================
Package Details:
Reading changelogs...
--- Changes for owncloud (owncloud owncloud-config-apache owncloud-server) ---
owncloud (8.1.3-13.1) stable; urgency=low
  * version number update by debtransform
 -- debtransform &amp;lt;build@opensuse.org&amp;gt;  Wed, 16 Sep 2015 14:39:25 +0000
owncloud (8.1.3-1) stable; urgency=low
  * Update to version 8.1.3
 -- Juergen Weigert &amp;lt;jw@owncloud.com&amp;gt;  Fri, 11 Sep 2015 11:48:14 +0200
owncloud (8.1.2-1) stable; urgency=low
  * Update to version 8.1.2
 -- Juergen Weigert &amp;lt;jw@owncloud.com&amp;gt;  Wed, 02 Sep 2015 12:39:29 +0200
owncloud (8.1.2~RC1-1) stable; urgency=low
  * Update to version 8.1.2~RC1
 -- Juergen Weigert &amp;lt;jw@owncloud.com&amp;gt;  Sun, 30 Aug 2015 15:20:03 +0200
owncloud (8.1.1-3) stable; urgency=low
  * Possible fix for https://github.com/owncloud/core/issues/18222
 -- Juergen Weigert &amp;lt;jw@owncloud.com&amp;gt;  Tue, 25 Aug 2015 17:42:12 +0200
owncloud (8.1.1-2) stable; urgency=low
  * Make occ executable. https://github.com/owncloud/core/issues/18508
  * Using DEBTRANSFORM-RELEASE to automate incrementing build release number.
  * Fix owncloud-server: php-script-but-no-phpX-cli-dep var/www/owncloud/occ
 -- Juergen Weigert &amp;lt;jw@owncloud.com&amp;gt;  Tue, 25 Aug 2015 14:25:48 +0200
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/43#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/72</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/72</guid>
        <title>#72: exim paniclog on crin3.crin.org</title>
        <pubDate>Tue, 19 Apr 2016 09:47:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/72#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/88</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/88</guid>
        <title>#88: enoch website is deactivated</title>
        <pubDate>Tue, 11 Oct 2016 10:13:17 GMT</pubDate>
        
        <dc:creator>matthew</dc:creator>

        <description></description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/88#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/92</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/92</guid>
        <title>#92: dev.crin.org needs /en appending the the URL for CSS to load</title>
        <pubDate>Tue, 08 Nov 2016 12:35:59 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This came up on &lt;a class="new ticket" href="https://trac.crin.org.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/92#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/48</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/48</guid>
        <title>#48: crin4 /tmp filling up</title>
        <pubDate>Wed, 28 Oct 2015 10:44:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A task is need to clear &lt;tt&gt;/tmp&lt;/tt&gt; on &lt;a class="wiki" href="https://trac.crin.org.archived.website/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.archived.website/trac/attachment/ticket/48/crin3-df-pinpoint-1443176117-1446027317.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/48/crin3-df-pinpoint-1443176117-1446027317.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/48#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/81</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/81</guid>
        <title>#81: crin3 backup issue</title>
        <pubDate>Fri, 19 Aug 2016 09:36:01 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/81#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/120</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/120</guid>
        <title>#120: crin2 mail queue</title>
        <pubDate>Thu, 15 Jun 2017 18:36:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/120#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/100</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/100</guid>
        <title>#100: crin.org site down</title>
        <pubDate>Sat, 18 Feb 2017 11:38:48 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/100#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/121</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/121</guid>
        <title>#121: [webarch-mail] Planned migration of the email services at	mail.webarch.net</title>
        <pubDate>Mon, 19 Jun 2017 09:30:05 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/121#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/38</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/38</guid>
        <title>#38: [URGENT] crin.org down</title>
        <pubDate>Tue, 08 Sep 2015 15:54:35 GMT</pubDate>
        
        <dc:creator>mori</dc:creator>

        <description>&lt;p&gt;
Hi Chris,
&lt;/p&gt;
&lt;p&gt;
Jenny just reached out to us by email reporting crin.org is down. The error message I see on crin.org is:
&lt;/p&gt;
&lt;p&gt;
&lt;tt&gt;PDOException: SQLSTATE[28000] [1045] Access denied for user 'newprod'@'crin2' (using password: YES) in lock_may_be_available() (line 167 of /var/www/prod/docroot/includes/lock.inc).&lt;/tt&gt;
&lt;/p&gt;
&lt;p&gt;
It sounds like it may be something that's related to the issue you mentioned in &lt;a class="closed ticket" href="https://trac.crin.org.archived.website/trac/ticket/36" title="defect: Piwik stats stopped on 31st August 2015 (closed: fixed)"&gt;#36&lt;/a&gt; (&lt;a href="https://trac.crin.org.archived.website/trac/ticket/36#comment:7"&gt;https://trac.crin.org.archived.website/trac/ticket/36#comment:7&lt;/a&gt; )
&lt;/p&gt;
&lt;p&gt;
Can you please have a look at this as a matter of urgency?
&lt;/p&gt;
&lt;p&gt;
Thanks,
&lt;/p&gt;
&lt;p&gt;
Mori
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/38#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/58</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/58</guid>
        <title>#58: You have 1 new fax, document 00000576492</title>
        <pubDate>Wed, 13 Jan 2016 20:10:03 GMT</pubDate>
        
        <dc:creator>incoming@…</dc:creator>

        <description>&lt;pre class="wiki"&gt;A new fax document for you.
Please, download fax document attached to this email.
Quality:            200 DPI
Sender:             Theodore Thompson
Pages:              12
Scanned in:         46 seconds
Document name:      scan.00000576492.doc
File size:          240 Kb
Scanned:            Wed, 13 Jan 2016 08:29:25 +0300
Thanks for using Interfax service!
&lt;/pre&gt;&lt;p&gt;
&lt;a class="missing attachment"&gt;scan.00000576492.zip&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/58#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/74</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/74</guid>
        <title>#74: Visit to CRIN office</title>
        <pubDate>Sun, 05 Jun 2016 19:04:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is to record the time spent visting the CRIN office on Friday 3rd June 2016.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/74#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/103</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/103</guid>
        <title>#103: Upgrade CRIN4 to 2GB of RAM</title>
        <pubDate>Thu, 16 Mar 2017 09:37:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to track the upgrading of &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; from 1GB to 2GB of RAM.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/103#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/114</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/114</guid>
        <title>#114: Update TLS certs for MySQL</title>
        <pubDate>Fri, 05 May 2017 12:20:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/114#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/123</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/123</guid>
        <title>#123: Update Email Settings</title>
        <pubDate>Mon, 24 Jul 2017 15:23:37 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This Trac site uses a @webarch.net email account and that domain has been migrated to a new server and a new account needs setting up and the fetchmail settings need updating.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/123#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/85</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/85</guid>
        <title>#85: Trac is run on a different IP</title>
        <pubDate>Tue, 04 Oct 2016 15:07:07 GMT</pubDate>
        
        <dc:creator>matthew</dc:creator>

        <description></description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/85#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/1</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/1</guid>
        <title>#1: Trac initial install and configuration</title>
        <pubDate>Tue, 28 Apr 2015 11:43:46 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Steps taken doing the initial install and configuration of Trac at &lt;a href="https://trac.crin.org.archived.website/trac"&gt;https://trac.crin.org.archived.website/trac&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/1#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/98</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/98</guid>
        <title>#98: Trac account for Russell</title>
        <pubDate>Mon, 30 Jan 2017 11:43:44 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Create a Trac account for the new Drupal developer, Russell.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/98#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/59</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/59</guid>
        <title>#59: Trac Spam</title>
        <pubDate>Wed, 13 Jan 2016 20:38:11 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
We might have to whitelist email addresses which can open tickets or something, see &lt;a class="closed ticket" href="https://trac.crin.org.archived.website/trac/ticket/58" title="defect: You have 1 new fax, document 00000576492 (closed: fixed)"&gt;ticket:58&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/59#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/37</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/37</guid>
        <title>#37: Site slowdown on 8th Sept 2015</title>
        <pubDate>Tue, 08 Sep 2015 13:15:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The site is really slow and the number of &lt;tt&gt;php5-fpm&lt;/tt&gt; processes has gone up dramatically and so has the memory usage.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/37#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/2</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/2</guid>
        <title>#2: Set up firewall and fail2ban to stop brute force ssh attacks</title>
        <pubDate>Tue, 28 Apr 2015 13:26:20 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The servers need only listen for HTTP, HTTPS and SSH traffic and brute force attacks on ssh accounts should be blocked using &lt;a class="ext-link" href="https://packages.debian.org/jessie/fail2ban"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://packages.debian.org/jessie/fail2ban&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/2#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/11</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/11</guid>
        <title>#11: Set up backups</title>
        <pubDate>Thu, 07 May 2015 11:51:13 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The plan is to use &lt;a class="ext-link" href="http://www.advania.com/datacentres/solutions/advania-cloud-services/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Advania S3 storage space&lt;/a&gt; (as &lt;a class="ext-link" href="https://www.greenqloud.com/public-cloud-faq/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;GreenQloud is shutting down&lt;/a&gt;) and &lt;a class="ext-link" href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-7-Wheezy-"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;S3QL&lt;/a&gt; to backup the existing Servers at GreenQloud and also, on an on-going basis, &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; and &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/11#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/102</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/102</guid>
        <title>#102: Security certificate issue</title>
        <pubDate>Fri, 10 Mar 2017 12:30:04 GMT</pubDate>
        
        <dc:creator>russell</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/102#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/39</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/39</guid>
        <title>#39: S3QL backup problems</title>
        <pubDate>Wed, 09 Sep 2015 11:36:18 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Often backups fail during the rsync with "Transport endpoint is not connected".
&lt;/p&gt;
&lt;p&gt;
The S3QL &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin3"&gt;Crin3&lt;/a&gt; backup script mounts on &lt;tt&gt;/tmp&lt;/tt&gt; but the other scripts don't so where there is some issue the unmount don't work as the S3QL system is mounted in an unknown location, see &lt;a class="closed ticket" href="https://trac.crin.org.archived.website/trac/ticket/35" title="defect: Problem with the S3QL backups for Crin1 (closed: fixed)"&gt;ticket:35&lt;/a&gt;. [SOLVED]
&lt;/p&gt;
&lt;p&gt;
There are also some unneeded scripts in &lt;tt&gt;/usr/local/bin&lt;/tt&gt; on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin3"&gt;Crin3&lt;/a&gt; which need removing to make things less confusing. [SOLVED]
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/39#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/67</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/67</guid>
        <title>#67: S3QL 2.17 has been released</title>
        <pubDate>Wed, 09 Mar 2016 19:07:56 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is worth noting:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
From the changelog:
&lt;/p&gt;
&lt;h2 id="a2016-03-08S3QL2.17"&gt;2016-03-08, S3QL 2.17&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;The internal file system revision has changed. File systems
created with S3QL 2.17 or newer are not compatible with prior S3QL
versions. To update an existing file system to the newest
revision, use the &lt;tt&gt;s3qladm upgrade&lt;/tt&gt; command.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://groups.google.com/forum/?_escaped_fragment_=topic/s3ql/t36XMqiS5TU#!topic/s3ql/t36XMqiS5TU"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://groups.google.com/forum/?_escaped_fragment_=topic/s3ql/t36XMqiS5TU#!topic/s3ql/t36XMqiS5TU&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Currently Debian unstable has 2.15:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://packages.debian.org/stretch/s3ql"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://packages.debian.org/stretch/s3ql&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
But it should update soon.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/67#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/57</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/57</guid>
        <title>#57: RSS requests from MediaWiki site to Drupal site</title>
        <pubDate>Thu, 07 Jan 2016 13:05:37 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="wiki" href="https://trac.crin.org.archived.website/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.archived.website/trac/ticket/54#comment:6" title="defect: 502 Errors (new)"&gt;ticket:54#comment:6&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/57#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/35</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/35</guid>
        <title>#35: Problem with the S3QL backups for Crin1</title>
        <pubDate>Mon, 07 Sep 2015 10:55:30 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Just tried mounting all the backup on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; and there was a problem with the &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; backup:
&lt;/p&gt;
&lt;pre class="wiki"&gt;umnt-s3ql crin1
/media/s3ql/crin1 is not on an S3QL file system
Can not check mounted file system.
mnt-s3ql crin1
Can not check mounted file system.
Filesystem check of s3c://s.qstack.advania.com:443/crin1 failed
Using 2 upload threads (memory limited).
Autodetected 65498 file descriptors available for cache entries
Using cached metadata.
File system damaged or not unmounted cleanly, run fsck!
Mounting s3c://s.qstack.advania.com:443/crin1 on /media/s3ql/crin1 failed
mnt-s3ql crin1 --force
Can not check mounted file system.
Filesystem check of s3c://s.qstack.advania.com:443/crin1 failed
Using 2 upload threads (memory limited).
Autodetected 65498 file descriptors available for cache entries
Using cached metadata.
File system damaged or not unmounted cleanly, run fsck!
Mounting s3c://s.qstack.advania.com:443/crin1 on /media/s3ql/crin1 failed
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/35#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/129</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/129</guid>
        <title>#129: Problem with image uploads</title>
        <pubDate>Mon, 11 Dec 2017 18:09:39 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/129#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/104</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/104</guid>
        <title>#104: Problem with CRIN1 and CRIN2 backups</title>
        <pubDate>Tue, 21 Mar 2017 09:32:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/104#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/20</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/20</guid>
        <title>#20: Problem adding Drupal user accounts</title>
        <pubDate>Mon, 15 Jun 2015 13:58:06 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/20#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/31</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/31</guid>
        <title>#31: Preparation for deployment to new prod</title>
        <pubDate>Mon, 10 Aug 2015 15:32:41 GMT</pubDate>
        
        <dc:creator>mori</dc:creator>

        <description>&lt;p&gt;
Hi Chris,
&lt;/p&gt;
&lt;p&gt;
In order to run the CRIN production site under the new codebase, we need to go through a number of steps to set up and test the site. We need your help to accomplish this.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Overview:&lt;/strong&gt; (please execute each step once we request you to do so through the comment)
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Chris to create a new entry for the new prod site on CRIN2
&lt;/li&gt;&lt;li&gt;Chris to create a new database for the new prod site on CRIN1
&lt;/li&gt;&lt;li&gt;Code+ and CRIN to test the new prod site and sign off
&lt;/li&gt;&lt;li&gt;Chris to update the nginx config so the new prod serves as the working prod
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;strong&gt;Rationale of the go-live process&lt;/strong&gt;
Because of the reasons listed below, deploying the new code to the existing prod results in an extended period of downtime:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;repository too large: cloning takes 10+ minutes
&lt;/li&gt;&lt;li&gt;changes to directory structure requires the registry to be rebuilt
&lt;/li&gt;&lt;li&gt;the new deployment process needs testing
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/31#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/36</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/36</guid>
        <title>#36: Piwik stats stopped on 31st August 2015</title>
        <pubDate>Tue, 08 Sep 2015 11:14:19 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The Piwik stats stopped on 31st August 2015.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/36/crin-piwik-2015-09-08.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/36/crin-piwik-2015-09-08.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The tracking code is missing, can the &lt;a class="ext-link" href="https://www.drupal.org/project/piwik"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Drupal Piwik module&lt;/a&gt; be re-installed / re-enabled please?
&lt;/p&gt;
&lt;p&gt;
In addition I believe the GA tracking code can be removed as the Piwik stats replace these.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/36#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/110</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/110</guid>
        <title>#110: Piwik Accounts for Peter and Lisa</title>
        <pubDate>Mon, 10 Apr 2017 13:53:26 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Peter and Lisa from the-organization.com need Piwik access
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/110#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/128</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/128</guid>
        <title>#128: Piwik 3.2.1</title>
        <pubDate>Thu, 07 Dec 2017 12:07:06 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Changelog: &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-2-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-2-1/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/128#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/126</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/126</guid>
        <title>#126: Piwik 3.2.0</title>
        <pubDate>Mon, 16 Oct 2017 12:27:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Changelog: &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-2-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-2-0/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/126#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/125</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/125</guid>
        <title>#125: Piwik 3.1.1</title>
        <pubDate>Thu, 21 Sep 2017 08:01:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/125#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/124</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/124</guid>
        <title>#124: Piwik 3.1.0</title>
        <pubDate>Fri, 15 Sep 2017 10:16:09 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Details: &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-1-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-1-0/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/124#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/118</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/118</guid>
        <title>#118: Piwik 3.0.4 and some setting changes</title>
        <pubDate>Fri, 02 Jun 2017 09:58:17 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/118#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/109</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/109</guid>
        <title>#109: Piwik 3.0.3</title>
        <pubDate>Wed, 05 Apr 2017 09:41:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
New version of Piwik, &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-0-3/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik 3.0.3&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/109#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/101</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/101</guid>
        <title>#101: Piwik 3.0.2</title>
        <pubDate>Thu, 02 Mar 2017 18:58:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Piwik"&gt;Piwik&lt;/a&gt; is out:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-0-2/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-0-2/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/101#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/96</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/96</guid>
        <title>#96: Piwik 3.0.1</title>
        <pubDate>Wed, 11 Jan 2017 13:18:36 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
New version of Piwik: &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-0-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-0-1/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/96#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/95</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/95</guid>
        <title>#95: Piwik 3.0.0</title>
        <pubDate>Mon, 09 Jan 2017 11:16:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
New version of Piwik, see &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-3-0-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-3-0-0/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/95#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/93</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/93</guid>
        <title>#93: Piwik 2.17.1</title>
        <pubDate>Fri, 02 Dec 2016 14:11:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/93#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/91</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/91</guid>
        <title>#91: Piwik 2.17.0</title>
        <pubDate>Thu, 27 Oct 2016 19:08:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
No security implications, see the &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-17-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/91#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/87</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/87</guid>
        <title>#87: Piwik 2.16.5</title>
        <pubDate>Wed, 05 Oct 2016 13:07:17 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-16-5/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.16.5 fixes a regression introduced yesterday in Piwik 2.16.3 and not fully fixed in Piwik 2.16.4. The Scheduled reports were not working for websites where the website’s timezone was UTC+N or UTC-N. This is now fixed.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/87#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/84</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/84</guid>
        <title>#84: Piwik 2.16.4</title>
        <pubDate>Tue, 04 Oct 2016 11:54:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-16-4/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.16.4 fixes a regression introduced yesterday in Piwik 2.16.3. The Scheduled reports were not working for websites where the website’s timezone was UTC+N or UTC-N. This is now fixed.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/84#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/83</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/83</guid>
        <title>#83: Piwik 2.16.3</title>
        <pubDate>Mon, 03 Oct 2016 10:00:18 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-16-3/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Changelog&lt;/a&gt; contains:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="Securityrelease"&gt;Security release&lt;/h2&gt;
&lt;p&gt;
&lt;strong&gt;&lt;span style="color: #FF0000"&gt;This release is rated critical.&lt;/span&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
The Piwik security engineering team has internally identified a critical security issue and has fixed it in Piwik 2.16.3. We recommend all users to upgrade to this latest version.
&lt;/p&gt;
&lt;h2 id="Databaseupgrade"&gt;Database upgrade&lt;/h2&gt;
&lt;p&gt;
Note: &lt;strong&gt;This release contains major database upgrades&lt;/strong&gt; and upgrading your database will take a long time if you have a lot of data in your database.
&lt;/p&gt;
&lt;p&gt;
Please make sure you read the &lt;a class="ext-link" href="https://piwik.org/docs/update/#database-upgrade-for-high-traffic-piwik-servers"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Update Piwik guide for high traffic instances&lt;/a&gt;.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/83#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/80</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/80</guid>
        <title>#80: Piwik 2.16.2</title>
        <pubDate>Tue, 16 Aug 2016 11:08:37 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;p&gt;
We are proud to announce Piwik 2.16.2: a new minor release of Piwik!
&lt;/p&gt;
&lt;p&gt;
We have identified and fixed several XSS security issues in this release.
&lt;/p&gt;
&lt;p&gt;
This release is rated critical.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-16-2/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-2-16-2/&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/80#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/71</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/71</guid>
        <title>#71: Piwik 2.16.1</title>
        <pubDate>Tue, 12 Apr 2016 10:33:41 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Updated needed, see &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-16-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-2-16-1/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/71#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/61</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/61</guid>
        <title>#61: Piwik 2.16.0</title>
        <pubDate>Sun, 07 Feb 2016 10:41:42 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-16-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="Whatsnew"&gt;What’s new?&lt;/h2&gt;
&lt;p&gt;
Piwik 2.16.0 is a release which includes more than 250 closed issues. To learn about the most important and visible changes, read our blog post: &lt;a class="ext-link" href="http://piwik.org/blog/2016/02/whats-new-piwik-2-16-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;What’s new in Piwik 2.16.0&lt;/a&gt;?
&lt;/p&gt;
&lt;p&gt;
This release is our &lt;a class="ext-link" href="https://piwik.org/blog/2016/01/announcing-long-term-support-in-piwik-2-the-analytics-platform-for-your-mission-critical-projects/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Long Term Support&lt;/a&gt; release.
&lt;/p&gt;
&lt;p&gt;
263 tickets have been closed by more than 30 contributors!
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/61#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/46</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/46</guid>
        <title>#46: Piwik 2.15.0</title>
        <pubDate>Fri, 16 Oct 2015 09:08:19 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-15-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik 2.15.0&lt;/a&gt; changelog:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
We are proud to announce Piwik 2.15.0 Release Candidate: a new major release of Piwik!
&lt;/p&gt;
&lt;h2 id="Whatsnew"&gt;What’s new?&lt;/h2&gt;
&lt;p&gt;
Piwik 2.15.0 is our Long Term Support release for Piwik 2.X. This release aims to be outstanding from a performance, security, and reliability point of view. It also includes a beautiful new design which lets you focus on your data, and a new awesome search bar to lets you easily navigate to any menu, website or segment in your Piwik dashboards. For administrators and power user, this release includes new diagnostic tools, logging messages, a new Log viewer plugin, and better overall performance and scalability. There are dozens other improvements, see the full list below. Piwik 2.15.0 is built to last.
&lt;/p&gt;
&lt;h2 id="Securityrelease"&gt;Security release&lt;/h2&gt;
&lt;p&gt;
&lt;em&gt;This release is rated critical.&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
We are grateful for Security researchers who disclosed security issues privately to the Piwik Security Response team: Elamaran Venkatraman, Egidio Romano and Dmitriy Shcherbatov. The following vulnerabilities were fixed: XSS, CSRF, possible file inclusion in older PHP versions (low impact), possible Object Injection Vulnerability (low impact).
&lt;/p&gt;
&lt;h2 id="Databaseupgrade"&gt;Database upgrade&lt;/h2&gt;
&lt;p&gt;
This release does not contain any major database upgrade.
&lt;/p&gt;
&lt;h2 id="PlatformChanges"&gt;Platform Changes&lt;/h2&gt;
&lt;p&gt;
Piwik is an open analytics platform. In an effort to help Piwik developers learn about improvements and changes in the core APIs, we document the changes since the last release.
&lt;/p&gt;
&lt;p&gt;
In this 2.15.0 release there are API deprecations, New features, New APIs, New commmands, Internal API changes.
&lt;/p&gt;
&lt;p&gt;
Read more in Platform Changelog for Developers to see all changes to the platform and APIs (you can also find it in the CHANGELOG.md in the root of your Piwik)
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/46#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/33</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/33</guid>
        <title>#33: Piwik 2.14.3</title>
        <pubDate>Mon, 24 Aug 2015 11:06:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-14-3/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
August 5, 2015
&lt;/p&gt;
&lt;p&gt;
Piwik 2.14.3 is a new minor release of Piwik.
&lt;/p&gt;
&lt;p&gt;
What’s new?
&lt;/p&gt;
&lt;p&gt;
This release addresses a regression introduced in 2.14.2 that prevents users from installing Piwik in some cases.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/33#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/30</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/30</guid>
        <title>#30: Piwik 2.14.2</title>
        <pubDate>Tue, 28 Jul 2015 10:48:31 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-14-2/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="WhatsnewinPiwik2.14.2"&gt;What’s new in Piwik 2.14.2?&lt;/h2&gt;
&lt;p&gt;
In this release we have focused on fixing a few regressions reported in the last major release Piwik 2.14.0, as well as 15 other small improvements. As always we – the Piwik team – are very interested to hear your feedback!
&lt;/p&gt;
&lt;p&gt;
15 tickets have been closed by 6 contributors.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
(I'll do this now and record the time in August)
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/30#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/29</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/29</guid>
        <title>#29: Piwik 2.14.1</title>
        <pubDate>Fri, 17 Jul 2015 08:41:19 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Piwik"&gt;Piwik&lt;/a&gt; is out, from the &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-14-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="WhatsnewinPiwik2.14.1"&gt;What’s new in Piwik 2.14.1?&lt;/h2&gt;
&lt;p&gt;
In this release we have focused on fixing a few regressions reported in the last major release Piwik 2.14.0, as well as 27 other small improvements. As always we – the Piwik team – are very interested to hear your feedback!
&lt;/p&gt;
&lt;p&gt;
27 tickets have been closed by 6 contributors.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/29#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/25</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/25</guid>
        <title>#25: Piwik 2.14.0</title>
        <pubDate>Wed, 24 Jun 2015 08:46:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of Piwik will be out very soon (probably best to wait for the full release, there is a release candidate out today) which fixes critical security issues - upgrading should take no more than 15 mins, would you like your site upgraded?
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Three security issues have been fixed. We are grateful for security researchers who responsibly disclosed these security issues to us: Abdullah Hussam Gazi (CSRF issue) and Dmitriy Shcherbatov (two XSS issues).
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-14-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/changelog/piwik-2-14-0/&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/25#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/44</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/44</guid>
        <title>#44: PHP temp session files need deleting</title>
        <pubDate>Fri, 18 Sep 2015 09:15:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
On &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; php session files are written to these directories:
&lt;/p&gt;
&lt;pre class="wiki"&gt;/var/www/piwik/tmp
/var/www/mediawiki/w/tmp
/var/www/mediawiki/tmp
/var/www/owncloud/tmp
&lt;/pre&gt;&lt;p&gt;
Something like &lt;a class="ext-link" href="https://packages.debian.org/jessie/tmpreaper"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;tmpreaper&lt;/a&gt; needs installing and configuring to delete old files.
&lt;/p&gt;
&lt;p&gt;
On &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; and &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; &lt;tt&gt;/tmp&lt;/tt&gt; is used and that could also do with old files being deleted.
&lt;/p&gt;
&lt;p&gt;
I have CC'd Mori in case there are any issues I need to be aware of regarding Drupal / Solr and temp files.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/44#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/32</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/32</guid>
        <title>#32: PHP error logs not found</title>
        <pubDate>Tue, 18 Aug 2015 14:41:56 GMT</pubDate>
        
        <dc:creator>mori</dc:creator>

        <description>&lt;p&gt;
I'm having issues on newprod, but I can't find PHP error logs. If they are logged, can you please let me know where they are? If they are not logged, can you start logging them on both CRIN2 and CRIN4? Thanks.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/32#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/19</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/19</guid>
        <title>#19: PHP Parser Error - node--country.tpl.php</title>
        <pubDate>Mon, 15 Jun 2015 10:21:19 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/19#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/66</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/66</guid>
        <title>#66: Optimise backups, omit some MySQL tables and delete old backups from s3ql</title>
        <pubDate>Tue, 08 Mar 2016 10:59:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Currently the &lt;a class="wiki" href="https://trac.crin.org.archived.website/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.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/66#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/94</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/94</guid>
        <title>#94: Ongoing high load caused by a bot</title>
        <pubDate>Thu, 15 Dec 2016 19:23:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to working out what to do with this issue...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/94#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/51</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/51</guid>
        <title>#51: Number of php5-fpm processes on Crin2</title>
        <pubDate>Wed, 09 Dec 2015 12:34:55 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Peter -- a couple of days ago the number of &lt;tt&gt;php5-fpm&lt;/tt&gt; processes on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; jumped from 9 to 39 and this uses upto 5G or RAM and there is only 4G, see the following &lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin2.crin.org/index.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Munin graphs&lt;/a&gt;:
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/51/crin2_multips-week.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/51/crin2_multips-week.png" /&gt;&lt;/a&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/51/crin2_multips_memory-week.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/51/crin2_multips_memory-week.png" /&gt;&lt;/a&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/51/crin2_memory-week.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/51/crin2_memory-week.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Note: See &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/TracTickets"&gt;TracTickets&lt;/a&gt; for help on using tickets.
&lt;/p&gt;
&lt;p&gt;
Any idea what changed?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/51#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/107</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/107</guid>
        <title>#107: New cert for Fetechmail</title>
        <pubDate>Tue, 04 Apr 2017 13:15:41 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
See &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Trac#email2trac"&gt;wiki:Trac#email2trac&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/107#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/113</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/113</guid>
        <title>#113: MySQL Performance</title>
        <pubDate>Tue, 25 Apr 2017 11:22:11 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/113#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/106</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/106</guid>
        <title>#106: MySQL Error</title>
        <pubDate>Mon, 27 Mar 2017 13:37:30 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
On Saturday morning the MySQL database on &lt;a class="wiki" href="https://trac.crin.org.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/106#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/119</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/119</guid>
        <title>#119: MySQL Downtime</title>
        <pubDate>Thu, 15 Jun 2017 10:31:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Just after midnight last night MySQL appears to have started having some issues.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/119#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/9</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/9</guid>
        <title>#9: Monitor and adjust server settings after Crin1 and Crin2 server go live</title>
        <pubDate>Thu, 07 May 2015 11:33:28 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
After the &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin1"&gt;Crin1&lt;/a&gt; and &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; server go live there will, no doubt, need to be some monitoring and adjustment of memory allocations, process numbers etc for MySQL, Memcache, Nginx and MySQL, this task will depend on having a &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Munin"&gt;Munin&lt;/a&gt; server and clients set up.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/9#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/55</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/55</guid>
        <title>#55: Migrating Crin2 server to new hardware</title>
        <pubDate>Fri, 01 Jan 2016 18:21:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
In order for the &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; server to have it's RAM doubled it needs to be migrated to a different physical server, I would expect this would take between 15 mins and an hour at most, is there any preference when this is done? I'd suggest doing it this weekend before everybody is back at work on Monday would make sense? I have contacted 1984.is about it and they can script it to happen at what ever time is best.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/55#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/50</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/50</guid>
        <title>#50: Migrate to INNODB</title>
        <pubDate>Wed, 25 Nov 2015 09:50:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from Peter:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
What is involved in changing any of the underlying server resources for
Crin.org.
&lt;/p&gt;
&lt;p&gt;
I think we generally have too many CPU's and not enough memory.
&lt;/p&gt;
&lt;p&gt;
To improve the site performance, we need to move the database to INNODB.
But we are also already using swap on the DB server, and INNODB wants the
entire DB in ram. I think we should switch to at least 8GB ram, but can
probably scale down to 4 cpus - and still get a performance increase.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/50#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/3</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/3</guid>
        <title>#3: Migrate ownCloud from GreenQloud</title>
        <pubDate>Wed, 29 Apr 2015 08:54:29 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Migrate the ownCloud site from the GreenQloud server to crin1.crin.org.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/3#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/4</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/4</guid>
        <title>#4: Migrate Piwik from GreenQloud</title>
        <pubDate>Wed, 29 Apr 2015 08:55:48 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Migrate the &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; Piwik site for the GreenQloud server to crin1.crin.org.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/4#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/5</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/5</guid>
        <title>#5: Migrate MediaWiki from GreenQloud</title>
        <pubDate>Wed, 29 Apr 2015 08:56:55 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Migrate the MediaWiki site at &lt;a class="ext-link" href="http://wiki.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wiki.crin.org/&lt;/a&gt; to crin1.crin.org.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/5#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/6</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/6</guid>
        <title>#6: Migrate Drupal site from GreenQloud</title>
        <pubDate>Wed, 29 Apr 2015 08:58:46 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Migrate the Drupal site at &lt;a class="ext-link" href="https://crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://crin.org/&lt;/a&gt; from GreenQloud to crin2.crin.org for Nginx and Solr and Memcache and crin1.crin.org for MySQL.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/6#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/34</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/34</guid>
        <title>#34: Memcache Munin Stats</title>
        <pubDate>Mon, 07 Sep 2015 09:48:01 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Munin stats for memcache stopped at the and of August 2015 and I'm not sure why.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/34/crin2_2015-09-07_memcached_bytes-week.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/34/crin2_2015-09-07_memcached_bytes-week.png" /&gt;&lt;/a&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/34/crin2_2015-09-07_memcached_rates-week.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/34/crin2_2015-09-07_memcached_rates-week.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/34#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/45</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/45</guid>
        <title>#45: MediaWiki 1.23.11</title>
        <pubDate>Fri, 16 Oct 2015 08:44:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/45#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/133</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/133</guid>
        <title>#133: Matomo 3.5.0</title>
        <pubDate>Wed, 09 May 2018 09:01:31 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Upgrading to the latest version.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/133#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/130</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/130</guid>
        <title>#130: Matomo 3.3.0</title>
        <pubDate>Mon, 15 Jan 2018 09:59:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of Matomo (formally Piwik) is out, 3.3.0,
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://matomo.org/changelog/matomo-3-3-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://matomo.org/changelog/matomo-3-3-0/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/130#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/75</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/75</guid>
        <title>#75: Load spike and small downtime</title>
        <pubDate>Sun, 03 Jul 2016 18:00:34 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since about 8:10am this morning there has been a noticeable increase in bandwidth usage and load on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; and at 18:33, for 20 seconds, the Webarchitects monitoring server was unable to connect.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/75#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/116</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/116</guid>
        <title>#116: Limit the number of MySQL connections from Crin4 to Crin1</title>
        <pubDate>Wed, 17 May 2017 11:44:18 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Both the dev, &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin4"&gt;Crin4&lt;/a&gt; and live &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;, servers use the MySQL database on &lt;a class="wiki" href="https://trac.crin.org.archived.website/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.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/116#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/64</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/64</guid>
        <title>#64: Let's Encrypt HTTPS Certs</title>
        <pubDate>Fri, 26 Feb 2016 11:30:54 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
These certs, on &lt;a class="wiki" href="https://trac.crin.org.archived.website/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.archived.website/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.crin.org.archived.website/&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.archived.website/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.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/64#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/131</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/131</guid>
        <title>#131: Let's Encrypt Certificates</title>
        <pubDate>Tue, 20 Feb 2018 21:17:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/131#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/99</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/99</guid>
        <title>#99: Let's Encrypt Cert for CRIN.org</title>
        <pubDate>Mon, 30 Jan 2017 14:32:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/99#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/8</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/8</guid>
        <title>#8: Install phpMyAdmin on crin1 and enable encrypted connections from crin2</title>
        <pubDate>Wed, 29 Apr 2015 11:34:03 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The plan is to have Drupal on crin2 connecting to the MySQL server on crin1 using SSL/TLS and also have phpMyAdmin running on crin1 with HTTP Authentication.
&lt;/p&gt;
&lt;p&gt;
See:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.howtoforge.com/managing-multiple-mysql-servers-from-one-phpmyadmin-installation-using-ssl-encryption"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.howtoforge.com/managing-multiple-mysql-servers-from-one-phpmyadmin-installation-using-ssl-encryption&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/8#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/117</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/117</guid>
        <title>#117: Install Newrelic on Crin2</title>
        <pubDate>Wed, 17 May 2017 11:51:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Peter has requested that Newrelic be installed on &lt;a class="wiki" href="https://trac.crin.org.archived.website/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.archived.website/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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/117#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/10</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/10</guid>
        <title>#10: Install Munin server and clients</title>
        <pubDate>Thu, 07 May 2015 11:35:37 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
In order to monitor and adjust memory allocations, process numbers etc for MySQL, Memcache, Nginx and MySQL (see &lt;a class="closed ticket" href="https://trac.crin.org.archived.website/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;) we will need a Munin server and clients set up so we have some data to use as a basis for making decisions.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/10#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/42</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/42</guid>
        <title>#42: How CRINmail deals with email addresses that no longer work</title>
        <pubDate>Thu, 10 Sep 2015 10:42:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/42#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/105</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/105</guid>
        <title>#105: High load and slow responses from Crin2</title>
        <pubDate>Mon, 27 Mar 2017 12:15:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Trac threw this error:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Warning:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Error with navigation contributor "&lt;a class="missing wiki"&gt;TimingEstimationAndBillingPage?&lt;/a&gt;"
&lt;/li&gt;&lt;li&gt;Error with navigation contributor "&lt;a class="missing wiki"&gt;AdminModule?&lt;/a&gt;"
&lt;/li&gt;&lt;li&gt;Error with navigation contributor "&lt;a class="missing wiki"&gt;SearchModule?&lt;/a&gt;"
&lt;/li&gt;&lt;li&gt;Failed to sync with repository "(default)": database is locked; repository information may be out of date. Look in the Trac log for more information including mitigation strategies.
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
&lt;p&gt;
And in &lt;tt&gt;/var/log/php5-fpm.log&lt;/tt&gt; we have:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[27-Mar-2017 10:20:42] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 10:30:10] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 11:54:51] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 11:56:35] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 11:57:08] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 11:57:58] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 12:01:48] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
[27-Mar-2017 12:02:26] WARNING: [pool www] server reached pm.max_children setting (10), consider raising it
&lt;/pre&gt;&lt;p&gt;
From an initial look at the Nginx logs the problem seesm to be caused but too much agressive crawling of the site by bots.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/105#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/78</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/78</guid>
        <title>#78: HTTP_PROXY possible security risk</title>
        <pubDate>Tue, 19 Jul 2016 10:21:46 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
See &lt;a class="ext-link" href="https://httpoxy.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;httpoxy&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/78#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/76</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/76</guid>
        <title>#76: Google Apps setup for crin.com</title>
        <pubDate>Wed, 06 Jul 2016 19:50:38 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is to track the time spent setting up Google Apps for crin.com.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/76#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/108</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/108</guid>
        <title>#108: Go live</title>
        <pubDate>Tue, 04 Apr 2017 16:01:05 GMT</pubDate>
        
        <dc:creator>russell</dc:creator>

        <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>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/108#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/49</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/49</guid>
        <title>#49: Frozen emails on crin4</title>
        <pubDate>Thu, 05 Nov 2015 19:22:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <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.archived.website/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.archived.website/trac/attachment/ticket/49/exim_mailqueue-day.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/49/exim_mailqueue-day.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/49#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/24</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/24</guid>
        <title>#24: Exim Mailqueue</title>
        <pubDate>Fri, 19 Jun 2015 10:04:32 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Yesterday a CRINmail newsletter was sent out (see also &lt;a class="new ticket" href="https://trac.crin.org.archived.website/trac/ticket/14#comment:5" title="defect: Blank CRINmail newsletters being sent out (new)"&gt;ticket:14#comment:5&lt;/a&gt;) and there are currently 245 emails stuck in the mail queue on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;, these are probably undeliverable addresses and there should be a way to mark them so and perhaps disable sending emails to these addresses in the future.
&lt;/p&gt;
&lt;p&gt;
In addition as the queue is greater that 100 it is resulting in &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;Munin&lt;/a&gt; sending a alert email every 5 mins, this threshold needs increasing to prevent these emails.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/24/exim_mailqueue-day-2018-06-19.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/24/exim_mailqueue-day-2018-06-19.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/24#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/7</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/7</guid>
        <title>#7: Enable Google Drive plugin for ownCloud</title>
        <pubDate>Wed, 29 Apr 2015 09:42:55 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Configure the &lt;a class="ext-link" href="https://doc.owncloud.org/server/7.0/admin_manual/configuration/external_storage_configuration_gui.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;external storage&lt;/a&gt; application on &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; on the existing GreenCloud server for mounting Google Drive.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/7#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/18</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/18</guid>
        <title>#18: Drush</title>
        <pubDate>Fri, 12 Jun 2015 16:34:39 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Drush doesn't work on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;su - www-data -s /bin/bash
drush pm-updatestatus
Command pm-updatestatus needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal        [error]
environment to run this command.
The drush command 'pm-updatestatus' could not be executed.                                                                         [error]
Drush was not able to start (bootstrap) the Drupal database.                                                                       [error]
Hint: This may occur when Drush is trying to:
 * bootstrap a site that has not been installed or does not have a configured database. In this case you can select another site
with a working database setup by specifying the URI to use with the --uri parameter on the command line. See `drush topic
docs-aliases` for details.
 * connect the database through a socket. The socket file may be wrong or the php-cli may have no access to it in a jailed shell.
See http://drupal.org/node/1428638 for details.
Drush was attempting to connect to:
 Drupal version         :  7.24
 Site URI               :  http://crin1.crin.org/
 Database driver        :  mysql
 Database hostname      :  crin1
 Database port          :
 Database username      :  drupal
 Database name          :  drupal
 PHP executable         :  /usr/bin/php
 PHP configuration      :  /etc/php5/cli/php.ini
 PHP OS                 :  Linux
 Drush script           :  /usr/local/src/drush-master/drush.php
 Drush version          :  7.0-dev
 Drush temp directory   :  /tmp
 Drush configuration    :  /var/www/.drush/drushrc.php
 Drush alias files      :
 Drupal root            :  /var/www/drupal
 Site path              :  sites/default
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/18#changelog</comments>
    </item>
 </channel>
</rss>