报错日志vi /opt/zbox/logs/mysql_error.log
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: Compressed tables use zlib 1.2.3.4
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: Using SSE crc32 instructions
2018-04-11 10:59:04 140620556592960 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-11 10:59:05 140620556592960 [Note] InnoDB: Completed initialization of buffer pool
2018-04-11 10:59:05 140620556592960 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-11 10:59:05 140620556592960 [Note] InnoDB: The log sequence numbers 1601075 and 1601075 in ibdata files do not match the log sequence number 84636095 in the ib_logfiles!
2018-04-11 10:59:05 140620556592960 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace xxl@002djob/XXL_JOB_QRTZ_TRIGGER_GROUP which uses space ID: 1 at filepath: ./xxl@002djob/XXL_JOB_QRTZ_TRIGGER_GROUP.ibd
2018-04-11 10:59:05 7fe4c652e740 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./xxl@002djob/XXL_JOB_QRTZ_TRIGGER_GROUP.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
180411 10:59:05 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

[root@kdddxx01 zbox]# ls -al /opt/zbox/etc
总用量 4
drwxr-xr-x. 5 git osa 41 4月 28 2017 .
drwxr-xr-x. 10 git osa 4096 4月 11 10:50 ..
drwxr-xr-x. 2 git osa 40 2月 24 17:03 apache
drwxr-xr-x. 2 git osa 62 4月 11 10:16 mysql
drwxr-xr-x. 2 git osa 45 11月 7 11:53 php
[root@kdddxx01 zbox]#

禅道里面有数据吗？
没有的话可以停止服务，重命名一下zbox文件夹，然后从新下载部署一下禅道试试