[Cgminer] connection to pool 0 interrupted (15$ btc bounty)

[joshv06]

Hey guys, was wondering if you could help me out.

I am running 12 HashLast baby jets on 2 separate computers. They keep to seem going down at random times due to the error:

connection to pool 0 interrupted

These are hosted at a datacenter. Is the internet there dropping?

Pool 1: us1.ghash.io

Pool 2: uk2.ghash.io

I am running them in IP format because the ant miners there seem to finicky when running the typed out URL, work perfect with IP.

Cgminer conf.

Code:

{
"pools" : [
	{
		"url" : "46.229.169.89:3333",
		"user" : "joshv06.11",
		"pass" : "123"
	},
	{
		"url" : "88.150.205.242:333",
		"user" : "joshv06.11",
		"pass" : "123"
	}
],

"failover-only" : true,
"no-submit-stale" : true,
"api-listen" : true,
"api-port" : "4028",
"api-allow" : "W:192.168.1.0/24,W:127.0.0.1"
}

Command line

cgminer --hfa-hash-clock 600

[-ck]

It is just as the message says: the connection is being interrupted. Usually it's a pool issue where they're dropping connections though it could be a routing problem or just an operating system flakiness. Trying a different pool, checking your routers upstream aren't overloaded for some other reason (because mining takes very little bandwidth), and using an operating system with a reliable network stack (like linux) are about all you can do. The message itself is actually relatively harmless since cgminer will just reconnect immediately if it can, the only issue is any shares you may be losing when it happens. As always, also make sure you are using the latest cgminer.

[joshv06]

It is just as the message says: the connection is being interrupted. Usually it's a pool issue where they're dropping connections though it could be a routing problem or just an operating system flakiness. Trying a different pool, checking your routers upstream aren't overloaded for some other reason (because mining takes very little bandwidth), and using an operating system with a reliable network stack (like linux) are about all you can do. The message itself is actually relatively harmless since cgminer will just reconnect immediately if it can, the only issue is any shares you may be losing when it happens. As always, also make sure you are using the latest cgminer.

Would there be any way to make Cgminer keep scanning for the pool or some what for that if the connection is lost, I don't have to remote in just to start it back up again?

Thanks!

[-ck]

I already said it tries to reconnect immediately - and it keeps retrying at regular intervals indefinitely. If it's disconnecting and then never reconnecting you have other problems in your networking.

[byt411]

It is just as the message says: the connection is being interrupted. Usually it's a pool issue where they're dropping connections though it could be a routing problem or just an operating system flakiness. Trying a different pool, checking your routers upstream aren't overloaded for some other reason (because mining takes very little bandwidth), and using an operating system with a reliable network stack (like linux) are about all you can do. The message itself is actually relatively harmless since cgminer will just reconnect immediately if it can, the only issue is any shares you may be losing when it happens. As always, also make sure you are using the latest cgminer.

Would there be any way to make Cgminer keep scanning for the pool or some what for that if the connection is lost, I don't have to remote in just to start it back up again?

Thanks!

It should attempt to reconnect itself. I suggest you add a backup pool, so when ghash goes down you continue mining.

By the way, you have the wrong port on pool 2. Its port 3333, not port 333.

[Jaqen]

Are your settings formatted the way they are shown in your post? Have you tried indenting the lines starting with "failover-only" so that they are in line with the { and } of the pool settings?

[byt411]

Are your settings formatted the way they are shown in your post? Have you tried indenting the lines starting with "failover-only" so that they are in line with the { and } of the pool settings?

The problem is not the pool selection method, it is the connection.
And of course his settings are that way, otherwise why would he post them?

[Jaqen]

Are your settings formatted the way they are shown in your post? Have you tried indenting the lines starting with "failover-only" so that they are in line with the { and } of the pool settings?

The problem is not the pool selection method, it is the connection.
And of course his settings are that way, otherwise why would he post them?

Well based on my experience with cgminer, the formatting is important like every other programming language. Just trying to rule out all possibilities...

[byt411]

Are your settings formatted the way they are shown in your post? Have you tried indenting the lines starting with "failover-only" so that they are in line with the { and } of the pool settings?

The problem is not the pool selection method, it is the connection.
And of course his settings are that way, otherwise why would he post them?

Well based on my experience with cgminer, the formatting is important like every other programming language. Just trying to rule out all possibilities...

The connection can be established, but it drops, so that's the server's problem.

[scratchy]

Its a connection interruption.
It can be on your side (if youre using wlan or any wireless connection),
otherwise its a pool issue.

Anyways you should setup a second pool as fail-over otherwise youre loosing mining time!