Thanks for helping.
The clock is already synced automatically. In fact the error shows that the clock is off by 2h exactly (the time zone difference between client and server).
I’m not even sure this is the issue because it does not explain why the dashboard works right after I restart the node.
CLI dashboard used to work (even if it took a while to fully load. 1 min or so).
Now, it does not seem to load any more. This is all it shows, then waits forever until ctrl-c.
My next steps would be to stop the node and check the disk for errors. Then I would check the databases for errors as well (step 5). Make sure you have the minimum version of sqlite installed, or the check may not work properly.
I’m facing the same issue. This is the second time with this version (1.14.7). The first time I solved it by stopping the node which btw, it took more than one hour with the command “docker stop -t 300 storagenode”
Everything on the node seems to be working fine. Docker ok, the listenning ports ok as well:
But when i issue a telnet to port 14002 of the container, i get refused:
Something weird with this version, and moreover, is my node working fine? The port 28967 is listenning…
Is there some way to check my node, but not querying the node itself? I mean, checking the satellite directly or something else.
I’m not facing any issue in the loading screen. On the other hand, the issue is that the connection is being refused by container despite the port is shown as listening in netstat table.
Btw @Alexey, any coments concerning my question about checking the node stats but without having to query the node directly?
this is to check the dashboard of the node, which I say that is not working.
As you can see in my previous post, when I issued a telnet to the docker and port 14002, i got refused.
Apart of asking what can be the cause of this previous behavior, I was asking if there are other ways to see the node stats (by querying to the satellite or something else), because the port 28967, is still working fine, so right now, I’m not able to see if my node is working or not.
Is the same. The host is natting the request to the container real ip. However, since i’m doing this from the host itself, I have direct visibility to the container, so I can do the telnet directly to its ip.
But if your checking locally on the same system there shouldnt be an issue seeing if the port is open, less there is a config or a issue on that system.
