<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket Query</title>
    <link>http://localhost:8080/trac/query?status=!closed&amp;cc=~ade&amp;order=type</link>
    <description>Support and issues tracking for the Transition Network Web Project.</description>
    <language>en-US</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/query?status=!closed&amp;cc=~ade&amp;order=type</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/834</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/834</guid>
        <title>#834: Slovenian State info missing again</title>
        <pubDate>Thu, 26 Feb 2015 10:41:47 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
The change that you made in this ticket:
&lt;a class="ext-link" href="https://trac.transitionnetwork.org/trac/ticket/802"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.transitionnetwork.org/trac/ticket/802&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Seems to have been lost. I am no longer able to edit &lt;a class="ext-link" href="https://www.transitionnetwork.org/node/37435/edit"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/37435/edit&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
As the state/province information is missing.
&lt;/p&gt;
&lt;p&gt;
Could you re-do the change please?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/834#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/836</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/836</guid>
        <title>#836: "Date is invalid" on film content type</title>
        <pubDate>Thu, 05 Mar 2015 14:30:22 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
Don't spend more than half an hour on this, if it takes longer I'll just remove the date field instead.
&lt;/p&gt;
&lt;p&gt;
If I edit: &lt;a class="ext-link" href="https://www.transitionnetwork.org/node/35510/edit"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/35510/edit&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Or add &lt;a class="ext-link" href="https://www.transitionnetwork.org/node/add/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/add/films&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
A film, the website it returns a "Year is invalid." error.
&lt;/p&gt;
&lt;p&gt;
In the settings it's set to 'Y'
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/node-type/films/fields/field_film_year"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/node-type/films/fields/field_film_year&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I'm entering a four digit date, eg 2010
&lt;/p&gt;
&lt;p&gt;
Any ideas?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/836#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/853</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/853</guid>
        <title>#853: Parrot access please</title>
        <pubDate>Tue, 19 May 2015 17:07:13 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
Ade &amp;amp; I were going to have a play around with making a proof of concept Wordpress microsite on Parrot.
&lt;/p&gt;
&lt;p&gt;
Could you add me as a SSH user using the SSH keys associated with my sam@… account so I can follow the instructions here: &lt;a class="ext-link" href="https://trac.transitionnetwork.org/trac/wiki/ParrotServer#AddingaNewWordPressSite"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.transitionnetwork.org/trac/wiki/ParrotServer#AddingaNewWordPressSite&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Or if you'd rather not do that, just spin up a site titled 'conference15' with a user 'conference15' and my TN email as the admin email.
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/853#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/856</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/856</guid>
        <title>#856: Blocked IP?</title>
        <pubDate>Tue, 02 Jun 2015 13:12:52 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I was trying to SSH into the site and got my password wrong a couple of times.
&lt;/p&gt;
&lt;p&gt;
Shortly afterwards the site appeared to be unavailable from this location.
&lt;/p&gt;
&lt;p&gt;
It seems fine in pingdom/proxy servers.
&lt;/p&gt;
&lt;p&gt;
My guess is something like fail2ban or similar has added this IP to a blacklist?
&lt;/p&gt;
&lt;p&gt;
I wouldn't be too bothered except it's Ade's address and I think he probably wants access..
&lt;/p&gt;
&lt;p&gt;
Could you check the logs if there is a blacklist and remove 146.198.11.57
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/856#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/857</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/857</guid>
        <title>#857: Tiny MCE weirdness</title>
        <pubDate>Tue, 02 Jun 2015 15:24:33 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul,
&lt;/p&gt;
&lt;p&gt;
Myself &amp;amp; Rob have both run into an intermittent issue where when editing a panel page the WYSYWG editor (Tiny MCE) sometimes appears, sometimes doesn't.
&lt;/p&gt;
&lt;p&gt;
When it doesn't appear you are left with the plain text html editor.
&lt;/p&gt;
&lt;p&gt;
There seems to be no obvious pattern to it. So might be a tricky one to debug.
&lt;/p&gt;
&lt;p&gt;
I see the version of Tiny MCE we are using is quite old, so I was thinking perhaps we should just try upgrading it on a dev server and see if that fixes it?
&lt;/p&gt;
&lt;p&gt;
If this seems reasonable could you stick the latest Tiny MCE on your dev server so we could test it out there? Or if you have any other ideas for getting to the bottom of it..
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/857#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/859</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/859</guid>
        <title>#859: Subscription emails broken</title>
        <pubDate>Tue, 16 Jun 2015 13:08:44 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi just got this mail
