Rancher server container keeps on restarting

Rancher 1.x
1

HI Team,

After restarted docker and rebooting the machine, rancher server container keeps on restarting and below are the error logs please help me in resolving the issue.

Docker version:
Docker version 1.13.1, build 94f4240/1.13.1

Rancher version;
rancher/server:v1.6.16

OS:
RHEL

190118 6:28:24 InnoDB: Error: unable to create temporary file; errno: 13
190118 6:28:24 [ERROR] Plugin ‘InnoDB’ init function returned error.
190118 6:28:24 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
190118 6:28:24 [ERROR] Unknown/unsupported storage engine: InnoDB
190118 6:28:24 [ERROR] Aborting
190118 6:28:24 [Note] /usr/sbin/mysqld: Shutdown complete
s6-svscanctl: fatal: unable to control /service: supervisor not listening
190118 6:35:14 [Note] /usr/sbin/mysqld (mysqld 5.5.59-0ubuntu0.14.04.1) starting as process 26 …
190118 6:35:14 [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.
190118 6:35:14 [Note] Plugin ‘FEDERATED’ is disabled.
190118 6:35:14 InnoDB: The InnoDB memory heap is disabled
190118 6:35:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190118 6:35:14 InnoDB: Compressed tables use zlib 1.2.8
190118 6:35:14 InnoDB: Using Linux native AIO
/usr/sbin/mysqld: Can’t create/write to file ‘/tmp/ibgaRplF’ (Errcode: 13)
190118 6:35:14 InnoDB: Error: unable to create temporary file; errno: 13
190118 6:35:14 [ERROR] Plugin ‘InnoDB’ init function returned error.
190118 6:35:14 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
190118 6:35:14 [ERROR] Unknown/unsupported storage engine: InnoDB
190118 6:35:14 [ERROR] Aborting
190118 6:35:14 [Note] /usr/sbin/mysqld: Shutdown complete
s6-svscanctl: fatal: unable to control /service: supervisor not listening

2

Usually has to do with a full disk or wrong permissions on the directories/files mounted in /var/lib/mysql

3

Disk is not full and below are the permissions, clould you please verify once

sudo docker run -d --restart=unless-stopped -v /data/mysql:/var/lib/mysql -p 8080:8080 --name=cri-rancher rancher/server:v1.6.16

drwxr-xr-x 5 root root 54 Jan 18 16:33 data
cd mysql
drwxr-xr-x 5 102 root 112 Jan 21 14:55 mysql
cd mysql
drwx------ 2 102 root 4096 Jan 18 11:43 mysql
drwx------ 2 102 105 4096 Dec 20 15:23 performance_schema
cd mysql
-rw-rw---- 1 102 105 8820 Dec 20 15:23 columns_priv.frm
-rw-rw---- 1 102 105 0 Dec 20 15:23 columns_priv.MYD
-rw-rw---- 1 102 105 4096 Dec 20 15:23 columns_priv.MYI

4

Hi, Same issue i am facing. below are the error log. Please need advise

190730 16:11:30 [Note] /usr/sbin/mysqld (mysqld 5.5.60-0ubuntu0.14.04.1) starting as process 24 …
s6-svscanctl: fatal: unable to control /service: supervisor not listening
190730 16:12:30 [Note] /usr/sbin/mysqld (mysqld 5.5.60-0ubuntu0.14.04.1) starting as process 24 …
s6-svscanctl: fatal: unable to control /service: supervisor not listening
190730 16:13:31 [Note] /usr/sbin/mysqld (mysqld 5.5.60-0ubuntu0.14.04.1) starting as process 24 …
s6-svscanctl: fatal: unable to control /service: supervisor not listening
190730 16:14:32 [Note] /usr/sbin/mysqld (mysqld 5.5.60-0ubuntu0.14.04.1) starting as process 24 …
s6-svscanctl: fatal: unable to control /service: supervisor not listening

5 
       Issue resolved after removing the mysql folder which will inside rancher folder, which seems corrupted mysql.