infinite loop in mysql service

Bug #1244181 reported by Karl-Philipp Richter on 2013-10-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gearman MySQL UDF
Undecided
Unassigned

Bug Description

Hi together,
when I invoke
<code>
sudo service mysql start
</code>
the command never returns. Following /var/log/mysql/error.log shows that the lines
<output>
131024 11:49:20 [Note] Plugin 'FEDERATED' is disabled.
131024 11:49:20 InnoDB: The InnoDB memory heap is disabled
131024 11:49:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131024 11:49:20 InnoDB: Compressed tables use zlib 1.2.8
131024 11:49:20 InnoDB: Using Linux native AIO
131024 11:49:20 InnoDB: Initializing buffer pool, size = 128.0M
131024 11:49:20 InnoDB: Completed initialization of buffer pool
131024 11:49:20 InnoDB: highest supported file format is Barracuda.
131024 11:49:21 InnoDB: Waiting for the background threads to start
131024 11:49:22 InnoDB: 5.5.32 started; log sequence number 1595685
131024 11:49:22 [ERROR] Aborting

131024 11:49:22 InnoDB: Starting shutdown...
131024 11:49:23 InnoDB: Shutdown completed; log sequence number 1595685
131024 11:49:23 [Note]
</output>
are printed repeatedly. How can I debug this, i.e. find out what's happening in order to provide more information to this bug (application should handle inconsistencies in settings or crash)?

Thanks in advance for taking care about this.

description: updated

This issue occurs if the datadir is mounted using bind mechanism and has wrong permissions drwxr-xr-x instead of drwx------.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers