Author Name: Mark Donohoe
Original Redmine Issue: 549, http://www.fossology.org/issues/549
Original Date: 2012/01/25
Original Assignee: Mary Laser
The agent logs do not contain enough information to determine what went wrong. Using an error code like 3 or agent code 12 does not indicate what the real error was. Saying only in the log that the agent failed is also not helpful when trying to figure out what the problem is or how it might be fixed.
The agents should give informative messages like 'file xxx not found', no permission to write to xxxx, can't schedule scheduler, go db error xxxx, etc...
Author Name: Mark Donohoe Original Redmine Issue: 549, http://www.fossology.org/issues/549 Original Date: 2012/01/25 Original Assignee: Mary Laser
The agent logs do not contain enough information to determine what went wrong. Using an error code like 3 or agent code 12 does not indicate what the real error was. Saying only in the log that the agent failed is also not helpful when trying to figure out what the problem is or how it might be fixed.
The agents should give informative messages like 'file xxx not found', no permission to write to xxxx, can't schedule scheduler, go db error xxxx, etc...