At the height of Oracle's hostility towards the open source community in
2014 Ubuntu CEO Mark Shuttleworth announced that Ubuntu 14.04 would keep
using MySQL, even after Debian itself (and other distros) switched to
MariaDB.
https://www.zdnet.com/article/shuttleworth-says-ubuntu-is-sticking-with-m
We have a Debian Stretch en Debian Buster cluster and both using MariaDB no
problems so far. Version 19.05.5 and we are planning to upgrade to 20.02
--
Bas van der Vlies
| Operations, Support & Development | SURFsara | Science Park 140 | 1098 XG
Amsterdam
| T +31 (0) 20 800 1300 | bas.vanderv
According to a very quick web search, migrating from MySQL to MariaDB is
(very) easy. Does anyone have any counter-experience with Slurm databases?
Thanks,
--dustin
On Thu, May 7, 2020 at 1:34 PM Christopher Samuel wrote:
> On 5/7/20 6:08 AM, Riebs, Andy wrote:
>
> > Alternatively, you could
On 5/7/20 6:08 AM, Riebs, Andy wrote:
Alternatively, you could switch to MariaDB; I've been using that for years.
Debian switched to only having MariaDB in 2017 with the release of
Debian 9 (Stretch), as a derivative distro I'm surprised that Ubuntu
still packages MySQL.
I'd second Andy's
users] Do not upgrade mysql to 5.7.30!
Definitively not up to now, just checked the sources of 20.02.2, the
same problem there.
Seems, someone with a contract needs to open a ticket.
Best
Marcus
Am 07.05.2020 um 10:50 schrieb Bill Broadley:
> On 5/6/20 11:30 AM, Dustin Lang wrot
Definitively not up to now, just checked the sources of 20.02.2, the
same problem there.
Seems, someone with a contract needs to open a ticket.
Best
Marcus
Am 07.05.2020 um 10:50 schrieb Bill Broadley:
On 5/6/20 11:30 AM, Dustin Lang wrote:
Hi,
Ubuntu has made mysql 5.7.30 the default vers
On 5/6/20 11:30 AM, Dustin Lang wrote:
Hi,
Ubuntu has made mysql 5.7.30 the default version. At least with Ubuntu 16.04,
this causes severe problems with Slurm dbd (v 17.x, 18.x, and 19.x; not sure
about 20).
I can confirm that kills slurmdbd on ubuntu 18.04 as well. I had compiled slurm
Yeah,
and I found the reason. Seems that (at least for the mysql procedure
get_parent_limits) mySQL 5.7.30 returns NULL where mySQL 5.7.29 returned
an empty string.
Running mySQL < 5.7.30 is a bad idea, as there exist two remotely
exploitable bugs with a CVSS score of 9.8!
(see also https:
Hi,
Ubuntu has made mysql 5.7.30 the default version. At least with Ubuntu
16.04, this causes severe problems with Slurm dbd (v 17.x, 18.x, and 19.x;
not sure about 20). Reverting to mysql 5.7.29 seems to make everything
work okay again.
cheers,
--dustin
