slurm平台Orphan Step导致节点状态变为down

文章描述了一种在Slurm集群管理软件中遇到的问题,计算节点状态频繁变为DOWN。问题源于OrphanStepId错误和socket通信超时,通过检查日志定位到异常slurmstep,然后杀死对应进程,最终解决了问题,一周内未再出现DOWN状态。
摘要由CSDN通过智能技术生成

问题描述:

slurm平台,计算节点的状态自动变为down,但是slurmd的status输出是正常的。重启slurmd服务能好使一会,但是过一段时间后还是会变为down。


问题定位

1、检查slurmctld服务日志,发现存在以下异常日志:

[2023-05-09T21:30:59.650] error: Orphan StepId=6639.extern reported on node node31
[2023-05-09T21:30:59.650] error: Orphan StepId=6639.0 reported on node node31
[2023-05-09T21:30:59.650] error: Orphan StepId=6652.extern reported on node node31
[2023-05-09T21:30:59.651] error: Orphan StepId=6652.0 reported on node node31
[2023-05-09T21:30:59.651] error: Orphan StepId=6653.extern reported on node node31
[2023-05-09T21:30:59.651] error: Orphan StepId=6653.0 reported on node node31
[2023-05-09T21:30:59.651] error: Orphan StepId=6651.extern reported on node node32
[2023-05-09T21:30:59.651] error: Orphan StepId=6649.extern reported on node node32
[2023-05-09T21:30:59.651] error: Orphan StepId=6650.extern reported on node node32
[2023-05-09T21:30:59.651] error: Orphan StepId=6651.0 reported on node node32
[2023-05-09T21:30:59.651] error: Orphan StepId=6650.0 reported on node node32
[2023-05-09T21:30:59.651] error: Orphan StepId=6649.0 reported on node node32
[2023-05-09T21:31:09.662] error: slurm_receive_msgs: [[node31]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:31:09.662] error: slurm_receive_msgs: [[node31]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:31:09.662] error: slurm_receive_msgs: [[node32]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:31:09.667] error: slurm_receive_msgs: [[node32]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:31:49.707] error: slurm_receive_msgs: [[node31]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:31:49.712] error: slurm_receive_msgs: [[node32]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:32:09.736] error: slurm_receive_msgs: [[node31]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:32:09.742] error: slurm_receive_msgs: [[node32]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:32:29.765] error: slurm_receive_msgs: [[node31]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:32:29.771] error: slurm_receive_msgs: [[node32]:6818] failed: Socket timed out on send/recv operation
[2023-05-09T21:32:39.789] error: Nodes node[31-32] not responding, setting DOWN

找到down的原因了,是从控制节点直接设置状态为down的,原因是Orphan slurm step

2、在计算节点检查slurmstep

计算节点上有存在异常的slurm step
在这里插入图片描述
在这里插入图片描述

3、杀掉对应的slurmstep

杀掉对应的slurmstep,持续观察是否恢复正常

4、 结果

持续观察一周后,没有再次出现down的现象,问题处理完毕


解决方案:

直接kill掉对应的step进程

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值