wdlinux
在mysql 安装目录下
新建 /home/wddata/var 文件即可 mysql-bin.000008
141026 20:13:49 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141026 20:13:49 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141026 20:13:49 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141026 20:13:50 InnoDB: Initializing buffer pool, size = 8.0M
141026 20:13:50 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141026 20:13:50 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
141026 20:13:50 InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141026 20:13:50 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141026 20:13:50 [ERROR] Could not open log file
141026 20:13:50 [ERROR] Can't init tc log
141026 20:13:50 [ERROR] Aborting
141026 20:13:50 InnoDB: Starting shutdown...
141026 20:13:55 InnoDB: Shutdown completed; log sequence number 0 44243
141026 20:13:55 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete
141026 20:13:55 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141029 20:12:20 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141029 20:12:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141029 20:12:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141029 20:12:20 InnoDB: Initializing buffer pool, size = 8.0M
141029 20:12:20 InnoDB: Completed initialization of buffer pool
141029 20:12:20 InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141029 20:12:20 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141029 20:12:20 [ERROR] Could not open log file
141029 20:12:20 [ERROR] Can't init tc log
141029 20:12:20 [ERROR] Aborting
141029 20:12:20 InnoDB: Starting shutdown...
141029 20:12:26 InnoDB: Shutdown completed; log sequence number 0 44243
141029 20:12:26 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete
141029 20:12:26 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 11:51:17 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 11:51:18 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 11:51:18 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 11:51:18 InnoDB: Initializing buffer pool, size = 8.0M
141101 11:51:18 InnoDB: Completed initialization of buffer pool
141101 11:51:19 InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 11:51:19 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 11:51:19 [ERROR] Could not open log file
141101 11:51:19 [ERROR] Can't init tc log
141101 11:51:19 [ERROR] Aborting
wdlinux 下数据库文件位置
/home/wddata/var
141101 11:51:19 InnoDB: Starting shutdown...
141101 11:51:24 InnoDB: Shutdown completed; log sequence number 0 44243
141101 11:51:24 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete
141101 11:51:24 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 19:03:50 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 19:03:50 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:03:50 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:03:50 InnoDB: Initializing buffer pool, size = 8.0M
141101 19:03:50 InnoDB: Completed initialization of buffer pool
141101 19:03:50 InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 19:03:50 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 19:03:50 [ERROR] Could not open log file
141101 19:03:50 [ERROR] Can't init tc log
141101 19:03:50 [ERROR] Aborting
141101 19:03:50 InnoDB: Starting shutdown...
141101 19:03:55 InnoDB: Shutdown completed; log sequence number 0 44243
141101 19:03:55 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete
141101 19:03:55 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 19:40:21 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 19:40:21 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:40:21 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:40:21 InnoDB: Initializing buffer pool, size = 8.0M
141101 19:40:21 InnoDB: Completed initialization of buffer pool
141101 19:40:21 InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 19:40:21 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 19:40:21 [ERROR] Could not open log file
141101 19:40:21 [ERROR] Can't init tc log
141101 19:40:21 [ERROR] Aborting
141101 19:40:21 InnoDB: Starting shutdown...
141101 19:40:26 InnoDB: Shutdown completed; log sequence number 0 44243
141101 19:40:26 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete
141101 19:40:26 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 19:57:20 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 19:57:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:57:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:57:20 InnoDB: Initializing buffer pool, size = 8.0M
141101 19:57:20 InnoDB: Completed initialization of buffer pool
141101 19:57:20 InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 19:57:20 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 19:57:20 [ERROR] Could not open log file
141101 19:57:20 [ERROR] Can't init tc log
141101 19:57:20 [ERROR] Aborting
141101 19:57:20 InnoDB: Starting shutdown...
141101 19:57:26 InnoDB: Shutdown completed; log sequence number 0 44243
141101 19:57:26 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete
141101 19:57:26 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
相关推荐
在使用MySQL数据库的过程中，有时会遇到“MySQL server PID file could not be found”的错误，这是一个常见的启动问题，通常意味着MySQL服务器无法找到其进程ID（PID）文件，该文件用于记录数据库服务的运行状态。...
MySQL数据库在运行过程中可能会遇到各种问题，其中一种常见的错误是"Starting MySQL.Manager of pid-file quit without updating file.[FAILED]"。这个错误通常表明MySQL服务在尝试启动时遇到了问题，导致进程管理器...
MySQL是世界上最流行的关系型数据库管理系统之一，当遇到“Starting MySQL… ERROR! The server quit without updating PID file”的启动错误时，通常意味着服务器未能成功启动并更新其进程ID（PID）文件，这可能是...
在LaTeX排版系统中，"file 'psfig.sty' not found" 是一个常见的错误信息，这通常意味着系统在编译文档时无法找到`psfig.sty`这个宏包文件。`psfig`宏包是LaTeX早期用于插入PostScript图形的工具，它允许用户在文档...
（DBX Error: Driver could not be properly initialized. Client library may be missing, not installed properly, ...）,我找到了合适的libmysql.dll和dbxmys.dll组合，把下面这个libmysql.dll拷贝到XE的bin目录...
Driver class 'org.gjt.mm.mysql.Driver' could not be found, make sure the 'MySQL' driver (jar file) is installed. org.gjt.mm.mysql.Driver】即（由于名为“org.gjt.mm.mysql.Driver”的数据库驱动类没有发现...
在Linux系统，特别是CentOS上安装MySQL数据库时，可能会遇到一些常见问题，其中之一就是"The server quit without updating PID file"。这个错误通常表明MySQL服务器在启动过程中遇到了问题，未能正确记录其进程ID...
如果出现“PID file could not be found”的错误，可能需要通过`kill`命令找到并终止MySQL进程。 5. **检查配置文件**： 检查MySQL的配置文件`my.cnf`，确保`pid-file`选项指向正确的PID文件位置。例如： ``` ...
Linux下安装初始化完MySQL数据库之后，使用... The server quit without updating PID file (/data/mysql/AY14020816093477605eZ.pid). 重启mysql会抛出上面红色字体的错误。 上面只能看到mysql启动失败，具体
然而，当遇到"MYSQL: The server quit without updating PID file"这样的错误时，通常意味着MySQL服务在启动过程中遇到了问题，无法正确地创建或更新其进程ID（PID）文件。PID文件用于记录MySQL服务的进程ID，以便...
GEE错误：Error: Projection: The CRS of a map projection could not be parsed. (Error code: 3) 我正在尝试在 Albers 等积投影 ( https://code.earthengine.google.com/ccab6721def78c24dc2a0e079866a6fe ) 中...
在安装MySQL过程中，有时会遇到一个常见的错误提示：“Could not start the service MySQL Error 0”。这个错误意味着MySQL服务无法启动，通常与系统环境、配置文件、依赖库或安装过程中的某些问题有关。以下将详细...
具体报错如下： Cannot complete the install because one or more required items could not be found. Software being installed: Activiti Eclipse BPMN 2.0 Designer 5.18.0.201508100929 (org.activiti....
3、Can’t connect to local MySQL server through socket ‘/Data/mydata/mysql.sock’ socket文件目录不对应导致的问题 4、今天要说的就是 没有打开only_full_group_by Cause:...
可以尝试停止MySQL，删除或移动`.ib_logfile`和`ibdata1`文件，然后重启MySQL以恢复默认设置。但请注意，这可能导致数据丢失，因此在进行此操作前应备份数据。 6. **检查配置文件**： 检查MySQL的配置文件（通常为...
Cause com.mysql.jdbc.exceptions.jdbc4.CommunicationsException The last packet successfully received from the server was 47,795,922 milliseconds ago. The last packet sent successfully to the server was...
System.out.println("Driver not found."); e.printStackTrace(); } catch (SQLException e) { System.out.println("Error connecting to the database."); e.printStackTrace(); } } } ``` 在上述代码中，`...