[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread Timo Rothenpieler via slurm-users
On 25.06.2024 17:54, stth via slurm-users wrote: Hi Timo, Thanks, The old data wasn’t important so I did that. I changed the line as follows in the /usr/lib/systemd/system/slurmctld.service : ExecStart=/usr/sbin/slurmctld --systemd -i $SLURMCTLD_OPTIONS You should be able to immediately remo

[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread stth via slurm-users
Hi Timo, Thanks, The old data wasn’t important so I did that. I changed the line as follows in the /usr/lib/systemd/system/slurmctld.service : ExecStart=/usr/sbin/slurmctld --systemd -i $SLURMCTLD_OPTIONS Slurmctld is now active Timo Rothenpieler via slurm-users schrieb am Di. 25. Juni 2024 um

[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread Timo Rothenpieler via slurm-users
On 25/06/2024 12:20, stth via slurm-users wrote: Jun 25 10:06:39 server slurmctld[63738]: slurmctld: fatal: Can not recover last_conf_lite, incompatible version, (9472 not between 9728 and 10240), start with '-i' to ignore this. Warning: using -i will lose the data that can't be recovered. Se

[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread stth via slurm-users
Hello Lorenzo, Thank you for your reply. Yes I got the 23.11.4 version. Lorenzo Bosio schrieb am Di. 25. Juni 2024 um 16:50: > Hello, > > I suppose the actual error is: > > slurmctld: fatal: Can not recover last_conf_lite, incompatible version, > (9472 not between 9728 and 10240), start with '-

[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread Lorenzo Bosio via slurm-users
Hello, I suppose the actual error is: slurmctld: fatal: Can not recover last_conf_lite, incompatible version, (9472 not between 9728 and 10240), start with '-i' to ignore this. Warning: using -i will lose the data that can't be recovered. did you upgrade from Slurm 21.08 (9472) to your actual

[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread stth via slurm-users
Hello, slurmctld.log and journalctl -u slurmctld --no-pager give the same info as I have already provided. “ Referenced but unset environment variable evaluates to an empty string: SLURMCTLD_OPTIONS* " has to do with the files on /etc/default (slurmdbd/slurmctld/slurmd), where there is a line: SLUR

[slurm-users] Re: Slurmctld Problems

2024-06-25 Thread daijiangkuicgo--- via slurm-users
What's your “ Referenced but unset environment variable evaluates to an empty string: SLURMCTLD_OPTIONS* ”? Meanwhile, you can check slurmctld.log and journalctl -u slurmctld --no-pager. -- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le.

[slurm-users] Slurmctld Problems

2024-06-25 Thread stth via slurm-users
Dear slurm users, It is my first time setting slurm up and I am looking for a solution to this errors. Has anyone here already ecountered this problem. I would really appreciate the help. mariadb, slurmdbd and slurmd are active. *×* slurmctld.service - Slurm controller daemon Loaded: loade

[slurm-users] Re: AllowAccounts partition setting

2024-06-25 Thread daijiangkuicgo--- via slurm-users
So, have you resolved this issue from 23? I am encountering the same problem. -- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com