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

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

It gets this for me,

Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)

ofc ipv6 is unreachable, since I disabled it in sysctl.conf.

it's the same thing as when bitcoind was screwed and wouldn't start when ipv6 was disabled

ed, oh, i let it run for a while longer and after the 10-15th try it stopped attempting ipv6

so working

ed: well, sort of.

Code:

Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 226 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 373 from relay server
Received transaction of size 226 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 472 from relay server
Received transaction of size 373 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 226 from relay server
Received transaction of size 470 from relay server
Received transaction of size 616 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 521 from relay server
Received transaction of size 191 from relay server
Received transaction of size 258 from relay server
Received transaction of size 434 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 225 from relay server
Received transaction of size 438 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 223 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 437 from relay server
Received transaction of size 227 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 470 from relay server
Received transaction of size 226 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 471 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)
Received transaction of size 436 from relay server
Closing bitcoind socket with nogleg, error during connect (101: Network is unreachable)

I guess it's a bit annoying, it is also opening up some godawful amount of ipv6 sockets

Code:

tcp6 0 0 ::1:54082 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54066 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54009 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54083 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54092 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54014 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54067 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54073 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54010 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54086 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54063 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54079 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54071 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54048 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54008 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54033 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54013 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54052 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54090 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54062 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54065 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54077 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54074 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54091 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54072 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54075 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54080 ::1:8333 TIME_WAIT -
tcp6 0 0 zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz ESTABLISHED 4226/relaynetworkcl
tcp6 0 0 ::1:54005 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54060 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54084 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54028 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54093 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54064 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54007 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54006 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54059 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54078 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54004 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54021 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54085 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54069 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54070 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54012 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54061 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54017 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54056 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54095 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54076 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54038 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54068 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54011 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54089 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54057 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54087 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54094 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54058 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54081 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54088 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54043 ::1:8333 TIME_WAIT -
tcp6 0 0 ::1:54015 ::1:8333 TIME_WAIT -

I also have onlynet defined in my bitcoin.conf;

onlynet=ipv4

that is proper text is it not?

oh well. i put it on other machine with ipv6 activated, and now it looks like

Code:

Received transaction of size 1337 from relay server
Received transaction of size 437 from relay server
Sent transaction of size 191 to relay server
Received transaction of size 191 from relay server
Sent transaction of size 436 to relay server
Received transaction of size 436 from relay server
Sent transaction of size 370 to relay server
Received transaction of size 370 from relay server
Sent transaction of size 584 to relay server
Received transaction of size 584 from relay server
Sent transaction of size 226 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 226 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 226 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 226 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 796 to relay server
Received transaction of size 796 from relay server
Sent transaction of size 225 to relay server
Received transaction of size 225 from relay server
Sent transaction of size 472 to relay server
Received transaction of size 472 from relay server
Sent transaction of size 35985 to relay server
Sent transaction of size 225 to relay server
Sent transaction of size 192 to relay server
Received transaction of size 225 from relay server
Received transaction of size 192 from relay server
Sent transaction of size 227 to relay server
Received transaction of size 227 from relay server
Sent transaction of size 615 to relay server
Sent transaction of size 225 to relay server
Received transaction of size 615 from relay server
Received transaction of size 225 from relay server
Sent transaction of size 225 to relay server
Received transaction of size 225 from relay server
Sent transaction of size 257 to relay server
Received transaction of size 257 from relay server
Sent transaction of size 225 to relay server
Received transaction of size 225 from relay server
Sent transaction of size 403 to relay server
Received transaction of size 403 from relay server
Sent transaction of size 259 to relay server
Received transaction of size 259 from relay server
Sent transaction of size 436 to relay server
Received transaction of size 436 from relay server
Sent transaction of size 226 to relay server
Sent transaction of size 225 to relay server
Received transaction of size 226 from relay server
Received transaction of size 225 from relay server
Sent transaction of size 405 to relay server
Received transaction of size 405 from relay server
Sent transaction of size 373 to relay server
Received transaction of size 373 from relay server
Sent transaction of size 226 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 374 to relay server
Received transaction of size 374 from relay server

so it is essentially just sending transactions that I send it back to me. how much bandwidth does this consume?

spin

sr. member

Activity: 362

Merit: 262

Quote from: IYFTech on February 09, 2015, 01:39:29 PM

Quote from: spin on February 09, 2015, 05:41:30 AM

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

EU server working fine here

Yes, also now fine for me.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: spin on February 09, 2015, 05:41:30 AM

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

EU server working fine here

spin

sr. member

Activity: 362

Merit: 262

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

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: Matt Corallo on January 03, 2015, 01:03:36 PM

Quote from: jedimstr on December 23, 2014, 02: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.

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?

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: jedimstr on December 23, 2014, 02: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.

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.

loshia

legendary

Activity: 1610

Merit: 1000

Quote from: jedimstr on December 23, 2014, 02: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.

with v0.10.0rc1 works charming Wink

jedimstr

hero member

Activity: 798

Merit: 1000

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.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: jedimstr on December 23, 2014, 02: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.

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

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: jedimstr on December 23, 2014, 02: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.

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

jedimstr

hero member

Activity: 798

Merit: 1000

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.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: spiccioli on December 21, 2014, 06:17:34 AM

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.

spiccioli

legendary

Activity: 1379

Merit: 1003

nec sine labore

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

hero member

Activity: 755

Merit: 515

Quote from: norgan on December 16, 2014, 06:25:20 AM

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

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

norgan

sr. member

Activity: 308

Merit: 250

Decentralize your hashing - p2pool - Norgz Pool

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

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: IYFTech on December 05, 2014, 02:07:57 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 Wink

entr04y

newbie

Activity: 23

Merit: 0

Quote from: IYFTech on December 05, 2014, 02:07:57 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

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

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

spin

sr. member

Activity: 362

Merit: 262

Quote from: Matt Corallo on November 28, 2014, 01:03:00 PM

You should pm me your ip, I cant reproduce.

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

entr04y

newbie

Activity: 23

Merit: 0

Quote from: Matt Corallo on December 02, 2014, 03:24:08 PM

Quote from: entr04y on December 02, 2014, 09: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)?

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

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