&lt;/p&gt;
&lt;p&gt;
"For some reason I realized I wasn't hearing from Rob. You might want to check your system because mine hasn't changed as far as I know."
&lt;/p&gt;
&lt;p&gt;
Had a look in my inbox &amp;amp; the last mail from Drupal subscription system was on 27th of May.
&lt;/p&gt;
&lt;p&gt;
I may be the guilty party, as I did go in to edit the message around this time.
&lt;/p&gt;
&lt;p&gt;
I'll investigate via the Drupal admin interface, but has anything else happened/ been done that could have stopped the mails?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/859#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/870</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/870</guid>
        <title>#870: MediaWiki 1.23.10</title>
        <pubDate>Mon, 24 Aug 2015 12:18:48 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://https://lists.wikimedia.org/pipermail/mediawiki-announce/2015-August/000179.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;announcement&lt;/a&gt; contains:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="BugFixesin1.23.10"&gt;Bug Fixes in 1.23.10&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;(bug 67644) Make AutoLoaderTest handle namespaces
&lt;/li&gt;&lt;li&gt;(T91653) Minimal PSR-3 debug logger to support backports from 1.25+.
&lt;/li&gt;&lt;li&gt;(T102562) Fix InstantCommons parameters to handle the new HTTPS-only policy of Wikimedia Commons.
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/870#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/874</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/874</guid>
        <title>#874: Please check &amp; then install Georss if no problems</title>
        <pubDate>Tue, 29 Sep 2015 13:31:02 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
We'd like to play around with generating Georss from our current site.
&lt;/p&gt;
&lt;p&gt;
Could you have a glance at the code /test &lt;a class="ext-link" href="https://www.drupal.org/project/georss"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/georss&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
If it seems like it's going to be unproblematic then please install it on the live site.
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/874#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/893</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/893</guid>
        <title>#893: BOA Cron Jobs</title>
        <pubDate>Thu, 24 Dec 2015 11:39:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
All the BOA cron jobs were stopped on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/846#comment:88" title="maintenance: Load Spikes on BOA PuffinServer (closed: fixed)"&gt;ticket:846#comment:88&lt;/a&gt;. This ticket is for looking at them all and deciding which, if any, are needed.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/893#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/909</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/909</guid>
        <title>#909: What's involved in enabling longer Piwik reports?</title>
        <pubDate>Thu, 10 Mar 2016 15:47:27 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I seem to remember you were able to make Piwik run reports longer than a couple of months by adding some RAM? Is this a virtual thing you can do remotely? Or do you have to physically visit the box to make this happen?
&lt;/p&gt;
&lt;p&gt;
I'd like to run longer reports to do a bit of analysis, but not if it's going to cost loads to make it happen.
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/909#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/855</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/855</guid>
        <title>#855: Piwik plugins</title>
        <pubDate>Tue, 26 May 2015 12:10:13 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I spotted Piwik has some plugins to extend it's usefulness.
&lt;/p&gt;
&lt;p&gt;
I'm quite interested in playing with some of them, particularly the clickheat one:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://stats.transitionnetwork.org/index.php?module=CorePluginsAdmin&amp;amp;action=userBrowsePlugins&amp;amp;idSite=1&amp;amp;period=range&amp;amp;date=previous30&amp;amp;activated="&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stats.transitionnetwork.org/index.php?module=CorePluginsAdmin&amp;amp;action=userBrowsePlugins&amp;amp;idSite=1&amp;amp;period=range&amp;amp;date=previous30&amp;amp;activated=&lt;/a&gt;#
&lt;/p&gt;
&lt;p&gt;
Is it OK for me to install it to try? Or do you think the whole thing would grind to a halt?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/855#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/868</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/868</guid>
        <title>#868: Is conference15.tn.org backed up in a convenient manner?</title>
        <pubDate>Tue, 28 Jul 2015 13:05:25 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I was just wondering if the conference site is backed up in such a way that it would be easy to restore?
