Sorry, forgot, we use by the way, slurm 18.08.7
I just saw, in an earlier coredump, that there is another (earlier) line
involved:
2136: if (row2[ASSOC2_REQ_MTPJ][0])
the corresponding mysql response was:
+-+--+--+--+--+---+---+---++---
Hi, same here :/
the segfault happens after the procedure call in mysql:
call get_parent_limits('assoc_table', 'rwth0515', 'rcc', 0); select
@par_id, @mj, @mja, @mpt, @msj, @mwpj, @mtpj, @mtpn, @mtmpj, @mtrm,
@def_qos_id, @qos, @delta_qos;
The mysql answer is:
+-+--+--+-
On 06-05-2020 07:38, Chris Samuel wrote:
We are experiencing exactly the same problem after mysql upgrade to 5.7.30,
moving database to old mysql server running 5.6 solves the problem.
Most likely downgrading mysql to 5.7.29 will work as well
I have no clue which change in mysql-server is causing
On Tuesday, 5 May 2020 3:21:45 PM PDT Dustin Lang wrote:
> Since this happens on a fresh new database, I just don't understand how I
> can get back to a basic functional state. This is exceedingly frustrating.
I have to say that if you're seeing this with 17.11, 18.08 and 19.05 and this
only st
Hi,
I've just upgraded to slurm 19.05.5.
With either my old database, OR creating an entirely new database, I am
unable to create a new 'cluster' entry in the database -- slurmdbd is
segfaulting!
# sacctmgr add cluster test3
Adding Cluster(s)
Name = test3
Would you like to commit ch
