rundeck job fails on rundom targets (windows + kerberos, rundeck 5.x)

[roman fominichev]

Hi

Could you share your experience if you met this issue before. Thank you

Rundeck (community edition, 5.x)

Targets are windows hosts.

Windows auth protocol - kerberos

The issue is present only if "Thread Count" for the job is set to some bigger number than default "1"

Errors are

kerberos.GSSError: (('Unspecified GSS failure.  Minor code may provide more information', 851968), ('Ticket expired', -1765328352))

kerberos.GSSError: (('Unspecified GSS failure.  Minor code may provide more information', 851968), ('Matching credential not found', -1765328243))

The issue is - error isn't returned by exact/specific windows host. When I set for example "50" as "Thread Count"  and execute job towards 50 targets, it may executes OK, or 1-3-5 targets can fails with errors I published early.
'Matching credential not found'  happens much more often.

But if I will re-execute the same jobs on the failed hosts, it will be finished OK.

This issue never happen if "Thread Count"  is default ("1")

additional rundeck configuration:
quartz.threadPool.threadCount = 100
-Xmx4096m -Xms1024m

Thank you.

[rac...@rundeck.com]

Hi!

It seems to be an issue related to the DNS. Please take a look at this and this.

Regards.

[roman fominichev]

Hi

Than you for your update. Sorry, but it isn't.

If I re-run the job manually on the failed nodes - all of them will be completed OK.

Also - random nodes fails each execution.

When "Thread Count" for the job is default (1) - it always OK.

When  "Thread Count" set to 5 (for example) - then about 90% of executions will be OK.

When it set to 30+ - almost each execution will report 1-3-5 nodes as "failed".

When the same node fails each execution - yes it can be DNS.

понедельник, 2 июня 2025 г. в 15:44:00 UTC+2, rac...@rundeck.com: