|
norgan
|
 |
September 13, 2014, 09:01:51 PM |
|
I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
What am I doing wrong?
10049 == WSAEADDRNOTAVAIL according to http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx. Any chance you're still on XP or have IPv6 explicitly disabled somewhere, which I think I might have broken in a recent push. It's server 2012 r2. I don't think ipv6 is disabled but I'll check. |
|
|
|
|
norgan
|
|
September 13, 2014, 09:13:14 PM |
|
I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
What am I doing wrong?
10049 == WSAEADDRNOTAVAIL according to http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx. Any chance you're still on XP or have IPv6 explicitly disabled somewhere, which I think I might have broken in a recent push. It's server 2012 r2. I don't think ipv6 is disabled but I'll check. It was disabled. Now its enabled but not configured and I still get the same error. I left it running overnight and it started blocking my bitcoind connection and took my node offline. |
|
|
|
|
Matt Corallo (OP)
|
|
September 13, 2014, 11:14:55 PM |
|
It was disabled. Now its enabled but not configured and I still get the same error. I left it running overnight and it started blocking my bitcoind connection and took my node offline.
Might've missed a windows flag, try again with the latest version? |
|
|
|
|
norgan
|
|
September 13, 2014, 11:37:08 PM |
|
It was disabled. Now its enabled but not configured and I still get the same error. I left it running overnight and it started blocking my bitcoind connection and took my node offline.
Might've missed a windows flag, try again with the latest version? Yup, working now. So I just run it along side p2pool and bitcoind right? |
|
|
|
|
Matt Corallo (OP)
|
|
September 14, 2014, 01:22:02 AM |
|
Yup, working now. So I just run it along side p2pool and bitcoind right?
Yupyup, just run and point to nearest relay node and bitcoind. |
|
|
|
|
Matt Corallo (OP)
|
|
September 14, 2014, 02:02:29 AM |
|
Added a list of pools to the second post, respond if you want added to the list.
|
|
|
|
|
norgan
|
|
September 14, 2014, 07:19:13 AM
Last edit: September 14, 2014, 07:29:21 AM by norgan |
|
Added a list of pools to the second post, respond if you want added to the list.
Norgzpool AU pool now running relay. will add to Singapore node as well shortly. Matt, do you need an Australian server? I have a 50mbit Fibre link that I could run a server behind, in the next month or two i'll have some Azure compute in AU also. |
|
|
|
|
Matt Corallo (OP)
|
|
September 14, 2014, 09:01:55 AM |
|
Norgzpool AU pool now running relay. will add to Singapore node as well shortly.
Matt, do you need an Australian server? I have a 50mbit Fibre link that I could run a server behind, in the next month or two i'll have some Azure compute in AU also.
Hmm, for now I think I'm gonna avoid listing every public p2pool node or pools without at least a few hundred THash/s mining on them. |
|
|
|
|
norgan
|
|
September 14, 2014, 09:04:49 AM |
|
Norgzpool AU pool now running relay. will add to Singapore node as well shortly.
Matt, do you need an Australian server? I have a 50mbit Fibre link that I could run a server behind, in the next month or two i'll have some Azure compute in AU also.
Hmm, for now I think I'm gonna avoid listing every public p2pool node or pools without at least a few hundred THash/s mining on them. yeah fair enough, I looked at the list after and realised it was more pools rather than nodes. no probs. |
|
|
|
|
smoothrunnings
|
|
September 17, 2014, 12:58:10 AM |
|
I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
What am I doing wrong?
10049 == WSAEADDRNOTAVAIL according to http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx. Any chance you're still on XP or have IPv6 explicitly disabled somewhere, which I think I might have broken in a recent push. It's server 2012 r2. I don't think ipv6 is disabled but I'll check. It was disabled. Now its enabled but not configured and I still get the same error. I left it running overnight and it started blocking my bitcoind connection and took my node offline. Disable the firewall. |
|
|
|
|
|
norgan
|
|
September 17, 2014, 01:02:08 AM |
|
I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
What am I doing wrong?
10049 == WSAEADDRNOTAVAIL according to http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx. Any chance you're still on XP or have IPv6 explicitly disabled somewhere, which I think I might have broken in a recent push. It's server 2012 r2. I don't think ipv6 is disabled but I'll check. It was disabled. Now its enabled but not configured and I still get the same error. I left it running overnight and it started blocking my bitcoind connection and took my node offline. Disable the firewall. nah it was a broken build. the firewall was off  |
|
|
|
|
norgan
|
|
September 17, 2014, 04:10:18 AM |
|
So far so good! 4 good blocks no orphan and no stale. (small I know) it's been tricky in AU to find good peers to reduce orphan blocks but this may be a good way to bring some of that latency.
|
|
|
|
jonnybravo0311
Legendary
 Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
September 17, 2014, 02:41:07 PM |
|
Hey Matt, I ran into a problem running the c++ client today. I did a git pull and rebuilt; however, when I started it up, I ran into this: miner@devildog:~/RelayNode/client$ ./relaynetworkclient public.us-east.relay.mattcorallo.com 127.0.0.1 8333
terminate called after throwing an instance of 'std::system_error'
what(): Enable multithreading to use std::thread: Operation not permitted
Aborted (core dumped)
I had to tweak the make.sh script as follows: g++ $DEFINES -std=c++11 -Wl,--no-as-needed -Wall -I. -I/usr/include ./client.cpp ./flaggedarrayset.cpp ./utils.cpp ./p2pclient.cpp ./crypto/sha2.cpp -o relaynetworkclient -pthread
Notice the inclusion of the "-Wl,--no-as-needed". There's apparently a known bug with gcc and Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1228201. Anyway, if anyone is having an issue getting the c++ client running on Ubuntu 14.04 LTS, editing the make.sh script as I have above, and recompiling the client will solve your problems. |
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
cypherdoc
Legendary
Offline
Activity: 1764
Merit: 1002
|
|
September 20, 2014, 08:03:47 PM |
|
Anyone know if Btcguild is running a relay node?
|
|
|
|
|
|
Matt Corallo (OP)
|
|
September 20, 2014, 08:06:31 PM |
|
Anyone know if Btcguild is running a relay node?
Read the second post  |
|
|
|
amaclin
Legendary
Offline
Activity: 1260
Merit: 1019
|
|
September 21, 2014, 06:28:35 PM |
|
what port does relaynetwork use?
8335 or 8336?
|
|
|
|
|
|
norgan
|
|
September 21, 2014, 11:42:06 PM |
|
Matt, looks like you have an issue with the SG node.
|
|
|
|
|
Matt Corallo (OP)
|
|
September 22, 2014, 05:58:31 AM |
|
what port does relaynetwork use?
8335 or 8336?
8336 Matt, looks like you have an issue with the SG node.
Strange, can you double-check now...there was a bug due to bitcoind banning relay servers... |
|
|
|
|
norgan
|
|
September 22, 2014, 05:59:28 AM |
|
what port does relaynetwork use?
8335 or 8336?
8336 Matt, looks like you have an issue with the SG node.
Strange, can you double-check now...there was a bug due to bitcoind banning relay servers... looks fine now, thanks. |
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
September 23, 2014, 09:54:43 AM |
|
I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
What am I doing wrong?
I'm getting this too with the windows exe client on Win7. It eventually killed my TCP/IP stack, all programs were getting TCP/IP errors until I killed the relay client. Going back to the python version here. M |
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me! |
|
|
|
