Bug #67041 | 'mysql' folder in datadir becomes empty after upgrade. | ||
---|---|---|---|
Submitted: | 1 Oct 2012 22:00 | Modified: | 2 Apr 2013 7:36 |
Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
Version: | 5.5.28 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[1 Oct 2012 22:00]
Peter Laursen
[1 Oct 2012 23:49]
MySQL Verification Team
Thank you for the bug report. I need help to try to repeat this bug report, my problem is that I don't had 5.5.23 installed then I download the package and installed it then I did the upgrade with the package 5.2.28 without problems. So I guess some particular condition of the 5.2.23 installation I didn't have on my environment so I can have success to find the bug. Du you have some clue about?. Thanks in advance.
[2 Oct 2012 7:59]
Peter Laursen
Well .. not really a clue. You should know that I have posted bug reports like this and also a few blogs: http://www.webyog.com/blog/2012/05/10/circus-oraclimus-installatus-upgradimus/ http://www.webyog.com/blog/2012/08/19/mysql-windows-installer-mess/ Also I am not the only one reporting similar bugs even though it seems that it materializes worse on my system than it does for most people affected. I have been upgrading 5.5 and 5.6 since very early 5.5 and 5.6.0 on this system. At one occasion I used an early 'unified installer'. Exactly what triggers this I don't know. It could have started long before 5.23. I don't have more data than I can easily dump in a few minutes, so I think I will have to completely remove 5.5 and 5.6 and start a fresh of both. But this should never happen. It is not a big deal to write software that 'works when it works'. It should also 'work when it does not work' (ie. exit gracefully without damage to the system if something is wrong)
[2 Oct 2012 9:18]
Peter Laursen
correction .. I used mysql-5.5.28-winx64.msi (and I had 5.5.23 64 bit installed in advance)
[2 Oct 2012 11:18]
Peter Laursen
I have uninstalled 5.5 and 5.6 and deleted *each and everything* from them + did a fresh install of 5.5.28 and 5.6.7 (using mysql-5.5.28-winx64.msi and mysql-5.6.7-rc-winx64.msi 'standalone installers'). Now let us see if I'll face any problems in the future. If I do I will come *furiously* back! :-) @Miguel .. you may set this to 'Need Feedback' if you think so. Personally I think MySQL supporters and/or Windows team should spend more effort to understand this, but that is your decision. It may be like searching a needle in a haystack and I cannot contribute any more as I have deleted everything.
[2 Apr 2013 7:36]
MySQL Verification Team
was continued in http://bugs.mysql.com/bug.php?id=67959