Search results

Yeah that's the problem I am: van82@ladar:~$ p2pool-drk 2014-09-29 23:34:28.222595 p2pool (version 59502b0) 2014-09-29 23:34:28.222773 2014-09-29 23:34:28.222895 Testing bitcoind RPC connection to 'http://127.0.0.1:9998/' with username 'darkcoinrpc'... 2014-09-29 23:34:28.248538...

I have no idea's that can help you but I can share that this is the exact same issue I have had with my p2pool node. I came back to find that p2pool had seg faulted over night. Nothing had chanced on my end then randomly I started seeing the exact same error as you describe after the seg fault...

root@ladar:~# iptables -4 -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination...

Firewall.... LOL? Nah for testing I have iptables empty shouldn't be anything blocking it. It show's its listening for udp port 53 traffic. udp 0 0 0.0.0.0:53 0.0.0.0:*

For shit's and giggle's I have started a second dnsseed on this machine. This one has an AAAA record pointing 1.dnsseed.masternode.io to it's ipv6 address and has the NS record for ipv6.dnsseed.masternode.io. Still can't figure out the query from dig though. evan82:~/>dnsseed -h...

addnode=[2001:19f0:ac00:1c1::64] addnode=[2001:41d0:a:1249::1] addnode=[2a01:4f8:110:522d::2] I have made AAAA records for these: addnode=1.dnsseed.masternode.io addnode=2.dnsseed.masternode.io addnode=3.dnsseed.masternode.io Should also work. Edit: These are just simple AAAA records for...

I do see some references under the darkcoin-dnsseed inside dns.h that seems to say it supports querying of AAAA records. Perhaps there just isn't any yet for it to pickup? evan82@ladar:~/> dig dnsseed.masternode.io AAAA @ladar.masternode.io ;; QUESTION SECTION: ;dnsseed.masternode.io...

Ok those are updated. I'm not really sure how to query the dnsseed in ipv6 have you ever messed with it?

Nope I will go a head and update that. Also I'm attempting to experiment with an ipv6 dnsseed. Do you have any idea if the dnsseed will support an ipv6 seed?

I have brought a node online with another backup copy of the official block explorer. At this point I'm still trying to work out the kinks with fastcgi to display it over port 80. Here is the link till I get that sorted out: http://explorer.masternode.io:8888/chain/Darkcoin Once I get the...

Here is a few more from a test wallet running on Ubuntu 12.04 which is doing 15,000 tDRK for 8 rounds. Probably going to butcher posting these but I think full size is the best way to view them. Shot of the wallet main screen. Shot of the send page when you have activated the advanced options...

I would think he is testing the rejecting of certain wallets but it doesn't make sense why the 13.10 client is throwing that error. I'm not choosing to not pay blocks. This wallet does run some of my testnet tools though so now that its offline so its the p2pool node and the faucet. Problem is...

evan82@klaus:~$ darkcoind getinfo { "version" : 101310, "protocolversion" : 70038, "walletversion" : 60001, ... "testnet" : true, "keypoololdest" : 1409778965, "keypoolsize" : 1001, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "Warning...

I've been trying since last night on three nodes to do 15,000/8 rounds. 2 mac nodes one windows node. No luck as of 13.7 wallet. Just restarted them all with 13.8 wallet.

Since evan is too lazy to make dns records: stratum+tcp://test.mpos.masternode.io:3333 http://test.mpos.masternode.io/ evan82@klaus:~$ dig test.mpos.masternode.io ;; ANSWER SECTION: test.mpos.masternode.io. 299 IN A 54.91.95.14 Also don't forget to register and account and add a...

I'm doing 15000 / 8 rounds on three nodes now. See if I can get them to finish up properly. Anyone else want to join in on that feel free.

I also attempted to denominate large amounts. 1000 / 8 rounds, 5,000/8 rounds, 10,000/8 rounds, 15,000/8 rounds. They all got to various levels of complete but none of them actually finished. Might just be taking time though cause it's a lot of coins to anon.

Thanks! I edited line 22 of /p2pool-drk/p2pool/bitcoin/p2p.py from version=70018 to version=70500 that should do me for all the revision's to come after RC5 launch :)

I have upgraded to wallet 13.7 and my p2pool node is not happy. Before posting this I went back to wallet 13.5 and all was well with p2pool. When on 13.7 as soon as I start p2pool my debug.log from testnet get spammed with the following: 2014-09-11 00:19:48 maxconnections check 248 2014-09-11...

LOL jelly of all our sweet domains. I see what you did there...