Disconnect-connect-disconnect from the last version update

Node Operators troubleshooting
, , ,
1

So, I have 2 nodes, in 2 locations, both are “old” nodes with years of running. One is behind an asus router, and one is under a tplink. Same ISP but geographycally ~100km away from each other, I think I know what I do.

About 4 days ago one of my nodes went offline. I checked all of my configs, nothing changed, so I restarted the container and it solved the quick misconfigured error. It was strange but I could live with it. About 12h later my other node went offline. Then I started to get online-offline emails all weekend without doing anything! I see a thread with kinda the same issue; QUIC reporting MISCONFIGURED on long-term running node - #8 by arrogantrabbit (old node, randomly get quick misconfed)

Qusetions:

  • is this a global problem/bug, or it is somehow just me?
  • should I be concered, or just ignore the mails, and we will get a patch?
  • can we get the window informations as a node from the satelites to better track online/offline time?
  • is there an easy way to postprocess the logs so find problems more easily?
2

Email that your node is offline should be checked… but you don’t get email if your node-is-up-but-QUIC-is-misconfigured. I’ll configure QUIC it and if it works it works… but if it’s misconfigured (but “Status = Online”) I ignore it.

The thread you linked says the problem was a dynamic DNS issue? If it wasn’t always pointing the Storj network to the correct node IP… that would definately result in offline email.

1 Like
3

Hello @tg44,
Welcome back!

I believe it’s a known problem of integrated ASUS DDNS, please change it to something more stable like no-ip or cloudflare.

4

I have some nodes from several months ago and have suffered disconnections only last days so I thing something is happening.

5

With ASUS DDNS - for sure. Many reported the same.