<?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;milestone=Maintenance&amp;group=resolution&amp;desc=1&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;milestone=Maintenance&amp;group=resolution&amp;desc=1&amp;order=type</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/495</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/495</guid>
        <title>#495: Replace Google Analytics with Piwki</title>
        <pubDate>Thu, 21 Feb 2013 10:20:25 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Unless we see any issue, turn GA off on 01/03/13.
Use Piwik instead.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/495#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/528</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/528</guid>
        <title>#528: patterns.transitionresearchnetwork.org DNS update</title>
        <pubDate>Tue, 26 Mar 2013 09:58:13 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Request from Ethan:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
We've moved the site back to the production server.  Would you be willing to set the CNAME for patterns.transitionresearchnetwork.org to patterns.transitionresearchnetwork.org.230.cldstr.com?
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
See also previous tickets &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/482" title="defect: transitionresearchnetwork.org domain name (closed: fixed)"&gt;ticket:482&lt;/a&gt; and &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/502" title="enhancement: patterns sub-domain for transitionresearchnetwork.org, was: Setting up ... (closed: fixed)"&gt;ticket:502&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/528#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/557</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/557</guid>
        <title>#557: Set up a re-direct</title>
        <pubDate>Tue, 04 Jun 2013 15:21:18 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please can you set up two re-direct/pointers
&lt;/p&gt;
&lt;p&gt;
from: "power.transitionnetwork.org"
to: "&lt;a class="ext-link" href="http://www.transitionnetwork.org/power-just-doing-stuff"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/power-just-doing-stuff&lt;/a&gt;"
&lt;/p&gt;
&lt;p&gt;
AND
&lt;/p&gt;
&lt;p&gt;
from: "&lt;a class="ext-link" href="http://www.thepowerofjustdoingstuff.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.thepowerofjustdoingstuff.org&lt;/a&gt;" (we own in gandi)
to: "&lt;a class="ext-link" href="http://www.transitionnetwork.org/power-just-doing-stuff"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/power-just-doing-stuff&lt;/a&gt;"
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/557#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/615</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/615</guid>
        <title>#615: Move to GMap 6.x-2.x-dev as and get clusterer to work</title>
        <pubDate>Sun, 10 Nov 2013 18:14:51 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
This is largely done, but the only tasks left are:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Make a patch and add to our makefile so our custom markers appear ok.
&lt;/li&gt;&lt;li&gt;Get the clusterer to work per the comments &amp;amp; issues in &lt;a href="http://localhost:8080/trac/ticket/615#comment:1" title="Comment 1 for Ticket #615"&gt;comment:1&lt;/a&gt; below.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Per an email I got from Google:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
As you may be aware, &lt;a class="missing wiki"&gt;JavaScript?&lt;/a&gt; Maps API v2 was scheduled for shutdown on May 19, 2013. After listening to feedback from developers we decided to extend the deprecation timeline by six months, to November 19, 2013 to allow more time for migration to v3 of the API.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
On November 19, 2013 we will deploy a &lt;a class="missing wiki"&gt;JavaScript?&lt;/a&gt; wrapper that attempts to automagically turn remaining v2 maps into v3 maps. Though we expect this wrapper to work for most simple maps, we cannot guarantee that your maps will continue to function. We therefore highly recommend that you migrate to v3 before November 19. The good news is that Google Maps &lt;a class="missing wiki"&gt;JavaScript?&lt;/a&gt; API v3 is more robust and feature rich than v2, and we’ve written a guide to assist the migration.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
So this ticket is to do the update to the GMap module, testing and tweaking.
&lt;/p&gt;
&lt;p&gt;
Critical as we only have until 19 November for this...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/615#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/617</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/617</guid>
        <title>#617: Help adding text to account creation email</title>
        <pubDate>Mon, 11 Nov 2013 17:16:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I want to add a link to the email a user receives following their creation of an account.
&lt;/p&gt;
&lt;p&gt;
this one: Subject: Account details for [user] at Transition Network
&lt;/p&gt;
&lt;p&gt;
Can I do this myself? I've looked in subs, notifications, logintoboggan etc. and can't find the place
&lt;/p&gt;
&lt;p&gt;
is it do-able?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/617#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/624</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/624</guid>
        <title>#624: Comment handling on pages: particularly Austerity one</title>
        <pubDate>Tue, 19 Nov 2013 11:16:02 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Rob is doing an austerity special over 8 days, with a different clip from an interview with NEF every day. I've set up a page here:
/austerity-basics
&lt;/p&gt;
&lt;p&gt;
Question:
&lt;/p&gt;
&lt;p&gt;
I know we can handle comments on pages, and I know that I don't get notifications of them. Can we arrange comment notifications for a page - asap - so that commenters get updates?
&lt;/p&gt;
&lt;p&gt;
If not, no problem. I heard about this plan *today* so am not expecting any massive tech leaps.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/624#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/628</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/628</guid>
        <title>#628: Change space notifications email from IJK.co.uk to TN.org</title>
        <pubDate>Thu, 21 Nov 2013 16:50:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The space notifications are coming from "space.transitionnetwork.org" &amp;lt;jim@…&amp;gt;
&lt;/p&gt;
&lt;p&gt;
can you make them from
"space.transitionnetwork.org" and a suitable TN address?
&lt;/p&gt;
&lt;p&gt;
Do I need to set up a suitable TN address? Perhaps
&lt;/p&gt;
&lt;p&gt;
space@…?
&lt;/p&gt;
&lt;p&gt;
Or is there a standard drupal system one in place already?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/628#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/630</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/630</guid>
        <title>#630: Archiving Transition Town Totnes site</title>
        <pubDate>Mon, 25 Nov 2013 11:54:35 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please estimate to archive TTT site as per conversation with Ed:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;convert to html
&lt;/li&gt;&lt;li&gt;host on Penguin (incl. any likely issues for Penguin doing this)
&lt;/li&gt;&lt;li&gt;any ongoing maintenance
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Then Ed will discuss with Frances at TTT as per agreement with Chris
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/630#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/631</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/631</guid>
        <title>#631: Move Transition Culture onto PARROT</title>
        <pubDate>Mon, 25 Nov 2013 11:57:44 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
We are about to move TC onto PARROT. List of likely actions here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Ed speak to Simon (move the host, keep the developer if poss)
&lt;/li&gt;&lt;li&gt;Chris speak to Simon about TC issues - traffic, size etc.
&lt;/li&gt;&lt;li&gt;analyse TC traffic and DB size
&lt;/li&gt;&lt;li&gt;prepare PARROT
&lt;/li&gt;&lt;li&gt;move TC
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Chris thinks we'll need to up PARROT to
VPS2 + 2 GB RAM
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/631#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/637</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/637</guid>
        <title>#637: What is the wordcount for the /news and /blogs/rob-hopkins teasers?</title>
        <pubDate>Thu, 28 Nov 2013 09:40:48 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/news"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/news&lt;/a&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/blogs/rob-hopkins"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/blogs/rob-hopkins&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
what is the teaser length - ie the first paragraph of a news or blog item that is published in the listings views?
&lt;/p&gt;
&lt;p&gt;
rob wants to know how many words he has for his introductions...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/637#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/648</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/648</guid>
        <title>#648: Edit the contact form reply in January</title>
        <pubDate>Thu, 12 Dec 2013 10:49:39 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Ed has edited the contact form replies for webproject@… on the contact form for TN.org which will now reply to users saying this:
&lt;/p&gt;
&lt;p&gt;
"Thank you for getting in touch. Please note that the website support is part time; and between mid-December 2013 and mid-January 2014 we are handing over the website support work as Ed goes on Paternity leave and Sam comes onboard, so please be patient - your replies are likely to take more time than usual. "
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/contact&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
SAM - when you are ready - probably mid-Jan - you will want to edit this back to something more suitable like:
&lt;/p&gt;
&lt;p&gt;
Thank you for getting in touch. Please note that the website support is part time, so while we will get back to you as soon as we can, that may be a few days
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/648#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/649</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/649</guid>
        <title>#649: Add commenting to /films/ content type in January</title>
        <pubDate>Thu, 12 Dec 2013 10:53:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
seen here:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/node-type/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/node-type/films&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/films&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/films/occupy-love"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/films/occupy-love&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/649#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/650</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/650</guid>
        <title>#650: Helping TN strategy consultation with online publishing</title>
        <pubDate>Thu, 12 Dec 2013 11:00:08 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Sarah will be working on the TN strategy and this is about the content and comms tactics therein. The guiding principle is to use TN.org as the most suitable place for this material and conversations, and social media and direct mailshots for marketing and communicating it (because Sarah/TN cannot manage multiple conversations in multiple locations atm).
&lt;/p&gt;
&lt;p&gt;
This is work for Sam to do from January onwards
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;set up a landing page ".../TN-strategy-consultation" with its own RHS block with manual links to different documents and interviews
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
SAM this can be a normal page with anchor links etc.
&lt;/p&gt;
&lt;ol start="2"&gt;&lt;li&gt;Use of blogs
&lt;/li&gt;&lt;li&gt;Rob's for outreach - it's got the momentum - for updates/alerts/subscriptions
&lt;/li&gt;&lt;li&gt;Sarah's for continuity (and looking back at it) - using tag "fn-strategy-consultation"
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="3"&gt;&lt;li&gt;other places for comms/engagement
&lt;/li&gt;&lt;li&gt;Forums not good; too open to trolls and spam; better in blog comments
&lt;/li&gt;&lt;li&gt;webinar? Possibly if suitable
&lt;/li&gt;&lt;li&gt;FB, twitter, other marketing channels - for marketing only
&lt;/li&gt;&lt;li&gt;online meeting with national hubs - quite possibly
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="4"&gt;&lt;li&gt;Direct Mail shot to PPOCs
&lt;/li&gt;&lt;li&gt;Sarah Let Sam know if this is happening; Sam you'll need to do an export of PPOCs (&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/initiatives/primary-contacts"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/initiatives/primary-contacts&lt;/a&gt;), tidy and dump into mail chimp using the standard template
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/650#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/651</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/651</guid>
        <title>#651: Report for tools content type</title>
        <pubDate>Thu, 12 Dec 2013 11:33:22 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
For January:
set up a report for tools content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;tool title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
No tools report exists yet - but lots of others here:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/651#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/652</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/652</guid>
        <title>#652: Report for resource content type</title>
        <pubDate>Thu, 12 Dec 2013 11:34:49 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
For January:
set up a report for tools content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;resource title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
you will be able to work from this report:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/resources"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/resources&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/652#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/653</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/653</guid>
        <title>#653: Report for ingredients content type</title>
        <pubDate>Thu, 12 Dec 2013 11:36:53 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
For January:
set up a report for ingredients content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;ingredient title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
No ingredients report exists yet - but lots of others here:
​&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/653#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/663</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/663</guid>
        <title>#663: De-commission the PSE</title>
        <pubDate>Wed, 18 Dec 2013 17:44:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
We are wrapping up the PSE to simplify our web traffic, codebase and support requirements before we move to TNv3.
&lt;/p&gt;
&lt;p&gt;
Ed has informed all the PSE alpha triallists twice and asked them to remove their widgets. About half have. Others say they will. So we can remove the service any time from now on.
&lt;/p&gt;
&lt;p&gt;
Ed has UNpublished the following pages:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;/pse/create
&lt;/li&gt;&lt;li&gt;/pse/about
&lt;/li&gt;&lt;li&gt;/pse/faq
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Jim - time to de-commission the service in a suitable way. Wrap this puppy up and turn it off. Please outline what you are going to do on this ticket and then do it.
&lt;/p&gt;
&lt;p&gt;
Ed suggests this is work for January 2014.
&lt;/p&gt;
&lt;p&gt;
Sam, Chris, fyi and any other changes needed?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/663#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/667</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/667</guid>
        <title>#667: Development handover process</title>
        <pubDate>Wed, 08 Jan 2014 16:40:47 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Work by the Ttech team to share Jim's knowledge and tasks around the team before he leaves in early February 2014. Please use this ticket to log your time spent on this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/667#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/685</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/685</guid>
        <title>#685: SSL certificate about to expire?</title>
        <pubDate>Thu, 23 Jan 2014 12:31:06 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris this dropped into my inbox this morning.
