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

NodeUi: All services offline #5311

Closed
Peter-SovietSquirrel opened this issue Jul 18, 2022 · 8 comments
Closed

NodeUi: All services offline #5311

Peter-SovietSquirrel opened this issue Jul 18, 2022 · 8 comments
Assignees

Comments

@Peter-SovietSquirrel
Copy link

A clear and concise description of what the bug is.
Without any user interaction in NodeUi Node status will say No services available. The service will still be running transferring data and is visible in discovery.
If this is left the the service will stop and it will not be in discovery and NodeUI will only show spinning circle is anything. At this point the actual Linux system will become unresponsive as it may take minutes to log in via SSH.
If nothing is still not done the sometime after a period of time the system will return to normal but this may take hours.

The screenshots were taken when the system was unresponsive

  • Node version: 0.1.9.5
  • OS: Ubuntu 18.04.6 LTS

This issue seem to happen when there has been a large amount of data transferred over a long continues length of time.

daba_node.zip
mystnodes1
mystnodes2

@Peter-SovietSquirrel
Copy link
Author

Peter-SovietSquirrel commented Jul 19, 2022

node.logs7.txt.zip
kern.log
Providing the latest log and also the kern.log

Another shutdown. at around 16:30 the service stopped being able to transfer data and it
went offline including the Linux system until around 22:51 that everything returned to normal.

@etherunit etherunit self-assigned this Jul 21, 2022
@etherunit
Copy link
Collaborator

Thanks for reporting @Peter-SovietSquirrel
We will investigate it further

@Peter-SovietSquirrel
Copy link
Author

heap.out.zip

Outputs of the myst process using 250 & 500MB

@Peter-SovietSquirrel
Copy link
Author

goroutine.out.zip

@Snawoot
Copy link
Contributor

Snawoot commented Jul 23, 2022

it created about 13000 goroutines and they consume a lot of memory:

pprof screenshot

root cause is in server side events code.

@Snawoot
Copy link
Contributor

Snawoot commented Jul 23, 2022

goroutines hang sending into this channel:

h.messages <- string(marshaled)

@etherunit
Copy link
Collaborator

relates to #5244

@Snawoot
Copy link
Contributor

Snawoot commented Jul 26, 2022

Fixed in 1.9.7.

@Snawoot Snawoot closed this as completed Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants