<?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?status=!closed&amp;component=crin1&amp;order=priority</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?status=!closed&amp;component=crin1&amp;order=priority</link>
    </image>
    <generator>Trac 1.0.2</generator>
    <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/17</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/17</guid>
        <title>#17: Debian System Updates</title>
        <pubDate>Tue, 09 Jun 2015 18:42:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is document system updates done to the servers.
&lt;/p&gt;
&lt;p&gt;
Sources for further information:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://lists.debian.org/debian-security-announce/recent"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Recent Debian security announcements&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://mailman.owncloud.org/pipermail/announcements/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;ownCloud announcements&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
These updates are generally done using the &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/AptitudeUpdateScript"&gt;wiki:AptitudeUpdateScript&lt;/a&gt; and this records all the changes in the &lt;tt&gt;/root/Changelog&lt;/tt&gt; and then the contents of the Changelog are pasted into the ticket to document the upgrade.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/17#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/65</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/65</guid>
        <title>#65: Custom 502 and 503 pages for crin.org</title>
        <pubDate>Sun, 28 Feb 2016 14:17:03 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It would be more informative if there were custom 502 and 503 error pages for &lt;a class="ext-link" href="https://www.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/&lt;/a&gt; rather than the default Nginx ones.
&lt;/p&gt;
&lt;p&gt;
I will write up some details below on the 502 and 503's we seeing getting, see also &lt;a class="new ticket" href="https://trac.crin.org.archived.website/trac/ticket/54" title="defect: 502 Errors (new)"&gt;ticket:54&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
I'm happy to create a static 502 and static 503 error page and will look at adding it to the git repo.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/65#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/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/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/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/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/127</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/127</guid>
        <title>#127: 1984.is Server Rebuild</title>
        <pubDate>Tue, 21 Nov 2017 19:26:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Due to critical hardware failure at 1984.is all three servers needed rebuilding from scratch.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/127#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/82</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/82</guid>
        <title>#82: Attempted DDOS?</title>
        <pubDate>Sat, 24 Sep 2016 09:20:39 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Yesterday evening there 1k 502 errors caused by one user agent from multiple IP addresses. This isn't an uncommon event, I usually don't write them  up, but I thought it might be useful for Mathew if I do with this one.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/82#changelog</comments>
    </item>
 </channel>
</rss>