MySQL迁移后启动不了

回贴
回帖数 10
阅读数 184
发表时间 2025-03-17 08:26:08
🐊
楼主

2025-03-17 7:46:18 0 [Note] InnoDB: Using Linux native AIO

2025-03-17 7:46:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2025-03-17 7:46:18 0 [Note] InnoDB: Uses event mutexes

2025-03-17 7:46:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2025-03-17 7:46:18 0 [Note] InnoDB: Number of pools: 1

2025-03-17 7:46:18 0 [Note] InnoDB: Using SSE2 crc32 instructions

2025-03-17 7:46:18 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M

2025-03-17 7:46:18 0 [Note] InnoDB: Completed initialization of buffer pool

2025-03-17 7:46:18 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2025-03-17 7:46:18 0 [Note] InnoDB: 128 out of 128 rollback segments are active.

250317 7:46:18 [ERROR] mysqld got signal 11 ;

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.3.13-MariaDB

key_buffer_size=16777216

read_buffer_size=262144

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137278 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 0x30000

2025-03-17 7:46:18 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2025-03-17 7:46:18 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2025-03-17 7:46:18 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2025-03-17 7:46:18 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2025-03-17 7:46:18 0 [Note] InnoDB: Waiting for purge to start

/opt/zbox/run/mysql/mysqld(my_print_stacktrace+0x29)[0x56072c374279]

/opt/zbox/run/mysql/mysqld(handle_fatal_signal+0x57d)[0x56072bec417d]

/opt/zbox/run/lib/libpthread.so.0(+0x12890)[0x7f35e46fb890]

/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0xcac8)[0x7f35e6328ac8]

/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0x150bd)[0x7f35e63310bd]

/opt/zbox/run/lib/libc.so.6(_dl_catch_exception+0x6f)[0x7f35e3ad32df]

/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0x147ca)[0x7f35e63307ca]

/opt/zbox/run/lib/libc.so.6(+0x1663ad)[0x7f35e3ad23ad]

/opt/zbox/run/lib/libc.so.6(_dl_catch_exception+0x6f)[0x7f35e3ad32df]

/opt/zbox/run/lib/libc.so.6(_dl_catch_error+0x2f)[0x7f35e3ad336f]

/opt/zbox/run/lib/libc.so.6(__libc_dlopen_mode+0x89)[0x7f35e3ad24d9]

/opt/zbox/run/lib/libpthread.so.0(+0x12deb)[0x7f35e46fbdeb]

/opt/zbox/run/lib/libpthread.so.0(+0x12fd4)[0x7f35e46fbfd4]

/opt/zbox/run/lib/libpthread.so.0(__pthread_unwind+0x40)[0x7f35e46f9f10]

/opt/zbox/run/lib/libpthread.so.0(+0x8ae5)[0x7f35e46f1ae5]

/opt/zbox/run/mysql/mysqld(+0x490ad5)[0x56072bc3cad5]

/opt/zbox/run/mysql/mysqld(+0x997206)[0x56072c143206]

/opt/zbox/run/lib/libpthread.so.0(+0x76db)[0x7f35e46f06db]

/opt/zbox/run/lib/libc.so.6(clone+0x3f)[0x7f35e3a8d88f]

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.

10个回复
于涛 沙发

您好,根据日志内容有关于mysql的信息可以看下这个250317 7:46:18 [ERROR] mysqld got signal 11 ;

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.

目前mysql的版本用的是什么版本?建议更换下mysql版本,This could be because you hit a bug. 当前版本有BUG

2025-03-17 09:03:10 于涛 回帖
🐊
板凳

使用的禅道一起的,不知道什么版本,没有单独按照MySQL,关键是原来服务器上的还能启动,如果是MySQLbug问题,原来的也应该启动不了吧

2025-03-17 09:07:40 姜 回帖
马超 #3

另外咱们是直接迁移数据库物理文件吗?如果直接迁移物理文件可能数据库会有兼容问题。建议在原禅道的 后台-系统设置-备份页面 点击备份,然后拷贝.sql.php 和.file 文件到新禅道中进行还原。

备份还原参考步骤:

1、搭建相同版本号的禅道,保证网页可以正常访问;

2、将备份文件 sql.php 用文本编辑器打开删除开头的 ,然后重命名去掉.php,然后导入禅道数据库中;

3、将附件文件 .file目录下upload/1放到新禅道 www/data/upload/ 下面。

2025-03-17 09:09:46 马超 最后编辑 2025-03-17 09:09:46 马超 回帖
于涛 #4 回复#2

两台服务器的系统和版本分别是什么?可以添加下我们页面下方的商务联系方式,邀请加入技术交流群中,将具体的信息提供下我们看下。

2025-03-17 09:09:42 于涛 回帖
🐊
#5

是直接压缩,然后解压迁移的

2025-03-17 09:10:18 姜 回帖
🐊
#6 回复#4

以下是MySQL启动报错的日志

2025-03-17 09:13:07 姜 最后编辑 2025-03-17 09:13:07 姜 回帖
马超 #7 回复#5

咱们是迁移的哪个目录?可以具体描述下,另外咱们迁移之前有没有停止服务。

2025-03-17 09:14:35 马超 回帖
🐊
#8 回复#7

停止服务的,都是在/opt目录下

2025-03-17 09:16:47 姜 回帖
🐊
#9 回复#7

将原来方服务器的禅道服务器停止,在将/opt/下的 回贴

马超 #10

建议可以重新按照下面的步骤迁移看下,如果还有问题,可以点击“联系我们”加一下的商务的QQ,商务邀请进群后具体帮您排查下。

  1. 可以停止服务禅道服务/opt/zbox/zbox stop

  1. 打包迁移/opt/zbox目录

  2. 到新服务器/opt目录下解压启动服务/opt/zbox/zbox start

  3. 访问禅道查看页面

2025-03-17 09:29:28 马超 回帖
联系我们
联系人
刘璐/高级客户经理
电话(微信)
18562550650
QQ号码
2845263372
联系邮箱
liulu@chandao.com
刘璐
高级客户经理
18562550650
2845263372
统一服务热线 4006-8899-23
我要提问提问有任何问题,您都可以在这里提问。 问题反馈反馈点击这里,让我们聆听您的建议与反馈。