&lt;/p&gt;
&lt;p&gt;
Can you tell from the following if it's a certificate we still use? Does it need to be renewed?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
&lt;p&gt;
---
&lt;/p&gt;
&lt;p&gt;
Hello,
&lt;/p&gt;
&lt;p&gt;
This mail is to inform you that your certificate SSL Standard (*.transitionnetwork.org) expires today, on 2014-01-24 00:59.
&lt;/p&gt;
&lt;p&gt;
Warning: for Pro and Business certificates, web browsers have increased security. It can now take up to several weeks, and so we strongly recommend that you perform the operation as soon as possible.
&lt;/p&gt;
&lt;p&gt;
If you would like to keep your certificate, we recommend renewing it today. For this you must launch the renewal process from the following page: &lt;a class="ext-link" href="https://www.gandi.net/admin/ssl/renew/26873"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.gandi.net/admin/ssl/renew/26873&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
If you do not want to keep your certificate, then no further action is necessary on your part. It will be automatically revoked by our services and rendered useless.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/685#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/688</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/688</guid>
        <title>#688: Password for innertransition@transitionnetwork.org ?</title>
        <pubDate>Thu, 13 Feb 2014 16:59:58 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
At the moment  innertransition@… is forwarded to innertransition@…
Sophie would like to disable the forward &amp;amp; and get the password for innertransition@… so she can set up Outlook.
&lt;/p&gt;
&lt;p&gt;
Can I access these online anywhere or is it something you need to do?
&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/688#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/691</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/691</guid>
        <title>#691: Upgrade Wagn hosting for patterns site</title>
        <pubDate>Fri, 21 Feb 2014 16:53:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="http://patterns.transitionresearchnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://patterns.transitionresearchnetwork.org/&lt;/a&gt; site is running using a development set up and the webrick server falls over every now and then, so the plan is to upgrade to a production style setup.
&lt;/p&gt;
&lt;p&gt;
References:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/635" title="maintenance: Transition Research Patterns WEBrick monitoring (closed: wontfix)"&gt;ticket:635&lt;/a&gt; webrick server problems
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/TransitionResearchWagn"&gt;wiki:TransitionResearchWagn&lt;/a&gt; documentation
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/561" title="maintenance: Move Transition Research patterns Wagn website onto Penguin (closed: fixed)"&gt;ticket:561&lt;/a&gt; the last install
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="http://wagn.org/installation"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wagn.org/installation&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/691#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/705</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/705</guid>
        <title>#705: Create a contents page on TransitionCulture.org Wordpress site</title>
        <pubDate>Wed, 26 Mar 2014 15:33:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Create a contents page on TC.org to see a listing of all the blog posts. Mike suggests:
"use category post list widget to pull in the titles and then use widgetise pages to add widget to a standard page.:
&lt;/p&gt;
&lt;p&gt;
Sam to follow up. MAX time: 1 hour.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/705#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/739</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/739</guid>
        <title>#739: Set up DEV and other drupal accounts for Annesley</title>
        <pubDate>Wed, 11 Jun 2014 14:38:42 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
is this you chris? or a sam job? or paul?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/739#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/773</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/773</guid>
        <title>#773: download copy of current TN D6 website</title>
        <pubDate>Wed, 06 Aug 2014 09:58:14 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
hi, am trying to get a copy of the current TN.org D6 database and filesystem down to my laptop to develop against. i had pulled from GIT, backed up from Backup&amp;amp;Migrate and got everything working but there are things missing.
&lt;/p&gt;
&lt;p&gt;
so i want to do a file copy. i started a tar operation but the tar size went over 1.3GB and i stopped it because it shouldn't be that big. as always BOA has restricted use of the "du" command so i can't really tell why the tar was so big. and i can't "df" to see if it's a problem
&lt;/p&gt;
&lt;p&gt;
should i let it continue? why is it so big?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/773#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/778</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/778</guid>
        <title>#778: need access to Parrot</title>
        <pubDate>Wed, 27 Aug 2014 12:16:39 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
i need a publicly available &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; demo install to play with. should this be on Parrot? what (sub)domain can i use?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/778#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/822</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/822</guid>
        <title>#822: Create TRAC id for Ade</title>
        <pubDate>Wed, 07 Jan 2015 09:54:13 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
name: ade
email: adestuart@…
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/822#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/826</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/826</guid>
        <title>#826: Switching MX records from United to Google</title>
        <pubDate>Thu, 15 Jan 2015 17:15:41 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
TN are switching the MX records from United to Google on Friday 23/1/15.
&lt;/p&gt;
&lt;p&gt;
Will this affect the website/Web Architects in any way that we need to plan for in advance? Scripts, web forms etc? Anything you can think of?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/826#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/878</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/878</guid>
        <title>#878: Reconomy.org add subdomains</title>
        <pubDate>Thu, 15 Oct 2015 11:35:03 GMT</pubDate>
        
        <dc:creator>ade</dc:creator>

        <description>&lt;pre class="wiki"&gt;Hi Chris,
I thought I had added this as a ticket, but does not seem to have come
through.
I have had a request to add the following to the reconomy.org website.
I notice that i do not have permission to do this myself via gandi.net so
could you please add for me.
many thanks
Ade
We're going to need to point the REfund API to a particular subdomain
of the reconomy.org domain in the next few weeks. This will also apply
to the frontend. Is there anyone I can email about this?
Here are the proposed subdomains:
funds.reconomy.org
api.funds.reconomy.org
Both subdomains should point to this IP: 178.62.93.215
--
Ade Stuart
Web Manager - Transition network
07595 331877
The Transition Network is a registered charity
address: 43 Fore St, Totnes, Devon, TQ9 5HN, UK
website: www.transitionnetwork.org
TN company no: 6135675 TN charity no: 1128675
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/878#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/906</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/906</guid>
        <title>#906: I borked it</title>
        <pubDate>Tue, 01 Mar 2016 22:27:10 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I recklessly tried to enable a module on the site that enabled sending articles to friends by email, this seems to have been one of my less-good ideas.
&lt;/p&gt;
&lt;p&gt;
It tried to enable a print-friendly page and this seems to have brought the whole crumbling edifice down
&lt;/p&gt;
&lt;p&gt;
Sorry about that. Can you fix it?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/906#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/207</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/207</guid>
        <title>#207: Logwatch Issues</title>
        <pubDate>Fri, 17 Dec 2010 14:19:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to track items that show up in the logwatch emails to root and often just take a few mins of reading time and response.
&lt;/p&gt;
&lt;p&gt;
Any issues that look like they might take longer than a few mins should have their own tickets opened.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/207#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/208</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/208</guid>
        <title>#208: Dblog Issues</title>
        <pubDate>Fri, 17 Dec 2010 14:53:29 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote&gt;
&lt;p&gt;
"The dblog module monitors your website, capturing system events in a log to be reviewed by an authorized individual at a later time. The dblog log is simply a list of recorded events containing usage data, performance data, errors, warnings and operational information. It is vital to check the dblog report on a regular basis as it is often the only way to tell what is going on."
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/dblog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/dblog&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This is a ticket to be used to flag up issues that are not going to take up enough time that they justify their own ticket -- if an issue is raised in a comment on this ticket that does look like it's going to take some significant time then best start a new ticket for it.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/208#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/218</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/218</guid>
        <title>#218: Debian upgrades and updates</title>
        <pubDate>Thu, 06 Jan 2011 13:34:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to track debian upgrades to the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt;, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; the time they take.
&lt;/p&gt;
&lt;p&gt;
See:
&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="http://lists.askmonty.org/pipermail/announce/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MariaDB Announce List archives&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
These updates are generally done using the &lt;a class="wiki" href="http://localhost:8080/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;
&lt;p&gt;
This ticket was was originally used for the &lt;del&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/DevelopmentServer"&gt;wiki:DevelopmentServer&lt;/a&gt;&lt;/del&gt; and the &lt;del&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/NewLiveServer"&gt;wiki:NewLiveServer&lt;/a&gt;&lt;/del&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/218#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/371</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/371</guid>
        <title>#371: Piwik Hosting</title>
        <pubDate>Mon, 05 Dec 2011 21:34:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Another option to consider for Piwik would be be to use a instance on another server, and there happens to be one here that could be used:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://stats.webarch.net/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stats.webarch.net/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Could this be considered?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/371#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/382</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/382</guid>
        <title>#382: Measurement and tracking requirements for TN and PSE</title>
        <pubDate>Tue, 13 Dec 2011 04:57:12 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
to list the measurement and tracking requirements for TN and PSE so that we can assess piwik vs google and decide which way to go.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/382#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/470</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/470</guid>
        <title>#470: Penguin install and configuration</title>
        <pubDate>Sat, 15 Dec 2012 16:05:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
penguin.webarch.net is a new 2GB RAM virtual server which will replace &lt;a class="wiki" href="http://localhost:8080/trac/wiki/NewLiveServer"&gt;NewLiveServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/DevelopmentServer"&gt;DevelopmentServer&lt;/a&gt; for running all non-Drupal sites and is due to go live in early 2013. Drupal sites from the old servers will be migrated to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
This ticket has been created for tracking time and tasks done during the install.
&lt;/p&gt;
&lt;p&gt;
See &lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/wiki/PenguinServer"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://tech.transitionnetwork.org/trac/wiki/PenguinServer&lt;/a&gt; and also the corresponding &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/470#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/494</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/494</guid>
        <title>#494: Email account for TRAC</title>
        <pubDate>Thu, 21 Feb 2013 10:16:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Set up: 'trac@…'
Password: going to Chris separately
Secure SSL/TLS Settings
Username: trac@…
Password: Use the email account’s password.
Incoming Server: mail.xssl.net
IMAP: Port 993
POP3: Port 995
Outgoing Server: mail.xssl.net
SMTP: Port 465
Authentication is required for IMAP, POP3, and SMTP.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/494#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/529</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/529</guid>
        <title>#529: New Barracuda BOA-2.0.7 Edition available</title>
        <pubDate>Fri, 05 Apr 2013 08:57:09 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
There is new BOA-2.0.7 Edition of Barracuda and Octopus available.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible
to receive all security updates and new features.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/529#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/530</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/530</guid>
        <title>#530: New Barracuda BOA-2.0.8 Edition available</title>
        <pubDate>Mon, 08 Apr 2013 07:44:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
If I had known this was about to come out I would have waited before doing the BOA-2.0.7 upgrade last night on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/529" title="maintenance: New Barracuda BOA-2.0.7 Edition available (closed: fixed)"&gt;ticket:529&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
There is new BOA-2.0.8 Edition of Barracuda and Octopus available.
&lt;/p&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible to receive all security updates and new features.
&lt;/p&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Is mostly to fix a problem for people using Percona, &lt;a class="ext-link" href="https://drupal.org/node/1962690"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/1962690&lt;/a&gt; and as we are using MariaDB this isn't an issue for us.
&lt;/p&gt;
&lt;p&gt;
Other updates in this version:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;ul&gt;&lt;li&gt;Allow to use [a-z0-9] subdomains and not only [www] for IDN domain names.
&lt;/li&gt;&lt;li&gt;Change the interval between platforms builds from 5 to 3 seconds.
&lt;/li&gt;&lt;li&gt;Forced 1s Speed Booster TTL for vhosts behind local proxy is deprecated.
&lt;/li&gt;&lt;li&gt;Move old firewall logs to backups to avoid crazy load after upgrade.
&lt;/li&gt;&lt;li&gt;Nginx: Better exceptions handling in the Abuse Guard for js/shs modules.
&lt;/li&gt;&lt;li&gt;PHP: CLI is at 5.3 since BOA-2.0.4, so symlink old 5.2 binary path to 5.3
&lt;/li&gt;&lt;li&gt;Update _LENNY_TO_SQUEEZE major upgrade procedure.
&lt;/li&gt;&lt;li&gt;Update contrib with login_security-7.x-1.2
&lt;/li&gt;&lt;li&gt;Use static downloads for all distros in stable edition.
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
&lt;p&gt;
I'll do this update tonight unless there are any objections, hopefully it should be quite quick.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/530#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/531</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/531</guid>
        <title>#531: Disk usage on puffin</title>
        <pubDate>Wed, 10 Apr 2013 13:12:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The disk usage on puffing is currently at 85% and it's been going up at around 5% a week, see:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/df.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/df.html&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This will become a critical issue in a couple of weeks, it would be good to find and address the cause before then.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/531#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/532</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/532</guid>
        <title>#532: Upgrade to Mediawiki 1.19.5</title>
        <pubDate>Mon, 15 Apr 2013 13:40:34 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
