起步软件技术论坛
搜索
 找回密码
 注册

QQ登录

只需一步,快速开始

查看: 2457|回复: 4

[结贴] oa部署出错

[复制链接]

2

主题

8

帖子

60

积分

初级会员

Rank: 2

积分
60
QQ
发表于 2015-12-29 16:57:23 | 显示全部楼层 |阅读模式
版本: 其它(帖子中说明) 小版本号:
数据库: 服务器操作系统: 应用服务器:
客户端操作系统: 浏览器:
使用版本BeX5 V3.3_pre.
从网站下载《北京起步办公自动化_3.2.1》,按照说明文档部署后,启动Mysql报错:mysqld.exe停止运行

91

主题

13万

帖子

3万

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
36074
发表于 2015-12-29 18:37:53 | 显示全部楼层
cmd命令行中运行批处理看看具体的错误信息是什么
远程的联系方法QQ1392416607,添加好友时,需在备注里注明其论坛名字及ID,公司等信息
发远程时同时也发一下帖子地址,方便了解要解决的问题  WeX5教程  WeX5下载



如按照该方法解决,请及时跟帖,便于版主结贴
回复 支持 反对

使用道具 举报

2

主题

8

帖子

60

积分

初级会员

Rank: 2

积分
60
QQ
 楼主| 发表于 2015-12-30 08:41:12 | 显示全部楼层
jishuang 发表于 2015-12-29 18:37
cmd命令行中运行批处理看看具体的错误信息是什么

正在启动MySQL...
.
...小提示..................................................................
.                                                                         .
. MySQL默认参数                                                           .
. 主机名/IP:127.0.0.1                                                    .
. 用户名:root                                                            .
. 密码:x5                                                                .
. 端口:3306                                                              .
.                                                                         .
...........................................................................
2015-12-30 08:39:42 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-12-30 08:39:42 0 [Note] mysqld (mysqld 5.6.26) starting as process 9980 ...
2015-12-30 08:39:42 9980 [Note] Plugin 'FEDERATED' is disabled.
2015-12-30 08:39:42 9980 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-12-30 08:39:42 9980 [Note] InnoDB: The InnoDB memory heap is disabled
2015-12-30 08:39:42 9980 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-12-30 08:39:42 9980 [Note] InnoDB: Memory barrier is not used
2015-12-30 08:39:42 9980 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-12-30 08:39:42 9980 [Note] InnoDB: Not using CPU crc32 instructions
2015-12-30 08:39:42 9980 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-12-30 08:39:42 9980 [Note] InnoDB: Completed initialization of buffer pool
2015-12-30 08:39:42 9980 [Note] InnoDB: Highest supported file format is Barracuda.
2015-12-30 08:39:42 9980 [Note] InnoDB: The log sequence numbers 16388760 and 16388760 in ibdata files do not match the log sequence number 95933404 in the ib_logfiles!
2015-12-30 08:39:42 9980 [Note] InnoDB: Database was not shutdown normally!
2015-12-30 08:39:42 9980 [Note] InnoDB: Starting crash recovery.
2015-12-30 08:39:42 9980 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-12-30 08:39:42 9980 [Note] InnoDB: Restoring possible half-written data pages
2015-12-30 08:39:42 9980 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 507525, file name .\mysql-bin.000020
2015-12-30 08:39:42 9980 [Warning] InnoDB: Resizing redo log from 2*320 to 2*3072 pages, LSN=95933404
2015-12-30 08:39:42 9980 [Warning] InnoDB: Starting to delete and rewrite log files.
2015-12-30 08:39:42 9980 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2015-12-30 08:39:43 9980 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2015-12-30 08:39:44 9980 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2015-12-30 08:39:44 9980 [Warning] InnoDB: New log files created, LSN=95933404
2015-12-30 08:39:44 9980 [Note] InnoDB: 1 rollback segment(s) are active.
2015-12-30 08:39:44 9980 [Note] InnoDB: Creating tablespace and datafile system tables.
2015-12-30 08:39:44 9980 [Note] InnoDB: Tablespace and datafile system tables created.
2015-12-30 08:39:44 9980 [Note] InnoDB: Waiting for purge to start
2015-12-30 08:39:44 9980 [Note] InnoDB: 5.6.26 started; log sequence number 95933404
2015-12-30 08:39:44 9980 [Note] Server hostname (bind-address): '*'; port: 3306
2015-12-30 08:39:44 9980 [Note] IPv6 is available.
2015-12-30 08:39:44 9980 [Note]   - '::' resolves to '::';
2015-12-30 08:39:44 9980 [Note] Server socket created on IP: '::'.
00:39:44 UTC - mysqld got exception 0xc0000005 ;
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.
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67460 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x58f5870
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...
c5fa73    mysqld.exe!?get_field@@YAPADPAUst_mem_root@@PAVField@@@Z()
c0bd09    mysqld.exe!?init@ACL_PROXY_USER@@QAEXPAUTABLE@@PAUst_mem_root@@@Z()
c0c9ea    mysqld.exe!?acl_reload@@YADPAVTHD@@@Z()
c103ef    mysqld.exe!?acl_init@@YAD_N@Z()
b6290a    mysqld.exe!?win_main@@YAHHPAPAD@Z()
b62c67    mysqld.exe!?mysql_service@@YAHPAX@Z()
ff751a    mysqld.exe!my_mb_ctype_mb()
777e3744    KERNEL32.DLL!BaseThreadInitThunk()
7791a064    ntdll.dll!RtlSetCurrentTransaction()
7791a02f    ntdll.dll!RtlSetCurrentTransaction()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2015-12-30 08:39:58 9980 [Warning] CTRL-C ignored during startup
回复 支持 反对

使用道具 举报

2

主题

8

帖子

60

积分

初级会员

Rank: 2

积分
60
QQ
 楼主| 发表于 2015-12-30 08:41:30 | 显示全部楼层
jishuang 发表于 2015-12-29 18:37
cmd命令行中运行批处理看看具体的错误信息是什么

正在启动MySQL...
.
...小提示..................................................................
.                                                                         .
. MySQL默认参数                                                           .
. 主机名/IP:127.0.0.1                                                    .
. 用户名:root                                                            .
. 密码:x5                                                                .
. 端口:3306                                                              .
.                                                                         .
...........................................................................
2015-12-30 08:39:42 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-12-30 08:39:42 0 [Note] mysqld (mysqld 5.6.26) starting as process 9980 ...
2015-12-30 08:39:42 9980 [Note] Plugin 'FEDERATED' is disabled.
2015-12-30 08:39:42 9980 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-12-30 08:39:42 9980 [Note] InnoDB: The InnoDB memory heap is disabled
2015-12-30 08:39:42 9980 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-12-30 08:39:42 9980 [Note] InnoDB: Memory barrier is not used
2015-12-30 08:39:42 9980 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-12-30 08:39:42 9980 [Note] InnoDB: Not using CPU crc32 instructions
2015-12-30 08:39:42 9980 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-12-30 08:39:42 9980 [Note] InnoDB: Completed initialization of buffer pool
2015-12-30 08:39:42 9980 [Note] InnoDB: Highest supported file format is Barracuda.
2015-12-30 08:39:42 9980 [Note] InnoDB: The log sequence numbers 16388760 and 16388760 in ibdata files do not match the log sequence number 95933404 in the ib_logfiles!
2015-12-30 08:39:42 9980 [Note] InnoDB: Database was not shutdown normally!
2015-12-30 08:39:42 9980 [Note] InnoDB: Starting crash recovery.
2015-12-30 08:39:42 9980 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-12-30 08:39:42 9980 [Note] InnoDB: Restoring possible half-written data pages
2015-12-30 08:39:42 9980 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 507525, file name .\mysql-bin.000020
2015-12-30 08:39:42 9980 [Warning] InnoDB: Resizing redo log from 2*320 to 2*3072 pages, LSN=95933404
2015-12-30 08:39:42 9980 [Warning] InnoDB: Starting to delete and rewrite log files.
2015-12-30 08:39:42 9980 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2015-12-30 08:39:43 9980 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2015-12-30 08:39:44 9980 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2015-12-30 08:39:44 9980 [Warning] InnoDB: New log files created, LSN=95933404
2015-12-30 08:39:44 9980 [Note] InnoDB: 1 rollback segment(s) are active.
2015-12-30 08:39:44 9980 [Note] InnoDB: Creating tablespace and datafile system tables.
2015-12-30 08:39:44 9980 [Note] InnoDB: Tablespace and datafile system tables created.
2015-12-30 08:39:44 9980 [Note] InnoDB: Waiting for purge to start
2015-12-30 08:39:44 9980 [Note] InnoDB: 5.6.26 started; log sequence number 95933404
2015-12-30 08:39:44 9980 [Note] Server hostname (bind-address): '*'; port: 3306
2015-12-30 08:39:44 9980 [Note] IPv6 is available.
2015-12-30 08:39:44 9980 [Note]   - '::' resolves to '::';
2015-12-30 08:39:44 9980 [Note] Server socket created on IP: '::'.
00:39:44 UTC - mysqld got exception 0xc0000005 ;
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.
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67460 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x58f5870
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...
c5fa73    mysqld.exe!?get_field@@YAPADPAUst_mem_root@@PAVField@@@Z()
c0bd09    mysqld.exe!?init@ACL_PROXY_USER@@QAEXPAUTABLE@@PAUst_mem_root@@@Z()
c0c9ea    mysqld.exe!?acl_reload@@YADPAVTHD@@@Z()
c103ef    mysqld.exe!?acl_init@@YAD_N@Z()
b6290a    mysqld.exe!?win_main@@YAHHPAPAD@Z()
b62c67    mysqld.exe!?mysql_service@@YAHPAX@Z()
ff751a    mysqld.exe!my_mb_ctype_mb()
777e3744    KERNEL32.DLL!BaseThreadInitThunk()
7791a064    ntdll.dll!RtlSetCurrentTransaction()
7791a02f    ntdll.dll!RtlSetCurrentTransaction()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2015-12-30 08:39:58 9980 [Warning] CTRL-C ignored during startup
回复 支持 反对

使用道具 举报

91

主题

13万

帖子

3万

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
36074
发表于 2015-12-30 11:40:13 | 显示全部楼层
http://www.iteye.com/problems/30931

这个是mysql的标准错误信息可以到网上查找
远程的联系方法QQ1392416607,添加好友时,需在备注里注明其论坛名字及ID,公司等信息
发远程时同时也发一下帖子地址,方便了解要解决的问题  WeX5教程  WeX5下载



如按照该方法解决,请及时跟帖,便于版主结贴
回复 支持 反对

使用道具 举报

2

主题

8

帖子

60

积分

初级会员

Rank: 2

积分
60
QQ
 楼主| 发表于 2015-12-30 14:57:52 | 显示全部楼层
jishuang 发表于 2015-12-30 11:40
http://www.iteye.com/problems/30931

这个是mysql的标准错误信息可以到网上查找

OK。已解决
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

小黑屋|手机版|X3技术论坛|Justep Inc.    

GMT+8, 2024-12-5 03:22 , Processed in 0.085144 second(s), 25 queries .

Powered by Discuz! X3.4

© 2001-2013 Comsenz Inc.

快速回复 返回顶部 返回列表