Thanks for the suggestion. I am using openssl because munge requires another software component (the munged) running on compute nodes and MUNGE is sensitive to time synchronization between the nodes. If this problem continues to appear, I will consider munge.
在 2013-07-05五的 21:23 -0700，Aaron Knister写道： > Hi Hongjia, > > While I don't have an answer to your ssl problem I can offer a suggestion. > Have you tried using munge? It's what I've always used with SLURM and I get > the feeling it's the "de facto" standard for SLURM authentication. > > -Aaron > > Sent from my iPhone > > On Jul 5, 2013, at 11:08 AM, Hongjia Cao <[email protected]> wrote: > > > > > Occasionally I run into task launch failures with error message: Invalid > > job credential. slurmd log shows that job credential verification failed > > with openssl error string "block type is not 01". A restart of the > > slurmctld will remove this problem but some time later it will happen > > again. > > > > We are using RSA for job credential keys. I googled and it seems this > > issue may be caused by openssl sign/verify padding scheme. But I do not > > know how to fix it. Does anyone else has this problem?
