Hi,

2025-01-29T00:33:32.123] CPU frequency setting not configured for this node

[2025-01-29T00:33:32.124] slurmd version 20.11.9 started

[2025-01-29T00:33:32.125] slurmd started on Wed, 29 Jan 2025 00:33:32 +0000

[2025-01-29T00:33:32.125] CPUs=20 Boards=1 Sockets=20 Cores=1 Threads=1 Memory=48269 TmpDisk=23308 Uptime=20 CPUSpecList=(null) FeaturesAvail=(null) FeaturesActive=(null)

[2025-01-29T00:40:36.557] error: Security violation, ping RPC from uid 12002

[2025-01-29T00:43:56.866] error: Security violation, ping RPC from uid 12002

[2025-01-29T00:45:36.025] error: Security violation, ping RPC from uid 12002

[2025-01-29T00:47:16.204] error: Security violation, ping RPC from uid 12002

[2025-01-29T00:48:56.351] error: Security violation, ping RPC from uid 12002

8><----
2025-01-30T19:43:49.773] error: Security violation, ping RPC from uid 12002

[2025-01-30T19:44:03.823] error: Security violation, batch launch RPC from uid 12002

[2025-01-30T19:44:03.836] error: Security violation: kill_job(8) from uid 12002

[2025-01-30T19:44:59.974] error: Security violation: kill_job(8) from uid 12002

[2025-01-30T19:45:29.024] error: Security violation, ping RPC from uid 12002
8><----

doh, I was looking in /var/log/slurm/ and not /var/log/ I can try running a job again to get a fresh log?

regards

Steven

From: Chris Samuel via slurm-users <slurm-users@lists.schedmd.com>
Sent: Monday, 3 February 2025 11:28 am
To: slurm-users@lists.schedmd.com <slurm-users@lists.schedmd.com>
Subject: [slurm-users] Re: Fw: Re: RHEL8.10 V slurmctld

On 2/2/25 1:54 pm, Steven Jones via slurm-users wrote:

> Thanks for the reply. I already went through this 🙁. I checked all
> nodes, id works as does a ssh login.

What is in your slurmd logs on that node?

--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-leave@lists.schedmd.com