CRIN Trac: Ticket Query

This release is rated critical.

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

CRIN Trac: Ticket Query

#33: Piwik 2.14.3

#84: Piwik 2.16.4

#87: Piwik 2.16.5

#91: Piwik 2.17.0

#7: Enable Google Drive plugin for ownCloud

#13: Access to db1.crin.org

#15: Create Trac accounts for Jenny and Gillian

#16: Add Trac account for Adam

#18: Drush

#21: Apache Solr HTTP 400 Bad Request Errors

#22: Add Trac Account for Peter

#23: Development and staging environment

#24: Exim Mailqueue

#26: Create ssh and Trac account(s) for Code Positive

#27: Crin2 certificate access

#28: Crin1 server email problem

#30: Piwik 2.14.2

What’s new in Piwik 2.14.2?

#31: Preparation for deployment to new prod

#32: PHP error logs not found

#34: Memcache Munin Stats

#35: Problem with the S3QL backups for Crin1

#36: Piwik stats stopped on 31st August 2015

#40: Check Bitbucket documentation

#43: ownCloud 8.1.3-13.1

#44: PHP temp session files need deleting

#46: Piwik 2.15.0

What’s new?

Security release

Database upgrade

Platform Changes

#47: ownCloud 8.1.4.2

#48: crin4 /tmp filling up

#50: Migrate to INNODB

#51: Number of php5-fpm processes on Crin2

#52: 404 for top article - caused by 'und' in URL not 'en'

#55: Migrating Crin2 server to new hardware

#58: You have 1 new fax, document 00000576492

#59: Trac Spam

#61: Piwik 2.16.0

What’s new?

#63: {Spam?} Best watches in the world>>

#67: S3QL 2.17 has been released

2016-03-08, S3QL 2.17

#68: {Spam?} Best watches.

#69: procmail, email2trac and TLS cert

#70: s3ql backup error

#71: Piwik 2.16.1

#74: Visit to CRIN office

#75: Load spike and small downtime

#78: HTTP_PROXY possible security risk

#80: Piwik 2.16.2

#95: Piwik 3.0.0

#96: Piwik 3.0.1

#98: Trac account for Russell

#101: Piwik 3.0.2

#105: High load and slow responses from Crin2

#107: New cert for Fetechmail

#109: Piwik 3.0.3

#110: Piwik Accounts for Peter and Lisa

#112: phpMyAdmin HTTP Authentication

#124: Piwik 3.1.0

#126: Piwik 3.2.0

#128: Piwik 3.2.1

#130: Matomo 3.3.0

#133: Matomo 3.5.0

#25: Piwik 2.14.0

#37: Site slowdown on 8th Sept 2015

#39: S3QL backup problems

#62: Crin3 ethernet interface fails to come up after a reboot

#83: Piwik 2.16.3

Security release

Database upgrade

#38: [URGENT] crin.org down

#29: Piwik 2.14.1

What’s new in Piwik 2.14.1?

#123: Update Email Settings