Bug #51576 | Error: Cannot create Windows service for MySql. Error: 0 | ||
---|---|---|---|
Submitted: | 27 Feb 2010 15:42 | Modified: | 8 Jul 2010 7:52 |
Reporter: | Angel Rivero | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
Version: | 5.1.44 | OS: | Windows (XP SP 3) |
Assigned to: | CPU Architecture: | Any |
[27 Feb 2010 15:42]
Angel Rivero
[27 Feb 2010 16:52]
Valeriy Kravchuk
What Windows service name did you use for 5.0.x? MySQL or MySQL5 maybe? Do you use the same service name when installing 5.1.x?
[27 Feb 2010 17:10]
popigu popigu
For 5.0.x = service MySQL For 5.1.x = service MySQL5
[27 Feb 2010 17:14]
Angel Rivero
Thanks for your comment. When I use MySQL 5.0.89 the service is MySQL, If I use MySQL 5.1.44 the service is MySQL5. It's wrong?
[27 Feb 2010 18:01]
Valeriy Kravchuk
Then it looks like a duplicate of http://bugs.mysql.com/bug.php?id=42820. Please, check. Please, send also your error log for 5.1.44 (it is usually the <hostname>.err file in the data subdirectory) and your my.ini file content.
[27 Feb 2010 22:10]
Angel Rivero
Here's the result: C:\>"C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe" --console Here's the result: 100227 23:04:18 [Warning] The syntax '--default-character-set' is deprecate will be removed in a future release. Please use --character-set-server ins 100227 23:04:18 [Note] Plugin 'FEDERATED' is disabled. 100227 23:04:18 - 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 diagno the problem, but since we have already crashed, something is definitely wro and this may fail. key_buffer_size=26214400 read_buffer_size=65536 max_used_connections=0 max_threads=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58231 bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0xf2c0e0 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... 0047E2CE mysqld.exe!ha_resolve_by_name()[handler.cc:135] 004DC4E8 mysqld.exe!open_binary_frm()[table.cc:880] 004DE21B mysqld.exe!open_table_def()[table.cc:633] 00461CE8 mysqld.exe!get_table_share()[sql_base.cc:379] 00461D4B mysqld.exe!get_table_share_with_create()[sql_base.cc:458] 00463C95 mysqld.exe!open_unireg_entry()[sql_base.cc:3860] 004669A1 mysqld.exe!open_table()[sql_base.cc:2919] 004674FA mysqld.exe!open_tables()[sql_base.cc:4594] 0046790A mysqld.exe!open_and_lock_tables_derived()[sql_base.cc:5000] 0042C1C9 mysqld.exe!plugin_load()[sql_plugin.cc:1387] 7C921028 ntdll.dll!wcsncpy() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 00000000=(null) thd->thread_id=0 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.
[28 Feb 2010 9:07]
Valeriy Kravchuk
So, server crashed, while loading plugin it seems. Please, send my.ini file for 5.1.44.
[28 Feb 2010 9:31]
Angel Rivero
My.ini MySQL Server 5.1
Attachment: my.ini (application/octet-stream, text), 8.74 KiB.
[6 Mar 2010 15:56]
Angel Rivero
Can you help me?
[6 Mar 2010 20:43]
Valeriy Kravchuk
Please, send the results of: dir "C:\Documents and Settings\All Users\Dati applicazioni\MySQL\MySQL Server 5.1\Data"
[6 Mar 2010 22:20]
popigu popigu
Microsoft Windows XP [Versione 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>dir "C:\Documents and Settings\All Users\Dati applicazioni\MySQL\MySQL Serve r 5.1\Data" Il volume nell'unità C non ha etichetta. Numero di serie del volume: C483-74AC Directory di C:\Documents and Settings\All Users\Dati applicazioni\MySQL\MySQL Server 5.1\Data 28/02/2010 21.16 <DIR> . 28/02/2010 21.16 <DIR> .. 28/02/2010 21.20 47.767 conroe94-775d2a.err 27/02/2010 13.33 10.485.760 ibdata1 27/02/2010 13.33 25.165.824 ib_logfile0 27/02/2010 12.56 25.165.824 ib_logfile1 27/02/2010 13.28 <DIR> mysql 27/02/2010 16.18 <DIR> test 4 File 60.865.175 byte 4 Directory 262.161.727.488 byte disponibili C:\>
[7 Mar 2010 10:54]
Angel Rivero
C:\>dir "C:\Documents and Settings\All Users\Dati applicazioni\MySQL\MySQL Serve r 5.1\Data" Il volume nell'unità C non ha etichetta. Numero di serie del volume: C483-74AC Directory di C:\Documents and Settings\All Users\Dati applicazioni\MySQL\MySQL Server 5.1\Data 28/02/2010 21.16 <DIR> . 28/02/2010 21.16 <DIR> .. 28/02/2010 21.20 47.767 conroe94-775d2a.err 27/02/2010 13.33 10.485.760 ibdata1 27/02/2010 13.33 25.165.824 ib_logfile0 27/02/2010 12.56 25.165.824 ib_logfile1 27/02/2010 13.28 <DIR> mysql 27/02/2010 16.18 <DIR> test 4 File 60.865.175 byte 4 Directory 262.159.847.424 byte disponibili C:\>
[13 Mar 2010 21:23]
Angel Rivero
Definitely I can use this version of MySQL-essential-5.1.44-win32.msi? Can someone help me? Thanks in advance. AR
[29 Mar 2010 20:44]
Angel Rivero
I fix the problem, this is the solution: - Remove MySQL 5.1 with Control Panel; - Delete this folder C:\Documents and Settings\All Users\Application Data\MySQL\MySQL Server 5.1 - Delete this folder C:\Program Files\MySQL Server 5.1 - Reinstalling mysql-essential-5.1.45-win32.msi That's easy !!!
[9 Apr 2010 9:26]
Torsten Rendelmann
Think, the real issue with the windows service is: the windows service point to an (old-outdated???) mysqld-nt.exe within the wrong path ("C:\MySQL...", while it is installed within "C:\Program Files\MySQL...". Also the whole setup configuration wizard hangs in that case! I've to kill it, after that the installation is incomplete, I have to cleanup all manually! Think the best way to go here to ignore the "run as windows service" completely and just run the deamon by double-click (cannot belive that, but enough for me, I'm a developer not a DB admin)
[8 Jul 2010 7:52]
Sveta Smirnova
Thank you for the feedback. As you deleted all data and stack trace looks similar to bug #41892 closing report as "Can't repeat". If you are able to repeat same crash again with latest version feel free to reopen the report.