Topic: Re: How (and why) to use the Relay Network - page 15. (Read 653 times)
Yup, EU relay has gone bonkers too - switching off for the time being
Sigh,
seems like another relay ddos.
Lots of txns over a short period of time followed by
"Closing relay socket, got freely relayed transaction too large (0: )"
Happening repeatedly.
seems like another relay ddos.
Lots of txns over a short period of time followed by
"Closing relay socket, got freely relayed transaction too large (0: )"
Happening repeatedly.
Hey Matt, Aussie node is playing up.
Indeed, it appears the host decided to reboot the server without warning (WTF?) and it didnt come back up properly.
Hey Matt, Aussie node is playing up.
EDIT - It's working. Dumb newbie (rushing) mistake. 
I forgot to open 8336 outbound on my firewall (iptables).
I have a couple of newbie questions. (I've been running p2pool for a long time, but not your relay client.)
How do we verify the client is working?
- I already had p2pool running, and ran "./relaynetworkclient public.us-east.relay.mattcorallo.com 127.0.0.1 8333" in a separate screen session.
- I see "Closing relay socket, failed to connect() (110: Connection timed out)" every so often, but this appears to be normal based on forum discussion.
Do I need to port forward 8336?
If yes, can I specify a different port?
I forgot to open 8336 outbound on my firewall (iptables).How do we verify the client is working?
- I already had p2pool running, and ran "./relaynetworkclient public.us-east.relay.mattcorallo.com 127.0.0.1 8333" in a separate screen session.
- I see "Closing relay socket, failed to connect() (110: Connection timed out)" every so often, but this appears to be normal based on forum discussion.
Do I need to port forward 8336?
If yes, can I specify a different port?
We now have an Australian node! Those of you already using the 'au' region should (at max) simply need to restart your client to connect to it, otherwise switch to the au region. Thanks to forum member norgan for providing the server.
US East Coast relay seems to be down. West is fine.
Ugh, yea, I think it ran out of fds, but I'm adding a bit more logging to be sure...It has been restarted and is working now, but I'll watch for further issues. US East Coast relay seems to be down. West is fine.
Confirmed east=down/west=fine from my side 
US East Coast relay seems to be down. West is fine.
eu server is back online
us-east did not work for long and shows same issue as eu 's one since about this morning
us-west working correctly
us-west working correctly
Code:
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Closing relay socket, failed to read message header (10054: Unknown error)
Finished connect handshake with bitcoind
Closing relay socket, failed to read message header (10054: Unknown error)
Some sort of oversize error (repeatedly) going on at the moment.
Getting this each time:
"Closing relay socket, got freely relayed transaction too large (0: )"
after a whole lot of txns (including some > 25k in size)
(about every 20s)
A ddos?
Edit: 20 minutes later still happening.
The main issue with it is that it's passing all the spam to bitcoind that's then rejecting it all.
Anyone know what's going on?
Looks like I'm gonna have to stop my relay
Edit2:
Yep had to kill it:
2014-10-26 12:04:25 Misbehaving: 127.0.0.1:45659 (10200 -> 10300) BAN THRESHOLD EXCEEDED
2014-10-26 12:04:25 Warning: not banning local node 127.0.0.1:45659!
Since the relay is local, bitcoind wont ignore it.
Edit3:
Restarted the relay and the spammer has gone now.
Getting this each time:
"Closing relay socket, got freely relayed transaction too large (0: )"
after a whole lot of txns (including some > 25k in size)
(about every 20s)
A ddos?
Edit: 20 minutes later still happening.
The main issue with it is that it's passing all the spam to bitcoind that's then rejecting it all.
Anyone know what's going on?
Looks like I'm gonna have to stop my relay
Edit2:
Yep had to kill it:
2014-10-26 12:04:25 Misbehaving: 127.0.0.1:45659 (10200 -> 10300) BAN THRESHOLD EXCEEDED
2014-10-26 12:04:25 Warning: not banning local node 127.0.0.1:45659!
Since the relay is local, bitcoind wont ignore it.
Edit3:
Restarted the relay and the spammer has gone now.
Getting socket errors every so often on the us-west here.
(the main issue with this is that it just sits there stalled for quite a while until it spits out the socket error message)
Seems to be all OK now - no errors in my screen scroll back buffer (which is about 20 minutes) but there were regular ones last night.(the main issue with this is that it just sits there stalled for quite a while until it spits out the socket error message)
I have 2 nodes, current pool and where I'm moving it, and they are both now putting out messages in sync.
Some kind of auto-switching to a working/fastest/less loaded server would be invaluable too......?
Getting socket errors every so often on the us-west here.
(the main issue with this is that it just sits there stalled for quite a while until it spits out the socket error message)
(the main issue with this is that it just sits there stalled for quite a while until it spits out the socket error message)
Yup, same here with the EU node.......
same issue for two days now, I'll switch to us-east this evening
I decided to connect to two nodes and forget about it. One will usually be working...
Getting lots of
Code:
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (104: Connection reset by peer)
On the EU node. us-east working fine for me.Closing relay socket, failed to read message header (104: Connection reset by peer)
Yup, same here with the EU node.......
Getting lots of
Code:
Closing relay socket, failed to read message header (0: )
Closing relay socket, failed to read message header (104: Connection reset by peer)
On the EU node. us-east working fine for me.Closing relay socket, failed to read message header (104: Connection reset by peer)
Jump to: