[MDEV-17378] mysqld got exception 0xc0000005 Created: 2018-10-05 Updated: 2019-04-17 Resolved: 2019-04-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1.35 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Ramarao | Assignee: | Marko Mäkelä |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
windows 10, xampp |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
|
| Comments |
| Comment by Elena Stepanova [ 2018-10-05 ] | ||
|
Please provide the portion of the error log before the first occurrence of the crash (from the server startup and up to and including the first crash). | ||
| Comment by Ramarao [ 2018-10-05 ] | ||
|
MYSQL_ERROR.LOG FILE IS NOT UPLOADING IT IS TOO BIG IN SIZE | ||
| Comment by Ramarao [ 2018-10-05 ] | ||
|
2018-10-04 15:58:51 8452 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2018-10-05 15:10:28 7560 [Note] InnoDB: Using mutexes to ref count buffer pool pages 3To report this bug, see https://mariadb.com/kb/en/reporting-bugs 5We will try our best to scrape up some info that will hopefully help 5Server version: 10.1.35-MariaDB 1Thread pointer: 0x7738fc0 | ||
| Comment by Ramarao [ 2018-10-05 ] | ||
|
2018-10-05 19:55:08 13c8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2018-10-05 19:55:08 5064 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2018-10-05 19:55:21 1644 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2018-10-05 19:55:21 5700 [Note] InnoDB: Using mutexes to ref count buffer pool pages | ||
| Comment by Ramarao [ 2018-10-08 ] | ||
|
Hi Marko Mäkelä, Hope you are doing well, Any advancement in the issue?. Why the issue has caused and what is the root cause for crashing xampp mysql server?. This is the second time i got the issue and xampp crashed. How I can make no repeat this error again? | ||
| Comment by Ramarao [ 2018-10-08 ] | ||
|
The Exact error is due to Just-in-time debugging of Visual Studio. Please find the attached image. Even though I have uninstalled visual studio from my system, it has been coming again. Please solve the issue as early as possible. | ||
| Comment by Ramarao [ 2018-10-08 ] | ||
|
I have deleted all log files in xampp>mysql>data folder. Then the attached MySQL error(#1932) is coming | ||
| Comment by Ramarao [ 2018-10-08 ] | ||
|
I am unable to open any database due to that error, although the table phpmyadmin.pma__tracking exixts on phpmyadmin database. Resolve the issue, as i unable to run my projects. The info and images attached are more sufficient to resolve the issue. Thanks in Advance | ||
| Comment by Ramarao [ 2018-10-09 ] | ||
|
Hi Marko Mäkelä, any advancement in the issue. | ||
| Comment by Marko Mäkelä [ 2018-10-16 ] | ||
|
ramaraob, sorry, I did not analyze this until now. I do not see how MariaDB could cause this kind of page corruption. Quoting the log:
Some of the page dump is interleaved with the rest of the output.
The output is 16384 bytes as it should be, but it does not look at all like an InnoDB page. You could run innochecksum on all the *.ibd files in order to see what other files are corrupted. You could also try to identify the file format with the file utility, in case the corrupted files were completely overwritten, and not only in part. Also, you could check kernel error mesages and run fsck or similar, to rule out file system corruption. | ||
| Comment by Vladislav Vaintroub [ 2018-10-16 ] | ||
|
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk | ||
| Comment by Marko Mäkelä [ 2018-10-16 ] | ||
|
On Microsoft Windows, I would recommend running chkdsk. I do not know any counterpart of the Unix file utility or /etc/magic, sorry. |