&lt;/p&gt;
&lt;p&gt;
I could set up a database backup onto some free file hosting if not?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/868#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/587</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/587</guid>
        <title>#587: Puffin MySQL Tuning</title>
        <pubDate>Thu, 05 Sep 2013 12:54:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is to track the tuning we do to MySQL on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
See also previous comments on this issue:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:12" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:12&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:15" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:15&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:16" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:16&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:17" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:17&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:20" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:20&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:29" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:29&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#SettingsChanged" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#SettingsChanged&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:39" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:39&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:56" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:56&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:57" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:57&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:60" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:60&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:65" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:65&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:66" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:66&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:67" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:67&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:68" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:68&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:82" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:82&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:85" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:85&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/587#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/701</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/701</guid>
        <title>#701: Emails &amp; Telephone calls</title>
        <pubDate>Tue, 18 Mar 2014 09:38:24 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description></description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/701#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/763</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/763</guid>
        <title>#763: Server Backups</title>
        <pubDate>Mon, 21 Jul 2014 17:09:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Two weeks ago &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754#comment:21" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;annesley asked&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
what off-site data storage, file backup and quick setup do we have?
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754#comment:22" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;answered&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
The 3 virtual servers have their file system mounted off a BSD/NFS/ZFS file server and the whole file system is backed up and stored onto another BSD/ZFS server in the same data centre. We did have backups also being copied to a server in Manchester but this is currently off-line as the Manchester server needs a disk swapping and rebuilding as a BSD/ZFS server.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
A problem with this is that it's only me and Alan that have access to these backups, so I'd like to suggest I set up a new account for backups on our backup server and sort out cron jobs to rsync data to this account and document how people can access these backups.
&lt;/p&gt;
&lt;p&gt;
The result would be that everybody would have SFTP access to 60 days worth of snapshots of backups from all three servers whenever needed without any need for my or Alan's intervention.
&lt;/p&gt;
&lt;p&gt;
I expect this would take abount an hour to set up and another hour to document and help people understand it.
&lt;/p&gt;
&lt;p&gt;
There would be no additional cost to the TN because backup space is already paid for.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/763#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/814</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/814</guid>
        <title>#814: Higher that usual loads on PuffinServer since early September</title>
        <pubDate>Wed, 03 Dec 2014 17:12:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The following &lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/load.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;load graph&lt;/a&gt; from &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; shows that the load increased substantially in early September 2014, does anyone know why?
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="http://localhost:8080/trac/attachment/ticket/814/puffin-load-2014-11-03.png"&gt;&lt;img src="http://localhost:8080/trac/raw-attachment/ticket/814/puffin-load-2014-11-03.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
When I found &lt;a class="ext-link" href="http://www.vdmi.nl/blog/i-went-drupal-733-and-all-i-got-was-slow-site"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;I went to Drupal 7.33 and all I got was a slow site&lt;/a&gt; I thought that perhaps a Drupal 7 site on the server could be the cause but 7.33 came out on &lt;a class="ext-link" href="https://www.drupal.org/drupal-7.33-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;7th November 2014&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Anyone have any ideas?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/814#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/821</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/821</guid>
        <title>#821: Projects forms being hammered by Spam</title>
        <pubDate>Wed, 07 Jan 2015 09:53:33 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Projects forms being hammered by spammers. I got 24 in the last 45 minutes.
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
What to do?
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ol&gt;&lt;li&gt;Lock off to a certain type of user?
&lt;/li&gt;&lt;li&gt;
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
?
&lt;/p&gt;
&lt;p&gt;
Adding Sam as owner to follow this up
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/821#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/824</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/824</guid>
        <title>#824: Analysis of the 2014 maintenance ticket time</title>
        <pubDate>Wed, 07 Jan 2015 15:48:14 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ed has ask that I spend up to 2 hours on an analysis of the 2014 maintenance ticket time for our meeting tomorrow in Bristol.
&lt;/p&gt;
&lt;p&gt;
See also:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/TransitionMaintenance"&gt;wiki:TransitionMaintenance&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/MaintenanceTasks"&gt;wiki:MaintenanceTasks&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/824#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/847</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/847</guid>
        <title>#847: Upgrade Servers to Debian Jessie</title>
        <pubDate>Mon, 27 Apr 2015 09:30:11 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The latest version of &lt;a class="ext-link" href="https://www.debian.org/News/2015/20150426"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Debian, Jessie, 8.0&lt;/a&gt;, came out over the weekend, we should consider upgrading the three servers, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; and what issues would arrise when we do.
