Bug #85448 | MYSQLD.exe keeps crashing | ||
---|---|---|---|
Submitted: | 14 Mar 2017 14:00 | Modified: | 18 Nov 2017 21:40 |
Reporter: | Dustin Sawejka | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: General | Severity: | S2 (Serious) |
Version: | OS: | Windows (Server 2008) | |
Assigned to: | CPU Architecture: | Any |
[14 Mar 2017 14:00]
Dustin Sawejka
[14 Mar 2017 17:18]
MySQL Verification Team
Please provide the exactly server version and attach the err log file generally in the data directory (use the Files tab for). Also check and provide description what were (was) the action done when the crash happens. Thanks.
[14 Mar 2017 17:24]
Dustin Sawejka
Microsoft Windows Server 2008 R2 Version 6.1 (Build 7601: Service Pack 1)
[14 Mar 2017 17:27]
Dustin Sawejka
I know this won't help to much but there was no major incident just over night the service will not stay started. I will start the service and after 30 seconds it will stop on its own.
[14 Mar 2017 17:33]
MySQL Verification Team
Thank you for the feedback, however you have not provided what I asked: the MySQL Server version 5.6.XX, 5.7.XX, etc and the error log file. THanks.
[14 Mar 2017 17:36]
Dustin Sawejka
I cant load file it states that it is to large.
[14 Mar 2017 17:37]
Dustin Sawejka
MySql Server 5.7.17
[15 Mar 2017 0:32]
MySQL Verification Team
Compress the file with a zip tool and if still is not suitable to attach then rename the current err log file so in the next server start is created a new one and if the crash happens compress the new log err file and attach it. Thanks.
[15 Mar 2017 14:20]
Dustin Sawejka
What type of file is the Error log?
[15 Mar 2017 14:32]
MySQL Verification Team
It's a file located generally in the datadir folder formed by host_machine_name.err i.e: a machine which it's name is Tikal the file is: c:\ProgramData\MySQL>dir "MySQL Server 5.7\Data"\*.err Volume in drive C has no label. Volume Serial Number is 484B-43B0 Directory of c:\ProgramData\MySQL\MySQL Server 5.7\Data 03/15/2017 07:09 AM 406,561 TIKAL.err 1 File(s) 406,561 bytes 0 Dir(s) 993,643,397,120 bytes free
[15 Mar 2017 14:33]
Dustin Sawejka
Shoretel.err
Attachment: SHORETEL.err (application/octet-stream, text), 8.21 KiB.
[15 Mar 2017 14:34]
Dustin Sawejka
Shoretel.pid
Attachment: ShoreTel.pid (application/octet-stream, text), 5 bytes.
[15 Mar 2017 14:39]
Dustin Sawejka
Shoretel.2.err
Attachment: SHORETEL.err (application/octet-stream, text), 126.80 KiB.
[15 Mar 2017 14:39]
MySQL Verification Team
Thank you for the feedback. When will happens the crash again then attach it again the file SHORETEL.err which now could show information about the crash.
[15 Mar 2017 14:45]
MySQL Verification Team
See you read the second err file you can see a recommendation to read: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html please try it. Thanks.
[15 Mar 2017 15:12]
Dustin Sawejka
170315 10:08:59 InnoDB: Error: table 'temp/#sql938_6_8' InnoDB: in InnoDB data dictionary has tablespace id 13950, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html InnoDB: for how to resolve the issue. 170315 10:08:59 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 170315 10:09:00 InnoDB: Started; log sequence number 7 2348344942 170315 10:09:00 [Note] Event Scheduler: Loaded 0 events 170315 10:09:00 [Note] C:\PROGRA~2\SHOREL~1\SHOREW~1\MYSQLM~1\MYSQLS~1\Bin\mysqld.exe: ready for connections. Version: '5.1.46sp1-enterprise-commercial-pro' socket: '' port: 4310 MySQL Enterprise Server - Pro Edition (Commercial) 170315 10:09:06 - mysqld got exception 0xc00000fd ; 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=57671680 read_buffer_size=524288 max_used_connections=5 max_threads=100 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 159352 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
[15 Mar 2017 15:15]
Dustin Sawejka
thd: 0x497e6c08 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... 0040FD17 mysqld.exe!_chkstk()[chkstk.asm:99] 497F9500 778C33D7 RtlQueryPerformanceCounter() 75DA3ECC ReadFile() 0066A6B3 _read_nolock()[read.c:233] FFFFFFFE FFFFFFFE Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 497F0588=CREATE TEMPORARY TABLE trunkgroupaggr5min_tmp_insert ENGINE=INNODB COLLATE = utf8_unicode_ci SELECT `SampleTime`, `TrunkGroupID`, `TotalCallCount`, `TotalWarnCallCount`,`TotalFailCallCount`,`TotalInboundCallCount`,`TotalOutboundCallCount`,`TotalStreamCount`,`TotalInboundStreamCount`,`TotalOutboundStreamCount`,`AvgCallDuration`,`ShortCallDuration`,`LongCallDuration`,`AvgActiveCallCount`,`MaxActiveCallCount`,`AvgActiveStreamCount`,`MaxActiveStreamCount`,`AvgTrunkOccupancyPercentage`,`MaxTrunkOccupancyPercentage`,`AvgActiveInboundStreamCount`,`MaxActiveInboundStreamCount`,`AvgActiveOutboundStreamCount`,`MaxActiveOutboundStreamCount`, `AvgActiveInterSiteCallCount`,`MaxActiveInterSiteCallCount`,`TotalInterSiteCallCount`,`TotalInterSiteStreamCount` FROM trunkgroupaggr5min WHERE 1 = 0 thd->thread_id=5 thd->killed=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.
[22 Mar 2017 15:05]
MySQL Verification Team
Are you tried to apply the trouble instructions in the documentation link I wrote here?. THanks.
[22 Mar 2017 15:09]
Dustin Sawejka
Yes I tired and it did nothing.
[18 Oct 2017 21:40]
MySQL Verification Team
It was not clear for me if you did the recommendation I asked you in my last comment.
[19 Nov 2017 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".