AxISQS
asked on
unable to start mysql55 service
When I browse to my website, I'm seeing "Database connection error (2): Could not connect to MySQL." I notice the MySQL55 service is not running, and will not start "error 1053: the service did not respond to the start or control request in a timely fashion." I dig down into the MySQL directory and bring up the .err file. it shows the following:
140812 16:08:40 [Note] Plugin 'FEDERATED' is disabled.
140812 16:08:40 InnoDB: The InnoDB memory heap is disabled
140812 16:08:40 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140812 16:08:40 InnoDB: Compressed tables use zlib 1.2.3
140812 16:08:40 InnoDB: Initializing buffer pool, size = 114.0M
140812 16:08:40 InnoDB: Completed initialization of buffer pool
140812 16:08:40 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 7527695018
140812 16:08:40 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...
140812 16:12:42 InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
This is a VMware esxi guest. MySQL has worked until just recently. What do I need to do? Thanks
140812 16:08:40 [Note] Plugin 'FEDERATED' is disabled.
140812 16:08:40 InnoDB: The InnoDB memory heap is disabled
140812 16:08:40 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140812 16:08:40 InnoDB: Compressed tables use zlib 1.2.3
140812 16:08:40 InnoDB: Initializing buffer pool, size = 114.0M
140812 16:08:40 InnoDB: Completed initialization of buffer pool
140812 16:08:40 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 7527695018
140812 16:08:40 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...
140812 16:12:42 InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
This is a VMware esxi guest. MySQL has worked until just recently. What do I need to do? Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you run regular (scheduled) snapshots (or backups) of the guest?
ASKER
negative. its backed up using symantec system restore. I think thats due to esxi being the free version.
ASKER
I've resolved my problem. all indication is that MySQL 1117 error points to hardware failure. basically, I cleared out resources on a different vm host, and used VMware converter to move my vm from the bad host to the new host.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for AxISQS's comment #a40259252
Assisted answer: 500 points for strivoli's comment #a40257874
for the following reason:
found solution myself
Accepted answer: 0 points for AxISQS's comment #a40259252
Assisted answer: 500 points for strivoli's comment #a40257874
for the following reason:
found solution myself
ASKER