Bug #1905

Scheduler becomes unresponsive when agents failed during process fork

Added by Alex Norton about 1 year ago. Updated about 1 year ago.

Status:Closed Start date:05/07/2012
Priority:High Due date:
Assignee:Alex Norton % Done:

0%

Category:Scheduler
Target version:2.0.0
Rank: Tester:

Description

If for some reason the process forking doesn't work when a new agent is created, the job that the agent belongs to doesn't get cleaned up correctly.

History

Updated by Alex Norton about 1 year ago

  • Status changed from In Progress to Closed

This should have been fixed by the same thing that fixed http://www.fossology.org/issues/1911.

Also available in: Atom PDF