Re: How (and why) to use the Relay Network - page 14.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: entr04y on December 02, 2014, 10:38:46 AM

Code:

Closing bitcoind socket with 127.0.0.1, failed to read message header (104: Connection reset by peer)
Closing bitcoind socket with 127.0.0.1, failed to read message header (0: )

I'm not seeing any errors in my bitcoin debug log, and the port is open on the server. I'm running the latest bitcoind and I pulled the relay client from github this morning (its the c++ version on linux)

Have you checked wireshark on your loopback interface, and are you sure bitcoind is listening on loopback and not only on your non-localhost address(es)?

entr04y

newbie

Activity: 23

Merit: 0

I'm getting this in the output:

Code:

Received transaction of size 226 from relay server
Received transaction of size 373 from relay server
Closing bitcoind socket with 127.0.0.1, failed to read message header (104: Connection reset by peer)
Closing bitcoind socket with 127.0.0.1, failed to read message header (0: )

I'm not seeing any errors in my bitcoin debug log, and the port is open on the server. I'm running the latest bitcoind and I pulled the relay client from github this morning (its the c++ version on linux)

edit: I'm starting the relay client like so:

Code:

./relaynetworkclient public.us-east.relay.mattcorallo.com 127.0.0.1 8333

I saw some other people were getting similar messages on the relay, but not on bitcoind. Any ideas?

Thanks!

OverHash

newbie

Activity: 42

Merit: 0

Quote from: Matt Corallo on November 30, 2014, 07:48:42 PM

As noted previously, I'm not gonna add pools to that list that dont have at least a few dozen TH on them.

Ah okay, that's fair enough. Sorry should have read a bit more thoroughly.

Thanks for designing the relay though

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: OverHash on November 30, 2014, 07:32:26 PM

Hi Matt Corallo,

If possible would you be able to add OverHash.com to the list of pools as we are running the C++ client for our pool.

As noted previously, I'm not gonna add pools to that list that dont have at least a few dozen TH on them.

OverHash

newbie

Activity: 42

Merit: 0

Quote from: Matt Corallo on September 02, 2014, 04:52:11 AM

The following pools (in alphabetical order) are known to use the C++ Relay Network Client (and, thus, will likely see slightly lower orphan rates):

P2Pool: If you're running your own P2Pool node you can (and should) absolutely run the client locally connected directly to your bitcoind. Also, many publicly hosted P2Pool nodes run the client as well.
Bitminter
BTCGuild
ckpool/hashmine.io
Eligius

If you are a pool operator and are running the C++ (or Java) client on or near your bitcoinds, please find me on IRC or PM me to get added to this list.

Hi Matt Corallo,

If possible would you be able to add OverHash.com to the list of pools as we are running the C++ client for our pool.

jedimstr

hero member

Activity: 798

Merit: 1000

Looks like East Coast Relay is down again... had to connect to the West Coast one.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: spin on November 28, 2014, 01:58:35 PM

Not it doesn't. It stays like that for as far back as my scroll back allows. It doesn't receive txs during this time, but does try to send to the relay node.

You should pm me your ip, I cant reproduce.

spin

sr. member

Activity: 362

Merit: 262

Quote from: Matt Corallo on November 27, 2014, 02:11:16 PM

Quote from: spin on November 27, 2014, 08:08:42 AM

It somehow ends up in that state from time to time. I only run one client (the defualt). I guess it loses connection at some point and when it rapidly reconnects it get's banned/blocked by the relay server?

Can I change the reconnect interval in the client?

Does it not get back in after ~10 seconds? Getting reset a few times while trying to reconnect shouldnt hurt anything.

Not it doesn't. It stays like that for as far back as my scroll back allows. It doesn't receive txs during this time, but does try to send to the relay node.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: spin on November 27, 2014, 08:08:42 AM

It somehow ends up in that state from time to time. I only run one client (the defualt). I guess it loses connection at some point and when it rapidly reconnects it get's banned/blocked by the relay server?

Can I change the reconnect interval in the client?

Does it not get back in after ~10 seconds? Getting reset a few times while trying to reconnect shouldnt hurt anything.

spin

sr. member

Activity: 362

Merit: 262

Quote from: Matt Corallo on November 26, 2014, 11:40:59 PM

Quote from: spin on November 26, 2014, 01:57:50 PM

Still some issues?

Code:

./relaynetworkclient public.eu.relay.mattcorallo.com 127.0.0.1 8333
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Sent transaction of size 223 to relay server
Sent transaction of size 223 to relay server
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (104: Connection reset by peer)
Sent transaction of size 226 to relay server
Sent transaction of size 473 to relay server
Sent transaction of size 436 to relay server
Sent transaction of size 226 to relay server
Closing relay socket, failed to read message header (104: Connection reset by peer)

