<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CRIN Trac: Ticket Query</title>
    <link>https://trac.crin.org.archived.website/trac/query?component=crin2&amp;milestone=Maintenance&amp;group=status&amp;order=priority</link>
    <description>Trac project for CRIN website and servers.</description>
    <language>en-US</language>
    <image>
      <title>CRIN Trac</title>
      <url>https://trac.crin.org.archived.website/trac/chrome/site/logo.gif</url>
      <link>https://trac.crin.org.archived.website/trac/query?component=crin2&amp;milestone=Maintenance&amp;group=status&amp;order=priority</link>
    </image>
    <generator>Trac 1.0.2</generator>
    <item>
        <link>https://trac.crin.org.archived.website/trac/ticket/38</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/38</guid>
        <title>#38: [URGENT] crin.org down</title>
        <pubDate>Tue, 08 Sep 2015 15:54:35 GMT</pubDate>
        
        <dc:creator>mori</dc:creator>

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

        <description>&lt;p&gt;
When attempting to use Drush, when not root, we are not able to access the certificate.
&lt;/p&gt;
&lt;p&gt;
SSL error: Unable to get certificate from '/etc/ssl/cacert/crin1_cert.pem'
&lt;/p&gt;
&lt;p&gt;
How should we manage access to certificates?
Should we create a developers group?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/27#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/31</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/31</guid>
        <title>#31: Preparation for deployment to new prod</title>
        <pubDate>Mon, 10 Aug 2015 15:32:41 GMT</pubDate>
        
        <dc:creator>mori</dc:creator>

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

        <description>&lt;p&gt;
I'm having issues on newprod, but I can't find PHP error logs. If they are logged, can you please let me know where they are? If they are not logged, can you start logging them on both CRIN2 and CRIN4? Thanks.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/32#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/40</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/40</guid>
        <title>#40: Check Bitbucket documentation</title>
        <pubDate>Wed, 09 Sep 2015 13:21:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Chris needs to read and check the documentation here: &lt;a class="ext-link" href="https://bitbucket.org/crin/crin/wiki/Home"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://bitbucket.org/crin/crin/wiki/Home&lt;/a&gt; and update the Trac documentation as need be.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/40#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/50</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/50</guid>
        <title>#50: Migrate to INNODB</title>
        <pubDate>Wed, 25 Nov 2015 09:50:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

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

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

        <description>&lt;p&gt;
Since about 8:10am this morning there has been a noticeable increase in bandwidth usage and load on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt; and at 18:33, for 20 seconds, the Webarchitects monitoring server was unable to connect.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/75#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/105</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/105</guid>
        <title>#105: High load and slow responses from Crin2</title>
        <pubDate>Mon, 27 Mar 2017 12:15:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

        <description>&lt;p&gt;
Russell, what's up? I'm really sorry I have to go out in 5 mins so I'm not around to help, what has gone wrong?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/100#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/73</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/73</guid>
        <title>#73: CRIN2 ran out of memory</title>
        <pubDate>Sun, 01 May 2016 19:16:38 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The site has been down since Sun, 01 May 2016 18:05:44, it is now 8:15. I'm rebooting the server, it ran out of memory.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/73#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/94</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/94</guid>
        <title>#94: Ongoing high load caused by a bot</title>
        <pubDate>Thu, 15 Dec 2016 19:23:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to working out what to do with this issue...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/94#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/54</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/54</guid>
        <title>#54: 502 Errors</title>
        <pubDate>Tue, 22 Dec 2015 11:06:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Last night the &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/NginxLogWatch"&gt;wiki:NginxLogWatch&lt;/a&gt; script found a lot of 502 errors:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Dec 22     288 502, 0 503 and 0 504 errors from crin2.crin.org
Dec 22    4283 502, 0 503 and 0 504 errors from crin2.crin.org
&lt;/pre&gt;&lt;p&gt;
I'm not sure why yet.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/54#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/56</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/56</guid>
        <title>#56: Drupal Caching</title>
        <pubDate>Sun, 03 Jan 2016 11:46:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to discuss and then implement some additional caching for the &lt;a class="ext-link" href="https://www.crin.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/&lt;/a&gt; Drupal site.
&lt;/p&gt;
&lt;p&gt;
Possible options:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Generating static content from Drupal and serving these to non-logged in users, for example using &lt;a class="ext-link" href="https://www.drupal.org/project/boost"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Boost&lt;/a&gt; or something like it.
&lt;/li&gt;&lt;li&gt;Caching PHP generated pages using Nginx.
&lt;/li&gt;&lt;li&gt;Using a caching server such as Varnish.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
My preference would for 1. and 2., I can start doing some research on how best to do 2. I'd rather not do 3. if possible due to the complication it would add: &lt;tt&gt;php5-fpm -&amp;gt; varnish -&amp;gt; nginx&lt;/tt&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/56#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/97</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/97</guid>
        <title>#97: Debian Stretch</title>
        <pubDate>Mon, 30 Jan 2017 10:59:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Debian Stretch will probably be released in May 2017 or so, we need a plan to migrate to it, specifically:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;PHP 7.0
&lt;/li&gt;&lt;li&gt;MariaDB 10
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This has been raised with Russell on Bitbucket.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/97#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/99</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/99</guid>
        <title>#99: Let's Encrypt Cert for CRIN.org</title>
        <pubDate>Mon, 30 Jan 2017 14:32:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The Gandi cert expires in a couple of weeks, in 17th Feb 2017, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=www.crin.org&amp;amp;latest"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.ssllabs.com/ssltest/analyze.html?d=www.crin.org&amp;amp;latest&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