New version out tonight:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Monday, April 15th between 20:00-21:00 UTC
(1-2pm PDT) Wikimedia Foundation will release security updates for
current and supported branches of the MediaWiki software. Downloads
and patches will be available at that time, with the git repositories
updated later that afternoon. CVSS scores are between 4.3 and 7.1,
most users will want to update.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000126.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000126.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/532#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/534</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/534</guid>
        <title>#534: Add accounts for Ben</title>
        <pubDate>Fri, 26 Apr 2013 17:16:23 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ben is a new member of the TTech team and accounts need setting up for him, this is a ticket to track the time taken to do this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/534#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/535</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/535</guid>
        <title>#535: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy</title>
        <pubDate>Fri, 26 Apr 2013 18:49:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Debian 7 is &lt;a class="ext-link" href="http://bits.debian.org/2013/04/release-date.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;due out on 5th May 2013&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt;, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; will need upgrading.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/535#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/536</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/536</guid>
        <title>#536: Upgrade Mediawiki to 1.19.6</title>
        <pubDate>Mon, 29 Apr 2013 20:35:32 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of Mediawiki is due out tomorrow:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Tuesday, April 30th between 20:00-21:00 UTC
(1-2pm PDT) Wikimedia Foundation will release security updates for
current and supported branches of the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; software. Downloads
and patches will be available at that time, with the git repositories
updated later that afternoon.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000128.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000128.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
The upgrade should simply be a matter of following the steps taken last time, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/532#comment:2" title="maintenance: Upgrade to Mediawiki 1.19.5 (closed: fixed)"&gt;ticket:532#comment:2&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/536#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/538</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/538</guid>
        <title>#538: intransitionmovie.com checks and updates</title>
        <pubDate>Tue, 30 Apr 2013 20:02:03 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="http://www.intransitionmovie.com/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.intransitionmovie.com/&lt;/a&gt; site has been migrated to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt;, the DNS might not have yet updated for everybody.
&lt;/p&gt;
&lt;p&gt;
Laura -- could you check that the site is working OK if you get a chance, especially the ecommerce elements?
&lt;/p&gt;
&lt;p&gt;
There are some outstanding updates, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; is version 3.3.2 need updating to 3.5.1 and there are 12 plugins with updates available:
&lt;/p&gt;
&lt;pre class="wiki"&gt;18 installed plugins:
 UA affiliates
 UA affiliates-woocommerce-light
 UA akismet
  A backupwordpress
 UI bad-behavior
 UA bwp-minify
  A contact-form-7
 UA event-o-matic
  A transposh-translation-filter-for-wordpress
 UA usernoise
  A woocommerce
 UA woocommerce-export-csv
  A woocommerce-currency-converter
 UA woocommerce-dynamic-pricing
  A woocommerce-delivery-notes
 UA woocommerce-shipping-table-rate
 UA wp-customer-reviews
 UI wp-super-cache
Legend: A = Active, I = Inactive, U = Update Available
&lt;/pre&gt;&lt;p&gt;
I'm happy to do all these updates but I wouldn't know what exactly to check to see that the updates don't break anything -- would Laura be able to help with a quick check that updates haven't broken anything?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/538#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/539</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/539</guid>
        <title>#539: REconomy site migration and updates</title>
        <pubDate>Wed, 01 May 2013 10:01:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is to keep track of the tasks undertaken and the time spent on the migration of the &lt;a class="ext-link" href="http://www.reconomy.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.reconomy.org/&lt;/a&gt; site to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/539#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/542</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/542</guid>
        <title>#542: Parrot RAM</title>
        <pubDate>Wed, 01 May 2013 20:35:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I'm concerned that &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; might not be able to cope with load spikes due to it only having 1GB of RAM, these are the Munin graphs we need to key an eye on:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/swap.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;swap&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/memory.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;memory usage&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/multips_memory.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;apache2 and mysql memory usage&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
If the server runs out of RAM it will basically stop responding.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/542#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/543</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/543</guid>
        <title>#543: Puffin Load Spike</title>
        <pubDate>Fri, 03 May 2013 20:48:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Puffin just had a massive load spike up to 65 and then it calmed down and it's up in the 70's again:
&lt;/p&gt;
&lt;pre class="wiki"&gt;uptime
 21:46:43 up 91 days,  3:01,  4 users,  load average: 73.45, 30.76, 28.09
&lt;/pre&gt;&lt;p&gt;
I'm trying to find the cause, it's making the TN site unresponsive.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/543#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/544</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/544</guid>
        <title>#544: CSF / LDF false positive blocks on Puffin</title>
        <pubDate>Sat, 04 May 2013 11:02:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to keep track of CSF /LDF issues on Puffin, see &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer#CSFLDF"&gt;wiki:PuffinServer#CSFLDF&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/544#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/546</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/546</guid>
        <title>#546: Trac documentation</title>
        <pubDate>Wed, 08 May 2013 18:47:09 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Better documentation of things like how to set billing times etc
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/546#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/547</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/547</guid>
        <title>#547: New Barracuda BOA-2.0.9 Edition available</title>
        <pubDate>Fri, 10 May 2013 11:28:17 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Do we want to upgrade to Wheezy, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/535" title="maintenance: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy (closed: fixed)"&gt;ticket:535&lt;/a&gt; at the same time as upgrading to BOA-2.0.9? Or should we wait a few weeks, as Jim suggested here &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/535#comment:3" title="maintenance: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy (closed: fixed)"&gt;ticket:535#comment:3&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I think we should schedule this update (to BOA-2.0.9) for an evening when there isn't much traffic on the site, perhaps Saturday or Sunday night. I don't think this update is super urgent as we have already upgraded Nginx, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/218#comment:80" title="maintenance: Debian upgrades and updates (closed: fixed)"&gt;ticket:218#comment:80&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
There is new BOA-2.0.9 Edition of Barracuda and Octopus available.
&lt;/p&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible
to receive all security updates and new features.
&lt;/p&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
The Changelog contains:
&lt;/p&gt;
&lt;pre class="wiki"&gt;# This is the first Barracuda-only Edition, released to address important
  security issue with Nginx server and provide system level upgrades.
  This Edition will not upgrade Aegir Master nor Aegir Satellite Instances,
  because there was no new Drupal core released since BOA-2.0.8 Edition and
  there were not enough updates to built-in platforms or contrib accumulated.
  Releasing Barracuda-only Edition separately from full Edition allows us
  to address system/services security issues without any extra delay,
  while releasing Octopus-only Edition will allow us to provide Drupal core
  or Aegir version upgrades, without affecting system level services.
  There is also another reason while separate releases will be useful.
  BOA-2.0.9 is the last Edition where Aegir 2.x uses still old Drush 4.6
  in the backend. We need to sync BOA specific Aegir 2.x with upstream
  and finally switch to Drush 5, or even Drush 6, if possible.
  This change, however, may cause issues if you still host legacy Drupal 5
  or some old Drupal 6 sites, with either core or contrib not compatible
  with PHP 5.3, which is now used by default.
  That is why we plan to introduce ability to install older/previous
  Barracuda and/or Octopus release, if you need more time to upgrade.
# New features and enhancements in this release:
  * Debian 7.0 Wheezy support.
  * Automated upgrade from Squeeze with _SQUEEZE_TO_WHEEZY=YES option.
  * Added config template with inline how-to in docs/cnf/barracuda.cnf
  * Added config template with inline how-to in docs/cnf/octopus.cnf
  * Added passwords encryption how-to in docs/BLOWFISH.txt
  * Added the list of symbols used on install in docs/PLATFORMS.txt
  * Forced mysql restart if there are too many high CPU mysqld processes.
  * Improved docs/NOTES.txt
  * Improved docs/README.txt
  * Install libpam-unix2 and libxcrypt1 by default.
  * Install s3cmd by default.
  * Issue #1974640 - Allow to use Midnight Commander for limited shell users.
  * Limited Shell Logs Monitor enabled by default.
  * Nginx: Check for Linux/Cdorked.A malware and delete if discovered.
  * Re-generate and sync Aegir passwords before and after instance upgrade.
  * The silent 'system' mode documented in docs/UPGRADE.txt
  * Allow to exclude platform from otherwise forced `drush en entitycache -y`
    if sites/all/modules/entitycache_dont_enable.info control file is present.
# Changes in this release:
  * Nginx 1.5.0 - security upgrade for CVE-2013-2028
  * PHP 5.3.25
  * Redis 2.6.13
  * Do not disable update module in platforms known to include it as required.
  * Firewall: Open port 1129 for outgoing connections (some gateways need it).
  * Force syslog module as disabled by default and save some disk I/O.
  * Tune kernel to always use max RAM and not swap, if possible.
# Fixes in this release:
  * Add outgoing port 25 SMTP to the list of requirements.
  * Firewall: Add truly permanent block for heavy abusers.
  * Fix for mytop support, available again on systems with MariaDB.
  * Fix permissions in the /data/all tree if required.
  * Fix the order of checks - they scan only the last (current) minute.
  * Force _STRONG_PASSWORDS=NO if locales still look broken on second check.
  * Improve detecting no longer running drush.php and/or cron PHP processes.
  * Improve fix_locales logic.
  * Improve global.inc symlinking on initial install and upgrade.
  * Improve messages displayed when fix_locales discovers broken locales.
  * Improve monitoring to avoid duplicate entries on low traffic systems.
  * Improve sanitize_string() filtering to avoid issues with strong passwords.
  * Improve syncpass tool - Update system user passwd and flush privileges.
  * Issue #1961226 - Warning: Could not change permissions of sites/all to 751.
  * Issue #1962458 - 403 for anonymous users on node/add.
  * Issue #1963044 - Force UTF-8 locales if not present/configured properly.
  * Issue #1974542 - Use /root/.home.no.wildcard.chmod.cnf control file.
  * Issue #1987936 - Restore ability to install PHP 5.2 for FPM and CLI.
  * Make sure that /dev/null is writable for everyone.
  * Make sure that all drushrc.php files are owned by Aegir system user.
  * Make sure that all expected sites/all/{modules,themes,libraries} dirs exist.
  * Make sure that DB server is restarted on upgrade after config tuning.
  * Make sure that pdnsd and resolvconf are properly installed.
  * Nginx: Remove duplicate Vary: Accept-Encoding headers.
  * Percona no longer supports older Ubuntu non-LTS releases.
  * PHP: Do not reload FPM every hour - it may cause error 502.
  * PHP: Fix paths depending on CLI version used.
  * PHP: Fix the extensions installation and upgrade logic.
  * PHP: Make sure that the FPM port is set correctly for D6 sites with 5.2
  * PHP: Properly uninstall all related packages when using source build.
  * PHP: Start more FPM workers on systems with enough RAM by default.
  * Purge bin logs before disabling them.
  * Run NewRelic re-install early enough to avoid locking full-upgrade.
  * Sync the load limits for spiders and backend tasks.
  * The Java/Jetty monitor should use higher allowed limits by default.
  * Update apticron message to recommend system mode instead of full upgrade.
  * Update docs for _BUILD_FROM_SRC option.
  * Use aggressive enough Jetty restart procedure on nightly services reload.
  * Use correct status messages on install and upgrade.
  * Use installer and not Aegir version download on stable install/upgrade.
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/547#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/550</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/550</guid>
        <title>#550: Transition Town Totnes migration</title>
        <pubDate>Sun, 19 May 2013 14:59:44 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It has been agreed to migrate Transition Town Totnes, &lt;a class="ext-link" href="http://transitiontowntotnes.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://transitiontowntotnes.org/&lt;/a&gt; to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; and this ticket has been created to record this process and the time spent on it and the documentation of the migration.
