Bug #1673861 “package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 f...” : Bugs : mysql-5.7 package : Ubuntu

Revision history for this message

Brian Richardson (stonehand13) wrote on 2017-03-17:

#1

.etc.apparmor.d.usr.sbin.mysqld.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (516 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (40.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (677 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (456 bytes, text/plain; charset="utf-8")
KernLog.txt Edit (8.7 KiB, text/plain; charset="utf-8")
Logs.var.log.mysql.error.log.txt Edit (31.7 KiB, text/plain; charset="utf-8")
MySQLConf.etc.mysql.my.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.conf.d.mysqld.cnf.txt Edit (3.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2017-03-17

tags:

removed: need-duplicate-check

Revision history for this message

Christian Ehrhardt  (paelzer) wrote on 2017-03-20:

#2

Hi,
thank you for your bug report and your help to make Ubuntu better.
In the Log I have found:
2017-03-17T18:47:56.048534Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-03-17T18:47:56.049259Z 0 [ERROR] InnoDB: mmap(136151040 bytes) failed; errno 12
2017-03-17T18:47:56.049290Z 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2017-03-17T18:47:56.049317Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-03-17T18:47:56.049343Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-03-17T18:47:56.049358Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-03-17T18:47:56.049370Z 0 [ERROR] Failed to initialize plugins.
2017-03-17T18:47:56.049379Z 0 [ERROR] Aborting

From this time on there are a few more like these, but the repedition might just be due to you retrying to upgrade the mysql package.

The MYSQL-Server is restarted on upgrade and the log indicates that this restart seems to fail.
The last good startup was at "170317 14:32:20 [Note] /usr/sbin/mysqld: ready for connections." with the old version "5.5.54".

Now 128 MB does not seem too much, yet I wanted to ask to be sure if this system is very small or in general memory constrained?
I see int the dmesg that it is a 256MB System, maybe it is just too low of a limit to run the newer mysql server with your configuration?

We usually try to work through an installation with 256MB, but I'm not so sure if that is true with "bigger" extra software like mysql. In your case it seems to want 50% of your memory, with the kernel having another ~15%.

Maybe you could either give the system more memory or consider shrinking the buffer pool size, be aware that this gets you lower than the buffer pool chunk, so you need to adapt that as well.
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-resize.html
There are certain other tweaks that can be tried to shrink the needs, like [1].

Common options also often include adding swap [2], decrease the need of mysql via more in [2] or in [3]. The same is in [4], I think you totally see where this is going.

[1]: http://serverfault.com/questions/789244/innodb-not-really-out-of-memory/790301#790301
[2]: https://www.digitalocean.com/community/questions/mysql-server-keeps-stopping-unexpectedly
[3]: http://askubuntu.com/questions/457923/why-did-installation-of-mysql-5-6-on-ubuntu-14-04-fail/457932#457932
[4]: http://www.webtrafficexchange.com/solved-mysql-crash-fatal-error-cannot-allocate-memory-buffer-pool

Hi,
thank you for your bug report and your help to make Ubuntu better.
In the Log I have found:
2017-03-17T18:47:56.048534Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-03-17T18:47:56.049259Z 0 [ERROR] InnoDB: mmap(136151040 bytes) failed; errno 12
2017-03-17T18:47:56.049290Z 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2017-03-17T18:47:56.049317Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-03-17T18:47:56.049343Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-03-17T18:47:56.049358Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-03-17T18:47:56.049370Z 0 [ERROR] Failed to initialize plugins.
2017-03-17T18:47:56.049379Z 0 [ERROR] Aborting

From this time on there are a few more like these, but the repedition might just be due to you retrying to upgrade the mysql package.

The MYSQL-Server is restarted on upgrade and the log indicates that this restart seems to fail.
The last good startup was at "170317 14:32:20 [Note] /usr/sbin/mysqld: ready for connections." with the old version "5.5.54".

Now 128 MB does not seem too much, yet I wanted to ask to be sure if this system is very small or in general memory constrained?
I see int the dmesg that it is a 256MB System, maybe it is just too low of a limit to run the newer mysql server with your configuration?

We usually try to work through an installation with 256MB, but I'm not so sure if that is true with "bigger" extra software like mysql. In your case it seems to want 50% of your memory, with the kernel having another ~15%.

Maybe you could either give the system more memory or consider shrinking the buffer pool size, be aware that this gets you lower than the buffer pool chunk, so you need to adapt that as well.
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-resize.html
There are certain other tweaks that can be tried to shrink the needs, like [1].

Common options also often include adding swap [2], decrease the need of mysql via more in [2] or in [3]. The same is in [4], I think you totally see where this is going.

[1]: http://serverfault.com/questions/789244/innodb-not-really-out-of-memory/790301#790301
[2]: https://www.digitalocean.com/community/questions/mysql-server-keeps-stopping-unexpectedly
[3]: http://askubuntu.com/questions/457923/why-did-installation-of-mysql-5-6-on-ubuntu-14-04-fail/457932#457932
[4]: http://www.webtrafficexchange.com/solved-mysql-crash-fatal-error-cannot-allocate-memory-buffer-pool

Revision history for this message

Christian Ehrhardt  (paelzer) wrote on 2017-03-20:

#3

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in mysql-5.7 (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-20:

#4

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.7 (Ubuntu):
status:	Incomplete → Expired

Ubuntu
mysql-5.7 package

package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntumysql-5.7 package

package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
mysql-5.7 package