&lt;/p&gt;
&lt;p&gt;
See the documentation on &lt;a class="ext-link" href="https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Upgrades from Debian 7 (wheezy)&lt;/a&gt; and &lt;a class="ext-link" href="https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Issues to be aware of for jessie&lt;/a&gt;, specifically:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#libv8"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Lack of security support for the ecosystem around libv8 and Node.js&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#apache-httpd-incomat"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Incompatible changes in Apache HTTPD 2.4&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#php-incompat"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;PHP 5.6 upgrade has behavioral changes&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/847#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/851</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/851</guid>
        <title>#851: Bot attacks on Transition Culture</title>
        <pubDate>Sun, 10 May 2015 11:12:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Yesterday there was a load spike on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; caused by a bot doing thousands of POSTs to &lt;tt&gt;xmlrpc.php&lt;/tt&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/851#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/871</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/871</guid>
        <title>#871: Brute Force Attacks Against WordPress Sites</title>
        <pubDate>Mon, 21 Sep 2015 13:41:26 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Today there have been 53,932 attempts to login to the &lt;a class="ext-link" href="http://www.transitiontowntotnes.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;TTT web site&lt;/a&gt; on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; all from the same IP address:
&lt;/p&gt;
&lt;pre class="wiki"&gt;grep POST /home/ttt/logs/access.log | grep wp-login.php | grep 217.174.240.254 | wc -l
53932
&lt;/pre&gt;&lt;p&gt;
I noticed this due the higher than usual load it was generating.
&lt;/p&gt;
&lt;p&gt;
Would it be OK to spend an hour or two installing the &lt;a class="ext-link" href="https://wordpress.org/plugins/wp-fail2ban/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;WP fail2ban&lt;/a&gt; plugin on all the sites on the server?
&lt;/p&gt;
&lt;p&gt;
Some more background on this issue:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://docs.webarch.net/wiki/WordPress#Brute_Force_Attacks"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://docs.webarch.net/wiki/WordPress#Brute_Force_Attacks&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/871#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/873</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/873</guid>
        <title>#873: New Wordpress site please</title>
        <pubDate>Tue, 22 Sep 2015 12:25:12 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I couldn't ssh into parrot for some reason, I think you said you created me a 'sam' user on there but I can't get in.
&lt;/p&gt;
&lt;p&gt;
So could you set up a new Wordpress site on there.
&lt;/p&gt;
&lt;p&gt;
wpdev.tn.org or similar, it's only going to be for testing some stuff so URL doesn't really matter.
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/873#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/875</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/875</guid>
        <title>#875: Free HTTPS certificates from Let's Encrypt</title>
        <pubDate>Mon, 05 Oct 2015 10:48:11 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From mid November 2015 &lt;a class="ext-link" href="https://www.letsencrypt.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Let's Encrypt&lt;/a&gt; should be live, providing free SSL/TLS certificates. Currently the TN pays for a Gandi wild card cert, costing £130.50 a year, in addition most the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; sites on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; don't have certs due to the cost, see &lt;a class="new ticket" href="http://localhost:8080/trac/ticket/540" title="maintenance: HTTPS for WordPress sites (new)"&gt;ticket:540&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
