解决中 17.8版本安装问题

系统是CentOS 6.9

按照教程解压到opt目录下,设置了端口/opt/zbox/zbox -ap 8086 -mp 3308,/opt/zbox/zbox start启动的时候mysql报错了Start Mysql fail. You can see the log /opt/zbox/logs/mysql_error.log

相关日志内容如下,有哪位遇到过这样的问题吗?


2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: The InnoDB memory heap is disabled
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Compressed tables use zlib 1.2.3.4
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Using SSE crc32 instructions
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Completed initialization of buffer pool
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Setting log file ./ib_logfile101 size to 256 MB
2022-11-16  3:29:23 139700034570112 [Note] InnoDB: Setting log file ./ib_logfile1 size to 256 MB
2022-11-16  3:29:24 139700034570112 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2022-11-16  3:29:24 139700034570112 [Warning] InnoDB: New log files created, LSN=4841465
2022-11-16  3:29:24 139700034570112 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
2022-11-16  3:29:24 139700034570112 [Note] InnoDB: Creating tablespace and datafile system tables.
2022-11-16  3:29:24 139700034570112 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18.  Tablespace is full. Dropping incompletely created tables.
2022-11-16 03:29:24 7f0e72ef8780  InnoDB: Assertion failure in thread 139700034570112 in file dict0crea.cc line 1903
InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
221116  3:29:24 [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.

Server version: 10.1.22-MariaDB
key_buffer_size=16777216
read_buffer_size=2097152
max_used_connections=0
max_threads=602
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2494519 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48400
/opt/zbox/run/mysql/mysqld(my_print_stacktrace+0x24)[0xb77074]
/opt/zbox/run/mysql/mysqld(handle_fatal_signal+0x45a)[0x73f73a]
/opt/zbox/run/lib/libpthread.so.0(+0x10330)[0x7f0e71c16330]
/opt/zbox/run/lib/libc.so.6(gsignal+0x37)[0x7f0e71237c37]
/opt/zbox/run/lib/libc.so.6(abort+0x148)[0x7f0e7123b028]
/opt/zbox/run/mysql/mysqld[0xa0ffdf]
/opt/zbox/run/mysql/mysqld[0x98db9e]
/opt/zbox/run/mysql/mysqld[0x8cc70b]
/opt/zbox/run/mysql/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x5b)[0x7419cb]
/opt/zbox/run/mysql/mysqld[0x5ebe54]
/opt/zbox/run/mysql/mysqld(_Z11plugin_initPiPPci+0x9b8)[0x5ecf08]
/opt/zbox/run/mysql/mysqld[0x557a20]
/opt/zbox/run/mysql/mysqld(_Z11mysqld_mainiPPc+0x86d)[0x55c93d]
/opt/zbox/run/lib/libc.so.6(__libc_start_main+0xf5)[0x7f0e71222f45]
/opt/zbox/run/mysql/mysqld[0x551b15]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.



禅道版本 17.7 Linux安装包
操作系统 CentOS
客户端浏览器 Chrome

提问者: 赵先生 悬赏: 5 日期: 2022-11-17 17:53:37 答案:1 点击:71
设置备注
答案列表
2022/11/18
您好,您的系统版本需要使用低版本linux一键安装包,https://www.zentao.net/dl/zentao/17.8/ZenTaoPMS.17.8.zbox_old.64.tar.gz,可以使用这个试下
2022/11/18
您好,我用的就是低版本的包,17.8和17.7都试了,都是mysql启动不了,都报这个错
2022/11/18
Tablespace is full,检查下磁盘空间还有吗?可以添加下首页同事,邀请到禅道交流群,方便交流