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

Huh, what OS/libc are you on?

Fixed by commenting these out:
I've no idea why it fails the remote connection on my server ...

Whats your connection like? If you have a particularly slow downstream you may get kicked off for not keeping up (this mostly happens if you're trying to connect to a server far away from you). PM me your ip and I'll look up why you got disconnected.

Nope:


...still getting flooded with large tx's all the same size too 

Fixed server memory usage, bumped the buffer size, should work now?

Pulled the latest, compiled without error on 14.04 64bit & it runs - but still getting disconnects in between bandwidth saturation with tx sizes 3404 using the eu node 

Strange, I'm not sure why that would have ever happened...bad connection on your end? Maybe the select loop was slow, though I'm not sure why that would have been....

Strange, the us-west node works for me?

Well the ping times are back to normal now.
I got this one a few hours ago:
Now it's normal.

But still after the pings I only get:

I waited for a block to go by to see if there was any other reply ... but no, since I presume it's not connected anyway.

I'm of course not running 0.11.x since there's no way I'd switch over to that soon after it's release ...
I'm on 0.10.2

It should now work again no matter your bitcoind version, and also compress blocks somewhat OK, though its not working nearly as well as it used to when entire mempools were in cache constantly.

In other news, Ive been digging into relay network in China to better connect the huge percent of the network there. Sadly, peering in Asia, especially with Chinese telecoms generally sucks. Does anyone (or a group of people) have any interest in sponsoring a node on Softlayer (25$/mo) Japan, which seems to be the only well-peered VPS provider in Tokyo?

Yes, it does. Its been on and off due to various bugs, most notably it worked last night and then I woke up and it had deadlocked . In any case, things are stabalizing some now that the network supports crazy over-large mempools (thought I had it working stable-y before the whole spam thing    ).

I'm on 0.11 as well... having just updated and rebuilt the client, this is what I see:

I haven't seen a single received transaction.
EDIT:
Just got my first received transaction:

I am on 0.11 also

I just done a git pull - it's working again, but I'm not receiving - only sending.........

I'm on 0.11 as of recently as well. Perhaps that's the common issue...

I've not been able to get it working since upgrading to Bitcoind v11 a few days ago..........

That is odd. I upgraded this morning and commented out some TX printf's

I see blocks but i am wandering why do i see

???Relay network is using a later version (PLEASE UPGRADE) ??

./relaynetworkclient 127.0.0.1 8333
Server 0 (public.us-east.relay.mattcorallo.com) took 2428 ms to respond 20 times.
Server 1 (public.us-west.relay.mattcorallo.com) took 3741 ms to respond 20 times.
Server 2 (public.eu.relay.mattcorallo.com) took 858 ms to respond 20 times.
Server 3 (public.sgp.relay.mattcorallo.com) took 6142 ms to respond 20 times.
Server 4 (public.jpy.relay.mattcorallo.com) took 5821 ms to respond 20 times.
Using server public.02.relay.mattcorallo.com
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Connected to relay node with protocol version the blocksize
[2015-07-16 05:30:40+00] 00000000000000000e96a0ff24ef141df395d2257f18dca51a65d1482c5b0ec3 recv'd, size 280356 with 282790 bytes on the wire
[2015-07-16 05:33:06+00] 00000000000000000078bd09b27f2cf08088feb9336e45ca629bd4a975d1e0a3 recv'd, size 932873 with 934667 bytes on the wire
[2015-07-16 05:34:20+00] 00000000000000000d1e51d46b6ccf5c54b787a4caef58c3019cb376c76545ea recv'd, size 749130 with 750464 bytes on the wire
[2015-07-16 05:43:45+00] 00000000000000000592738f801e87e8ecd19f1503dd4842f086e47df5f7202b recv'd, size 998191 with 1001090 bytes on the wire
[2015-07-16 05:44:25+00] 000000000000000004e6ce77718d9a42c9024d95b7b8efba45b9f0a47bd376db recv'd, size 209 with 145 bytes on the wire
[2015-07-16 06:07:56+00] 00000000000000001432cd6c4cc7b757f9765a5c8c2f6cdf208202feb5435680 recv'd, size 949143 with 956012 bytes on the wire
public.02.relay.mattcorallo.com Disconnect: failed to read message header (Transport endpoint is not connected)
Relay network is using a later version (PLEASE UPGRADE)
Connected to relay node with protocol version the blocksize
[2015-07-16 06:21:31+00] 0000000000000000012b7407d2546b6f4e669a63876425222ef6677617d05179 recv'd, size 998070 with 1002864 bytes on the wire
Failed to process block from bitcoind (SEEN)
public.02.relay.mattcorallo.com Disconnect: failed to read message header (Transport endpoint is not connected)
Relay network is using a later version (PLEASE UPGRADE)
Connected to relay node with protocol version the blocksize
[2015-07-16 06:23:10+00] 000000000000000001785d0840164a5ef27ecb4d847b7690903fce64ce3b0085 recv'd, size 749191 with 750810 bytes on the wire
[2015-07-16 06:58:56+00] 00000000000000000a8a1e247226a15b3c055ab3e3f13a12e351b6680aadaa15 recv'd, size 830343 with 839567 bytes on the wire
[2015-07-16 07:23:39+00] 00000000000000000220392a7944d4454e0b62903530ce51f9b7c2bcd97d64c0 recv'd, size 266 with 202 bytes on the wire
[2015-07-16 07:26:08+00] 00000000000000000f8f405ce360f6da4744d9a9e0ec71284de1881ae9685011 recv'd, size 989208 with 996552 bytes on the wire
[2015-07-16 07:31:14+00] 00000000000000000018a610c4133feeea6403a5e27876d279ff1804a8daec8c recv'd, size 998087 with 1002056 bytes on the wire
Failed to process block from bitcoind (SEEN)
[2015-07-16 07:55:11+00] 0000000000000000128b4f3fc564bf84c8483d1c87bbe171584c266d43ac1c91 recv'd, size 934443 with 942117 bytes on the wire
[2015-07-16 07:56:12+00] 00000000000000000c09e33dd20f69e76506e6796ec0b44bcdb271e2c604ccf1 recv'd, size 98929 with 99330 bytes on the wire
[2015-07-16 08:11:39+00] 000000000000000014ddf3f1756dded5fd7a39ff3456b682197965267d1dfda6 recv'd, size 492914 with 497943 bytes on the wire
[2015-07-16 08:16:28+00] 0000000000000000033b7f9875e58d51646d6a98b6e2d06faaa13f98900e4207 recv'd, size 186463 with 188302 bytes on the wire
Failed to process block from bitcoind (SEEN)
[2015-07-16 08:20:49+00] 00000000000000000d0870d681ac8a346a596685291f851a58f8b28fa91344d4 recv'd, size 184175 with 185804 bytes on the wire
Failed to process block from bitcoind (SEEN)
[2015-07-16 08:21:33+00] 000000000000000007ee91112a839f09569119925a3f5a433e3afdb90e4615b5 recv'd, size 99994 with 101693 bytes on the wire
Failed to process block from bitcoind (SEEN)
[2015-07-16 08:28:43+00] 000000000000000007ed25a03616c31ea33e54e854f8f6148160520fca58e7d0 recv'd, size 913328 with 916607 bytes on the wire

My relay said
So I obediently upgraded. I can't see any blocks being propagated in the messages any more.

So ... I've been trying to work out what's the actual state of the relay over the past few days.
Anyone got any idea if it is actually working properly?

For the past few days I've only ever been sending transactions, never receiving any except of course if I exit the client and start it again.
Blocks do show up on the relay, but never any received transactions.

I updated the code an hour or so ago and then connected again and now the console shows nothing other than the ping tests and connecting to my bitcoind.

Does no one use it any more?
Does it still work?

Yes. But RelayNetwork depends of you.
So, this is centralization and may be dangerous.
You are able to relay blocks to one pools faster and to other pools slower.
I do not say that you are doing it. But... You have possibility and right to do it.
Even if RelayNetwork is used with the normal BitcoinNetwork.

Except without compressing blocks, which saves a ton of time, which is why the transactions have to be relayed first to begin with