Re: How (and why) to use the Relay Network

[OverHash]

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

[1714651273]

1714651273

[1714651273]

1714651273

[1714651273]

1714651273

[entr04y]

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!

[Matt Corallo]

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]

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)?

I just double checked that and it is listening on both ipv4 and ipv6.  If I telnet to the port using localhost it connects and then immediately closes the connection. 

then the penny dropped:  maxconnections is set to 20 in my bitcoin.conf and guess how many peers I have connected?

[spin]

You should pm me your ip, I cant reproduce.

Will do when it happens again.  Won't restart then either.

[IYFTech]

Is the relay network down? I can't connect to any of the different nodes.......

[entr04y]

Is the relay network down? I can't connect to any of the different nodes.......

My instance of the relay client seems to be working happily...

[IYFTech]

Is the relay network down? I can't connect to any of the different nodes.......

Edit: Seems the issue was at my end. My apologies 

[norgan]

Hi Matt, got an issue on the Aussie node. Unable to read message header

[Matt Corallo]

Hi Matt, got an issue on the Aussie node. Unable to read message header

Ugh, sorry I missed this...should be fixed now

[spiccioli]

Hi Matt,

I'm getting tons of these on eu node with java client

Code:

Dec 21, 2014 12:15:33 PM com.google.bitcoin.net.ConnectionHandler handleKeyWrite
SEVERE: Error handling SelectionKey write: null
Dec 21, 2014 12:15:35 PM com.google.bitcoin.net.NioClientManager handleKey
INFO: Successfully connected to public.eu.relay.mattcorallo.com/146.185.173.241:8336
Connected to relay peer!
Dec 21, 2014 12:15:35 PM com.google.bitcoin.net.ConnectionHandler handleKeyRead
SEVERE: Error handling SelectionKey read: Connection reset by peer

No problems using us-east.

Best regards

spiccioli

[Matt Corallo]

I'm getting tons of these on eu node with java client

Ugh, yea...there are, I think, three known issues now with the server-side stuff. Sadly its been on the backburner so the servers just keep getting restarted instead of fixed (luckily clients reconnect quickly and it doesnt really matter), but I should have some time in the next week to catch up on the technical debt on the server-side.

[jedimstr]

With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for Relay Clients?  I see in the release notes that there are quite a few header related changes.

[kano]

With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for Relay Clients?  I see in the release notes that there are quite a few header related changes.

Without even looking, I'll say that the header will of course be backwards compatible.
The devs don't do hard forks.

[Matt Corallo]

With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for Relay Clients?  I see in the release notes that there are quite a few header related changes.

Shouldnt be...Ive been running relay clients against master forever.

[jedimstr]

Thanks Kano and Matt, just checking

Can never be too careful.  I'll probably still wait until the final release of 0.10.0 before switching though.

[loshia]

With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for Relay Clients?  I see in the release notes that there are quite a few header related changes.

with v0.10.0rc1 works charming

[Matt Corallo]

With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for Relay Clients?  I see in the release notes that there are quite a few header related changes.

HAH! Now that I say that, it looks like there may actually be issues hiding here (specifically, https://github.com/bitcoin/bitcoin/issues/5588 may be related). Anyway, if it is, its a bug in bitcoin core, to be fixed there.

[jedimstr]

With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for Relay Clients?  I see in the release notes that there are quite a few header related changes.

HAH! Now that I say that, it looks like there may actually be issues hiding here (specifically, https://github.com/bitcoin/bitcoin/issues/5588 may be related). Anyway, if it is, its a bug in bitcoin core, to be fixed there.

Well, if it's an issue, better found now in the first RC than in the gold version right?

[spin]

Matt, I've been having issues connecting again.  Both EU and US-east. That's after weeks of rock solid stability.