Difference between revisions of "Dashboard FAQ"
(→The Dashboard isn't updating) |
(→The Dashboard isn't updating) |
||
| Line 2: | Line 2: | ||
*[[LRM Dashboard FAQ]] |
*[[LRM Dashboard FAQ]] |
||
== The Dashboard isn't updating == |
== The Dashboard isn't updating == |
||
| − | If you have run the Jenkins automation job for a project and the Lingoport Dashboard is not updating, first check |
+ | If you have run the Jenkins automation job for a project and the Lingoport Dashboard is not updating, first check the Console Output of the Jenkins job. Sometimes, the job is SUCCESSful, but not everything worked as it should. |
| + | If everything looks good on the Jenkins side, check the Dashboard to see if there is a red box with '''Failed''' when you select the project. |
||
| − | If you select Failed and go to the logs, open the logs. Check for ERROR messages. If there is an ERROR that looks like: |
||
| + | |||
| + | If you select Failed and go to the logs, open the logs. Look for ERROR messages. If there is an ERROR that looks like: |
||
<pre> |
<pre> |
||
Revision as of 17:45, 18 May 2018
The Dashboard isn't updating
If you have run the Jenkins automation job for a project and the Lingoport Dashboard is not updating, first check the Console Output of the Jenkins job. Sometimes, the job is SUCCESSful, but not everything worked as it should.
If everything looks good on the Jenkins side, check the Dashboard to see if there is a red box with Failed when you select the project.
If you select Failed and go to the logs, open the logs. Look for ERROR messages. If there is an ERROR that looks like:
### Error updating database. Cause: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (4382559 > 4194304). You can change this value on the server by setting the max_allowed_packet' variable.
Then follow these instructions to continue.
