Hi,
I am trying to cleanup the old records in the mysql DB which is present
from Oct 2015.
I used below settings in the slurmdbd.conf file, but didn't get cleaned up
any records last night. May be due to huge no:of records its not able to
purge?
How can we handle this situation? We want to keep
Hello,
Slurm Upgrade got failed while migrating mysqlDB due to space issue. Now we
increased the space and May I know how to kick start the migration process
back again?
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 8
Hello,
I see all the slurm logs file gets created with restricted file permission.
Is it any wat to change ti by default to allow groups to read the file?
-rw--- 1 sassrv sas 372 Sep 27 14:36 slurmdbd.27Sep2016.log
-rw--- 1 sassrv sas 281841 Sep 27 14:36 slurmctld.27Sep2016.log
e=EM Nodes=okdev1447 DefMemPerCPU=512 MaxTime=INFINITE
State=UP shared=force:4
PartitionName=admin Nodes=okdev1368,okdev1447,okdev1367,okdev1324,okdev1314
DefMemPerCPU=512 MaxTime=INFINITE State=UP shared=force:5
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technol
Socket(s): 4
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
: REQUEST_KILL_JOB job 81205
uid 11510
Any idea what is missing?
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
On Sat, Aug 20, 2016 at 12:10 AM, Barbara Krasovec <barb
Thanks. What are the components have to upgrade in the slurm control nodes?
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
On Thu, Aug 18, 2016 at 2:45 PM, Barbara Kraso
Sorry. Its for compute nodes.. (Not on Control nodes)
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
On Fri, Aug 19, 2016 at 2:52 PM, Balaji Deivam <balaji.dei...@seaga
@cloudlg017223 x86_64]#
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
On Thu, Aug 18, 2016 at 4:57 AM, Barbara Krasovec <barba...@arnes.si> wrote:
> Helllo!
>
>
&g
Hi,
> Can someone give me the detailed step on "Upgrade the slurmdbd daemon" ?
I have downloaded the Slrum source tar file and looking for how to upgrade
only the slurmdbd from that tar file.
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Tech
& Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
Hi,
After changing the perm to 644 -> /etc/hosts, it got resolved.
So now its work fine.
Thanks & Regards,
Balaji Deivam
Staff Analyst - Business Data Center
Seagate Technology - 389 Disc Drive, Longmont, CO 80503 | 720-684-
<720-684-2363>*3395*
On Wed, May 4, 2016 at 3
Hello,
I am facing issue with accessing slurmdbd host, which states DB host not
found. Could you please help me to fix this issue?
[sassrv@cloudlg016127 bin]$ *./sacctmgr create cluster name=cloudlg016127*
sacctmgr: error: Unable to resolve "localhost": Unknown host
sacctmgr: error: Unable to
13 matches
Mail list logo