open All Channels
seplocked Linux
blankseplocked Socket closed?
This thread is older than 90 days and has been locked due to inactivity.

Author Topic

Mr M
Posted - 2010.07.28 01:00:00 - [1]

The socket closed bug that many have problem with, do you guys have problem with that? I'm running debian lenny here and I only think it has happened to me once so I was thinking maybe that's a problem with the windows tcp/ip stack.

Deep Core Mining Inc.
Posted - 2010.07.28 16:21:00 - [2]

I think that is a general problem for some people.

If I should guess it is the TCP connection that is closed by whatever means.

What you could do is dumping all your TQ connection data and wait for a connection close to happen. Then look at how the connection was closed.
sudo tcpdump -i eth0 -s 0 -n -w dumpfile.bin tcp port 26000
should capture the connection (don't know if that is against the EULA but the data is encrypted anyway)
then you can open it in wireshark and lok how the connection was closed (the last 10 packets should show that)

an alternative could be to use a different port to connect to TQ (I think there was a blog about that some time ago) something to read

Mr M
Posted - 2010.07.28 20:41:00 - [3]

My problem is that it never happens to me Smile I only hear from others that they're getting booted off all the time

Yarod Cool
Posted - 2010.07.30 01:45:00 - [4]

It's not a "socket closed bug". The message means that the connection was dropped. Easy to reproduce with flaky wireless, hub, or ISP problems.


This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only