-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discrepancy in Task Execution number and Test CNX on Crynux Node UI versus the Web UI #209
Comments
Node UI is lagging the Web UI. Task execution number is reflected higher on the Web UI versus the Node UI stuck at the same number. |
It might be related to the Rollapp down. Can you please try it again when the Rollapp is running? |
In the latest version, there is still a discrepancy between task execution number on the node versus on the web UI. |
I think this is due the Node UI stopped refreshing due to some previous errors. Is there error messages on the Node UI? And can you also provide us the logs when it happens? |
Problem Description
I see that there is a discrepancy with what I can see on the Crynux Node UI versus what I see by accessing the dashboard through the IP Address:port on a different computer but under the same network.
Please see the attached images.
Error Log
On the Node UI, there's persistent Network error. Will try again later msg.
In the Node UI, the Task Execution for today stays at 284 with a green running status.
The task Execution on the Dashboard by accessing the IPaddress from a different computer under the same network, shows 445 with an Idle status.
There's also a discrepancy between the number test CNX accumulated displaying on both UIs.
Please see attached files. They were taken at the same time.
Device Position
Operating System
How do you Start the Crynux Node
Error message on the WebUI
Currently, the Node UI dashboard does not update its task execution number. But the test CNX number does change. The web UI task execution number and the test CNX number change after a refresh of the page.
The text was updated successfully, but these errors were encountered: