<?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;priority=critical&amp;desc=1&amp;order=milestone</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;priority=critical&amp;desc=1&amp;order=milestone</link>
    </image>
    <generator>Trac 1.0.2</generator>
    <item>
        <link>https://trac.crin.org.archived.website/trac/ticket/73</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/73</guid>
        <title>#73: CRIN2 ran out of memory</title>
        <pubDate>Sun, 01 May 2016 19:16:38 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The site has been down since Sun, 01 May 2016 18:05:44, it is now 8:15. I'm rebooting the server, it ran out of memory.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/73#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/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/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>
 </channel>
</rss>