| << Back to previous view |
|
[QB-3627] Two big issues occur now 1) Read timed out 2) Unable to find job
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 10.0.24 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Yoongeon Lee | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | windows 10 x64 | ||
| File Attachments: |
console.log
node issue 1.png
node issue 2.png
node issue 3.png
node issue 4 - build agent.png
node issue 5 - build agent.png
quickbuild.log
timeout issue cx2021-2.png
timeout issue cx2021.png
|
| Description |
|
Hi, Robin
We're getting two big issues now. After upgrading ci server and build agent to 10.0.24, two issues occur frequently.In CI Server, the following two errors occur. 1. Read timed out ( refer attached image name - node issue 2.png ) 2. Unable to find job ...... on node ( refer attached image name - node issue 3.png ) When an error occurs, the build agent displays the following error message. 1. Could not send response error 500 javax.servlet.servletexception......( refer attached image name - node issue 4~5.png ) Please let me know what to check. hard time now.. all nodes are not working |
| Comments |
| Comment by Robin Shen [ 13/Oct/20 04:56 AM ] |
| Please check if this still happens when server load is not high. If so, I guess there is some networking issue as QB10 is released for some time and we have not got this report from other sites. |
| Comment by Yoongeon Lee [ 13/Oct/20 07:18 AM ] |
| I have attached log files (including console.log and quickbuild.log ) please see them. Where can I check the server load? |
| Comment by Robin Shen [ 13/Oct/20 07:38 AM ] |
| If there is only a few builds in queue, the load should be low. Also if this happens for every agent, please check if the agent and server can connect to each other via "telnet <QB server/agent port>" from server/agent machine. |
| Comment by Robin Shen [ 18/Oct/20 05:30 AM ] |
| Adding SSL encryption between agent and server solved the problem. |