Bug #49233 | Services failes to start on Windows Server 2008R2 (64bit) | ||
---|---|---|---|
Submitted: | 30 Nov 2009 20:22 | Modified: | 12 Jan 2010 9:37 |
Reporter: | Donald Campbell | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
Version: | 5.1.41 | OS: | Windows (Server 2008R2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 2008R2, 64bit, service |
[30 Nov 2009 20:22]
Donald Campbell
[1 Dec 2009 7:16]
Sveta Smirnova
Thank you for the report. Please send us your configuration file and output of `dir PATH/TO/datadir`: I want to check sizes of ib* files.
[1 Dec 2009 8:09]
Donald Campbell
Copy of the my.ini file
Attachment: my-prod.ini (application/octet-stream, text), 8.95 KiB.
[1 Dec 2009 8:10]
Donald Campbell
File sizes as requested: J:\CADSDatafiles>dir Volume in drive J is DataDisk1 Volume Serial Number is D4A4-0DEB Directory of J:\CADSDatafiles 01/12/2009 08:05 <DIR> . 01/12/2009 08:05 <DIR> .. 29/11/2009 22:55 <DIR> college 30/11/2009 23:30 153,092,096 ibdata1 30/11/2009 23:30 104,857,600 ib_logfile0 12/11/2009 22:26 104,857,600 ib_logfile1 20/04/2009 19:05 9,163 my-prod.ini 29/11/2009 22:55 <DIR> mysql 29/11/2009 22:57 816 win2003-02.err 29/11/2009 22:57 4 win2003-02.pid 6 File(s) 362,817,279 bytes 4 Dir(s) 158,289,534,976 bytes free
[1 Dec 2009 8:47]
Bogdan Degtyariov
Hi Donald, Did you copy InnoDB files and mysql directory created by another version of MySQL server? If yes, can you please specify the version? This bug should be qualified as InnoDB problem instead of "Installing". The new MySQL server installation worked normally before copying data files. Thanks.
[1 Dec 2009 9:38]
Donald Campbell
Hi The original was from the production system with 5.1.34. (32 bit windows server 2003R2). It copies and works fine on our 32bit windows server 2003R2 with 5.1.39. When I first tried with 5.1.41 and failed, I did unistall and then installed 5.1.39 which gave me the same problem. I have also tried on W7 ultimate 64bit and I get the same issue.
[1 Dec 2009 11:08]
MySQL Verification Team
I have a doubt: you wrote: "it. However, when I try and startup (5.1.41) on the 2008R2 server it "aborts". however the log shows: Version: '5.1.39-community' socket: '' port: 3306 MySQL Community Server (GPL) 091129 22:57:11 [Note] Event Scheduler: scheduler thread started with id 1 Then my doubt: it is actually the binary of server 5.1.41 or it was replaced by copy/paste for the older 5.1.39?. When that error is displayed what is the output from a command prompt of mysqld --version? Thanks in advance.
[1 Dec 2009 11:36]
Donald Campbell
Hi The two logs on the initial report were from different machines The 5.1.39 is from our windows 2003R2 (32bit) machine and works fine. The 5.1.41 is from the new windows 2008R2 (64bit) machine and fails. The only items that were copied from the originaing machine was a ZIP of the data files and a copy of the my.ini file. The binaries came from a install. The "solution" I found was on the failing 2008R2 machine I copied the MySQL folder from "program files (x86)" to "program files" (i.e. I had the installation files in both places).
[12 Jan 2010 9:37]
Tonci Grgin
Hello Donald. After reading your report for several times, I still don't know what and why you did. All I see is that you did not follow the proper procedure of moving data with DUMP/RESTORE. If you can repeat the problem while following the proper procedure and installing proper MySQL server in proper "Program Files" please reopen the report. As I do not see any bug here, I'm closing the report now. My environment: Win2008SE x64 with 8GB RAM, using administrator account.