Had a lot of trouble with the relay over the past day.
Anyone else seeing problems with us-west?
And like at the moment, I seem to often be the only one sending data to the relay, not receiving anything from the relay.
... it suddenly comes back to life with a truck load of Receives for a very short time, but again now back to only me Sending
Topic: Re: How (and why) to use the Relay Network - page 12. (Read 653 times)
I rearranged my bitcoinds (10 days ago) and ended up with the relay using the external IP
(will fix it next time I restart bitcoind, don't like doing that too often)
Anyway, as a result it got itself banned - seems the relay had a lot of bad transactions 6 hours ago
2015-04-07 16:01:35 Misbehaving: a.b.c.d:33466 (0 -> 10)
2015-04-07 16:25:06 Misbehaving: a.b.c.d:33466 (90 -> 100) BAN THRESHOLD EXCEEDED
That's the first message in the 10 days, then only 24 minutes to hit the threshold
Can you paste the log contents around those lines (ie why it got banned?)(will fix it next time I restart bitcoind, don't like doing that too often)
Anyway, as a result it got itself banned - seems the relay had a lot of bad transactions 6 hours ago
2015-04-07 16:01:35 Misbehaving: a.b.c.d:33466 (0 -> 10)
2015-04-07 16:25:06 Misbehaving: a.b.c.d:33466 (90 -> 100) BAN THRESHOLD EXCEEDED
That's the first message in the 10 days, then only 24 minutes to hit the threshold
Code:
2015-04-07 16:23:53 ERROR: CheckTransaction() : vin empty
2015-04-07 16:23:53 ERROR: AcceptToMemoryPool: : CheckTransaction failed
I'll PM you more of the log 2015-04-07 16:23:53 ERROR: AcceptToMemoryPool: : CheckTransaction failed
I rearranged my bitcoinds (10 days ago) and ended up with the relay using the external IP
(will fix it next time I restart bitcoind, don't like doing that too often)
Anyway, as a result it got itself banned - seems the relay had a lot of bad transactions 6 hours ago
2015-04-07 16:01:35 Misbehaving: a.b.c.d:33466 (0 -> 10)
2015-04-07 16:25:06 Misbehaving: a.b.c.d:33466 (90 -> 100) BAN THRESHOLD EXCEEDED
That's the first message in the 10 days, then only 24 minutes to hit the threshold
Can you paste the log contents around those lines (ie why it got banned?) (will fix it next time I restart bitcoind, don't like doing that too often)
Anyway, as a result it got itself banned - seems the relay had a lot of bad transactions 6 hours ago
2015-04-07 16:01:35 Misbehaving: a.b.c.d:33466 (0 -> 10)
2015-04-07 16:25:06 Misbehaving: a.b.c.d:33466 (90 -> 100) BAN THRESHOLD EXCEEDED
That's the first message in the 10 days, then only 24 minutes to hit the threshold
I rearranged my bitcoinds (10 days ago) and ended up with the relay using the external IP
(will fix it next time I restart bitcoind, don't like doing that too often)
Anyway, as a result it got itself banned - seems the relay had a lot of bad transactions 6 hours ago
2015-04-07 16:01:35 Misbehaving: a.b.c.d:33466 (0 -> 10)
2015-04-07 16:25:06 Misbehaving: a.b.c.d:33466 (90 -> 100) BAN THRESHOLD EXCEEDED
That's the first message in the 10 days, then only 24 minutes to hit the threshold
(will fix it next time I restart bitcoind, don't like doing that too often)
Anyway, as a result it got itself banned - seems the relay had a lot of bad transactions 6 hours ago
2015-04-07 16:01:35 Misbehaving: a.b.c.d:33466 (0 -> 10)
2015-04-07 16:25:06 Misbehaving: a.b.c.d:33466 (90 -> 100) BAN THRESHOLD EXCEEDED
That's the first message in the 10 days, then only 24 minutes to hit the threshold
Well, both US East and US West are dead for me for the last few days. Figured Matt was traveling per his post above so didn't complain.
Matt - Any chance you could just set both US East/West servers to just automatically restart every day at midnight or something?
Just fixed a bug which could cause the resets we've seen. Lets see what happens now..... Matt - Any chance you could just set both US East/West servers to just automatically restart every day at midnight or something?
I think something is wrong with us-east. I'm pointed to us-west now, which is working fine for me.
With us-east, I get messages below. My outbound transactions are working.
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (0: )
Sent transaction of size 373 to relay server
Closing relay socket, failed to read message header (0: )
With us-east, I get messages below. My outbound transactions are working.
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (0: )
Sent transaction of size 373 to relay server
Closing relay socket, failed to read message header (0: )
Well, both US East and US West are dead for me for the last few days. Figured Matt was traveling per his post above so didn't complain.
Matt - Any chance you could just set both US East/West servers to just automatically restart every day at midnight or something?
I think something is wrong with us-east. I'm pointed to us-west now, which is working fine for me.
With us-east, I get messages below. My outbound transactions are working.
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (0: )
Sent transaction of size 373 to relay server
Closing relay socket, failed to read message header (0: )
With us-east, I get messages below. My outbound transactions are working.
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (0: )
Sent transaction of size 373 to relay server
Closing relay socket, failed to read message header (0: )
My relay connection is recently getting banned by bitcoind. Two things have changed for my node. The Linux host is now a VM, although with plenty of resources and running on SSD. And I have recently upgraded bitcoind to v10. The clock is synched via ntp and resources do not appear stressed.
The messages below are from the bitcoind debug log. 192.168.44.100 is one of the local IP's. relaynetworkclient runs on the same Linux VM as bitcoind.
2015-03-21 13:04:21 ERROR: CheckBlock() : hashMerkleRoot mismatch
2015-03-21 13:04:21 ERROR: ProcessNewBlock : CheckBlock FAILED
2015-03-21 13:04:21 Misbehaving: 192.168.44.100:34761 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-03-21 13:04:22 connection from 192.168.44.100:38277 dropped (banned)
relaynetworkclient version below. I did not re-compile after migrating the Linux host to a VM.
relaynetworkclient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=4460be497a8f032b9305ebcd951652a0fe0c29f4, stripped
Hmmmm....there seems to be a bug in the merkle tree parsing somewhere...I'll dig into it a bit later The messages below are from the bitcoind debug log. 192.168.44.100 is one of the local IP's. relaynetworkclient runs on the same Linux VM as bitcoind.
2015-03-21 13:04:21 ERROR: CheckBlock() : hashMerkleRoot mismatch
2015-03-21 13:04:21 ERROR: ProcessNewBlock : CheckBlock FAILED
2015-03-21 13:04:21 Misbehaving: 192.168.44.100:34761 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-03-21 13:04:22 connection from 192.168.44.100:38277 dropped (banned)
relaynetworkclient version below. I did not re-compile after migrating the Linux host to a VM.
relaynetworkclient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=4460be497a8f032b9305ebcd951652a0fe0c29f4, stripped
. That said, you should probably be running on localhost anyway as a malicious actor could potentially get you to ban the relay client (though its not very possible to DoS very significantly over the relay network) So.... are the relays just not being maintained anymore?
No, they are...minimally. Sadly other things are taking precedance, but when I'm not travelling they do get restarted as things fall over .
So.... are the relays just not being maintained anymore?
East Coast still down (connection resets)
(connection resets)
Getting connection resets from the East Coast Node again for the last day or so. On West for now.
You could whitelist the ip of the relayclient in your bitcoin.conf? It should really connect with 127.0.0.1 ip though, if it is running on the same machine.
My relay connection is recently getting banned by bitcoind. Two things have changed for my node. The Linux host is now a VM, although with plenty of resources and running on SSD. And I have recently upgraded bitcoind to v10. The clock is synched via ntp and resources do not appear stressed.
The messages below are from the bitcoind debug log. 192.168.44.100 is one of the local IP's. relaynetworkclient runs on the same Linux VM as bitcoind.
2015-03-21 13:04:21 ERROR: CheckBlock() : hashMerkleRoot mismatch
2015-03-21 13:04:21 ERROR: ProcessNewBlock : CheckBlock FAILED
2015-03-21 13:04:21 Misbehaving: 192.168.44.100:34761 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-03-21 13:04:22 connection from 192.168.44.100:38277 dropped (banned)
relaynetworkclient version below. I did not re-compile after migrating the Linux host to a VM.
relaynetworkclient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=4460be497a8f032b9305ebcd951652a0fe0c29f4, stripped
The messages below are from the bitcoind debug log. 192.168.44.100 is one of the local IP's. relaynetworkclient runs on the same Linux VM as bitcoind.
2015-03-21 13:04:21 ERROR: CheckBlock() : hashMerkleRoot mismatch
2015-03-21 13:04:21 ERROR: ProcessNewBlock : CheckBlock FAILED
2015-03-21 13:04:21 Misbehaving: 192.168.44.100:34761 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-03-21 13:04:22 connection from 192.168.44.100:38277 dropped (banned)
relaynetworkclient version below. I did not re-compile after migrating the Linux host to a VM.
relaynetworkclient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=4460be497a8f032b9305ebcd951652a0fe0c29f4, stripped
Had a quick look at this but couldn't see it was possible.
Would it be much effort to allow it to connect to multiple bitcoinds?
i.e. if you had 2 bitcoinds in a local network, have it talk to both directly
(having 2 local bitcoinds pointing at each other is crap slow and unreliable
)
The somewhat stale branch of https://github.com/TheBlueMatt/RelayNode/commits/for-w does exactly this. It should be an easy rebase. Would it be much effort to allow it to connect to multiple bitcoinds?
i.e. if you had 2 bitcoinds in a local network, have it talk to both directly
(having 2 local bitcoinds pointing at each other is crap slow and unreliable
)
Had a quick look at this but couldn't see it was possible.
Would it be much effort to allow it to connect to multiple bitcoinds?
i.e. if you had 2 bitcoinds in a local network, have it talk to both directly
(having 2 local bitcoinds pointing at each other is crap slow and unreliable)
Would it be much effort to allow it to connect to multiple bitcoinds?
i.e. if you had 2 bitcoinds in a local network, have it talk to both directly
(having 2 local bitcoinds pointing at each other is crap slow and unreliable
) Is there a method to get it to just relay blocks instead of blocks and transactions? It doesn't accept connections to port 8334 anymore, is the only way to do it to modify the source?
That would defeat the purpose. It compresses blocks by pre-relaying transactions. 
ofc ipv6 is unreachable, since I disabled it in sysctl.conf.
If you disable ipv6 in sysctl by removing all ipv6 support things are going to break. You need ipv6 support, though you dont need to have ipv6 configured (it just uses ipv6 sockets for ipv4 because doing both is way too much code complexity)
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
thing going on.
Is there a method to get it to just relay blocks instead of blocks and transactions? It doesn't accept connections to port 8334 anymore, is the only way to do it to modify the source?
East Coast US relay is spouting errors. Using US West for now.
ofc ipv6 is unreachable, since I disabled it in sysctl.conf.
If you disable ipv6 in sysctl by removing all ipv6 support things are going to break. You need ipv6 support, though you dont need to have ipv6 configured (it just uses ipv6 sockets for ipv4 because doing both is way too much code complexity)
Jump to: