-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
change node "Disconnected" information in WebGUI... #367
Comments
"Offline" is "Disconnected", and "Idle" as you describe it here isn't really supposed to happen...? |
Then there is something wrong with this information, because many nodes are often "disconnected" but they are alive. Maybe syncthing doesn't ping them often? |
Disconnected means exactly that we do not have a connection to the node. Either it's down, unreachable or discovery doesn't find it. |
(There might be a bug here, but it's probably not the wording - run with STTRACE=net to figure out what it's trying to connect to and not) |
Exist there a state for:
|
No. We can't know if the PC is up or down unless we can talk to syncthing on that box. If there are connection errors, then they show up in the warnings list in the GUI. |
syncthing can't use ping? Because it has no root rights? I try to figure out what happen here. I have used One thing i found out:
Relate to this: If you start up syncthing and look into WebGUI all clients are disconnected as default. What's about change this to "wait..." or the same as on repo "unknown"? On first failed connection, change to "disconnect" |
I think the "disconnect" information of a node is confusing. "Disconnect" is more a Node is complete offline than a kind of idle state. It's more "Have i input the wrong IP?"
If i see it right there is only the state "Disconnected", "Syncing (x %)" and "Up to Date", isn't it?
Maybe: remove "disconnected" and add "offline" and "idle":
"Offline" is a node if it's really not alive: e.g.: no ping
"idle" is a node, if it's online, but no transfer is active, but also not "Up to Date"
The text was updated successfully, but these errors were encountered: