OverHash
Newbie
Offline
Activity: 42
Merit: 0
|
|
November 30, 2014, 11:50:07 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
|
|
|
|
entr04y
Newbie
Offline
Activity: 23
Merit: 0
|
|
December 02, 2014, 02:38:46 PM |
|
I'm getting this in the output: 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: ./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 (OP)
|
|
December 02, 2014, 08:24:08 PM |
|
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
Offline
Activity: 23
Merit: 0
|
|
December 02, 2014, 08:43:09 PM |
|
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
|
|
December 03, 2014, 07:38:38 AM |
|
You should pm me your ip, I cant reproduce.
Will do when it happens again. Won't restart then either.
|
If you liked this post buy me a beer. Beers are quite cheap where I live! bc1q707guwp9pc73r08jw23lvecpywtazjjk399daa
|
|
|
IYFTech
|
|
December 05, 2014, 07:07:57 PM |
|
Is the relay network down? I can't connect to any of the different nodes.......
|
|
|
|
entr04y
Newbie
Offline
Activity: 23
Merit: 0
|
|
December 05, 2014, 07:23:05 PM |
|
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
|
|
December 05, 2014, 07:42:16 PM |
|
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
|
|
December 16, 2014, 11:25:20 AM |
|
Hi Matt, got an issue on the Aussie node. Unable to read message header
|
|
|
|
Matt Corallo (OP)
|
|
December 20, 2014, 12:13:06 AM |
|
Hi Matt, got an issue on the Aussie node. Unable to read message header
Ugh, sorry I missed this...should be fixed now
|
|
|
|
spiccioli
Legendary
Offline
Activity: 1378
Merit: 1003
nec sine labore
|
|
December 21, 2014, 11:17:34 AM |
|
Hi Matt, I'm getting tons of these on eu node with java client 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 (OP)
|
|
December 21, 2014, 09:11:09 PM |
|
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
|
|
December 23, 2014, 07:53:24 PM |
|
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
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
December 23, 2014, 11:52:25 PM |
|
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 (OP)
|
|
December 24, 2014, 01:06:47 PM |
|
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
|
|
December 24, 2014, 01:59:07 PM |
|
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
Legendary
Offline
Activity: 1610
Merit: 1000
|
|
December 29, 2014, 07:39:19 AM |
|
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 (OP)
|
|
January 03, 2015, 06:03:36 PM |
|
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
|
|
January 03, 2015, 07:33:38 PM |
|
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
|
|
February 09, 2015, 10:41:30 AM |
|
Matt, I've been having issues connecting again. Both EU and US-east. That's after weeks of rock solid stability.
|
If you liked this post buy me a beer. Beers are quite cheap where I live! bc1q707guwp9pc73r08jw23lvecpywtazjjk399daa
|
|
|
|