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.

Sign up for GitHub

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

Jump to bottom

Conode got stuck with CPU at 100% and no disk space left #1851

Closed
Gilthoniel opened this issue May 3, 2019 · 1 comment · Fixed by dedis/onet#542
Closed

Conode got stuck with CPU at 100% and no disk space left #1851

Gilthoniel opened this issue May 3, 2019 · 1 comment · Fixed by dedis/onet#542
Assignees
@Gilthoniel
Labels
bug high priority

Comments

@Gilthoniel
Copy link
Contributor 

3 19/03/05 11:38:11.709596754: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709618186: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709635656: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709651224: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709671772: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709688378: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709704252: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709727943: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709745071: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709760842: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709776529: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709799001: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709821500: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709840153: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709856128: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error
3 19/03/05 11:38:11.709885903: (            network.(*Router).handleConn: 338) - tls://fairywren.ch:7770 Error with connection 128.178.243.22:7770 => Unknown Error

Looking at the timestamps, I wonder if there is an infinite loop or something similar happening here.
@Gilthoniel Gilthoniel self-assigned this May 3, 2019
Gilthoniel pushed a commit to dedis/onet that referenced this issue May 3, 2019
Drop connection if an unknown error occurs
847de9c 
This fixes a potential infinite loop when an unknown error occurs and
will happen every time the connection is handled. This was causing an
infinite loop in some situation.

Fixes dedis/cothority#1851
@Gilthoniel Gilthoniel mentioned this issue May 3, 2019
Merged
@ineiti
Copy link
Member

ineiti commented May 6, 2019

On the other end (conode.c4dt.org), I get a lot of these:

2 19/06/05 07:47:16.926775122: (     network.NewTLSListenerWithListenAddr.func1:  249) - Got new connection request from: 71.19.148.171:60330

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Gilthoniel Gilthoniel

Labels
bug high priority
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Drop connection if an unknown error occurs dedis/onet
2 participants
@ineiti @Gilthoniel