LDAP etc.
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Legoktm
	May 24 2021, 7:14 AM

Description

I've had multiple grid jobs get stuck with an error entry of can't get password entry for user "tools.<tool>". Either user does not exist or error with NIS/LDAP etc.

In each case qstat shows the job in Eqw state, which I guess means that jsub -once will not run a new job.

Related Objects

Mentioned Here: T282474: tools.topicmatcher update_items_from_sparql.php frequently running Toolforge nodes out of resources

Event Timeline

Legoktm created this task.May 24 2021, 7:14 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 24 2021, 7:14 AM

CptViraj subscribed.May 24 2021, 7:15 AM

@Majavah believes this is caused by stuff like T282474: tools.topicmatcher update_items_from_sparql.php frequently running Toolforge nodes out of resources which is causing the node to run out of resources, so new jobs will somehow have issues talking to LDAP.

Haven't seen this in a while. Closing.

Toolforge grid jobs stuck with: can't get password entry for user "tools.<tool>". Either user does not exist or error with NIS/LDAP etc.Closed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Toolforge grid jobs stuck with: can't get password entry for user "tools.<tool>". Either user does not exist or error with NIS/LDAP etc.
Closed, ResolvedPublic
Actions