Tests not updating - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Tests not updating - Connect IT Community | Kaseya

PROBLEM

Why are the tests not updating?

CAUSE

If the status, results, and duration of all tests on a DGE Extension are all unknown this might be caused by the inability of the DGE extension (DGEx) to connect to TCP port 9443 on the upstream DGE.

This may also be indicated in 'monitor.log' on the DGEx by an entry such as:

2014-07-14 19:25:31,089 dc.DCMessageConsumer[ActiveMQ Session Task-1]: (WARN) Unable to communicate with upstream DGE; Results will be stored locally while attempting to restore connection

The key entry here is: (WARN) Unable to communicate with upstream DGE; Results will be stored locally while attempting to restore connection

RESOLUTION

This may be resolved by confirming:

the configured IP address of the upstream DGE is correct for this DGEx by navigating to 'Superuser->DGE Mgmt->Update'
connectivity from the Extension to TCP port 9443 on the upstream DGE at the address specified in step (1). To do so 'telnet' from a Windows command prompt on the DGEx:

telnet upstream_dge_ip_or_fqdn 9443

or access the following URL from a web browser:

https://upstream_dge_ip_or_fqdn:9443/dc

Once changes are made to the DGEx configuration on the web app, you will need to restart the DGE component on the DGEx for the changes to take effect.

Once this issue is resolved, the DGEx will be able to forward its test results to the upstream DGE as indicated in 'monitor.log' on the DGEx:

2014-07-15 14:01:29,723 m.d.DCTestResultMessageConsumer[ActiveMQ Session Task-407668]: (INFO \) Published 30 test results to upstream DGE

APPLIES TO

All versions of Traverse.

REFERENCE

None.