Skip to content
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

Closed
jedie opened this issue Jun 16, 2014 · 7 comments
Closed

change node "Disconnected" information in WebGUI... #367

jedie opened this issue Jun 16, 2014 · 7 comments
Labels
frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion

Comments

@jedie
Copy link
Contributor

jedie commented Jun 16, 2014

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"

@calmh
Copy link
Member

calmh commented Jun 16, 2014

"Offline" is "Disconnected", and "Idle" as you describe it here isn't really supposed to happen...?

@jedie
Copy link
Contributor Author

jedie commented Jun 16, 2014

"Offline" is "Disconnected"

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?

@calmh
Copy link
Member

calmh commented Jun 16, 2014

Disconnected means exactly that we do not have a connection to the node. Either it's down, unreachable or discovery doesn't find it.

@calmh
Copy link
Member

calmh commented Jun 16, 2014

(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)

@calmh calmh closed this as completed Jun 16, 2014
@jedie
Copy link
Contributor Author

jedie commented Jun 16, 2014

Exist there a state for:

  • PC is running, ping to IP is ok, but syncthing not running?
  • Node is running, syncthing runs, but doesn't communicate with other syncthing note (maybe version mismatch or certificate error or wrong note ID etc.)

@calmh
Copy link
Member

calmh commented Jun 16, 2014

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.

@jedie
Copy link
Contributor Author

jedie commented Jun 17, 2014

syncthing can't use ping? Because it has no root rights?

I try to figure out what happen here. I have used STTRACE=net
First: It seems that only failed connection messages are traced. There is not message about a successfully connection, isn't it?

One thing i found out:

  • Node foo listed node bar with disconnected
  • at the same time: Node bar listed node foo as connected with all informations, but stays with 0bps Up-/Download rate

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"

@st-review st-review added the frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion label Jun 17, 2017
@syncthing syncthing locked and limited conversation to collaborators Jun 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion
Projects
None yet
Development

No branches or pull requests

3 participants