&lt;/p&gt;
&lt;p&gt;
There is also an issue regarding what, if anything, to do with the old Drupal site at &lt;a class="ext-link" href="http://archive.transitiontowntotnes.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://archive.transitiontowntotnes.org/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/550#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/551</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/551</guid>
        <title>#551: Mediawiki 1.19.7 upgrade</title>
        <pubDate>Tue, 21 May 2013 08:25:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From &lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-May/000130.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MediaWiki-announce&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Tuesday, May 21st between 20:00-21:00 UTC
(1-2pm PDT) Wikimedia Foundation will release security updates for
current and supported branches of the MediaWiki software. Downloads
and patches will be available at that time, with the git repositories
updated later that afternoon. Although &lt;strong&gt;MediaWiki does not have the&lt;/strong&gt;
&lt;strong&gt;vulnerable feature enabled by default&lt;/strong&gt;, most wiki using common advanced
features will want to patch for this issue.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/551#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/552</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/552</guid>
        <title>#552: Puffin Downtime 23rd May 2013</title>
        <pubDate>Thu, 23 May 2013 20:54:15 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There was a massive load spike on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; this afternoon, the load average peaked at over 60 and at exactly the same time there was also one on the virtual server serving &lt;a class="ext-link" href="http://webarch.net/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://webarch.net/&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Pingdom reported:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;www.transitionnetwork.org down since 23/05/2013  12:11:57
&lt;/li&gt;&lt;li&gt;www.transitionnetwork.org is UP again at 23/05/2013  12:19:57, after 8m of downtime
&lt;/li&gt;&lt;li&gt;www.transitionnetwork.org is down since 23/05/2013  12:26:57
&lt;/li&gt;&lt;li&gt;www.transitionnetwork.org is UP again at 23/05/2013  12:58:57, after 32m of downtime
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
When I did managed to get back into the server php-fpm and nginx were not running and it took several attempt to get them to start up.
&lt;/p&gt;
&lt;p&gt;
Attached is the munin graps of the load from today, munin didn't record the start of the spike but it did start recording it as it came down.
&lt;/p&gt;
&lt;p&gt;
This ticket has been created to report the issue and also to record anything that might be found in the logs to explain what happened.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/552#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/554</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/554</guid>
        <title>#554: Site slow down and MySQL load increase</title>
        <pubDate>Tue, 28 May 2013 18:11:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since the upgrade to &lt;a class="ext-link" href="http://blog.mariadb.org/mariadb-5-5-31-now-available/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MariaDB 5.5.31&lt;/a&gt;, done on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/218#comment:93" title="maintenance: Debian upgrades and updates (closed: fixed)"&gt;ticket:218#comment:93&lt;/a&gt; (and fixed on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/548#comment:32" title="defect: All Admin functions broken on TN.org (closed: fixed)"&gt;ticket:548#comment:32&lt;/a&gt;) there appears to have been been a noticeable slowdown in the time for pages to be generated, measuring with &lt;a class="ext-link" href="http://tools.pingdom.com/fpt/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://tools.pingdom.com/fpt/&lt;/a&gt; the front page alone takes around 5 seconds to generate.
&lt;/p&gt;
&lt;p&gt;
There is a clear increase in the amount of MySQL/MariaDB activity measured by Munin, see the attached graphs, the upgrade was done around midday on 24th May 2013. There has also been a increase in traffic according to the firewall graphs. The memory usage of redis has also dropped right down and the database memory usage has significantly increased.
&lt;/p&gt;
&lt;p&gt;
It's not totally clear if the cause of this change in behaviour of the site is related to the MySQL/MariaDB upgrade or if there was a coincidental change in the traffic to the site at the same time. There is no noticeable change in the visitors recorded in the Piwik stats.
&lt;/p&gt;
&lt;p&gt;
According to pingdom the front page of the site is now "slower than 77% of all tested websites"  with a total load time of around 6 seconds, almost all of this is down to the wait of around 5 seconds for the index.php file. This can also be tested from parrot with Apache bench, sometimes cached pages are served up and these appear in an instance, if the front page is generated it takes around 5 seconds, see &lt;a class="wiki" href="http://localhost:8080/trac/wiki/LoadTimes#a2013-05-28"&gt;wiki:LoadTimes#a2013-05-28&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/554#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/555</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/555</guid>
        <title>#555: Load spikes causing the TN site to be stopped for 15 min at a time</title>
        <pubDate>Wed, 29 May 2013 09:53:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The BOA &lt;tt&gt;/var/xdrago/second.sh&lt;/tt&gt; script is run every minute via the root crontab and if it detects a certain load level it changes the nginx config to a "high load" config which results in bots being served 503 errors when they spider the site, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/563" title="maintenance: 503 Errors (closed: fixed)"&gt;ticket:563&lt;/a&gt;. When the load goes higher and hits another threshold the &lt;tt&gt;second.sh&lt;/tt&gt; script kills the webserver applications, nginx and php-fpm, and waits till the load has dropped before starting them up again. This was happening once or twice a day following the increase in traffic around the launch of &lt;a class="ext-link" href="https://www.transitionnetwork.org/power-just-doing-stuff"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;The Power of Just Doing Stuff&lt;/a&gt;. This has been addressed by multiplying the thresholds by 5 in &lt;tt&gt;second.sh&lt;/tt&gt;.
&lt;/p&gt;
&lt;h2 id="OriginalDescription"&gt;Original Description&lt;/h2&gt;
&lt;p&gt;
This morning at 10:19:24 I received the following alert from puffin:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Subject: lfd on puffin.webarch.net: High 5 minute load average alert - 6.59
Time:                    Wed May 29 10:17:02 2013 +0100
1 Min Load Avg:          23.39
5 Min Load Avg:          6.59
15 Min Load Avg:         2.57
Running/Total Processes: 44/326
&lt;/pre&gt;&lt;p&gt;
At 10:21:57 I got an alert regarding ssh:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Service: SSH
Host: puffin
Address: puffin.webarch.net
State: CRITICAL
Date/Time: Wed May 29 10:21:57 BST 2013
Additional Info:
CRITICAL - Socket timeout after 10 seconds
&lt;/pre&gt;&lt;p&gt;
Then at 10:26:47 ssh appeared to have recovered:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Service: SSH
Host: puffin
Address: puffin.webarch.net
State: OK
Date/Time: Wed May 29 10:26:47 BST 2013
Additional Info:
SSH OK - OpenSSH_5.5p1 Debian-6+squeeze3 (protocol 2.0)
&lt;/pre&gt;&lt;p&gt;
But then pingdom reported at 10:29:07:
&lt;/p&gt;
&lt;pre class="wiki"&gt;www.transitionnetwork.org is down since 29/05/2013  10:24:57.
&lt;/pre&gt;&lt;p&gt;
There was then a report regarding Nginx at 10:32:07:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Notification Type: PROBLEM
Service: HTTP
Host: puffin
Address: puffin.webarch.net
State: CRITICAL
Date/Time: Wed May 29 10:32:07 BST 2013
Additional Info:
Connection refused
&lt;/pre&gt;&lt;p&gt;
So at 10:33:47 I ssh'd in and found that php53-fpm and nginx were not running and it took several attempts to get them running again.
&lt;/p&gt;
&lt;p&gt;
The up email from pingdom reported:
&lt;/p&gt;
&lt;pre class="wiki"&gt;www.transitionnetwork.org is UP again at 29/05/2013  10:36:57, after 12m of downtime.
&lt;/pre&gt;&lt;p&gt;
I can't find anything in the logs to indicate what caused the load spike and php-fpm and nginx to stopp running.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/555#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/556</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/556</guid>
        <title>#556: Upgrade Piwik to version 1.12</title>
        <pubDate>Thu, 30 May 2013 21:40:48 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of Piwik came out today with some interesting looking features:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://piwik.org/blog/2013/05/piwik-1-12/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/blog/2013/05/piwik-1-12/&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://piwik.org/blog/2013/05/last-piwik-1-x-release-v1-12-new-features-api-improvements-screenshots/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/blog/2013/05/last-piwik-1-x-release-v1-12-new-features-api-improvements-screenshots/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/556#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/563</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/563</guid>
        <title>#563: 503 Errors</title>
        <pubDate>Wed, 19 Jun 2013 10:59:54 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The BOA &lt;tt&gt;/var/xdrago/second.sh&lt;/tt&gt; script is run every minute via the root crontab and if it detects a certain load level it changes the nginx config to a "high load" config which results in bots being served 503 errors when they spider the site. When the load goes higher and hits another threshold the &lt;tt&gt;second.sh&lt;/tt&gt; script stops the site, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555&lt;/a&gt;.
&lt;/p&gt;
&lt;h2 id="OriginalDescription"&gt;Original Description&lt;/h2&gt;
&lt;p&gt;
The site is generating a lot of 503 errors, 83 since 6:30am today and there were around 750 yesterday.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/563#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/565</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/565</guid>
        <title>#565: Blogs breadcrumbs incorrect on listings views</title>
        <pubDate>Tue, 25 Jun 2013 13:21:56 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Blogs breadcrumbs are wrong at main all blogs view and one author's full list view:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blog&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/ed-mitchell"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/ed-mitchell&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Jim can you sort this in under 15 minutes (which is what you have left)
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/565#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/567</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/567</guid>
        <title>#567: Update BOA for new Redis 2.6.14</title>
        <pubDate>Tue, 02 Jul 2013 11:10:27 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A suggestion from Jim:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
