|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 23/Nov/18 08:02 PM
Updated: 19/Jan/19 08:25 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
7.0.16
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
console.log.zip (1.02 Mb)
|
|
Environment:
|
Operating System Linux 4.4.114-94.14-default, amd64
OS User Name root
JVM Java HotSpot(TM) 64-Bit Server VM 1.7.0_79, Oracle Corporation
QuickBuild Version 7.0.16 - Fri May 12 09:57:15 EDT 2017
Total Memory 1.98 GB
Used Memory 1.02 GB
Configurations 7629
Operating System Linux 4.4.114-94.14-default, amd64
OS User Name root
JVM Java HotSpot(TM) 64-Bit Server VM 1.7.0_79, Oracle Corporation
QuickBuild Version 7.0.16 - Fri May 12 09:57:15 EDT 2017
Total Memory 1.98 GB
Used Memory 1.02 GB
Configurations 7629
|
|
|
Support,
On the morning of 11/22 at 1 am, the Quickbuild UI became non responsive. You could hit the sign in page but any attempt to login was met with a spinning browser. A look in the log files for the time showed only that the Automated DB backup had kicked off. In addition there were a number of messages indicating that jobs scheduled for 1 am we put in a "sleep" state. As we were unable to get to the UI even after waiting over an hour, we rebooted the system around 2 am. The UI came back at that time. We then turned off the auto backup function in the UI and this morning there was no issue. Can we get an RCA about what happened with our server during this time? Is there some tuning that needs to be done to allow the auto backup to work smoothly?
|
|
Description
|
Support,
On the morning of 11/22 at 1 am, the Quickbuild UI became non responsive. You could hit the sign in page but any attempt to login was met with a spinning browser. A look in the log files for the time showed only that the Automated DB backup had kicked off. In addition there were a number of messages indicating that jobs scheduled for 1 am we put in a "sleep" state. As we were unable to get to the UI even after waiting over an hour, we rebooted the system around 2 am. The UI came back at that time. We then turned off the auto backup function in the UI and this morning there was no issue. Can we get an RCA about what happened with our server during this time? Is there some tuning that needs to be done to allow the auto backup to work smoothly? |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Closed
Major
Automated Database Bacup Causes issues with QB Ui