The &lt;a class="ext-link" href="https://github.com/letsencrypt/letsencrypt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Let's Encrypt code&lt;/a&gt; is designed to be set up to run automatically -- certs are only valid for 90 days and the automatic renewal process runs when the cert is 60 days old.
&lt;/p&gt;
&lt;p&gt;
We should consider if we want to use &lt;a class="ext-link" href="https://www.letsencrypt.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Let's Encrypt&lt;/a&gt; and what things would need to be put in place to use it, the wild card cert is due to expire on 22/01/16.
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; -- are we still going to be running &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; in January 2016? Is there any chance that we might be able to consider the suggestions in &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754#comment:61" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754#comment:61&lt;/a&gt;? I'm not sure if I want to spend time trying to get Let's Encrypt working with &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/872" title="defect: BOA 2.4.6 (closed: wontfix)"&gt;a old version of BOA&lt;/a&gt;, up to date versions of BOA might &lt;a class="ext-link" href="https://github.com/omega8cc/boa/issues/500"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;support it out of the box&lt;/a&gt;.
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;PenguinServer&lt;/a&gt; -- this site hosts a lot of sites, see &lt;a class="ext-link" href="https://penguin.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;the listing&lt;/a&gt;, automating Let's Encrypt would probably be a hour or two of work, it might makes sense to upgrade it to Debian Jessie at the same time.
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; -- I suggest we rebuild this server from scratch, this would enable it to have the latest version of the &lt;a class="ext-link" href="https://docs.webarch.net/wiki/Webarch_Secure_Hosting"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Webarch Secure Hosting scripts&lt;/a&gt; and this include support for fail2ban for &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; and phpMyAdmin, thus solving &lt;a class="new ticket" href="http://localhost:8080/trac/ticket/871" title="maintenance: Brute Force Attacks Against WordPress Sites (new)"&gt;ticket:871&lt;/a&gt; and includes automatic provisioning of Let's Encrypt certs for sites.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
What do people think?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/875#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/879</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/879</guid>
        <title>#879: MediaWiki 1.23.11</title>
        <pubDate>Fri, 16 Oct 2015 08:42:45 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>http://localhost:8080/trac/ticket/879#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/881</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/881</guid>
        <title>#881: Site on ParrotServer with a memory leak?</title>
        <pubDate>Fri, 23 Oct 2015 11:19:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It appears a site, or application, on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; might have a memory leak.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="http://localhost:8080/trac/attachment/ticket/881/parrot-memory-pinpoint-1411038915-1445598915.png"&gt;&lt;img src="http://localhost:8080/trac/raw-attachment/ticket/881/parrot-memory-pinpoint-1411038915-1445598915.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/881#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/892</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/892</guid>
        <title>#892: MediWiki Security Release: 1.26.1, 1.25.4, 1.24.5 and 1.23.12</title>
        <pubDate>Fri, 18 Dec 2015 10:46:18 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email to the &lt;a class="ext-link" href="https://lists.wikimedia.org/pipermail/mediawiki-announce/2015-December/000186.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;announcements list&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;I would like to announce the release of MediaWiki 1.26.1, 1.25.4, 1.24.5,
and
1.23.12.
These releases fix five security issues in core, in addition to other bug
fixes. Download links are given at the end of this email
== Security fixes ==
(T117899) SECURITY: $wgArticlePath can no longer be set to relative paths
that
do not begin with a slash. This enabled trivial XSS attacks. Configuration
values such as "http://my.wiki.com/wiki/$1" are fine, as are "/wiki/$1". A
value such as "$1" or "wiki/$1" is not and will now throw an error
(T119309) SECURITY: Use hash_compare() for edit token comparison
(T118032) SECURITY: Don't allow cURL to interpret POST parameters starting
with
'@' as file uploads
(T115522) SECURITY: Passwords generated by User::randomPassword() can no
longer
be shorter than $wgMinimalPasswordLength
(T97897) SECURITY: Improve IP parsing and trimming. Previous behavior could
result in improper blocks being issued
(T109724) SECURITY: Special:MyPage, Special:MyTalk, Special:MyContributions
and
related pages no longer use HTTP redirects and are now redirected by
MediaWiki
== Note about EOL of 1.24.x ==
Please note that 1.24.5 marks the end of support for the 1.24.x series of
releases. Technically this ended a few weeks ago with the release of 1.26.0
but
we dropped one final release of 1.24.x here to give it a nicer send off for
those who have not yet upgraded.
== Release notes ==
Full release notes for 1.26.1:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.26&amp;gt;
Full release notes for 1.25.4:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.25&amp;gt;
Full release notes for 1.24.5:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.24&amp;gt;
Full release notes for 1.23.12:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.23&amp;gt;
For information about how to upgrade, see
&amp;lt;https://www.mediawiki.org/wiki/Manual:Upgrading&amp;gt;
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/892#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/894</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/894</guid>
        <title>#894: Brute Force Attacks Against WordPress XMLRPC</title>
        <pubDate>Thu, 07 Jan 2016 11:23:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
