[Maria-discuss] Serious problem with latest (10.0.16) Windows installer - destroys services.
I have MariaDB 5.5, 10.0 and 10.1 installed (as Windows services named 'maria55'. 'maria10' and 'maria10_1' ) and always update them to latest soon after an update is available. Yesterday morning I installed 10.0.16 on top of 10.0.15 using the .msi installer. When I tried to connect to it a few hours later it was not possible. I thought the service might not be running. It wasn't. Actually it did not exist anymore at all! "net start maria10" returned "service does not exist" (and indeed it did not appear in Windows "services management" interface). I copied the /datadir, uninstalle , did a fresh install of 10.0.16d (choosing the option not to upgrade any existing server) and copied the old /datadir back. Now Maria 10.0(.16) works again. But now I see that the 'maria55' service is also gone from the system. Files are intact. I can repeat the exercise I did with 10.0 of course or install service again from commandline. Not a big problem, but very annoying and waste of time. MariaDB 10.1 installaton is not affected. 5 diiferent Oracle/MySQL servers (from 5.0 to 5.7) also are not. I need all those instances for application testing. Questions: * Has somebody else experienced this? * Has somebody replaced @wlad as maintainer of Windows installers? @wlad was the only person who ever was able to write reasonable MySQL/MariaDB installers. So I would regret that. It is perfectly legal on Windows to have multiple MariaDB servers simultaneously running as Windows services. They won't conflict as long as service name, port, basedir and datadir are all different. What happens with one should not affect another. I the installer does not respect this, it is a bug. -- Peter -- Webyog
Hi Peter, On Sat, Jan 31, 2015 at 11:33 AM, Peter Laursen <peter_laursen@webyog.com> wrote:
I have MariaDB 5.5, 10.0 and 10.1 installed (as Windows services named 'maria55'. 'maria10' and 'maria10_1' ) and always update them to latest soon after an update is available. Yesterday morning I installed 10.0.16 on top of 10.0.15 using the .msi installer. When I tried to connect to it a few hours later it was not possible. I thought the service might not be running. It wasn't. Actually it did not exist anymore at all! "net start maria10" returned "service does not exist" (and indeed it did not appear in Windows "services management" interface). I copied the /datadir, uninstalle , did a fresh install of 10.0.16d (choosing the option not to upgrade any existing server) and copied the old /datadir back. Now Maria 10.0(.16) works again.
We were aware that an older version of the 10.0.16 MSI installer for Windows inadvertently removed the maria service. I believe the MSI installer that is now available for download does not have this problem. For anyone else who is experiencing this issue, Elena has posted a fix in the comments of the JIRA issue: https://mariadb.atlassian.net/browse/MDEV-7531
But now I see that the 'maria55' service is also gone from the system. Files are intact. I can repeat the exercise I did with 10.0 of course or install service again from commandline. Not a big problem, but very annoying and waste of time.
Thanks for pointing this out. I'm not sure if anyone was aware that the installer also removed services of other versions of MariaDB. Maybe a variant of Elena's fix will get these other services back for you? e.g. (make sure the paths match yours): "C:\Program Files\MariaDB 5.5\bin\mysqld.exe" --install maria55 "--defaults-file=C:\Program Files\MariaDB 5.5\data\my.ini" "C:\Program Files\MariaDB 10.1\bin\mysqld.exe" --install maria10_1 "--defaults-file=C:\Program Files\MariaDB 10.1\data\my.ini" Thanks, Geoff
Hi, Peter! On Jan 31, Peter Laursen wrote:
I have MariaDB 5.5, 10.0 and 10.1 installed (as Windows services named 'maria55'. 'maria10' and 'maria10_1' ) and always update them to latest soon after an update is available. Yesterday morning I installed 10.0.16 on top of 10.0.15 using the .msi installer. When I tried to connect to it a few hours later it was not possible. ... Questions: * Has somebody else experienced this?
Yes, https://mariadb.atlassian.net/browse/MDEV-7531 I've already fixed it and we've replaced msi packages with fixed ones. Of course, it was already too late for you, I know :( At least, I hope, it'll help those users who are not as fast as you are.
* Has somebody replaced @wlad as maintainer of Windows installers? @wlad was the only person who ever was able to write reasonable MySQL/MariaDB installers. So I would regret that.
At the moment we don't have a dedicated Windows developer, unfortunately. Regards, Sergei
Ok ..so it seems I am not a complete idiot this time! :-) Please be careful that next 10.1 release does not have same problem. Because as I understand the problem it will probably remove all mariadb services if it has. -- Peter On Sat, Jan 31, 2015 at 6:18 PM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Peter!
On Jan 31, Peter Laursen wrote:
I have MariaDB 5.5, 10.0 and 10.1 installed (as Windows services named 'maria55'. 'maria10' and 'maria10_1' ) and always update them to latest soon after an update is available. Yesterday morning I installed 10.0.16 on top of 10.0.15 using the .msi installer. When I tried to connect to it a few hours later it was not possible. ... Questions: * Has somebody else experienced this?
Yes, https://mariadb.atlassian.net/browse/MDEV-7531
I've already fixed it and we've replaced msi packages with fixed ones. Of course, it was already too late for you, I know :(
At least, I hope, it'll help those users who are not as fast as you are.
* Has somebody replaced @wlad as maintainer of Windows installers? @wlad was the only person who ever was able to write reasonable MySQL/MariaDB installers. So I would regret that.
At the moment we don't have a dedicated Windows developer, unfortunately.
Regards, Sergei
I think because the .msi installer use one name in windows add/remove program. I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service Dikirim dari Yahoo Mail pada Android
Hi, Destroying services is a problem of 10.0.16 MSI packages released earlier, see https://mariadb.atlassian.net/browse/MDEV-7531 for more details. The packages have now been fixed and re-uploaded; unfortunately they won't help you if you have already gotten your services removed. I couldn't quite understand from your text whether you have re-created the services already; if not, please see the last comment to the JIRA issue above about how it can be done. If you have 5 server instances on one machine, you might have to re-create all 5 services. If you experience a problem while re-creating services or know a better way to do it than described in the comment, please let us know. I apologize for the inconvenience that this bug caused. Regards, Elena Stepanova On 01.02.2015 4:00, Irwanto wrote:
I think because the .msi installer use one name in windows add/remove program.
I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service
Dikirim dari Yahoo Mail pada Android
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
I have already re-created the removed/destroyed MariaDB 5.5 and 10.0 services (one by re-installing and one by (re-)creating the servcie from commandline ("mysqld --install .."). I think I am quite an experienced (Windows) user and can handle it. As I wrote: it is not a big problem (add: if you understand what happened). It just took a little time to figure out that MariaDB 10.0.16 Windows installer was the culprit. But it could be a 'showstopper' for novice users, that upgrading MariaDB removes the existing service(s). Anyway. I think you replaced the installers in a timely manner, and few people will be affected, probably. We will help those affected, if any. -- Peter On Sun, Feb 1, 2015 at 3:43 PM, Elena Stepanova <elenst@montyprogram.com> wrote:
Hi,
Destroying services is a problem of 10.0.16 MSI packages released earlier, see https://mariadb.atlassian.net/browse/MDEV-7531 for more details.
The packages have now been fixed and re-uploaded; unfortunately they won't help you if you have already gotten your services removed. I couldn't quite understand from your text whether you have re-created the services already; if not, please see the last comment to the JIRA issue above about how it can be done. If you have 5 server instances on one machine, you might have to re-create all 5 services. If you experience a problem while re-creating services or know a better way to do it than described in the comment, please let us know.
I apologize for the inconvenience that this bug caused.
Regards, Elena Stepanova
On 01.02.2015 4:00, Irwanto wrote:
I think because the .msi installer use one name in windows add/remove program.
I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service
Dikirim dari Yahoo Mail pada Android
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Hi Peter, On 01.02.2015 19:27, Peter Laursen wrote:
I have already re-created the removed/destroyed MariaDB 5.5 and 10.0 services (one by re-installing and one by (re-)creating the servcie from commandline ("mysqld --install .."). I think I am quite an experienced (Windows) user and can handle it. As I wrote: it is not a big problem (add: if you understand what happened). It just took a little time to figure out that MariaDB 10.0.16 Windows installer was the culprit.
Of course, I didn't mean you, I was replying to email from 'Irwanto'. It came to my box with a bit weird subject format, so I didn't realize it was a reply to yours, and thought it was a new independent report of the same problem until I already sent my answer. Anyway, my personal apologies to everyone affected by the issue. I will try to add MSI upgrade tests in buildbot, we don't have them now. Regards, Elena
But it could be a 'showstopper' for novice users, that upgrading MariaDB removes the existing service(s). Anyway. I think you replaced the installers in a timely manner, and few people will be affected, probably. We will help those affected, if any.
-- Peter
On Sun, Feb 1, 2015 at 3:43 PM, Elena Stepanova <elenst@montyprogram.com> wrote:
Hi,
Destroying services is a problem of 10.0.16 MSI packages released earlier, see https://mariadb.atlassian.net/browse/MDEV-7531 for more details.
The packages have now been fixed and re-uploaded; unfortunately they won't help you if you have already gotten your services removed. I couldn't quite understand from your text whether you have re-created the services already; if not, please see the last comment to the JIRA issue above about how it can be done. If you have 5 server instances on one machine, you might have to re-create all 5 services. If you experience a problem while re-creating services or know a better way to do it than described in the comment, please let us know.
I apologize for the inconvenience that this bug caused.
Regards, Elena Stepanova
On 01.02.2015 4:00, Irwanto wrote:
I think because the .msi installer use one name in windows add/remove program.
I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service
Dikirim dari Yahoo Mail pada Android
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Problem seems to persist in 10.0.17. Service is not created. :-( -- Peter On Sun, Feb 1, 2015 at 5:50 PM, Elena Stepanova <elenst@montyprogram.com> wrote:
Hi Peter,
On 01.02.2015 19:27, Peter Laursen wrote:
I have already re-created the removed/destroyed MariaDB 5.5 and 10.0 services (one by re-installing and one by (re-)creating the servcie from commandline ("mysqld --install .."). I think I am quite an experienced (Windows) user and can handle it. As I wrote: it is not a big problem (add: if you understand what happened). It just took a little time to figure out that MariaDB 10.0.16 Windows installer was the culprit.
Of course, I didn't mean you, I was replying to email from 'Irwanto'. It came to my box with a bit weird subject format, so I didn't realize it was a reply to yours, and thought it was a new independent report of the same problem until I already sent my answer.
Anyway, my personal apologies to everyone affected by the issue. I will try to add MSI upgrade tests in buildbot, we don't have them now.
Regards, Elena
But it could be a 'showstopper' for novice users, that upgrading MariaDB removes the existing service(s). Anyway. I think you replaced the installers in a timely manner, and few people will be affected, probably. We will help those affected, if any.
-- Peter
On Sun, Feb 1, 2015 at 3:43 PM, Elena Stepanova <elenst@montyprogram.com> wrote:
Hi,
Destroying services is a problem of 10.0.16 MSI packages released earlier, see https://mariadb.atlassian.net/browse/MDEV-7531 for more details.
The packages have now been fixed and re-uploaded; unfortunately they won't help you if you have already gotten your services removed. I couldn't quite understand from your text whether you have re-created the services already; if not, please see the last comment to the JIRA issue above about how it can be done. If you have 5 server instances on one machine, you might have to re-create all 5 services. If you experience a problem while re-creating services or know a better way to do it than described in the comment, please let us know.
I apologize for the inconvenience that this bug caused.
Regards, Elena Stepanova
On 01.02.2015 4:00, Irwanto wrote:
I think because the .msi installer use one name in windows add/remove
program.
I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service
Dikirim dari Yahoo Mail pada Android
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
The 10.0.17 announcement just arrived to my mailbox. Did you fix the problem with service being destroyed in the build I downloaded 2 days ago? -- Peter On Sat, Feb 28, 2015 at 11:31 AM, Peter Laursen <peter_laursen@webyog.com> wrote:
Problem seems to persist in 10.0.17. Service is not created. :-(
-- Peter
On Sun, Feb 1, 2015 at 5:50 PM, Elena Stepanova <elenst@montyprogram.com> wrote:
Hi Peter,
On 01.02.2015 19:27, Peter Laursen wrote:
I have already re-created the removed/destroyed MariaDB 5.5 and 10.0 services (one by re-installing and one by (re-)creating the servcie from commandline ("mysqld --install .."). I think I am quite an experienced (Windows) user and can handle it. As I wrote: it is not a big problem (add: if you understand what happened). It just took a little time to figure out that MariaDB 10.0.16 Windows installer was the culprit.
Of course, I didn't mean you, I was replying to email from 'Irwanto'. It came to my box with a bit weird subject format, so I didn't realize it was a reply to yours, and thought it was a new independent report of the same problem until I already sent my answer.
Anyway, my personal apologies to everyone affected by the issue. I will try to add MSI upgrade tests in buildbot, we don't have them now.
Regards, Elena
But it could be a 'showstopper' for novice users, that upgrading MariaDB removes the existing service(s). Anyway. I think you replaced the installers in a timely manner, and few people will be affected, probably. We will help those affected, if any.
-- Peter
On Sun, Feb 1, 2015 at 3:43 PM, Elena Stepanova <elenst@montyprogram.com
wrote:
Hi,
Destroying services is a problem of 10.0.16 MSI packages released earlier, see https://mariadb.atlassian.net/browse/MDEV-7531 for more details.
The packages have now been fixed and re-uploaded; unfortunately they won't help you if you have already gotten your services removed. I couldn't quite understand from your text whether you have re-created the services already; if not, please see the last comment to the JIRA issue above about how it can be done. If you have 5 server instances on one machine, you might have to re-create all 5 services. If you experience a problem while re-creating services or know a better way to do it than described in the comment, please let us know.
I apologize for the inconvenience that this bug caused.
Regards, Elena Stepanova
On 01.02.2015 4:00, Irwanto wrote:
I think because the .msi installer use one name in windows add/remove
program.
I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service
Dikirim dari Yahoo Mail pada Android
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
At least 10.1.3 does not suffer from this defect. :-) -- Peter On Mon, Mar 2, 2015 at 4:31 PM, Peter Laursen <peter_laursen@webyog.com> wrote:
The 10.0.17 announcement just arrived to my mailbox. Did you fix the problem with service being destroyed in the build I downloaded 2 days ago?
-- Peter
On Sat, Feb 28, 2015 at 11:31 AM, Peter Laursen <peter_laursen@webyog.com> wrote:
Problem seems to persist in 10.0.17. Service is not created. :-(
-- Peter
On Sun, Feb 1, 2015 at 5:50 PM, Elena Stepanova <elenst@montyprogram.com> wrote:
Hi Peter,
On 01.02.2015 19:27, Peter Laursen wrote:
I have already re-created the removed/destroyed MariaDB 5.5 and 10.0 services (one by re-installing and one by (re-)creating the servcie from commandline ("mysqld --install .."). I think I am quite an experienced (Windows) user and can handle it. As I wrote: it is not a big problem (add: if you understand what happened). It just took a little time to figure out that MariaDB 10.0.16 Windows installer was the culprit.
Of course, I didn't mean you, I was replying to email from 'Irwanto'. It came to my box with a bit weird subject format, so I didn't realize it was a reply to yours, and thought it was a new independent report of the same problem until I already sent my answer.
Anyway, my personal apologies to everyone affected by the issue. I will try to add MSI upgrade tests in buildbot, we don't have them now.
Regards, Elena
But it could be a 'showstopper' for novice users, that upgrading MariaDB removes the existing service(s). Anyway. I think you replaced the installers in a timely manner, and few people will be affected, probably. We will help those affected, if any.
-- Peter
On Sun, Feb 1, 2015 at 3:43 PM, Elena Stepanova < elenst@montyprogram.com> wrote:
Hi,
Destroying services is a problem of 10.0.16 MSI packages released earlier, see https://mariadb.atlassian.net/browse/MDEV-7531 for more details.
The packages have now been fixed and re-uploaded; unfortunately they won't help you if you have already gotten your services removed. I couldn't quite understand from your text whether you have re-created the services already; if not, please see the last comment to the JIRA issue above about how it can be done. If you have 5 server instances on one machine, you might have to re-create all 5 services. If you experience a problem while re-creating services or know a better way to do it than described in the comment, please let us know.
I apologize for the inconvenience that this bug caused.
Regards, Elena Stepanova
On 01.02.2015 4:00, Irwanto wrote:
I think because the .msi installer use one name in windows add/remove
program.
I use 5 instance service in one computer with different port and i use .msi but with manual extractor using universal extractor and run my manual script to create first data dir and install service
Dikirim dari Yahoo Mail pada Android
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
participants (5)
-
Elena Stepanova -
Geoff Montee -
Irwanto -
Peter Laursen -
Sergei Golubchik