<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CRIN Trac: Ticket Query</title>
    <link>https://trac.crin.org.archived.website/trac/query?status=closed&amp;component=drupal&amp;milestone=Maintenance&amp;group=resolution&amp;order=version</link>
    <description>Trac project for CRIN website and servers.</description>
    <language>en-US</language>
    <image>
      <title>CRIN Trac</title>
      <url>https://trac.crin.org.archived.website/trac/chrome/site/logo.gif</url>
      <link>https://trac.crin.org.archived.website/trac/query?status=closed&amp;component=drupal&amp;milestone=Maintenance&amp;group=resolution&amp;order=version</link>
    </image>
    <generator>Trac 1.0.2</generator>
    <item>
        <link>https://trac.crin.org.archived.website/trac/ticket/18</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/18</guid>
        <title>#18: Drush</title>
        <pubDate>Fri, 12 Jun 2015 16:34:39 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Drush doesn't work on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;su - www-data -s /bin/bash
drush pm-updatestatus
Command pm-updatestatus needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal        [error]
environment to run this command.
The drush command 'pm-updatestatus' could not be executed.                                                                         [error]
Drush was not able to start (bootstrap) the Drupal database.                                                                       [error]
Hint: This may occur when Drush is trying to:
 * bootstrap a site that has not been installed or does not have a configured database. In this case you can select another site
with a working database setup by specifying the URI to use with the --uri parameter on the command line. See `drush topic
docs-aliases` for details.
 * connect the database through a socket. The socket file may be wrong or the php-cli may have no access to it in a jailed shell.
See http://drupal.org/node/1428638 for details.
Drush was attempting to connect to:
 Drupal version         :  7.24
 Site URI               :  http://crin1.crin.org/
 Database driver        :  mysql
 Database hostname      :  crin1
 Database port          :
 Database username      :  drupal
 Database name          :  drupal
 PHP executable         :  /usr/bin/php
 PHP configuration      :  /etc/php5/cli/php.ini
 PHP OS                 :  Linux
 Drush script           :  /usr/local/src/drush-master/drush.php
 Drush version          :  7.0-dev
 Drush temp directory   :  /tmp
 Drush configuration    :  /var/www/.drush/drushrc.php
 Drush alias files      :
 Drupal root            :  /var/www/drupal
 Site path              :  sites/default
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/18#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/21</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/21</guid>
        <title>#21: Apache Solr HTTP 400 Bad Request Errors</title>
        <pubDate>Wed, 17 Jun 2015 15:01:15 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There are lots of errors like this in the &lt;a class="ext-link" href="https://www.crin.org/en/admin/reports/dblog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;dblog&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Type		Apache Solr
Date		Wednesday, June 17, 2015 - 15:53
User		Anonymous
Location	http://www.crin.org/fr/biblioth%C3%A8que/archives-des-actualit%C3%A9s?page=8
Message	HTTP 400; Bad Request: Bad Request
Severity	error
&lt;/pre&gt;&lt;p&gt;
And
&lt;/p&gt;
&lt;pre class="wiki"&gt;Type		Apache Solr
Date		Wednesday, June 17, 2015 - 15:53
User		Anonymous
Location	http://www.crin.org/fr/biblioth%C3%A8que/archives-des-actualit%C3%A9s?page=8
Message		HTTP Status: 400;
Message: 	Bad Request: Bad Request;
Response: 	&amp;lt;html&amp;gt;&amp;lt;head&amp;gt;&amp;lt;title&amp;gt;Apache Tomcat/7.0.56 (Debian) - Error report&amp;lt;/title&amp;gt;&amp;lt;style&amp;gt;&amp;lt;!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--&amp;gt;&amp;lt;/style&amp;gt; &amp;lt;/head&amp;gt;&amp;lt;body&amp;gt;&amp;lt;h1&amp;gt;HTTP Status 400 - undefined field hash&amp;lt;/h1&amp;gt;&amp;lt;HR size="1" noshade="noshade"&amp;gt;&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;type&amp;lt;/b&amp;gt; Status report&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;message&amp;lt;/b&amp;gt; &amp;lt;u&amp;gt;undefined field hash&amp;lt;/u&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;description&amp;lt;/b&amp;gt; &amp;lt;u&amp;gt;The request sent by the client was syntactically incorrect.&amp;lt;/u&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;HR size="1" noshade="noshade"&amp;gt;&amp;lt;h3&amp;gt;Apache Tomcat/7.0.56 (Debian)&amp;lt;/h3&amp;gt;&amp;lt;/body&amp;gt;&amp;lt;/html&amp;gt;;
Request: GET /solr/select?start=0&amp;amp;rows=5&amp;amp;fq=hash%3A7as1z6&amp;amp;fq=hash%3A7as1z6&amp;amp;q=id%3A7as1z6%2Fnode%2F266&amp;amp;qt=mlt&amp;amp;fl=entity_id%2Centity_type%2Clabel%2Cpath%2Curl%2Chash%2Csite&amp;amp;mlt.fl=path_alias%2Ctaxonomy_names&amp;amp;mlt.mintf=1&amp;amp;mlt.mindf=1&amp;amp;mlt.minwl=3&amp;amp;mlt.maxwl=15&amp;amp;mlt.maxqt=20&amp;amp;wt=json&amp;amp;json.nl=map HTTP/1.0 User-Agent: Drupal (+http://drupal.org/) Host: localhost:8080 ;
Caller: call_user_func_array() (line Inconnu of Inconnu)
Severity	error
&lt;/pre&gt;&lt;p&gt;
Requests for pages such as &lt;a class="ext-link" href="http://www.crin.org/fr/biblioth%C3%A8que/archives-des-actualit%C3%A9s?page=8"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;the one in the example above&lt;/a&gt; generate both the above errors.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/21#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/24</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/24</guid>
        <title>#24: Exim Mailqueue</title>
        <pubDate>Fri, 19 Jun 2015 10:04:32 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Yesterday a CRINmail newsletter was sent out (see also &lt;a class="new ticket" href="https://trac.crin.org.archived.website/trac/ticket/14#comment:5" title="defect: Blank CRINmail newsletters being sent out (new)"&gt;ticket:14#comment:5&lt;/a&gt;) and there are currently 245 emails stuck in the mail queue on &lt;a class="wiki" href="https://trac.crin.org.archived.website/trac/wiki/Crin2"&gt;Crin2&lt;/a&gt;, these are probably undeliverable addresses and there should be a way to mark them so and perhaps disable sending emails to these addresses in the future.
&lt;/p&gt;
&lt;p&gt;
In addition as the queue is greater that 100 it is resulting in &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;Munin&lt;/a&gt; sending a alert email every 5 mins, this threshold needs increasing to prevent these emails.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/24/exim_mailqueue-day-2018-06-19.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/24/exim_mailqueue-day-2018-06-19.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/24#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/36</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/36</guid>
        <title>#36: Piwik stats stopped on 31st August 2015</title>
        <pubDate>Tue, 08 Sep 2015 11:14:19 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The Piwik stats stopped on 31st August 2015.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="https://trac.crin.org.archived.website/trac/attachment/ticket/36/crin-piwik-2015-09-08.png"&gt;&lt;img src="https://trac.crin.org.archived.website/trac/raw-attachment/ticket/36/crin-piwik-2015-09-08.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The tracking code is missing, can the &lt;a class="ext-link" href="https://www.drupal.org/project/piwik"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Drupal Piwik module&lt;/a&gt; be re-installed / re-enabled please?
&lt;/p&gt;
&lt;p&gt;
In addition I believe the GA tracking code can be removed as the Piwik stats replace these.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/36#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/37</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/37</guid>
        <title>#37: Site slowdown on 8th Sept 2015</title>
        <pubDate>Tue, 08 Sep 2015 13:15:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The site is really slow and the number of &lt;tt&gt;php5-fpm&lt;/tt&gt; processes has gone up dramatically and so has the memory usage.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/37#changelog</comments>
    </item><item>
        <link>https://trac.crin.org.archived.website/trac/ticket/52</link>
        <guid isPermaLink="false">https://trac.crin.org.archived.website/trac/ticket/52</guid>
        <title>#52: 404 for top article - caused by 'und' in URL not 'en'</title>
        <pubDate>Sat, 12 Dec 2015 16:06:20 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The first articles linked to on the front page of &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; is a 404 not found:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
CIVIL SOCIETY UNDER THREAT: Old and new challenges for human and children's rights advocates in Eurasia
11 Dec 2015
In recent years, the space afforded to civil society to operate freely has been shrinking dramatically across the world,...
&lt;a class="ext-link" href="https://www.crin.org/und/library/publications/civil-society-under-threat-old-and-new-challenges-human-and-childrens-rights"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/und/library/publications/civil-society-under-threat-old-and-new-challenges-human-and-childrens-rights&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
The article is actually here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://www.crin.org/en/library/publications/civil-society-under-threat-old-and-new-challenges-human-and-childrens-rights"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.crin.org/en/library/publications/civil-society-under-threat-old-and-new-challenges-human-and-childrens-rights&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The problem is the &lt;tt&gt;und&lt;/tt&gt; rather then &lt;tt&gt;en&lt;/tt&gt; in the URL?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>https://trac.crin.org.archived.website/trac/ticket/52#changelog</comments>
    </item>
 </channel>
</rss>