|
IYFTech
|
 |
February 09, 2015, 06:39:29 PM |
|
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
|
|
February 10, 2015, 02:07:43 PM |
|
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. |
If you liked this post buy me a beer. Beers are quite cheap where I live!
bc1q707guwp9pc73r08jw23lvecpywtazjjk399daa
|
|
|
zvs
Legendary
 Offline
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
|
|
February 27, 2015, 07:14:48 PM
Last edit: February 27, 2015, 08:15:01 PM by zvs |
|
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. 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 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 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? |
|
|
|
|
|
Matt Corallo (OP)
|
|
February 27, 2015, 10:22:50 PM |
|
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) |
|
|
|
|
jedimstr
|
|
March 11, 2015, 10:32:40 PM |
|
East Coast US relay is spouting errors. Using US West for now.
|
|
|
|
zvs
Legendary
Offline
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
|
|
March 16, 2015, 11:27:43 AM |
|
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) Yah, had the 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? |
|
|
|
|
|
Matt Corallo (OP)
|
|
March 19, 2015, 04:55:20 AM |
|
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. |
|
|
|
kano
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
March 19, 2015, 05:32:17 AM |
|
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  ) |
|
|
|
|
Matt Corallo (OP)
|
|
March 19, 2015, 07:26:00 PM |
|
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. |
|
|
|
|
MissouriMiner
|
|
March 22, 2015, 11:06:33 PM |
|
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
|
|
|
|
|
|
spin
|
|
March 22, 2015, 11:16:58 PM |
|
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.
|
If you liked this post buy me a beer. Beers are quite cheap where I live!
bc1q707guwp9pc73r08jw23lvecpywtazjjk399daa
|
|
|
|
jedimstr
|
|
March 24, 2015, 11:48:56 AM |
|
Getting connection resets from the East Coast Node again for the last day or so. On West for now.
|
|
|
|
|
jedimstr
|
|
March 25, 2015, 12:30:21 PM |
|
East Coast still down  (connection resets) |
|
|
|
|
jedimstr
|
|
March 28, 2015, 01:42:01 PM |
|
So.... are the relays just not being maintained anymore?
|
|
|
|
|
Matt Corallo (OP)
|
|
March 30, 2015, 06:57:14 PM |
|
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 . |
|
|
|
|
Matt Corallo (OP)
|
|
March 30, 2015, 08:06:25 PM |
|
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 . 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) |
|
|
|
|
MissouriMiner
|
|
April 02, 2015, 10:03:39 PM |
|
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: )
|
|
|
|
|
|
jedimstr
|
|
April 06, 2015, 10:36:49 AM |
|
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: )
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? |
|
|
|
|
Matt Corallo (OP)
|
|
April 07, 2015, 01:39:23 AM |
|
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..... |
|
|
|
kano
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
April 07, 2015, 10:32:45 PM |
|
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 |
|
|
|
|
