
Key: |
QB-3311
|
Type: |
Bug
|
Status: |
Closed
|
Resolution: |
Cannot Reproduce
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
Todd Scholl
|
Votes: |
0
|
Watchers: |
1
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 17/Dec/18 02:12 PM
Updated: 17/Jan/19 06:01 AM
|
|
Component/s: |
None
|
Affects Version/s: |
7.0.16
|
Fix Version/s: |
None
|
|
Support,
On this morning 12/17 at ~ 1 am the GUI for our QB server became non responsive. The logs for the time show a sharp drop in activity, but do not mention any crash. The logs show jobs still launching, but no jobs reached the agents after this time and nothing appears to have gone into the QB database after ~1:06 am. I had to initiate a server restart at 2:34 am to try and recover the server and after that information and jobs started to flow. I executed the "./server.sh dump" command twice be fore restarting.
After recovery, several of the agents displayed errors and would not reconnect to the server. I had to do a series on manual restarts on them until about ~3 am when the remaining troublesome agents just started working without intervention.
I need to know what was causing these issues and what we can do to fix it.
I am attaching logs for the issue though some of them may be too large. Is there a place I can sftp them too for the big ones?
|
Description
|
Support,
On this morning 12/17 at ~ 1 am the GUI for our QB server became non responsive. The logs for the time show a sharp drop in activity, but do not mention any crash. The logs show jobs still launching, but no jobs reached the agents after this time and nothing appears to have gone into the QB database after ~1:06 am. I had to initiate a server restart at 2:34 am to try and recover the server and after that information and jobs started to flow. I executed the "./server.sh dump" command twice be fore restarting.
After recovery, several of the agents displayed errors and would not reconnect to the server. I had to do a series on manual restarts on them until about ~3 am when the remaining troublesome agents just started working without intervention.
I need to know what was causing these issues and what we can do to fix it.
I am attaching logs for the issue though some of them may be too large. Is there a place I can sftp them too for the big ones? |
Show » |
No work has yet been logged on this issue.
|
|