For a few months I have see a lot of requests going to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; &lt;tt&gt;/xmlrpc.php&lt;/tt&gt; and wasn't sure why, now it is clear:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Instead of going against wp-login.php (which can be easily blocked or protected via .htaccess) or doing a single attempt against xmlrpc, attackers are leveraging the system.multicall method to attempt to guess hundreds of passwords within just one HTTP request.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://blog.sucuri.net/2015/10/brute-force-amplification-attacks-against-wordpress-xmlrpc.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://blog.sucuri.net/2015/10/brute-force-amplification-attacks-against-wordpress-xmlrpc.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I'd like to install &lt;a class="ext-link" href="https://wordpress.org/plugins/stop-xmlrpc-attack/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Stop XML-RPC Attack&lt;/a&gt; on all the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; site we host, unless anyone has a good reason not to. This plugin simply whitelists the JetPack/Automattic's subnets and blocks all other access to &lt;tt&gt;/xmlrpc.php&lt;/tt&gt;.
&lt;/p&gt;
&lt;p&gt;
I started tracking the abuse a while ago and you can see it and manually address it on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;sudo -i
wp-xmlrpc-abuse
IP addresses accessing xmlrpc.php more than twice for the last 1000 lines of each access.log:
      2 46.148.XX.XX
    733 195.62.53.243
    177 195.62.53.243
      2 66.76.XX.XX
dig -x 195.62.53.243 +short
  53-243.static.spheral.ru.
ipdrop 195.62.53.243
&lt;/pre&gt;&lt;p&gt;
But we need to be more pro-active in blocking access or we are going to probably see some compromised sites.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/894#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/897</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/897</guid>
        <title>#897: Hosting information/requirements for 2016</title>
        <pubDate>Tue, 19 Jan 2016 10:14:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to track the time spent on an email thread with Ade.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/897#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/901</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/901</guid>
        <title>#901: Enable SSH access to PuffinServer for Ade</title>
        <pubDate>Wed, 03 Feb 2016 13:25:27 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to track the time spent sorting out SSH access for Ade to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/901#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/903</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/903</guid>
        <title>#903: Large load spike on PuffinServer</title>
        <pubDate>Mon, 08 Feb 2016 08:46:37 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There was a large load spike this morning on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;, which appears to have been caused by 12k requests for pages (Nginx doesn't log requests for anything other than PHP generated pages) from one IP address, this IP address has been blocked and I'll post some details below.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/903#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/904</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/904</guid>
        <title>#904: Issues to consider in the migration from Drupal to WordPress</title>
        <pubDate>Fri, 19 Feb 2016 10:41:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A few weeks ago Ade said he though it would be worth me opening a ticket to use to flag up some issues to be considered in the migration of the &lt;a class="ext-link" href="https://www.transitionnetwork.org.uk/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Transition Network site&lt;/a&gt; from Drupal 6 to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/904#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/905</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/905</guid>
        <title>#905: TN site down due to redis not running</title>
        <pubDate>Thu, 25 Feb 2016 10:28:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I'm working on this...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/905#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/907</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/907</guid>
        <title>#907: TN Drupal database size</title>
        <pubDate>Wed, 02 Mar 2016 10:20:10 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
6 weeks ago the datadase dump was 447M, see &lt;a class="ext-link" href="http://trac.edgewall.org/intertrac/ticket/896%23comment%3A3" title="ticket/896#comment:3 in Trac project trac"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;trac:ticket/896#comment:3&lt;/a&gt; but now it is 1.8G:
&lt;/p&gt;
&lt;pre class="wiki"&gt;ls -lah /var/backups/mysql/sqldump/transitionnetw_0.sql
-rw------- 1 root root 1.8G Mar  2 01:23 /var/backups/mysql/sqldump/transitionnetw_0.sql
&lt;/pre&gt;&lt;p&gt;
Anyone have any idea what happened to cause this? Are we keeping too many log entries?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/907#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/860</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/860</guid>
        <title>#860: More details on Server provision</title>
        <pubDate>Fri, 19 Jun 2015 10:29:09 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
we would like the following details on all servers provided by &lt;a class="missing wiki"&gt;WebArchitects?&lt;/a&gt; (Penguin, Puffin and Parrot):
&lt;/p&gt;
&lt;p&gt;
CPU type, speed, and characteristics
Disk Space
RAID type
Traffic limits and characteristics
Bandwidth limits and characteristics
&lt;/p&gt;
&lt;p&gt;
Thanks!
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/860#changelog</comments>
    </item>
 </channel>
</rss>