[Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
In both error logs, I see this sequence (with varying timestamps and seq numbers, of course): 2015-03-29 15:03:37 2265 [Note] InnoDB: The log sequence numbers 10740390801 and 10740390801 in ibdata files do not match the log sequence number 11404279789 in the ib_logfiles! 2015-03-29 15:03:37 2265 [Note] InnoDB: Database was not shutdown normally! 2015-03-29 15:03:37 2265 [Note] InnoDB: Starting crash recovery. I think that's the core of the problem. 5.5 was not shut down properly before upgrading, so it's left to 5.6 to try to recover. For some reason it can't, and it crashes. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1437846/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1422391] Re: my-default.cnf missing
The file is indeed missing. It should've been in the mysql-server- core-5.6 package, but it's not. In ruby-mysql2: Add --keep-my-cnf to the mysql_install_db command line. Since the server is started with --no-defaults, it's not going to read the my.cnf file, and mysql_install_db doesn't need to create it. In mysql-server-core-5.6: Add usr/share/mysql/my-default.cnf to the package. mysql_install_db expects to find it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1422391 Title: my-default.cnf missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1422391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396210] [NEW] Backporting the mysql_no_login plugin to 5.6
Public bug reported: As agreed with Robie Basak (racb), I'm filing this request for backporting a feature from 5.7 to the 5.6 stable branch so that it can be considered by the SRU Team and returned as input to upstream. Upstream is waiting for response from distros before deciding whether to backport or not. Background == There's a new plugin in MySQL 5.7 that makes it possible to have accounts that can't log in: CREATE USER foo@localhost IDENTIFIED WITH 'mysql_no_login'; The mysql_no_login plugin simply denies all login attempts. This is useful for users that are created, e.g., to serve as proxy users, or as owners of stored programs/functions, views or events. This new plugin doesn't fix known security defects in the server, but does provide new and better means to harden security. Best practices for security include application of least-required privileges, and in some cases, that means no client connections for privileged accounts. This new plugin provides means to implement such restrictions in a standard way. Because of the security benefits, upstream would proposes backporting it to 5.6. This does not fall under the existing micro-release exception for mysql-5.6, and so must be considered separately. In consideration of the micro-release exception requirements, upstream are interested in a decision for acceptance in an Ubuntu SRU before making the change upstream, so that any change made, or not made, is consistent across upstream, Ubuntu and any other distribution that wish to follow suit. We would like a +1 or a -1 from the SRU team (or Technical Board if appropriate) on 1) backporting the plugin into the 5.6 source code, and 2) for each of the options presented below. Impact == If backported, the plugin would at least be available in the source tarball. That doesn't mean it has to be distributed in Ubuntu: - A patch can be applied to remove the plugin from the source code before building (it's only a few lines of code). - Compilation of the plugin can be disabled. - It can be built but the resulting plugin binary can be left out of packages. - It can be built and packaged. The DBA still has to explicitly enable it and alter the user accounts to use it. Proposed development fix Either 1) Build and package the plugin, or 2) allow the plugin in source code, but don't package it (either by disabling it before compilation or skipping the binary in packaging). Fedora/Red Hat has +1'ed a backport: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2014-October/007195.html Proposed stable fix === Same as development fix. Regression potential Upstream considers the regression potential to be very low. - Since this is a plugin, it doesn't touch server code. - All new code is in a plugin that must be enabled explicitly by the DBA. - The code itself is very simple. It's only one line of real code (unconditionally return authentication failure), plus necessary plugin plumbing to fill out the plugin API. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1396210 Title: Backporting the mysql_no_login plugin to 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1396210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076656] Re: mysql --ssl-capath option doesn't work
Despite have_openssl YES, the community edition of MySQL uses yaSSL, not OpenSSL (have_openssl is just an alias for have_ssl). You've probably stumbled upon this difference between OpenSSL and yaSSL (cut and pasted from http://dev.mysql.com/doc/refman/5.5/en/ssl-options.html #option_general_ssl-capath): MySQL distributions built with OpenSSL support the --ssl-capath option. Distributions built with yaSSL do not because yaSSL does not look in any directory and does not follow a chained certificate tree. yaSSL requires that all components of the CA certificate tree be contained within a single CA certificate tree and that each certificate in the file has a unique SubjectName value. To work around this yaSSL limitation, concatenate the individual certificate files comprising the certificate tree into a new file. Then specify the new file as the value of the --ssl-capath option. The reason this changed is probably that the build options used when packaging for Ubuntu changed. Earlier versions of MySQL in Ubuntu may have been linked against OpenSSL since it was built with the WITH_SSL=yes option. This made the build system pick up OpenSSL if it was installed on the system and use the bundled yaSSL library otherwise, so which library the package used depended on whether the system where the package was built happened to have OpenSSL installed or not. This is obviously not good, so in more recent builds this option has been set to WITH_SSL=bundled, wich means that the bundled yaSSL library will always be used. Regards, Norvald H. Ryeng -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/1076656 Title: mysql --ssl-capath option doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/1076656/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-mysql] MySQL Roundtable
Blueprint changed by Norvald H. Ryeng: Whiteboard changed: Things to discuss: * What to do about lack of unit tests in recent patch releases of MySQL * MariaDB and Percona Server in the distro * Upstream MariaDB and Pecona Server package compatibility w/ distro * Synchronizing packaging between Ubuntu and Debian * Collaboration on MySQL Juju charm * Adding Galera Support to Packaging * General HA solutions (Critical for OpenStack deployments) + * MySQL 5.6 + * MySQL release schedule User Stories: Risks: Test Plans: Release Note: -- MySQL Roundtable https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-mysql -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