BOA now includes Redis
2.6.14 &amp;lt;&lt;a class="ext-link" href="https://raw.github.com/antirez/redis/2.6/00-RELEASENOTES"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://raw.github.com/antirez/redis/2.6/00-RELEASENOTES&lt;/a&gt;&amp;gt; if
you do a 'barracda up-stable system'... What interests me about this is
these lines from the changelog:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
UPGRADE URGENCY: HIGH because of the following two issues:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Lua scripting + Replication + AOF in slaves problem (see Issue #1164).
&lt;/li&gt;&lt;li&gt;AOF + expires possible race condition (see Issue #1079).
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
&lt;p&gt;
It's a long shot, but that could maybe be part of the issue we've seen
recently.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I'm not sure if this is best done now or later tonight when the site is less busy?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/567#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/572</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/572</guid>
        <title>#572: Design changes for homepage and TC section</title>
        <pubDate>Wed, 17 Jul 2013 14:17:25 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Design changes for TN homepage and TC section done by Ben to be part of maintenance budget.
&lt;/p&gt;
&lt;p&gt;
list here:
&lt;a class="ext-link" href="https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/572#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/573</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/573</guid>
        <title>#573: MariaDB 5.5.32 is available for Puffin</title>
        <pubDate>Thu, 18 Jul 2013 19:11:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I could either update this via aptitude and it would be quick and have little down time or I could update it via BOA and it'll take 3 or 4 times as long and involved extra downtime.
&lt;/p&gt;
&lt;p&gt;
Jim -- which way would you like it done?
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
The MariaDB project is pleased to announce the immediate availability
of MariaDB 5.5.32.
&lt;/p&gt;
&lt;p&gt;
This is a bug-fix release. See the Release Notes and Changelog for
details.
&lt;/p&gt;
&lt;p&gt;
MariaDB 5.5.32 Stable (GA)
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Release Notes: &lt;a class="ext-link" href="https://kb.askmonty.org/en/mariadb-5532-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://kb.askmonty.org/en/mariadb-5532-release-notes&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Changelog: &lt;a class="ext-link" href="https://kb.askmonty.org/en/mariadb-5532-changelog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://kb.askmonty.org/en/mariadb-5532-changelog&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="ext-link" href="http://lists.askmonty.org/pipermail/announce/2013-July/000048.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.askmonty.org/pipermail/announce/2013-July/000048.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/573#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/577</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/577</guid>
        <title>#577: Transition Streets Wordpress Migration</title>
        <pubDate>Tue, 06 Aug 2013 21:28:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to document the migration of the Transition Totnes &lt;a class="ext-link" href="http://www.transitionstreets.org.uk/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionstreets.org.uk/&lt;/a&gt; &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;wiki:WordPress&lt;/a&gt; site to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/577#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/580</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/580</guid>
        <title>#580: php5-fpm starting when puffin boots</title>
        <pubDate>Mon, 12 Aug 2013 16:03:06 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
When &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; is booted &lt;tt&gt;/etc/init.d/php5-fpm&lt;/tt&gt; is started and this causes errors with the site.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/580#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/581</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/581</guid>
        <title>#581: Remove 'add to newsletter' option for site editors/admins</title>
        <pubDate>Mon, 26 Aug 2013 13:24:17 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please remove the option for site editors/admins to 'add this to the newsletter' (which would send it to the newsletter nodequeue). Please also for now make the newsletter nodequeue non-active.
&lt;/p&gt;
&lt;p&gt;
It's been confusing for staff members, and was for the simmplemail service really, so we're going to trial using a google doc for staff to add their stories to the newsletter instead.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/581#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/585</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/585</guid>
        <title>#585: TTech Meeting 5th September 2013</title>
        <pubDate>Thu, 05 Sep 2013 07:47:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket has been created for the TTech Skype meeting due to take place today.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/585#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/586</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/586</guid>
        <title>#586: New Relic Monitoring for BOA</title>
        <pubDate>Thu, 05 Sep 2013 08:35:17 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to document the consideration, and possible installation, of &lt;a class="ext-link" href="https://newrelic.com/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://newrelic.com/&lt;/a&gt; on the &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/586#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/588</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/588</guid>
        <title>#588: RSS feed caching</title>
        <pubDate>Fri, 06 Sep 2013 09:43:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
At the meeting on 5th September &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt; one thing we discussed was that:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
The biggest single source of bandwidth by URL is Rob's RSS feed, 34.5GB of data, 150k hits. This represents half the total site data transfer, the RSS files is 0.4MB but will hopefully be mostly served gzipped at 0.1MB.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
This ticket is to follow up on that -- are the RSS feeds served directly by Nginx?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/588#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/589</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/589</guid>
        <title>#589: Blocking spammers at a firewall level</title>
        <pubDate>Fri, 06 Sep 2013 09:48:59 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
At the meeting on 5th September &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt; one thing we discussed was that for August 2013:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
More data is transferred for /user/register than the front page, 5.1GB compared to 3.6GB.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Most of this will be spam bots trying to register to post spam. Jim suggested that we could look at blocking some of these spam bots at a firewall level to save on resources. This ticket is to follow up on this suggestion.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/589#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/591</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/591</guid>
        <title>#591: Move MySQL temporary directory to tmpfs</title>
        <pubDate>Mon, 09 Sep 2013 12:47:41 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
Chris, please read: &lt;a class="ext-link" href="http://2bits.com/articles/reduce-your-servers-resource-usage-moving-mysql-temporary-directory-ram-disk.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://2bits.com/articles/reduce-your-servers-resource-usage-moving-mysql-temporary-directory-ram-disk.html&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I think we could easily drop a little MySQL memory to give it some in-memory disk space to do the temporary table munching Drupal is causing it. I see there are already some mounted tmpfs partitions.
&lt;/p&gt;
&lt;p&gt;
Related to &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/590" title="defect: Drupal performance improvements (assigned)"&gt;#590&lt;/a&gt; (proposal L: Review slow query log, explain queries, tweak as necessary/flag poorly behaving modules)
&lt;/p&gt;
&lt;p&gt;
What do you think? Worth doing?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/591#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/593</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/593</guid>
        <title>#593: Migrating Puffin to a ZFS file server</title>
        <pubDate>Wed, 11 Sep 2013 15:52:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is for the migration of &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; to a ZFS file server, this will involve some downtime but should result in better IO and easier backups.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/593#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/594</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/594</guid>
        <title>#594: WordPress 3.6.1 Maintenance and Security Release</title>
        <pubDate>Wed, 11 Sep 2013 22:05:01 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The following is from &lt;a class="ext-link" href="http://wordpress.org/news/2013/09/wordpress-3-6-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wordpress.org/news/2013/09/wordpress-3-6-1/&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; 3.6.1 is also a security release for all previous &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; versions and we strongly encourage you to update your sites immediately. It addresses three issues fixed by the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; security team:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Block unsafe PHP unserialization that could occur in limited situations and setups, which can lead to remote code execution. Reported by Tom Van Goethem.
&lt;/li&gt;&lt;li&gt;Prevent a user with an Author role, using a specially crafted request, from being able to create a post “written by” another user. Reported by Anakorn Kyavatanakij.
&lt;/li&gt;&lt;li&gt;Fix insufficient input validation that could result in redirecting or leading a user to another website. Reported by Dave Cummo, a Northrup Grumman subcontractor for the U.S. Centers for Disease Control and Prevention.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Additionally, we’ve adjusted security restrictions around file uploads to mitigate the potential for cross-site scripting.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/594#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/595</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/595</guid>
        <title>#595: Upgrade Mediawiki to 1.19.8 from 1.19.7</title>
        <pubDate>Wed, 11 Sep 2013 22:18:05 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From &lt;a class="ext-link" href="https://git.wikimedia.org/blob/mediawiki%2Fcore.git/REL1_19/RELEASE-NOTES-1.19"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://git.wikimedia.org/blob/mediawiki%2Fcore.git/REL1_19/RELEASE-NOTES-1.19&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="MediaWiki1.19.8"&gt;MediaWiki 1.19.8&lt;/h2&gt;
&lt;p&gt;
This is a security and maintenance release of the MediaWiki 1.19 branch.
&lt;/p&gt;
&lt;h3 id="Changessince1.19.7"&gt;Changes since 1.19.7&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;SECURITY: Sanitize ResourceLoader exception messages
&lt;/li&gt;&lt;li&gt;SECURITY: Token-getting functions will fail when using jsonp callbacks.
&lt;/li&gt;&lt;li&gt;SECURITY: Fix extension detection with 2 .'s
&lt;/li&gt;&lt;li&gt;Allow a string other than '*' as condition for DatabaseBase::delete()
&lt;/li&gt;&lt;li&gt;Purge upstream caches when deleting file assets.
&lt;/li&gt;&lt;li&gt;jquery.tablesorter: Add missing dependency on jquery.mwExtension
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/595#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/597</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/597</guid>
        <title>#597: Default owner for tickets</title>
        <pubDate>Tue, 17 Sep 2013 08:04:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ben reported that the default owner for tickets is laura and that this should be changed.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/597#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/599</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/599</guid>
        <title>#599: Server time drift</title>
        <pubDate>Sun, 29 Sep 2013 21:57:59 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The servers are not keeping good time at the moment.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/599#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/600</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/600</guid>
        <title>#600: Numbers missing from Initiatives search page</title>
        <pubDate>Mon, 30 Sep 2013 11:46:20 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
When users do a search on /initiatives we are missing a number which pertains to the results of the report:
&lt;/p&gt;
&lt;p&gt;
It should say "XXX initiatives match your search criteria"
&lt;/p&gt;
&lt;p&gt;
The XXX bit is missing
&lt;/p&gt;
&lt;p&gt;
please check and resolve
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/600#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/601</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/601</guid>
        <title>#601: TTech Meeting 3rd October 2013</title>
        <pubDate>Thu, 03 Oct 2013 09:03:42 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket for notes and times for the online meeting held on 3rd October 2013.
&lt;/p&gt;
&lt;p&gt;
The ticket for the last meeting is &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/601#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/611</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/611</guid>
        <title>#611: Adding Trac Account for Alan</title>
        <pubDate>Thu, 17 Oct 2013 12:55:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Alan, the other sysadmin at Webarchitects is in a  better position than me to help with some of the more complex sysadmin issues so I hope it's OK that I have added an account for him here following the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/TracUserAdmin"&gt;wiki:TracUserAdmin&lt;/a&gt; notes.
&lt;/p&gt;
&lt;p&gt;
He is looking at helping with these tickets:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/599" title="maintenance: Server time drift (closed: fixed)"&gt;ticket:599&lt;/a&gt; Server time drift
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555&lt;/a&gt; Load spikes causing the TN site to be stopped for 15 min at a time
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/593" title="maintenance: Migrating Puffin to a ZFS file server (closed: fixed)"&gt;ticket:593&lt;/a&gt; Migrating Puffin to a ZFS file server
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
I don't expect he will be recording much time, I hope that is OK, he already has sudo access to all the servers.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/611#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/612</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/612</guid>
        <title>#612: Upgrade to BOA-2.1.1 Stable Edition</title>
        <pubDate>Sun, 03 Nov 2013 11:11:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I have been sent this email from &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
There is new BOA-2.1.0 Stable Edition available.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible
to receive all security updates and new features.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I could potentially do this upgrade tonight as it's a quite time for the server -- Jim, any reason not to apply this update tonight?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/612#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/613</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/613</guid>
        <title>#613: Parrot mysql console errors</title>
        <pubDate>Mon, 04 Nov 2013 09:48:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I connected to the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; &lt;a class="wiki" href="http://localhost:8080/trac/wiki/XenShell"&gt;wiki:XenShell&lt;/a&gt; to check the bandwidth usage and there was the following output, we should try to track down the cause of this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;parrot login: [41569.058444] hrtimer: interrupt took 59422559 ns
[442920.164115] INFO: task mysqld:3522 blocked for more than 120 seconds.
[442920.164133] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[442920.164142] mysqld        D ffff880003755c40     0  3522    711 0x00000000
[442920.164153]  ffff8800bfa68e20 0000000000000282 ffff8800565fb9e8 ffff8800565fb9e4
[442920.164165]  00000000000157c8 0000000000000000 000000000000f9e0 ffff8800565fbfd8
[442920.164175]  00000000000157c0 00000000000157c0 ffff88000180c6a0 ffff88000180c998
[442920.164185] Call Trace:
[442920.164200]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164211]  [&amp;lt;ffffffff8130de82&amp;gt;] ? io_schedule+0x73/0xb7
[442920.164219]  [&amp;lt;ffffffff8110fbd1&amp;gt;] ? sync_buffer+0x3b/0x40
[442920.164228]  [&amp;lt;ffffffff8130f142&amp;gt;] ? _spin_unlock_irqrestore+0xd/0xe
[442920.164237]  [&amp;lt;ffffffff8130e292&amp;gt;] ? __wait_on_bit_lock+0x3f/0x84
[442920.164246]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164253]  [&amp;lt;ffffffff8130e342&amp;gt;] ? out_of_line_wait_on_bit_lock+0x6b/0x77
[442920.164262]  [&amp;lt;ffffffff81066360&amp;gt;] ? wake_bit_function+0x0/0x23
[442920.164271]  [&amp;lt;ffffffff8110ffc3&amp;gt;] ? sync_dirty_buffer+0x29/0x93
[442920.164286]  [&amp;lt;ffffffffa001be04&amp;gt;] ? journal_dirty_data+0xd1/0x1b0 [jbd]
[442920.164301]  [&amp;lt;ffffffffa0032f4c&amp;gt;] ? ext3_journal_dirty_data+0xf/0x34 [ext3]
[442920.164312]  [&amp;lt;ffffffffa00313f5&amp;gt;] ? walk_page_buffers+0x65/0x8b [ext3]
[442920.164322]  [&amp;lt;ffffffffa0032f71&amp;gt;] ? journal_dirty_data_fn+0x0/0x13 [ext3]
[442920.164333]  [&amp;lt;ffffffffa0034a93&amp;gt;] ? ext3_ordered_write_end+0x73/0x10f [ext3]
[442920.164343]  [&amp;lt;ffffffff810b648a&amp;gt;] ? generic_file_buffered_write+0x18d/0x278
[442920.164352]  [&amp;lt;ffffffff810b6926&amp;gt;] ? __generic_file_aio_write+0x25f/0x293
[442920.164361]  [&amp;lt;ffffffff810b69b3&amp;gt;] ? generic_file_aio_write+0x59/0x9f
[442920.164369]  [&amp;lt;ffffffff810f0316&amp;gt;] ? do_sync_write+0xce/0x113
[442920.164377]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[442920.164385]  [&amp;lt;ffffffff8130f6fa&amp;gt;] ? error_exit+0x2a/0x60
[442920.164394]  [&amp;lt;ffffffff8101251d&amp;gt;] ? retint_restore_args+0x5/0x6
[442920.164403]  [&amp;lt;ffffffff8102de30&amp;gt;] ? pvclock_clocksource_read+0x3a/0x8b
[442920.164411]  [&amp;lt;ffffffff810f0c68&amp;gt;] ? vfs_write+0xa9/0x102
[442920.164419]  [&amp;lt;ffffffff810f0d7d&amp;gt;] ? sys_write+0x45/0x6e
[442920.164427]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[442920.164435] INFO: task mysqld:21061 blocked for more than 120 seconds.
[442920.164441] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[442920.164448] mysqld        D ffff8800018b0e20     0 21061    711 0x00000000
[442920.164457]  ffff8800018b0e20 0000000000000282 ffffffff8100c426 ffffffff8100e233
[442920.164469]  ffff880003755d10 0000000000000002 000000000000f9e0 ffff8800bdde3fd8
[442920.164480]  00000000000157c0 00000000000157c0 ffff8800bd9462e0 ffff8800bd9465d8
[442920.164492] Call Trace:
[442920.164498]  [&amp;lt;ffffffff8100c426&amp;gt;] ? pfn_to_mfn+0xe/0x22
[442920.164506]  [&amp;lt;ffffffff8100e233&amp;gt;] ? arbitrary_virt_to_machine+0x28/0x73
[442920.164515]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164523]  [&amp;lt;ffffffff8106ce4a&amp;gt;] ? timekeeping_get_ns+0xe/0x2e
[442920.164531]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164538]  [&amp;lt;ffffffff8130de82&amp;gt;] ? io_schedule+0x73/0xb7
[442920.164545]  [&amp;lt;ffffffff8110fbd1&amp;gt;] ? sync_buffer+0x3b/0x40
[442920.164554]  [&amp;lt;ffffffff8130f142&amp;gt;] ? _spin_unlock_irqrestore+0xd/0xe
[442920.164561]  [&amp;lt;ffffffff8130e292&amp;gt;] ? __wait_on_bit_lock+0x3f/0x84
[442920.164569]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164576]  [&amp;lt;ffffffff8130e342&amp;gt;] ? out_of_line_wait_on_bit_lock+0x6b/0x77
[442920.164584]  [&amp;lt;ffffffff81066360&amp;gt;] ? wake_bit_function+0x0/0x23
[442920.164592]  [&amp;lt;ffffffff8110ffc3&amp;gt;] ? sync_dirty_buffer+0x29/0x93
[442920.164600]  [&amp;lt;ffffffffa001be04&amp;gt;] ? journal_dirty_data+0xd1/0x1b0 [jbd]
[442920.164611]  [&amp;lt;ffffffffa0032f4c&amp;gt;] ? ext3_journal_dirty_data+0xf/0x34 [ext3]
[442920.164622]  [&amp;lt;ffffffffa00313f5&amp;gt;] ? walk_page_buffers+0x65/0x8b [ext3]
[442920.164632]  [&amp;lt;ffffffffa0032f71&amp;gt;] ? journal_dirty_data_fn+0x0/0x13 [ext3]
[442920.164643]  [&amp;lt;ffffffffa0034a93&amp;gt;] ? ext3_ordered_write_end+0x73/0x10f [ext3]
[442920.164652]  [&amp;lt;ffffffff810b648a&amp;gt;] ? generic_file_buffered_write+0x18d/0x278
[442920.164661]  [&amp;lt;ffffffff810b6926&amp;gt;] ? __generic_file_aio_write+0x25f/0x293
[442920.164670]  [&amp;lt;ffffffff810b69b3&amp;gt;] ? generic_file_aio_write+0x59/0x9f
[442920.164677]  [&amp;lt;ffffffff810f0316&amp;gt;] ? do_sync_write+0xce/0x113
[442920.164685]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[442920.164693]  [&amp;lt;ffffffff810f0c68&amp;gt;] ? vfs_write+0xa9/0x102
[442920.164700]  [&amp;lt;ffffffff810f0d18&amp;gt;] ? sys_pwrite64+0x57/0x77
[442920.164706]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/613#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/618</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/618</guid>
        <title>#618: Migrate Penguin and Parrot to the ZFS fileserver</title>
        <pubDate>Fri, 15 Nov 2013 09:37:36 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; has been running from the ZFS fileserver, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/593" title="maintenance: Migrating Puffin to a ZFS file server (closed: fixed)"&gt;ticket:593&lt;/a&gt;, it has been performing better -- we should also migrate &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; to the ZFS server prior to upgrading them to Debian Wheezy on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/535" title="maintenance: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy (closed: fixed)"&gt;ticket:535&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/618#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/620</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/620</guid>
        <title>#620: Upgrade MediaWiki to 1.19.9</title>
        <pubDate>Fri, 15 Nov 2013 14:57:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
See the announcement email:
&lt;/p&gt;
&lt;pre class="wiki"&gt;I would like to announce the release of MediaWiki 1.21.3, 1.20.8 and
1.19.9. These releases fix 2 security related bugs that could affect users
of MediaWiki. Download links are given at the end of this email.
* Kevin Israel (Wikipedia user PleaseStand) identified and reported two
vectors for injecting Javascript in CSS that bypassed MediaWiki's blacklist
(CVE-2013-4567, CVE-2013-4568).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=55332&amp;gt;
* Internal review while debugging a site issue discovered that MediaWiki
and the CentralNotice extension were incorrectly setting cache headers when
a user was autocreated, causing the user's session cookies to be cached,
and returned to other users (CVE-2013-4572).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=53032&amp;gt;
Additionally, the following extensions have been updated to fix security
issues:
* CleanChanges: MediaWiki steward Teles reported that revision-deleted IP's
are not correctly hidden when this extension is used (CVE-2013-4569).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=54294&amp;gt;
* ZeroRatedMobileAccess: Tomasz Chlebowski reported an XSS vulnerability
(CVE-2013-4573).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=55991&amp;gt;
* CentralAuth: MediaWiki developer Platonides reported a login CSRF in
CentralAuth (CVE-2012-5394).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=40747&amp;gt;
Full release notes for 1.21.3:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.21&amp;gt;
Full release notes for 1.20.8:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.20&amp;gt;
Full release notes for 1.19.9:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.19&amp;gt;
For information about how to upgrade, see
&amp;lt;https://www.mediawiki.org/wiki/Manual:Upgrading&amp;gt;
&lt;/pre&gt;&lt;p&gt;
The steps followed for the last upgrade can be followed again, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/595" title="maintenance: Upgrade Mediawiki to 1.19.8 from 1.19.7 (closed: fixed)"&gt;ticket:595&lt;/a&gt; and see also the documentation at &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer#wiki.transitionnetwork.org"&gt;wiki:PenguinServer#wiki.transitionnetwork.org&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/620#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/632</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/632</guid>
        <title>#632: Add accounts for Sam</title>
        <pubDate>Mon, 25 Nov 2013 14:41:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Following &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/534" title="maintenance: Add accounts for Ben (closed: fixed)"&gt;ticket:534&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/632#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/633</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/633</guid>
        <title>#633: RHS blocks changes for homepage</title>
        <pubDate>Mon, 25 Nov 2013 15:27:15 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Re-arrange/add/edit the RHS blocks to appear the order below
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Why/how etc. : NO change
&lt;/li&gt;&lt;li&gt;newsletter promo: NO change
&lt;/li&gt;&lt;li&gt;POJDS book button: much smaller - can you set book image to lhs and buy button to rhs within block? might need a special .png to have both in it
&lt;/li&gt;&lt;li&gt;Transition nearby button: NO change
&lt;/li&gt;&lt;li&gt;New iT2 film promo button: needs a graphic
&lt;/li&gt;&lt;li&gt;New TFP button: NEW: Trucie providing a graphic to fit in
&lt;/li&gt;&lt;li&gt;Training button: NEW: Ed asking for training graphic to fit in
&lt;/li&gt;&lt;li&gt;Social media promo button: NEW: needs some very modest SM logos to link to SM outposts FB and twitter
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
NB: Rob is only thinking of the homepage; Ed is not sure of the implications elsewhere on site... please advise on how/if this affects things elsewhere...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/633#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/641</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/641</guid>
        <title>#641: Enable dynamic Munin graphs</title>
        <pubDate>Mon, 02 Dec 2013 15:25:45 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
If we only generate munin graphs on the fly we will also get the zoom function working, this example config looks good: &lt;a class="ext-link" href="http://uname.pingveno.net/blog/index.php/post/2013/08/25/Configure-Munin-graphs-with-Nginx-and-Debian-7"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://uname.pingveno.net/blog/index.php/post/2013/08/25/Configure-Munin-graphs-with-Nginx-and-Debian-7&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/641#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/642</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/642</guid>
        <title>#642: Trac "databasee  is locked" errors in /var/log/messages</title>
        <pubDate>Sat, 07 Dec 2013 13:46:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I have just noticed these errors in &lt;tt&gt;/var/log/messages&lt;/tt&gt; on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor TimingEstimationAndBillingPage: OperattionalError: database is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor AdminModule: OperationalError: databasse is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor SearchModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor QueryModule: OperationalError: databasse is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor ReportModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor RoadmapModule: OperationalError: databbase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor TicketModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor TimelineModule: OperationalError: dataabase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor BrowserModule: OperationalError: databbase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor WikiModule: OperationalError: databaseeis locked
&lt;/pre&gt;&lt;p&gt;
There are lots more of these, including some from this morning.
&lt;/p&gt;
&lt;p&gt;
Trac still seems to be working OK so I don't know how significant they are.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/642#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/656</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/656</guid>
        <title>#656: Spam being sent out via Transition Culture</title>
        <pubDate>Sat, 14 Dec 2013 14:48:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I'm getting several of thee day day:
&lt;/p&gt;
&lt;pre class="wiki"&gt;From: Mail Delivery System &amp;lt;Mailer-Daemon@parrot.webarch.net&amp;gt;
Date: Sat, 14 Dec 2013 13:21:02 +0000
To: tc@parrot.webarch.net
Subject: Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
  inxzkysnf@gmail.com
    SMTP error from remote mail server after RCPT TO:&amp;lt;inxzkysnf@gmail.com&amp;gt;:
    host gmail-smtp-in.l.google.com [173.194.78.26]:
    550-5.1.1 The email account that you tried to reach does not exist. Please try
    550-5.1.1 double-checking the recipient's email address for typos or
    550-5.1.1 unnecessary spaces. Learn more at
    550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 l11si2175565wjw.16 - gsmtp
------ This is a copy of the message, including all the headers. ------
Return-path: &amp;lt;tc@parrot.webarch.net&amp;gt;
Received: from tc (uid=1011)
        by parrot.webarch.net with local (Exim 4.80)
        (envelope-from &amp;lt;tc@parrot.webarch.net&amp;gt;)
        id 1Vrp9L-0002BF-Kf
        for inxzkysnf@gmail.com; Sat, 14 Dec 2013 13:20:56 +0000
To: inxzkysnf@gmail.com
Subject: Thanks for your message
X-PHP-Originating-Script: 1011:lib_nonajax.php
From: robjhopkins@gmail.com
Reply-To: robjhopkins@gmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----MIME_BOUNDRY_main_message"
Message-Id: &amp;lt;E1Vrp9L-0002BF-Kf@parrot.webarch.net&amp;gt;
Date: Sat, 14 Dec 2013 13:20:55 +0000
This is a multi-part message in MIME format.
------MIME_BOUNDRY_main_message
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Dear timberland france,
Thank you for your message on the Transition Culture website - I will get back to you as soon as possible.
------MIME_BOUNDRY_main_message
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
&amp;lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"&amp;gt;
&amp;lt;HTML&amp;gt;&amp;lt;BODY&amp;gt;
&amp;lt;div style=3D"font:normal 1em arial; margin-top:10px"&amp;gt;&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Dear timberland france,&amp;lt;/strong&amp;gt;&amp;lt;/p&amp;gt;
&amp;lt;p&amp;gt;Thank you for your message on the Transition Culture website - I will get back to you as soon as possible.
&amp;lt;div style=3D"width:80%; background:#f4faff ; color:#aaa; font-size:11px; padding:10px; margin-top:20px"&amp;gt;&amp;lt;strong&amp;gt;This is an automatic
+confirmation message. 14 December, 2013.&amp;lt;/strong&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/BODY&amp;gt;&amp;lt;/HTML&amp;gt;
&lt;/pre&gt;&lt;p&gt;
It appears to be spam sent fro the Transition Culture &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; site to a Gnmail user who doesn't exist.
&lt;/p&gt;
&lt;p&gt;
It appears, from the email headers that this form is being used for the spamming &lt;tt&gt;/home/tc/sites/default/wp-content/plugins/contactforms/lib_nonajax.php&lt;/tt&gt;.
&lt;/p&gt;
&lt;p&gt;
This needs some more investigation.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/656#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/660</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/660</guid>
        <title>#660: Piwik 2.0</title>
        <pubDate>Tue, 17 Dec 2013 09:36:18 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The new version of Piwik will be out soon, the &lt;a class="ext-link" href="http://piwik.org/blog/2013/12/piwik-2-0-release-candidate/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik 2.0 Release Candidate&lt;/a&gt; just came out.
&lt;/p&gt;
&lt;p&gt;
This ticket has beed created to document the upgrade.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/660#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/664</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/664</guid>
        <title>#664: Upgrade Piwik to 2.0.2</title>
        <pubDate>Tue, 24 Dec 2013 14:35:06 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a bugfix version which fixes 3 issues, see &lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-0-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-0-1/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Upgrade notes are here, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PiwikServer#Updates"&gt;wiki:PiwikServer#Updates&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/664#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/665</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/665</guid>
        <title>#665: Wagn "Problem Loading Page" error</title>
        <pubDate>Mon, 06 Jan 2014 14:02:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Bug report from Tom:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I've encountered a problem when trying to set up new accounts: I get a 'Problem Loading Page' error when it tries to load &lt;a class="ext-link" href="http://localhost:3000/wagn/Invite_Success"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://localhost:3000/wagn/Invite_Success&lt;/a&gt;. This seems to be explained at &lt;a class="ext-link" href="http://wagn.org/Special_Urls_and_Ports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wagn.org/Special_Urls_and_Ports&lt;/a&gt; - which I am hoping falls under your area of responsibility as I'm not sure how to do it myself,! But let me know if not...
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/665#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/666</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/666</guid>
        <title>#666: Parrot lockups</title>
        <pubDate>Wed, 08 Jan 2014 11:31:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
We have this on the console, I'm going to reboot it:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[28800.164426]  [&amp;lt;ffffffffa001c1ba&amp;gt;] ? do_get_write_access+0x22c/0x452 [jbd2]
[28800.164435]  [&amp;lt;ffffffff81066360&amp;gt;] ? wake_bit_function+0x0/0x23
[28800.164443]  [&amp;lt;ffffffff8104b51c&amp;gt;] ? try_to_wake_up+0x289/0x29b
[28800.164453]  [&amp;lt;ffffffffa001c402&amp;gt;] ? jbd2_journal_get_write_access+0x22/0x33 [jbd2]
[28800.164475]  [&amp;lt;ffffffffa006289e&amp;gt;] ? __ext4_journal_get_write_access+0x4e/0x56 [ext4]
[28800.164492]  [&amp;lt;ffffffffa0042b8e&amp;gt;] ? ext4_reserve_inode_write+0x37/0x73 [ext4]
[28800.164508]  [&amp;lt;ffffffffa0042c05&amp;gt;] ? ext4_mark_inode_dirty+0x3b/0x1c4 [ext4]
[28800.164528]  [&amp;lt;ffffffffa005bdc7&amp;gt;] ? ext4_journal_start_sb+0xd4/0x10e [ext4]
[28800.164543]  [&amp;lt;ffffffffa0042eb0&amp;gt;] ? ext4_dirty_inode+0x30/0x46 [ext4]
[28800.164553]  [&amp;lt;ffffffff81109ead&amp;gt;] ? __mark_inode_dirty+0x25/0x14a
[28800.164560]  [&amp;lt;ffffffff8110138b&amp;gt;] ? file_update_time+0x101/0x130
[28800.164569]  [&amp;lt;ffffffff810b6835&amp;gt;] ? __generic_file_aio_write+0x16e/0x293
[28800.164578]  [&amp;lt;ffffffff810b69b3&amp;gt;] ? generic_file_aio_write+0x59/0x9f
[28800.164588]  [&amp;lt;ffffffff810f0316&amp;gt;] ? do_sync_write+0xce/0x113
[28800.164596]  [&amp;lt;ffffffff810fcd0c&amp;gt;] ? filldir+0x0/0xb7
[28800.164605]  [&amp;lt;ffffffff810549b1&amp;gt;] ? _local_bh_enable_ip+0x22/0x8f
[28800.164613]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[28800.164626]  [&amp;lt;ffffffff8130f1a1&amp;gt;] ? _spin_lock_bh+0x9/0x25
[28800.164626]  [&amp;lt;ffffffff810f0c68&amp;gt;] ? vfs_write+0xa9/0x102
[28800.164632]  [&amp;lt;ffffffff810f0d18&amp;gt;] ? sys_pwrite64+0x57/0x77
[28800.164639]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[28800.164657] INFO: task apache2:31559 blocked for more than 120 seconds.
[28800.164665] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[28800.164675] apache2       D 0000000000000000     0 31559  28011 0x00000000
[28800.164691]  ffffffff8149f1f0 0000000000000286 0000000000000000 ffffffff81274f4f
[28800.164711]  ffff880002dc99d8 ffff8800bd1ca000 000000000000f9e0 ffff880002dc9fd8
[28800.164730]  00000000000157c0 00000000000157c0 ffff8800bd9746a0 ffff8800bd974998
[28800.164752] Call Trace:
[28800.164762]  [&amp;lt;ffffffff81274f4f&amp;gt;] ? sch_direct_xmit+0x7f/0x14c
[28800.164773]  [&amp;lt;ffffffff81066253&amp;gt;] ? bit_waitqueue+0x10/0xa0
[28800.164787]  [&amp;lt;ffffffffa001c1ba&amp;gt;] ? do_get_write_access+0x22c/0x452 [jbd2]
[28800.164798]  [&amp;lt;ffffffff81066360&amp;gt;] ? wake_bit_function+0x0/0x23
[28800.164812]  [&amp;lt;ffffffffa001c402&amp;gt;] ? jbd2_journal_get_write_access+0x22/0x33 [jbd2]
[28800.164833]  [&amp;lt;ffffffffa006289e&amp;gt;] ? __ext4_journal_get_write_access+0x4e/0x56 [ext4]
[28800.164852]  [&amp;lt;ffffffffa0042b8e&amp;gt;] ? ext4_reserve_inode_write+0x37/0x73 [ext4]
[28800.164871]  [&amp;lt;ffffffffa0042c05&amp;gt;] ? ext4_mark_inode_dirty+0x3b/0x1c4 [ext4]
[28800.164890]  [&amp;lt;ffffffffa005bdc7&amp;gt;] ? ext4_journal_start_sb+0xd4/0x10e [ext4]
[28800.164908]  [&amp;lt;ffffffffa0042eb0&amp;gt;] ? ext4_dirty_inode+0x30/0x46 [ext4]
[28800.164921]  [&amp;lt;ffffffff81109ead&amp;gt;] ? __mark_inode_dirty+0x25/0x14a
[28800.164932]  [&amp;lt;ffffffff8110138b&amp;gt;] ? file_update_time+0x101/0x130
[28800.164943]  [&amp;lt;ffffffff810b6835&amp;gt;] ? __generic_file_aio_write+0x16e/0x293
[28800.164958]  [&amp;lt;ffffffff8125227b&amp;gt;] ? sock_aio_write+0x0/0xbc
[28800.164969]  [&amp;lt;ffffffff8100cc43&amp;gt;] ? xen_make_pte+0x7b/0x83
[28800.164980]  [&amp;lt;ffffffff810b69b3&amp;gt;] ? generic_file_aio_write+0x59/0x9f
[28800.164992]  [&amp;lt;ffffffff810f0316&amp;gt;] ? do_sync_write+0xce/0x113
[28800.165003]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[28800.165015]  [&amp;lt;ffffffff810ce24c&amp;gt;] ? handle_mm_fault+0x3b8/0x80f
[28800.165027]  [&amp;lt;ffffffff810f0c68&amp;gt;] ? vfs_write+0xa9/0x102
[28800.165038]  [&amp;lt;ffffffff810f0d7d&amp;gt;] ? sys_write+0x45/0x6e
[28800.165049]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[125024.867759] hrtimer: interrupt took 38561246 ns
[1412520.196163] INFO: task mysqld:7928 blocked for more than 120 seconds.
[1412520.196183] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[1412520.196191] mysqld        D 0000000000000000     0  7928  18454 0x00000000
[1412520.196203]  ffff8800bfa69530 0000000000000286 0000000000000000 0000000000000000
[1412520.196215]  0007ffffffffffff 0000000000000001 000000000000f9e0 ffff880074cb5fd8
[1412520.196226]  00000000000157c0 00000000000157c0 ffff880002ce1530 ffff880002ce1828
[1412520.196236] Call Trace:
[1412520.196259]  [&amp;lt;ffffffffa00232bf&amp;gt;] ? jbd2_log_wait_commit+0xbf/0x112 [jbd2]
[1412520.196273]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[1412520.196293]  [&amp;lt;ffffffffa003fb41&amp;gt;] ? ext4_sync_file+0x199/0x25c [ext4]
[1412520.196304]  [&amp;lt;ffffffff8110d6e0&amp;gt;] ? vfs_fsync_range+0x73/0x9e
[1412520.196319]  [&amp;lt;ffffffff8110d78a&amp;gt;] ? do_fsync+0x28/0x39
[1412520.196325]  [&amp;lt;ffffffff8110d7b9&amp;gt;] ? sys_fsync+0xb/0x10
[1412520.196333]  [&amp;lt;ffffffff81011b63&amp;gt;] ? sysret_check+0x17/0x5a
[1412520.196341]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/666#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/668</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/668</guid>
        <title>#668: Wagn transition_mod</title>
        <pubDate>Sat, 11 Jan 2014 08:52:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from Ethan via Tom:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I was doing some work on wagn mods today and I realized that I'd created a mod (as in "modification" or "module", whichever you like) for the transition site that probably never survived the move to the new server.
&lt;/p&gt;
&lt;p&gt;
Looking at &lt;a class="ext-link" href="https://patterns.transitionresearchnetwork.org/Building_Resilience"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://patterns.transitionresearchnetwork.org/Building_Resilience&lt;/a&gt; confirmed this for me.  The confidence shows up as the words "2 stars" rather than actual star images.  That's one thing the mod does.  The other has to do with reducing visual redundancy (recurring names) in pattern summaries.
&lt;/p&gt;
&lt;p&gt;
I've attached the mod file here.  Unless you've gotten creative with your configuration, you should be able to stick this file in local/mods and restart the server and have that fixed. Let me know if any of this doesn't make sense.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/668#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/669</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/669</guid>
        <title>#669: Mediawiki upgrade to 1.19.10</title>
        <pubDate>Sat, 11 Jan 2014 09:00:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from Mediawiki:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Tuesday, January 14th between 00:00-01:00 UTC (*Monday* January 13th, 4-5pm PST) Wikimedia Foundation will release security updates for current and supported branches of the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; software, as well as several extensions. Downloads and patches will be available at that time.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/669#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/670</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/670</guid>
        <title>#670: Roll back performance customisations and use stock BOA settings where possible</title>
        <pubDate>Sat, 11 Jan 2014 20:51:30 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