It would make sense to switch to use &lt;a class="ext-link" href="https://letsencrypt.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://letsencrypt.org/&lt;/a&gt; and the client implementation I suggest we use is this one &lt;a class="ext-link" href="https://github.com/Neilpang/acme.sh"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/Neilpang/acme.sh&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/99#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/115</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/115</guid>
        <title>#115: 500 Errors for crin.org</title>
        <pubDate>Tue, 16 May 2017 17:00:33 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There have been a lot of 500 errors today and they appear to be related to lines like this in &lt;tt&gt;/var/log/php/error.log&lt;/tt&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[16-May-2017 17:33:08 Europe/London] PHP Fatal error:  Call to undefined function entity_translation_language_load() in /var/www/prod/docroot/includes/menu.inc on line 593
&lt;/pre&gt;&lt;p&gt;
The section on the file in question:
&lt;/p&gt;
&lt;pre class="wiki"&gt; 538
 539 /**
 540  * Loads objects into the map as defined in the $item['load_functions'].
 541  *
 542  * @param $item
 543  *   A menu router or menu link item
 544  * @param $map
 545  *   An array of path arguments; for example, array('node', '5').
 546  *
 547  * @return
 548  *   Returns TRUE for success, FALSE if an object cannot be loaded.
 549  *   Names of object loading functions are placed in $item['load_functions'].
 550  *   Loaded objects are placed in $map[]; keys are the same as keys in the
 551  *   $item['load_functions'] array.
 553  */
 554 function _menu_load_objects(&amp;amp;$item, &amp;amp;$map) {
 555   if ($load_functions = $item['load_functions']) {
 556     // If someone calls this function twice, then unserialize will fail.
 557     if (!is_array($load_functions)) {
 558       $load_functions = unserialize($load_functions);
 559     }
 560     $path_map = $map;
 561     foreach ($load_functions as $index =&amp;gt; $function) {
 562       if ($function) {
 563         $value = isset($path_map[$index]) ? $path_map[$index] : '';
 564         if (is_array($function)) {
 565           // Set up arguments for the load function. These were pulled from
 566           // 'load arguments' in the hook_menu() entry, but they need
 567           // some processing. In this case the $function is the key to the
 568           // load_function array, and the value is the list of arguments.
 569           list($function, $args) = each($function);
 570           $load_functions[$index] = $function;
 571
 572           // Some arguments are placeholders for dynamic items to process.
 573           foreach ($args as $i =&amp;gt; $arg) {
 574             if ($arg === '%index') {
 575               // Pass on argument index to the load function, so multiple
 576               // occurrences of the same placeholder can be identified.
 577               $args[$i] = $index;
 578             }
 579             if ($arg === '%map') {
 580               // Pass on menu map by reference. The accepting function must
 581               // also declare this as a reference if it wants to modify
 582               // the map.
 583               $args[$i] = &amp;amp;$map;
 584             }
 585             if (is_int($arg)) {
 586               $args[$i] = isset($path_map[$arg]) ? $path_map[$arg] : '';
 587             }
 588           }
 589           array_unshift($args, $value);
 590           $return = call_user_func_array($function, $args);
 591         }
 592         else {
 593           $return = $function($value);
 594         }
 595         // If callback returned an error or there is no callback, trigger 404.
 596         if ($return === FALSE) {
 597           $item['access'] = FALSE;
 598           $map = FALSE;
 599           return FALSE;
 600         }
 601         $map[$index] = $return;
 602       }
 603     }
 604     $item['load_functions'] = $load_functions;
 605   }
 606   return TRUE;
 607 }
 608
&lt;/pre&gt;&lt;p&gt;
Peter, is the the cause of the 500 errors or is it a symptom, or is it unrelated? Do you have an idea what is going on here?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/115#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/117</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/117</guid>
        <title>#117: Install Newrelic on Crin2</title>
        <pubDate>Wed, 17 May 2017 11:51:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Peter has requested that Newrelic be installed on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Note that last time it was installed we had to remove it due to the resources it was using, see this thread &lt;a class="new ticket" href="https://trac.crin.org.archived.website/trac/ticket/73#comment:24" title="defect: CRIN2 ran out of memory (new)"&gt;ticket:73#comment:24&lt;/a&gt;, so I'd advise against leaving it on the server all the time.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/117#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/129</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/129</guid>
        <title>#129: Problem with image uploads</title>
        <pubDate>Mon, 11 Dec 2017 18:09:39 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;p&gt;
unable to upload new documents and images to the website.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/129#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/108</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/108</guid>
        <title>#108: Go live</title>
        <pubDate>Tue, 04 Apr 2017 16:01:05 GMT</pubDate>
        
        <dc:creator>russell</dc:creator>

        <description>&lt;p&gt;
Hi Chris,
&lt;/p&gt;
&lt;p&gt;
I've got a round of work ready to go onto Crin live. All tested and signed off on stage. The code element is very light. I don't expect any problems, but just letting you know. I'm planning to get into this as the working day is finishing today.
&lt;/p&gt;
&lt;p&gt;
Best,
Russell
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/108#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/120</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/120</guid>
        <title>#120: crin2 mail queue</title>
        <pubDate>Thu, 15 Jun 2017 18:36:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There is a mail queue on Crin2, we haven't had one of these for ages, Munin reports:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
crin.org :: crin2.crin.org :: Exim Mailqueue
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
WARNINGs: frozen mails is 171.00 (outside range 100).
OKs: queued mails is 230.00.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Graph here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://munin.crin.org/munin/crin.org/crin2.crin.org/exim_mailqueue.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://munin.crin.org/munin/crin.org/crin2.crin.org/exim_mailqueue.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Anyone know if this is something to be concerned about?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/120#changelog</comments>
    </item>
 </channel>
</rss>