[debian-mysql] Serious mess while upgrading mysql server

[Bjoern Boschman]

Hi Didier,

please always reply to pkg-mailinglist as well.

regarding 1)

I'm still missing a bug report. what was done, what happened, what
said the error-log, etc.

regarding 2 I think we agree that a special "mysql-server will be
restarted during upgrade" is not mandatory

Cheers
B

2014-11-07 12:02 GMT+01:00 Didier Kryn <kryn at in2p3.fr>:
> Le 04/11/2014 17:26, Bjoern Boschman a écrit :
>>
>> Hi Didier,
>>
>> regarding 1)
>> I would like to know what is not compatible?
>> I doubt that there was a change in terms of configuration?
>> could you be so kind and provide more info from your mysql admin?
>> mysql-5.1->mysql-5.5 upgrade is handled similar like java-6->java-7
>> (but they cannot be isntalled side-by-side)
>
>
>     My mysql admin was probably exagerating a little bit: the
> incompatibility was actually "dynamic": the slave database, running version
> 5.5.38 was unhappy to see that the master was running 5.5.40, because, just
> by chance, it happened that I upgraded the master first.
>>
>>
>> regarding 2)
>> Each upgrade (even minor upgrades) require server restart, as new
>> binaries have to be loaded.
>> This is the case for afaik every server software that's not running
>> via tcp-warpper (e.g. apache, nginx, etc.)
>> It is well know that this software will be restarted during upgrade
>> (since ever?)
>> I guess we will not extra note the user.
>
>
>     Yes, I agree, for sure the server must be restarted, but, while
> restarting ssh or nfs servers has no effect, restarting mysql has a big
> effect in systems using the service across severall hosts. I remember that,
> years ago, when upgrading a server, the operator was asked something like
> "OK to restart nfs-kernel-server" or the like.
>
>     I acknowledge that I was not carefull enough during this general upgrade
> - I'm becomming so confident in Debian :-) - but I think I would have made a
> "denkpause" before going on, would have I gotten this warning.
>
>     Nevertheless, let me take this opportunity to thank you warmfully, you
> and all Debian, for providing for free such a wonderfull system.
>
>     Didier Kryn
>>
>>
>> Cheers
>> Bjoern
>>
>> 2014-11-04 16:16 GMT+01:00 Didier Kryn <kryn at in2p3.fr>:
>>>
>>>      Dear mysql Debian maintainers,
>>>
>>>      As the administrator of a few Dell PowerEdge servers running Debian
>>> Wheezy, I made a general upgrade of two machines today. This triggered an
>>> upgrade of our mysql servers which had several consequences:
>>>
>>>      1) the new version (5.5.40) is not fully compatible with version
>>> 5.5.38
>>> . The mysql administrator complained that his service would not work
>>> without
>>> changing configuration files.
>>>      2) the simple fact of restarting a server while it is involved in
>>> databases replications also causes serious harm according to him.
>>>
>>>      Would you be kind enough to consider the following suggestions:
>>>
>>>      1) when a new version is not fully compatible with the previous one,
>>> maybe the two versions might be in the repository, but the new one not
>>> considered an upgrade of the old one, so that routine upgrades do not
>>> touch
>>> it but the administrator must explicitely install one and remove the
>>> other
>>> (like for java-6 vs java-7).
>>>
>>>      2) Even for simple upgrades (the ones which do not touch the user
>>> interface), when about to stop the mysql server, display a warning about
>>> the
>>> possible consequences and ask if the administrator really wants to
>>> continue.
>>>
>>>      Thank you for your attention.
>>>
>>>      Didier Kryn
>>>      Laboratoire APC
>>>      Universite Paris-Diderot
>>>
>>>
>>> _______________________________________________
>>> pkg-mysql-maint mailing list
>>> pkg-mysql-maint at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
>>
>>
>>
>
>



-- 
Mit freundlich Grüßen / Kind regards

Björn Boschman