&lt;strong&gt;Issue&lt;/strong&gt;
Given so much has changed since the initial issues on the server, I now strongly recommend reverting all settings changes that do not add features back to stock BOA settings after the next BOA release.
&lt;/p&gt;
&lt;p&gt;
These would include all MySQL, PHP, FPM, Redis and other settings that have been for performance reasons, or to combat the situation where there was hardware/IO issues with the underlying server. I'm most interested in FPM and MySQL settings.
&lt;/p&gt;
&lt;p&gt;
The next version of BOA will include some improvements we need (&lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/629"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;see 629: Upgrades to BOA&lt;/a&gt; which should handle load on our server with a lot of CPU cores. With this in place we'll be able to revert more easily to stock settings.
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;Rationale&lt;/em&gt;
I'm not talking about rolling back changes that provide us with features or mission-critical capabilities, just the changes to the subsystems I list above for performance reasons.
&lt;/p&gt;
&lt;p&gt;
It's my belief that these enhancements no longer match the needs of the server since the changes to filesystem and underlying hardware fixes have been completed. They also represent an ongoing risk around updates, future planning -- plus it's possible they might mean Puffin's web services need more memory than it otherwise would, costing TN more than it should need to spend on hardware.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Proposed solution&lt;/strong&gt;
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Await the next version of BOA, and setup the enhanced load settings per the documentation.
&lt;/li&gt;&lt;li&gt;Revert all other changes to conf files for MySQL, PHP, FPM, Redis that do not add a feature or are not mission-critical.
&lt;/li&gt;&lt;li&gt;Review &lt;tt&gt;/root/.barracuda.cnf&lt;/tt&gt; and turn off any overrides and customisations we don't now need as a result of 2).
&lt;/li&gt;&lt;li&gt;Run the BOA &lt;tt&gt;BOND.sh&lt;/tt&gt; script to do the tuning of the server appropriate to the memory requirements. This will tune for the current levels on first pass.
&lt;/li&gt;&lt;li&gt;Review Munin and site performance. If we need to make any tweaks then we can do a minimal set as required -- keeping an eye on memory usage.
&lt;/li&gt;&lt;li&gt;Once a few days have gone by I would hope that the overall memory use will be lower, OR with more cached data. At this point we can either re-run the barracuda installer with the &lt;tt&gt;_RESERVED_RAM&lt;/tt&gt; set to 1-4 Gb, or simply reduce the memory available to Puffin.
&lt;/li&gt;&lt;li&gt;Repeat from 4, using BOND.sh to optimise for the new memory footprint.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Clearly, it's possible no memory savings can be made, or just 1Gb or so is sensible. Either way, rolling back the changes made for a system that has changed immensely is worth attempting to compare current (tweaked) performance to the stock system. Since current settings are all documented and can be backed up, we should be able to test this with no risk and the ability to roll back as needed.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Next steps&lt;/strong&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Chris and Ed to give their thoughts.
&lt;/li&gt;&lt;li&gt;Ed to green-light before we proceed in too much detail or take any action.
&lt;/li&gt;&lt;li&gt;Chris and Jim to establish the changes and outcomes.
&lt;/li&gt;&lt;li&gt;Chris, Jim and whoever to do the new optimisation process.
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/670#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/672</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/672</guid>
        <title>#672: Upgrade to Piwik 2.0.3</title>
        <pubDate>Mon, 13 Jan 2014 10:13:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the &lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-0-3/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.0.3 is a bug-fix release. To ensure the highest quality and reliability for your Piwik 2.0 setup, we have fixed all known major bugs, as well as made some small improvements.
&lt;/p&gt;
&lt;p&gt;
...
&lt;/p&gt;
&lt;p&gt;
We highly recommend that you upgrade your server to Piwik 2.0.3 today to benefit from the latest improvements.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/672#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/673</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/673</guid>
        <title>#673: Install mosh - the mobile shell</title>
        <pubDate>Mon, 13 Jan 2014 11:27:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The mobile shell enables terminal connections to stay up when using really bad connections, for example on a train, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://mosh.mit.edu/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://mosh.mit.edu/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/673#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/674</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/674</guid>
        <title>#674: Puffin locked up</title>
        <pubDate>Tue, 14 Jan 2014 09:59:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is on the console, no response via web or ssh :
&lt;/p&gt;
&lt;pre class="wiki"&gt;[4478428.894563]  [&amp;lt;ffffffff810f3634&amp;gt;] ? sys_readlinkat+0x25/0x8d
[4478428.894571]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[4478428.894581] INFO: task cron:46009 blocked for more than 120 seconds.
[4478428.894587] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[4478428.894595] cron          D ffff8801fb270e20     0 46009   8829 0x00000080
[4478428.894606]  ffff8801fb270e20 0000000000000286 0000000000000001 00000001810423b0
[4478428.894617]  ffff88000bcf87c0 000000000000000b 000000000000f9e0 ffff8800cbb9dfd8
[4478428.894628]  00000000000157c0 00000000000157c0 ffff8801fa458000 ffff8801fa4582f8
[4478428.894640] Call Trace:
[4478428.894648]  [&amp;lt;ffffffff811976a6&amp;gt;] ? vsnprintf+0x40a/0x449
[4478428.894656]  [&amp;lt;ffffffff8130e5c3&amp;gt;] ? __mutex_lock_common+0x122/0x192
[4478428.894666]  [&amp;lt;ffffffff8130e6eb&amp;gt;] ? mutex_lock+0x1a/0x31
[4478428.894673]  [&amp;lt;ffffffff810f7eac&amp;gt;] ? do_lookup+0x80/0x15d
[4478428.894681]  [&amp;lt;ffffffff810f892c&amp;gt;] ? __link_path_walk+0x5a5/0x6f5
[4478428.894689]  [&amp;lt;ffffffff810f826a&amp;gt;] ? do_follow_link+0x1fa/0x317
[4478428.894697]  [&amp;lt;ffffffff810f86e0&amp;gt;] ? __link_path_walk+0x359/0x6f5
[4478428.894705]  [&amp;lt;ffffffff810f8caa&amp;gt;] ? path_walk+0x66/0xc9
[4478428.894713]  [&amp;lt;ffffffff810fa114&amp;gt;] ? do_path_lookup+0x20/0x77
[4478428.894721]  [&amp;lt;ffffffff810fa2a0&amp;gt;] ? do_filp_open+0xe5/0x94b
[4478428.894729]  [&amp;lt;ffffffff81012cdb&amp;gt;] ? xen_hypervisor_callback+0x1b/0x20
[4478428.894738]  [&amp;lt;ffffffff8130dda8&amp;gt;] ? thread_return+0x79/0xe0
[4478428.894746]  [&amp;lt;ffffffff811901fb&amp;gt;] ? _atomic_dec_and_lock+0x33/0x50
[4478428.894755]  [&amp;lt;ffffffff81103705&amp;gt;] ? alloc_fd+0x67/0x10c
[4478428.894763]  [&amp;lt;ffffffff810eeacf&amp;gt;] ? do_sys_open+0x55/0xfc
[4478428.894770]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[4478669.197427] INFO: task vnstatd:1920 blocked for more than 120 seconds.
[4478669.197448] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[4478669.197458] vnstatd       D 0000000000000000     0  1920      1 0x00000000
[4478669.197469]  ffff8801ff18bf90 0000000000000282 ffff8801fa651e10 ffff880000009680
[4478669.197482]  0000000000000000 000000000000000a 000000000000f9e0 ffff8801fa651fd8
[4478669.197494]  00000000000157c0 00000000000157c0 ffff8801fe335bd0 ffff8801fe335ec8
[4478669.197505] Call Trace:
[4478669.197520]  [&amp;lt;ffffffff8130f6fa&amp;gt;] ? error_exit+0x2a/0x60
[4478669.197531]  [&amp;lt;ffffffff8101251d&amp;gt;] ? retint_restore_args+0x5/0x6
[4478669.197542]  [&amp;lt;ffffffff8130e5c3&amp;gt;] ? __mutex_lock_common+0x122/0x192
[4478669.197551]  [&amp;lt;ffffffff8130e6eb&amp;gt;] ? mutex_lock+0x1a/0x31
[4478669.197561]  [&amp;lt;ffffffff810f7eac&amp;gt;] ? do_lookup+0x80/0x15d
[4478669.197569]  [&amp;lt;ffffffff810f86aa&amp;gt;] ? __link_path_walk+0x323/0x6f5
[4478669.197577]  [&amp;lt;ffffffff810f8caa&amp;gt;] ? path_walk+0x66/0xc9
[4478669.197585]  [&amp;lt;ffffffff810fa114&amp;gt;] ? do_path_lookup+0x20/0x77
[4478669.197593]  [&amp;lt;ffffffff810fa2a0&amp;gt;] ? do_filp_open+0xe5/0x94b
[4478669.197602]  [&amp;lt;ffffffff8130f054&amp;gt;] ? _spin_lock_irqsave+0x15/0x34
[4478669.197612]  [&amp;lt;ffffffff81068fa6&amp;gt;] ? hrtimer_try_to_cancel+0x3a/0x43
[4478669.197622]  [&amp;lt;ffffffff8102de30&amp;gt;] ? pvclock_clocksource_read+0x3a/0x8b
[4478669.197631]  [&amp;lt;ffffffff81103705&amp;gt;] ? alloc_fd+0x67/0x10c
[4478669.197641]  [&amp;lt;ffffffff810eeacf&amp;gt;] ? do_sys_open+0x55/0xfc
[4478669.197649]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
&lt;/pre&gt;&lt;p&gt;
Rebooting...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/674#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/677</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/677</guid>
        <title>#677: Spike in MyISAM (search) database activity, Redis unable to cache such requests</title>
        <pubDate>Wed, 15 Jan 2014 10:49:33 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since Sunday there has been a marked increase in MySQL activity and also a drop in Redis memory use, I suspect these things are related.
&lt;/p&gt;
&lt;p&gt;
I'll post some Munin graphs below to illustrate this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/677#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/682</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/682</guid>
        <title>#682: Create Trac &amp; Wiki account for Paul</title>
        <pubDate>Wed, 22 Jan 2014 12:39:18 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi it looks like i@… will be joining us to pick up some of Jim's role as he moves on.
&lt;/p&gt;
&lt;p&gt;
Chris could you create a trac &amp;amp; Wiki account for him please?
&lt;/p&gt;
&lt;p&gt;
His email is; i@…
&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/682#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/683</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/683</guid>
        <title>#683: Create Aegir account for Paul</title>
        <pubDate>Wed, 22 Jan 2014 12:42:48 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Jim
&lt;/p&gt;
&lt;p&gt;
It looks like i@… will be joining us to pick up some of your work.
&lt;/p&gt;
&lt;p&gt;
Could you create an Aegir account for him please?
&lt;/p&gt;
&lt;p&gt;
I was also wondering about the Transition Network Github repo, do we need to do anything to hand that over?
&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/683#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/684</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/684</guid>
        <title>#684: Adding Paul and Nick to Transition Network on github.org</title>
        <pubDate>Thu, 23 Jan 2014 10:42:23 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It looks like Ed and Jim are the only one with permissions to add members to &lt;a class="ext-link" href="https://github.com/orgs/transitionnetwork/members"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Transition Network on GitHub&lt;/a&gt; as they are listed as owners and the rest of us are members.
&lt;/p&gt;
&lt;p&gt;
Paul and Nick can you post you account names to this ticket so you can be added?
&lt;/p&gt;
&lt;p&gt;
Jim could you make me and/or Ben owners as well so we can add people?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/684#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/686</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/686</guid>
        <title>#686: MediaWiki 1.19.11 Update</title>
        <pubDate>Wed, 29 Jan 2014 09:53:13 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
On the &lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2014-January/000140.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MediaWiki-announce list&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I would like to announce the release of MediaWiki 1.22.2, 1.21.5 and 1.19.11.
&lt;/p&gt;
&lt;p&gt;
Your MediaWiki installation is affected by a remote code execution vulnerability if you have enabled file upload support for DjVu (natively supported by MediaWiki) or PDF files (in combination with the PdfHandlerxtension). Neither file type is enabled by default in MediaWiki installations. If you are affected, we strongly urge you to update immediately.
&lt;/p&gt;
&lt;p&gt;
Affected supported versions: All
&lt;/p&gt;
&lt;h2 id="Securityfixes"&gt;Security fixes&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Netanel Rubin from Check Point discovered a remote code execution
vulnerability in MediaWiki's thumbnail generation for DjVu files. Internal
review also discovered similar logic in the PdfHandler extension, which
could be exploited in a similar way. (CVE-2014-1610)
&lt;a class="ext-link" href="https://bugzilla.wikimedia.org/show_bug.cgi?id=60339"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://bugzilla.wikimedia.org/show_bug.cgi?id=60339&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="BugFixesin1.22.2"&gt;Bug Fixes in 1.22.2&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;(bug 58253) Check for very old PCRE versions in installer and updater
&lt;/li&gt;&lt;li&gt;(bug 60054) Make WikiPage::$mPreparedEdit public
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Full release notes for 1.19.9:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.mediawiki.org/wiki/Release_notes/1.19"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.mediawiki.org/wiki/Release_notes/1.19&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/686#changelog</comments>
    </item>
 </channel>
</rss>