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

diode client stops sending/receiving data #37

Closed
dominicletz opened this issue Jul 28, 2020 · 5 comments
Closed

diode client stops sending/receiving data #37

dominicletz opened this issue Jul 28, 2020 · 5 comments
Assignees

Comments

@dominicletz
Copy link
Member

Client Version:
v0.4.5

Affected domain:
https://mediaserver.diode.link/index.html

Reported in telegram chat:
Screenshot_2020-07-28-13-03-04-326_org telegram messenger

Log:
[EROR] Failed to submit ticket: send call to channel timeout server=europe.testnet.diode.io:41046
9 [EROR] Failed to submit ticket: send call to channel timeout server=europe.testnet.diode.io:41046
5 [EROR] Failed to submit ticket: send call to channel timeout server=europe.testnet.diode.io:41046
4 [WARN] Cannot find the portclose connected device 01913849 server=europe.testnet.diode.io:41046
0 [WARN] Cannot find the portclose connected device 7b74ac75 server=europe.testnet.diode.io:41046
5 [EROR] Failed to submit ticket: send call to channel timeout server=europe.testnet.diode.io:41046
1 [WARN] Cannot find the portsend connected device 7e945538 server=europe.testnet.diode.io:41046
1 [WARN] Cannot find the portsend connected device 71f76ade server=europe.testnet.diode.io:41046
1 [WARN] Cannot find the portclose connected device 71f76ade server=europe.testnet.diode.io:41046
1 [WARN] Cannot find the portclose connected device 7e945538 server=europe.testnet.diode.io:41046

@sc0Vu
Copy link
Contributor

sc0Vu commented Jul 28, 2020

Looks like some rpc failed with timeout error, and blocks the others rpc.

Should we restart client once rpc timeout?

@jimthedj65
Copy link

Looks like some rpc failed with timeout error, and blocks the others rpc.

Should we restart client once rpc timeout?

This morning I started up my server, I run nginx out to two networks, my own L4 O L7 and Diode, everything was running ok to my own network, no errors. I was getting a 404 on diode until I restarted the systemd service manually. I could ping my diode address ok, it looks like there is a possible sync/time issue on startup.

@dominicletz
Copy link
Member Author

Yep, there is some deadlock in the client it seems. We need to replace the channel that is timing out and also find the root cause of the timeout.

@jimthedj65
Copy link

I am getting connect fails since yesterday

07/31/2020 11:36:16 [EROR] Failed to connect local: dial tcp 127.0.
Jul 31 11:36:17 mediaserver.diode.link diode[31950]: 07/31/2020 11:36:17 [EROR] Failed to connect local: dial tcp 127.0.
Jul 31 11:36:19 mediaserver.diode.link diode[31950]: 07/31/2020 11:36:19 [EROR] Failed to connect local: dial tcp 127.0.
Jul 31 11:36:20 mediaserver.diode.link diode[31950]: 07/31/2020 11:36:20 [EROR] Failed to connect local: dial tcp 127.0.

@dominicletz
Copy link
Member Author

This should be gone with v0.4.9 https://github.com/diodechain/diode_go_client/releases/tag/v0.4.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants