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

wsarecv: An established connection was aborted by the software in your host machine. #183

Closed
3 tasks done
zhonghaoling opened this issue Nov 12, 2018 · 15 comments
Closed
3 tasks done
Labels

Comments

@zhonghaoling
Copy link

zhonghaoling commented Nov 12, 2018

Subject of the issue

wsarecv: An established connection was aborted by the software in your host machine.

Is this a bug report of a feature request?

  • Bug report
    6600

Your environment

Server-side

  • localhost
  • Your own setup:
    • windows 10
    • version: 0.15.9-rc1
@or-else
Copy link
Contributor

or-else commented Nov 12, 2018

It seems like you don't have a connection to your database. The "invalid connection" means the call to database has failed because there is no connection.

@or-else
Copy link
Contributor

or-else commented Nov 12, 2018

Since websocket connections are failing too, it seems like you have a network problem. Maybe a misconfigured firewall?

@zhonghaoling
Copy link
Author

Since websocket connections are failing too, it seems like you have a network problem. Maybe a misconfigured firewall?

It seems like you don't have a connection to your database. The "invalid connection" means the call to database has failed because there is no connection.

The firewall is turned off and this problem is still present, "Error:internal error(500)".So, I refresh the page, try a few more, it seems to be successful. However, this error message will still appear.

@zhonghaoling
Copy link
Author

Since websocket connections are failing too, it seems like you have a network problem. Maybe a misconfigured firewall?

There is no such problem under Linux system, such as CentOS 7.2

@or-else
Copy link
Contributor

or-else commented Nov 12, 2018

The problem seems to be due to network failure.

Check your Windows Defender settings. See here:
https://superuser.com/questions/1335258/windows-10-private-firewall-blocks-all-internet-traffic

@or-else
Copy link
Contributor

or-else commented Nov 12, 2018

It does not seem to be related to Tinode. It's that something is blocking network connections.

@or-else
Copy link
Contributor

or-else commented Nov 13, 2018

Have you been able to solve the problem?

@zhonghaoling
Copy link
Author

Have you been able to solve the problem?

Not at all. Try it according to your suggestion, the firewall is also closed, but it failed. So, I found the local environment test, windows10 system, mysql-5.7, tinode v0.15.9-rc1, and found no errors. But running on my cloud server, I got this error. This kind of mistake seems to be unreproducible

@or-else
Copy link
Contributor

or-else commented Nov 13, 2018

In your cloud setup, can you connect to the database from your compute instance?

Like run mysql client in the same instance where you run Tinode server and try connecting to your mysql database using the same credentials as Tinode.

@or-else
Copy link
Contributor

or-else commented Nov 13, 2018

Make sure your cloud instance of mysql is configured with the same user and password which you use in tinode config.

@zhonghaoling
Copy link
Author

In your cloud setup, can you connect to the database from your compute instance?

Like run mysql client in the same instance where you run Tinode server and try connecting to your mysql database using the same credentials as Tinode.

Database account and password are no problem.It can be connected to the database from my compute instance.

@or-else
Copy link
Contributor

or-else commented Nov 14, 2018

Is it possible that your mysql instance is preempted?

Given the limited information you shared, I can't really think of anything else. Sorry.

@or-else
Copy link
Contributor

or-else commented Nov 14, 2018

This is probably what's happening: go-sql-driver/mysql#657

@zhonghaoling
Copy link
Author

This is probably what's happening: go-sql-driver/mysql#657

After I modified the database configuration file, and set 'wait_timeout=30', the bug has not appeared.Thank you very much!

@or-else
Copy link
Contributor

or-else commented Nov 15, 2018

Great!

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

No branches or pull requests

2 participants