|
|
沙发#
发布于:2015-05-11 14:13
这个配置是正确的,应该是data目录内有几个表和现在版本不匹配,具体表现为mysql/data/mysql文件夹下,具体看新的data目录内.err文件[error]报错。
另外注意以前和现在数据库是否存在启动冲突。如果用upupw的数据库需要先停用以前的数据库服务并设置为手动启动服务以免自动启动带来冲突。 |
|
板凳#
发布于:2015-05-11 15:12
150511 15:10:42 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150511 15:10:42 [Note] InnoDB: The InnoDB memory heap is disabled 150511 15:10:42 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150511 15:10:42 [Note] InnoDB: Memory barrier is not used 150511 15:10:42 [Note] InnoDB: Compressed tables use zlib 1.2.3 150511 15:10:42 [Note] InnoDB: Not using CPU crc32 instructions 150511 15:10:42 [Note] InnoDB: Initializing buffer pool, size = 64.0M 150511 15:10:42 [Note] InnoDB: Completed initialization of buffer pool 150511 15:10:42 [Note] InnoDB: Highest supported file format is Barracuda. 150511 15:10:42 [Note] InnoDB: 128 rollback segment(s) are active. 150511 15:10:42 [Note] InnoDB: Waiting for purge to start 150511 15:10:42 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-71.0 started; log sequence number 1616928 150511 15:10:42 [Note] Plugin 'FEEDBACK' is disabled. 150511 15:10:42 [Note] Server socket created on IP: '::'. 150511 15:10:42 [Note] Event Scheduler: Loaded 0 events 150511 15:10:42 [Note] D:\upupw\MariaDB\bin\mysqld.exe: ready for connections. Version: '10.0.16-MariaDB' socket: '' port: 3306 mariadb.org binary distribution |
|
地板#
发布于:2015-05-11 15:12
麻烦老大看下错误日志,谢谢,一上午了,搞不定。
|
|
4楼#
发布于:2015-05-11 16:02
|
|
5楼#
发布于:2015-05-11 16:18
进程中没有mysqld.exe,data已经移走,能否给发个完整的配置表,my.ini
|
|
6楼#
发布于:2015-05-11 16:19
更改了目录的,用在upupw中的
|
|
7楼#
发布于:2015-05-11 16:22
150511 16:21:18 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
150511 16:21:34 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150511 16:21:34 [Note] InnoDB: The InnoDB memory heap is disabled 150511 16:21:34 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150511 16:21:34 [Note] InnoDB: Memory barrier is not used 150511 16:21:34 [Note] InnoDB: Compressed tables use zlib 1.2.3 150511 16:21:34 [Note] InnoDB: Not using CPU crc32 instructions 150511 16:21:34 [Note] InnoDB: Initializing buffer pool, size = 64.0M 150511 16:21:34 [Note] InnoDB: Completed initialization of buffer pool 150511 16:21:34 [Note] InnoDB: Highest supported file format is Barracuda. 150511 16:21:34 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463 150511 16:21:34 [Note] InnoDB: Database was not shutdown normally! 150511 16:21:34 [Note] InnoDB: Starting crash recovery. 150511 16:21:34 [Note] InnoDB: Reading tablespace information from the .ibd files... 150511 16:21:34 [Note] InnoDB: Restoring possible half-written data pages 150511 16:21:34 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 1600607 150511 16:21:34 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 150511 16:21:35 [Note] InnoDB: 128 rollback segment(s) are active. 150511 16:21:35 [Note] InnoDB: Waiting for purge to start 150511 16:21:35 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-71.0 started; log sequence number 1600607 150511 16:21:35 [Note] Plugin 'FEEDBACK' is disabled. 150511 16:21:35 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 150511 16:21:35 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 150511 16:21:35 [Note] Server socket created on IP: '::'. 150511 16:21:35 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist |
|
8楼#
发布于:2015-05-11 16:23
删除了upupw中数据库中data,进程中没有mysqld,以上是新日志
|
|
9楼#
发布于:2015-05-11 16:44
不改路径,正常运行,但硬盘有限,必须改路径,望帮忙,谢谢
|
|
10楼#
发布于:2015-05-11 20:04
建议你把以前的数据库导出SQL文件,然后把upupw的data目录挪到预定位置并指定路径,启动成功后再把sql文件导入。用upupw面板的14数据库管理导入sql文件非常方便快捷。
|
|
11楼#
发布于:2015-05-12 08:43
好的,现在是总启动不成功,只要改路径,就启动不了,把改路径的那句话注释掉,就启动成功,data目录文件也剪切到新位置了,原因不明中。
|
|
12楼#
发布于:2015-05-12 15:49
|
|
13楼#
发布于:2016-01-12 10:45
我去,我也碰到这个问题,终于解决了
在[mysqld]下添加这行,一定要在前面加“#”,不知道为什么 #datadir=F:/server/MariaDB/data |
|
14楼#
发布于:2016-01-12 17:44
fire1936255:我去,我也碰到这个问题,终于解决了加#就注释掉了,还在默认的data目录。 旧版本面板在更改data位置后启动时会误报,其实已经启动了,因为要检查默认data下的pid文件,而更改data位置后不会在默认位置生成pid导致检测不到出错。 新版本1510, 1511, 1512 , k1.8后改用了检测方法修复了此问题,请升级面板后再用。 |
|
上一页
下一页