# System reboot signal 150303 10:15:04 [Note] /usr/sbin/mysqld: Normal shutdown 150303 10:15:04 [Note] Event Scheduler: Purging the queue. 0 events 150303 10:15:04 InnoDB: Starting shutdown... 150303 10:15:05 InnoDB: Shutdown completed; log sequence number 1595745 150303 10:15:05 [Note] /usr/sbin/mysqld: Shutdown complete
# Machine is back 150303 10:15:26 [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. 150303 10:15:26 [Note] Plugin 'FEDERATED' is disabled. 150303 10:15:26 InnoDB: The InnoDB memory heap is disabled 150303 10:15:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150303 10:15:26 InnoDB: Compressed tables use zlib 1.2.8 150303 10:15:26 InnoDB: Using Linux native AIO 150303 10:15:26 InnoDB: Initializing buffer pool, size = 128.0M 150303 10:15:26 InnoDB: Completed initialization of buffer pool 150303 10:15:26 InnoDB: highest supported file format is Barracuda. 150303 10:15:26 InnoDB: Waiting for the background threads to start 150303 10:15:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150303 10:15:26 [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. 150303 10:15:26 [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. 150303 10:15:26 [Note] Plugin 'FEDERATED' is disabled. 150303 10:15:26 InnoDB: The InnoDB memory heap is disabled 150303 10:15:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150303 10:15:26 InnoDB: Compressed tables use zlib 1.2.8 150303 10:15:26 InnoDB: Using Linux native AIO 150303 10:15:26 InnoDB: Initializing buffer pool, size = 128.0M 150303 10:15:26 InnoDB: Completed initialization of buffer pool InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 150303 10:15:26 InnoDB: Retrying to lock the first data file 150303 10:15:27 InnoDB: 5.5.41 started; log sequence number 1595745 150303 10:15:27 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 150303 10:15:27 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 150303 10:15:27 [Note] Server socket created on IP: '127.0.0.1'. 150303 10:15:27 [Note] Event Scheduler: Loaded 0 events 150303 10:15:27 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.41-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) InnoDB: Unable to lock ./ibdata1, error: 11 # "error: 11" goes on and on 150303 10:17:08 InnoDB: Unable to open the first data file InnoDB: Error in opening ./ibdata1 150303 10:17:08 InnoDB: Operating system error number 11 in a file operation. InnoDB: Error number 11 means 'Resource temporarily unavailable'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html 150303 10:17:08 InnoDB: Could not open or create data files. 150303 10:17:08 InnoDB: If you tried to add new data files, and it failed here, 150303 10:17:08 InnoDB: you should now edit innodb_data_file_path in my.cnf back 150303 10:17:08 InnoDB: to what it was, and remove the new ibdata files InnoDB created 150303 10:17:08 InnoDB: in this failed attempt. InnoDB only wrote those files full of 150303 10:17:08 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 150303 10:17:08 InnoDB: remove old data files which contain your precious data! 150303 10:17:08 [ERROR] Plugin 'InnoDB' init function returned error. 150303 10:17:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150303 10:17:08 [ERROR] Unknown/unsupported storage engine: InnoDB 150303 10:17:08 [ERROR] Aborting 150303 10:17:08 [Note] /usr/sbin/mysqld: Shutdown complete 150303 10:17:08 mysqld_safe Number of processes running now: 0 150303 10:17:08 mysqld_safe mysqld restarted 150303 10:17:08 [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. 150303 10:17:08 [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. 150303 10:17:08 [Note] Plugin 'FEDERATED' is disabled. 150303 10:17:08 InnoDB: The InnoDB memory heap is disabled 150303 10:17:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150303 10:17:08 InnoDB: Compressed tables use zlib 1.2.8 150303 10:17:08 InnoDB: Using Linux native AIO 150303 10:17:08 InnoDB: Initializing buffer pool, size = 128.0M 150303 10:17:08 InnoDB: Completed initialization of buffer pool InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 150303 10:17:08 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 # "error: 11" goes on and on 150303 10:18:48 InnoDB: Unable to open the first data file InnoDB: Error in opening ./ibdata1 150303 10:18:48 InnoDB: Operating system error number 11 in a file operation. InnoDB: Error number 11 means 'Resource temporarily unavailable'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html 150303 10:18:48 InnoDB: Could not open or create data files. 150303 10:18:48 InnoDB: If you tried to add new data files, and it failed here, 150303 10:18:48 InnoDB: you should now edit innodb_data_file_path in my.cnf back 150303 10:18:48 InnoDB: to what it was, and remove the new ibdata files InnoDB created 150303 10:18:48 InnoDB: in this failed attempt. InnoDB only wrote those files full of 150303 10:18:48 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 150303 10:18:48 InnoDB: remove old data files which contain your precious data! 150303 10:18:48 [ERROR] Plugin 'InnoDB' init function returned error. 150303 10:18:48 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150303 10:18:48 [ERROR] Unknown/unsupported storage engine: InnoDB 150303 10:18:48 [ERROR] Aborting 150303 10:18:48 [Note] /usr/sbin/mysqld: Shutdown complete 150303 10:18:48 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended # At this point MySQL is unusable: no unix socket but the process still runs (the PID is gone) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425995 Title: mysql does not always create a Unix socket on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1425995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
