History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3266
Type: Bug Bug
Status: Closed Closed
Resolution: Incomplete
Priority: Major Major
Assignee: Robin Shen
Reporter: Todd Scholl
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.

Agent non responsive after Error

Created: 01/Oct/18 10:15 AM   Updated: 23/Jan/19 05:39 AM
Component/s: None
Affects Version/s: 7.0.16
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
During a routine job run this morning, 2 of our agents became non responsive(they disappeared from the grid) to the server. The error was "Can not find any node matching specified criteria.". Upon further checking and reruns, one agent had recovered the other had not. I managed to do a "hard restart"(double run of the stop agent command) on the non-recovered one and restart it.

I would like to know why the one agent did not recover on its own and why both agents became non responsive in the first place?

I am attaching logs for both agent and server.

 All   Comments   Work Log   Change History      Sort Order:
Todd Scholl [01/Oct/18 10:34 AM]
Apparently my server logs are to big to attach to this? Is there another way I can get this to you?

Robin Shen [02/Oct/18 12:47 AM]
Please send to [robin AT pmease DOT com]