Posted by & filed under MySQL.

Packages of MySQL 5.5.31 are now available for Debian 6.0 “Squeeze” on both amd64 and i386 architectures. They fix some serious vulnerabilities and InnoDB-, partition- and replication-related bugs as well.

Please note that the Pinba engine has also been rebuilt to be used against this new version.

As usual, please read carefully the full Changelog before upgrading.

21 Responses to “MySQL 5.5.31 for Squeeze”

  1. huglester

    Hello everyone,

    I’m trying to switch from 5.1 to: 5.5 mysql and get this error:
    Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
    invoke-rc.d: initscript mysql, action “start” failed.
    dpkg: error processing mysql-server-5.5 (–configure):
    subprocess installed post-installation script returned error exit status 1
    configured to not write apport reports
    dpkg: dependency problems prevent configuration of mysql-server:
    mysql-server depends on mysql-server-5.5; however:
    Package mysql-server-5.5 is not configured yet.
    dpkg: error processing mysql-server (–configure):
    dependency problems – leaving unconfigured
    configured to not write apport reports
    Errors were encountered while processing:
    mysql-server-5.5
    mysql-server
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    Not sure what I’m missing since logs/mysql.log and logs/mysql.err are empty …

    Reply
  2. huglester

    Guillaume thanks for help. Indeed it helped. Had my custom mysql config with some options already not supported, removed it temporary and now it is ok :)

    Reply
  3. huglester

    By the way, what would be the best to get the default config of mysql 5.5 in todteb repo? Download deb file and extract config? or is there a clearer way?

    Because I would like to replace my 5.1 config with default 5.5 and start modifying it ..

    Reply
  4. I. D.

    @huglester check default conf files at

    /usr/share/doc/mysql-server-5.5/examples/my-huge.cnf.gz
    /usr/share/doc/mysql-server-5.5/examples/my-innodb-heavy-4G.cnf.gz
    /usr/share/doc/mysql-server-5.5/examples/my-large.cnf.gz
    /usr/share/doc/mysql-server-5.5/examples/my-medium.cnf.gz
    /usr/share/doc/mysql-server-5.5/examples/my-small.cnf

    Reply
  5. razorness

    Just today set up a new server with Nginx, MySQL and PHP on Debian Squeeze by using dotdeb repositories.

    Is there a problem with having PHP MySQL client API v5.1.66 while dotdeb gave me MySQL v5.5.31?

    Installed packages:

    php-pear 5.4.15-1~dotdeb.1
    php5-apc 5.4.15-1~dotdeb.1
    php5-cli 5.4.15-1~dotdeb.1
    php5-common 5.4.15-1~dotdeb.1
    php5-curl 5.4.15-1~dotdeb.1
    php5-dev 5.4.15-1~dotdeb.1
    php5-fpm 5.4.15-1~dotdeb.1
    php5-gd 5.4.15-1~dotdeb.1
    php5-imagick 5.4.15-1~dotdeb.1
    php5-intl 5.4.15-1~dotdeb.1
    php5-mcrypt 5.4.15-1~dotdeb.1
    php5-mysql 5.4.15-1~dotdeb.1
    php5-sqlite 5.4.15-1~dotdeb.1

    mysql-client-5.5 5.5.31-1~dotdeb.0
    mysql-client-core-5.5 5.5.31-1~dotdeb.0
    mysql-common 5.5.31-1~dotdeb.0
    mysql-server-5.5 5.5.31-1~dotdeb.0
    mysql-server-core-5.5 5.5.31-1~dotdeb.0

    Kind regards,
    razorness

    Reply
    • Guillaume Plessis

      @razorness : no problem with that. PHP is built against 5.1.66 to avoid segfaults and duplicate symbols when loaded with other MySQL-linked pieces of software. If you want to get rid of warnings, install php5-mysqlnd instead of php5-mysql

      Reply
  6. razorness

    Thank you for your fast and good response.

    Done it with php5-msqlnd. :-)

    Reply
  7. Denis

    Hi Guillaume
    Thank you for all your hard work. Just tried to upgrade my squeeze distro and it gives me following:
    The following packages have unmet dependencies:
    mysql-client-core-5.5 : Breaks: mysql-client-5.5 (< 5.5.31-1~dotdeb.0) but 5.5.30-1~dotdeb.0 is installed

    Any ideas?
    Thanks

    Denis

    Reply
  8. HK

    Having trouble upgrading from mysql 5.1:

    The following packages have been kept back:
    mysql-server
    0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.


    The following packages have unmet dependencies:
    mysql-server : Depends: mysql-server-5.5 but it is not going to be installed
    E: Broken packages

    The following packages have unmet dependencies:
    mysql-server-5.5 : Depends: mysql-server-core-5.5 (= 5.5.31-1~dotdeb.0) but it is not going to be installed
    E: Broken packages

    The following packages have unmet dependencies:
    mysql-server-core-5.5 : Depends: libaio1 but it is not installable
    E: Broken packages

    Reply
      • immobilia

        There is any problem, your job is already a great help for Debian deployments. And thx for that!
        In the meantime I use an alternative solution deported on programing language, and I stay with 5.1 MySQL version in production, who seems to be faster than 5.5 and probably than the new 5.6 (at least for MyISAM).
        Have good job, and after work, unfortunately time is not scalable …

        Reply
  9. immobilia

    There is any problem, your job is already a great help for Debian deployments. And thx for that!
    In the meantime I use an alternative solution deported on programing language, and I stay with 5.1 MySQL version in production, who seems to be faster than 5.5 and probably than the new 5.6 (at least for MyISAM).
    Have good job, and after work, unfortunately time is not scalable …

    Reply
  10. Line117

    Debian 6, MySql 5.1 -> 5.5

    I had a same error:

    @huglester:
    “I’m trying to switch from 5.1 to: 5.5 mysql and get this error:
    Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!

    …”

    Found @Guillaume Plessis’s anwer:
    “MySQL errors go to /var/log/syslog. Take a look at it, you’ll know why your server won’t start”

    In my syslog:
    Oct 23 21:21:03 mysqld: 131023 21:21:03 InnoDB: The InnoDB memory heap is disabled
    Oct 23 21:21:03 mysqld: 131023 21:21:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    Oct 23 21:21:03 mysqld: 131023 21:21:03 InnoDB: Compressed tables use zlib 1.2.3.4
    Oct 23 21:21:03 mysqld: 131023 21:21:03 InnoDB: Using Linux native AIO
    Oct 23 21:21:03 mysqld: 131023 21:21:03 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
    Oct 23 21:21:03 mysqld: InnoDB: Warning: io_setup() attempt 1 failed.
    Oct 23 21:21:03 mysqld: InnoDB: Warning: io_setup() attempt 2 failed.
    Oct 23 21:21:04 mysqld: InnoDB: Warning: io_setup() attempt 3 failed.
    Oct 23 21:21:04 mysqld: InnoDB: Warning: io_setup() attempt 4 failed.
    Oct 23 21:21:05 mysqld: InnoDB: Warning: io_setup() attempt 5 failed.
    Oct 23 21:21:05 mysqld: 131023 21:21:05 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
    Oct 23 21:21:05 mysqld: InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
    Oct 23 21:21:05 mysqld: 131023 21:21:05 InnoDB: Fatal error: cannot initialize AIO sub-system
    Oct 23 21:21:05 mysqld: 131023 21:21:05 [ERROR] Plugin ‘InnoDB’ init function returned error.
    Oct 23 21:21:05 mysqld: 131023 21:21:05 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
    Oct 23 21:21:05 mysqld: 131023 21:21:05 [ERROR] Unknown/unsupported storage engine: InnoDB
    Oct 23 21:21:05 mysqld: 131023 21:21:05 [ERROR] Aborting
    Oct 23 21:21:05 mysqld:
    Oct 23 21:21:05 mysqld: 131023 21:21:05 [Note] /usr/sbin/mysqld: Shutdown complete
    Oct 23 21:21:05 mysqld:
    Oct 23 21:21:05 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
    Oct 23 21:21:17 /etc/init.d/mysql[18366]: 0 processes alive and ‘/usr/bin/mysqladmin –defaults-file=/etc/mysql/debian.cnf ping’ result$
    Oct 23 21:21:17 /etc/init.d/mysql[18366]: ^G/usr/bin/mysqladmin: connect to server at ‘localhost’ failed
    Oct 23 21:21:17 /etc/init.d/mysql[18366]: error: ‘Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)’
    Oct 23 21:21:17 /etc/init.d/mysql[18366]: Check that mysqld is running and that the socket: ‘/var/run/mysqld/mysqld.sock’ exists!

    Added “setting innodb_use_native_aio = 0″ in my.cnf
    Restart mysql service. Success!
    Guillaume thanks for help. : )

    Reply

Leave a Reply

  • (will not be published)


9 + = twelve