I tried removing Docker, but the Docker files are still being written to the mount point, and Docker is still listed under Services in the OMV3 GUI.
When removing Docker, via the OMV3 GUI I:
- disabled the Docker service
- uninstalled Docker under Plugins
- toggled off 'Docker CE' under OMV-Extras
- rebooted
Any idea why I'm still seeing Docker listed under Services and also having Docker files written at boot?
My Docker service is writing files to my ZFS mount point at boot before ZFS has mounted, preventing my ZFS pool from actually mounting (similar to https://forum.openmediavault.o…read/15018-Startup-order/).
How can I ensure my ZFS pools mount before any other services run?
Is there a systemd Required-Start dependency I can set in my /etc/init.d/docker ?
### BEGIN INIT INFO
# Provides: docker
# Required-Start: $syslog $remote_fs
# Required-Stop: $syslog $remote_fs
# Should-Start: cgroupfs-mount cgroup-lite
# Should-Stop: cgroupfs-mount cgroup-lite
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Create lightweight, portable, self-sufficient containers.
# Description:
# Docker is an open-source project to easily create lightweight, portable,
# self-sufficient containers from any application. The same container that a
# developer builds and tests on a laptop can run at scale, in production, on
# VMs, bare metal, OpenStack clusters, public clouds and more.
### END INIT INFOThanks for your help!
Is your MySQL data directory on a ZFS filesystem? Mine is and I had the same problem as you, so I followed these steps to fix it:
root@OpenMediaVault:~# mysqld_safe --log-error=/var/log/mysql.err
150222 20:23:06 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-error configuration options for --syslog to take effect.
150222 20:23:06 mysqld_safe Logging to '/var/log/mysql.err'.
150222 20:23:06 mysqld_safe Starting mysqld daemon with databases from /OMV-ZFS/MySQL/
150222 20:23:06 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid endedroot@OpenMediaVault:~# cat /var/log/mysql.err
150222 20:23:06 mysqld_safe Starting mysqld daemon with databases from /OMV-ZFS/MySQL/
150222 20:23:06 [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.
150222 20:23:06 [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.
150222 20:23:06 [Note] Plugin 'FEDERATED' is disabled.
150222 20:23:06 InnoDB: The InnoDB memory heap is disabled
150222 20:23:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150222 20:23:06 InnoDB: Compressed tables use zlib 1.2.7
150222 20:23:06 InnoDB: Using Linux native AIO
150222 20:23:06 InnoDB: Initializing buffer pool, size = 128.0M
150222 20:23:06 InnoDB: Completed initialization of buffer pool
150222 20:23:06 InnoDB: highest supported file format is Barracuda.
150222 20:23:06 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'aio write'.
InnoDB: Cannot continue operation.
150222 20:23:06 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid endedA quick Google search found this post which shows how to fix the error:
root@OpenMediaVault:~# vi /etc/mysql/my.cnf
[mysqld]
innodb_use_native_aio = 0(In case it's not obvious, append innodb_use_native_aio = 0 to the end of your [mysqld] section in /etc/mysql/my.cnf)
After this, MySQL started OK for me. Hope it helps!