Your message dated Wed, 23 Jul 2014 16:33:11 +0200
with message-id <1406125991.3753.1.ca...@zefram.himalaya.sns.it>
and subject line Re: mysql-server-5.5 fails to start after security upgrade
from 5.5.37-0+wheezy1 to 5.5.38-0+wheezy1
has caused the Debian Bug report #755781,
regarding mysql-server-5.5 fails to start after security upgrade from
5.5.37-0+wheezy1 to 5.5.38-0+wheezy1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
755781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server-5.5
Version: 5.5.38-0+wheezy1
Severity: grave
Justification: renders package unusable
Dear maintainers,
after the security upgrade from 5.5.37-0+wheezy1 to 5.5.38-0+wheezy1 mysql
fails to start:
> # service mysql start
> [FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . .
> failed!
This the logs:
/var/log/syslog
> Jul 23 10:11:45 debian mysqld_safe: Starting mysqld daemon with databases
> from /var/lib/mysql
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [Warning] Using unique option
> prefix key_buffer instead of key_buffer_size is deprecated and will be
> removed in a future release. Please use the full name instead.
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [Warning] Using unique option
> prefix myisam-recover instead of myisam-recover-options is deprecated and
> will be removed in a future release. Please use the full name instead.
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [Note] Plugin 'FEDERATED' is
> disabled.
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: The InnoDB memory heap
> is disabled
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Mutexes and rw_locks
> use GCC atomic builtins
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Compressed tables use
> zlib 1.2.7
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Using Linux native AIO
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Initializing buffer
> pool, size = 128.0M
> Jul 23 10:11:45 debian mysqld: InnoDB: mmap(137363456 bytes) failed; errno 12
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Completed
> initialization of buffer pool
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Fatal error: cannot
> allocate memory for the buffer pool
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [ERROR] Plugin 'InnoDB' init
> function returned error.
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [ERROR] Plugin 'InnoDB'
> registration as a STORAGE ENGINE failed.
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [ERROR] Unknown/unsupported
> storage engine: InnoDB
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [ERROR] Aborting
> Jul 23 10:11:45 debian mysqld:
> Jul 23 10:11:45 debian mysqld: 140723 10:11:45 [Note] /usr/sbin/mysqld:
> Shutdown complete
> Jul 23 10:11:45 debian mysqld:
> Jul 23 10:11:45 debian mysqld_safe: mysqld from pid file
> /var/run/mysqld/mysqld.pid ended
> Jul 23 10:11:59 debian /etc/init.d/mysql[1980]: 0 processes alive and
> '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
> Jul 23 10:11:59 debian /etc/init.d/mysql[1980]: #007/usr/bin/mysqladmin:
> connect to server at 'localhost' failed
> Jul 23 10:11:59 debian /etc/init.d/mysql[1980]: error: 'Can't connect to
> local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
> Jul 23 10:11:59 debian /etc/init.d/mysql[1980]: Check that mysqld is running
> and that the socket: '/var/run/mysqld/mysqld.sock' exists!
> Jul 23 10:11:59 debian /etc/init.d/mysql[1980]:
/var/log/mysql* are all empty
The workarounds described on bug #682232 (start with innodb_force_recovery=1 or
rm /var/lib/mysql/ib*) didn't work
I haven't changed the default configuration (and the machine was installed a
week ago with the last debian version).
Downgrading the mysql-server-5.5 to 5.5.37-0+wheezy1 doesn't solve the issue.
Regards
Enrico
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mysql-server-5.5 depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.49
ii initscripts 2.88dsf-41+deb7u1
ii libc6 2.13-38+deb7u3
ii libdbi-perl 1.622-1+deb7u1
ii libgcc1 1:4.7.2-5
ii libstdc++6 4.7.2-5
ii lsb-base 4.1+Debian8+deb7u1
ii mysql-client-5.5 5.5.38-0+wheezy1
ii mysql-common 5.5.38-0+wheezy1
ii mysql-server-core-5.5 5.5.38-0+wheezy1
ii passwd 1:4.1.5.1-1
ii perl 5.14.2-21+deb7u1
ii psmisc 22.19-1+deb7u1
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages mysql-server-5.5 recommends:
ii bsd-mailx [mailx] 8.1.2-0.20111106cvs-1
ii libhtml-template-perl 2.91-1
Versions of packages mysql-server-5.5 suggests:
pn tinyca <none>
-- debconf information:
* mysql-server/root_password_again: (password omitted)
* mysql-server/root_password: (password omitted)
mysql-server/error_setting_password:
mysql-server-5.5/postrm_remove_databases: false
mysql-server-5.5/start_on_boot: true
mysql-server-5.5/nis_warning:
mysql-server-5.5/really_downgrade: false
mysql-server/password_mismatch:
mysql-server/no_upgrade_when_using_ndb:
--- End Message ---
--- Begin Message ---
Ops, I should pay more attention to the log messages. Freeing some
memory resolves the issue.
Thanks for the support
Enrico
On Wed, 2014-07-23 at 15:44 +0200, Arne Rusek wrote:
> Hi Enrico,
>
> for me, upgrade was w/o problems.
>
> > Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Initializing buffer
> > pool, size = 128.0M
> > Jul 23 10:11:45 debian mysqld: InnoDB: mmap(137363456 bytes) failed; errno
> > 12
> > Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Completed
> > initialization of buffer pool
> > Jul 23 10:11:45 debian mysqld: 140723 10:11:45 InnoDB: Fatal error: cannot
> > allocate memory for the buffer pool
>
> Your logs indicate you ran out of memory ;-)
>
> # perror 12
> OS error code 12: Cannot allocate memory
>
> If you got it twice, sorry, but debian bts said it forwarded mail only
> to maintainers. So sending it to you directly as well.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755781
>
--- End Message ---