That looks like you have multiple connections from the same IP (note that it takes up to 10 seconds before you can connect again after a disconnect, though I think most clients are set to reconnect every second).

It somehow ends up in that state from time to time. I only run one client (the defualt). I guess it loses connection at some point and when it rapidly reconnects it get's banned/blocked by the relay server?

Can I change the reconnect interval in the client?

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: spin on November 26, 2014, 01:57:50 PM

Still some issues?

Code:

./relaynetworkclient public.eu.relay.mattcorallo.com 127.0.0.1 8333
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Sent transaction of size 223 to relay server
Sent transaction of size 223 to relay server
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (104: Connection reset by peer)
Sent transaction of size 226 to relay server
Sent transaction of size 473 to relay server
Sent transaction of size 436 to relay server
Sent transaction of size 226 to relay server
Closing relay socket, failed to read message header (104: Connection reset by peer)

That looks like you have multiple connections from the same IP (note that it takes up to 10 seconds before you can connect again after a disconnect, though I think most clients are set to reconnect every second).

spin

sr. member

Activity: 362

Merit: 262

Still some issues?

Code:

./relaynetworkclient public.eu.relay.mattcorallo.com 127.0.0.1 8333
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Sent transaction of size 223 to relay server
Sent transaction of size 223 to relay server
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (104: Connection reset by peer)
Sent transaction of size 226 to relay server
Sent transaction of size 473 to relay server
Sent transaction of size 436 to relay server
Sent transaction of size 226 to relay server
Closing relay socket, failed to read message header (104: Connection reset by peer)

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: chinesebob on November 25, 2014, 08:04:09 PM

How can I test whether running the relay client is actually benefiting me? In 24 hours since starting it I have 4 shares in p2pool, 2 of which are orphaned, this is high compared to my previous 20 days. I'm running bitcoind, p2pool, and relaynetworkclient all on the same system.

p2pool shares are unrelated to the relay client ...

norgan

sr. member

Activity: 308

Merit: 250

Decentralize your hashing - p2pool - Norgz Pool

Quote from: chinesebob on November 25, 2014, 08:04:09 PM

How can I test whether running the relay client is actually benefiting me? In 24 hours since starting it I have 4 shares in p2pool, 2 of which are orphaned, this is high compared to my previous 20 days. I'm running bitcoind, p2pool, and relaynetworkclient all on the same system.

it's just a matter of testing over time. It can't make things worse Wink

norgan

sr. member

Activity: 308

Merit: 250

Decentralize your hashing - p2pool - Norgz Pool

Quote from: Matt Corallo on November 25, 2014, 06:58:28 PM

Quote from: norgan on November 25, 2014, 06:30:11 PM

sweet, can we have a new exe compiled please?

Dont need it, just a server-side bug.

ah! cool, thanks mate.

chinesebob

newbie

Activity: 64

Merit: 0

How can I test whether running the relay client is actually benefiting me? In 24 hours since starting it I have 4 shares in p2pool, 2 of which are orphaned, this is high compared to my previous 20 days. I'm running bitcoind, p2pool, and relaynetworkclient all on the same system.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: norgan on November 25, 2014, 06:30:11 PM

sweet, can we have a new exe compiled please?

Dont need it, just a server-side bug.

norgan

sr. member

Activity: 308

Merit: 250

Decentralize your hashing - p2pool - Norgz Pool

Quote from: kano on November 25, 2014, 05:56:46 PM

Quote from: Matt Corallo on November 24, 2014, 07:57:30 PM

Quote from: kano on November 24, 2014, 06:29:38 PM

Sigh,
seems like another relay ddos.
Lots of txns over a short period of time followed by
"Closing relay socket, got freely relayed transaction too large (0: )"

Happening repeatedly.

This is not a dos, this is a bug. Specifically, this one. (Fixed now).

Oh nice

Bugs are better (IMO) than a ddos, coz there's a definite fix for it

Updated.
Thanks.

sweet, can we have a new exe compiled please?

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Matt Corallo on November 24, 2014, 07:57:30 PM

Quote from: kano on November 24, 2014, 06:29:38 PM

Sigh,
seems like another relay ddos.
Lots of txns over a short period of time followed by
"Closing relay socket, got freely relayed transaction too large (0: )"

Happening repeatedly.

This is not a dos, this is a bug. Specifically, this one. (Fixed now).

Oh nice

Bugs are better (IMO) than a ddos, coz there's a definite fix for it

Updated.
Thanks.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: kano on November 24, 2014, 06:29:38 PM

Sigh,
seems like another relay ddos.
Lots of txns over a short period of time followed by
"Closing relay socket, got freely relayed transaction too large (0: )"

Happening repeatedly.

This is not a dos, this is a bug. Specifically, this one. (Fixed now).

Topic: Re: How (and why) to use the Relay Network - page 14. (Read 653 times)