just need some quick assistance. make -f makefile.unix USE_UNPN=-
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/don/Downloads/primecoin/src -I/home/don/Downloads/primecoin/src/obj -DUSE_UPNP=0 -DUSE_IPV6=1 -I/home/don/Downloads/primecoin/src/leveldb/include -I/home/don/Downloads/primecoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/alert.d -o obj/alert.o alert.cpp
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
make: *** [obj/alert.o] Error 4
when i try to compile the primecoind i keep getting this error. note: i have other wallets compiled with this ubuntu 12.04 server so i know i have all the requirements for those. Thanks |
|
|
|
By main node i take it you mean the bootstrap address from the networks.py? Interesting observations.
yup |
|
|
|
Did you install the yac scrypt module (python setup.py install in the yac-script dir)?
Yeah orphan rate is pretty high today... luckily it's not permanent. Still wonder why this p2pool version is so prone to orphans.
i'm pretty sure this is the problem. you gotta check your router / firewall settings. using this new code for 10 sec shares causes high amounts of tcp connections to be open, hence you guys were getting "too many files open" with this new code over the original p2pool source. digging deeper my firewall is dropping connection once it reaches it's peak open connection count causing orphans. well really causing our pools to be out of sync per say. to resolve this issue: (I believe, i can be wrong about this) Main node must be restarted to drop all the connection and start again. but with in 8 - 10 hours it will be the same again. or change firewall to drop tcp connection every 5 min or less. |
|
|
|
i think it's happeninig again. last 5 block orphns 94188 Fri Jun 14 2013 22:00:12 GMT-0400 (EDT) 0000000014041567626a53b12a712f3c2ad5db2af5e316397048efc24067a097 →
94187 Fri Jun 14 2013 21:59:07 GMT-0400 (EDT) 00000000d6e1d199dbb257297ee821bf97ef2bba6865bc9512a34e997f084fe9 →
94167 Fri Jun 14 2013 21:41:25 GMT-0400 (EDT) 00000000b4ecce6c8c9fb8f70774af458b8b1cb7a59f9d3c815f42ed72f09bd6 →
94154 Fri Jun 14 2013 21:33:25 GMT-0400 (EDT) 0000000062ae0b29fdd2e384d0cdb04160bbab273cc7089b47364820bcd8f59c →
94123 Fri Jun 14 2013 21:09:31 GMT-0400 (EDT) 00000000acdc3b237f89848bbd8a5057785265bfba9faa7ca32d264230297f56 →
94104 Fri Jun 14 2013 20:48:40 GMT-0400 (EDT) 00000000b71495cb571d8c1cca72899442d269d48cc9b884cec5e830bd78cbe2 → |
|
|
|
Looks like pos+pow combo is painfull when reorganize and orphan lots of blocks :/
Thats why I change payment for last 10 blocks, orphans will happen.
Also updated git to make share chain persist and not download it every time on pool restart.
i had mine set to true since the started with your code few days ago. |
|
|
|
Total Hash: 71.2MH/s Round Shares: 2818 Round Time: 0:30 difficulty: 0.93 that's the stats from yac.ltcoin.net with 71 mhs it's taking 30+ mins to find a block. is something going on with chain? like this? WindMaster:
"PoS blocks 91036 and 91037 were staked by someone operating off-network (whether intentionally or unintentionally) and then reintroduced to the network, triggering the reorg and orphaning 75 blocks. Anyone here have really good familiarity with the Novacoin PoS code?" https://bitcointalk.org/index.php?topic=206577.640 |
|
|
|
Honestly no. I restarted my yacoind and p2pool services but if that won't work i guess we'll have to change again...
i restarted a few time, but still nope. orphan galore |
|
|
|
That's weird, last one was solved Fri Jun 14 2013 19:27:47 GMT+0200, only orphans since then.  ya, that's what got me looking. any ideas? |
|
|
|
it seems that our pools are out of sync with actual chain. i don't know if i'm saying that right. example yac.ltcoin.pl 06-15 04:04:41 00:00:40 phillip0101 93696 399 our p2pools 93696 Fri Jun 14 2013 16:04:02 GMT-0400 (Eastern Daylight Time) we submitted for the block 41 seconds before them and still we are orphaned. or i could just be paranoid. our last 10~ or so blocks was the same way |
|
|
|
i have a problem sending funds when i do yacoind sendtoaddress xxxxxxx xx
i get error: {"code":-4,"message":"Error: Transaction creation failed "}
thanks in advanced Ill try and help although ive never used yacoind to send funds Firstly make sure your yacoind is synced first before you try sending funds type yacoind getinfo to check your balence to make sure you have funds then yacoind getmininginfo to see what block your daemon is synced to as of right now mine says 88886 if its not synced then it wont let you send funds if it is synced let me know if that helps i understand your running your own p2pool node i have one also but havent sent funds from it yet and im not sure if you are able to send while its running with python as ive never tried yes it is synced up, and yes i am runing my own p2pool node. i turned it off and tried to send payment. no good. try restarting it with the -rescan command it could be a number of things any chance you have looked at the debug log maybe there are too many inputs also are you accounting for the transaction fee its hard to help if we i cant see any logs because that error would come up for a number of reasons you can try running it with the command yacoind -rescan -keypool 1000 Break the amount you want to send into few smaller ones. It is very likely that you are attempting to send so much inputs that YACoin client refuses to create such transaction due to transaction size and / or fee limits. As far as I know, -keypool value works only when making new wallet. It specifies the number of keys wallet is to keep as reserve at all times and it is useful only if person is not making wallet backups frequently but regulary and frequently creates many new addresses for receiving coins. If both criteria are fulfilled but person uses default keypool of 100, it can happen that when rolling back to old backup some coins will be missing due to keypool of old wallet being exhausted, e.g. newer wallet "knows" more used keys than older one. Thats correct its for creating reserve addresses I was trying to get him to throw random ideas at the problem notice how i didnt format -keypool 1000 properly that was also a work of deductive arts  Sherlock would be so proud, but thanks mate so this is what i have tried so far. breaking it into smaller portions., i have a total of 100 yac stuck in there. went from trying to pull 90 to 45 to 1 and still get the error. removed everything and allow to redownload block chain. still error moved wallet to windows 7 with yac client. shows the amount. but still same error. i'm out of idea  Can i have you address ill send you a chunk of YAC and see if you can send it back didn't give that a try yet. i'll send my self yac. don't want you getting yours stuck in my blackhole wallet. thanks for this advice |
|
|
|
i have a problem sending funds when i do yacoind sendtoaddress xxxxxxx xx
i get error: {"code":-4,"message":"Error: Transaction creation failed "}
thanks in advanced Ill try and help although ive never used yacoind to send funds Firstly make sure your yacoind is synced first before you try sending funds type yacoind getinfo to check your balence to make sure you have funds then yacoind getmininginfo to see what block your daemon is synced to as of right now mine says 88886 if its not synced then it wont let you send funds if it is synced let me know if that helps i understand your running your own p2pool node i have one also but havent sent funds from it yet and im not sure if you are able to send while its running with python as ive never tried yes it is synced up, and yes i am runing my own p2pool node. i turned it off and tried to send payment. no good. try restarting it with the -rescan command it could be a number of things any chance you have looked at the debug log maybe there are too many inputs also are you accounting for the transaction fee its hard to help if we i cant see any logs because that error would come up for a number of reasons you can try running it with the command yacoind -rescan -keypool 1000 Break the amount you want to send into few smaller ones. It is very likely that you are attempting to send so much inputs that YACoin client refuses to create such transaction due to transaction size and / or fee limits. As far as I know, -keypool value works only when making new wallet. It specifies the number of keys wallet is to keep as reserve at all times and it is useful only if person is not making wallet backups frequently but regulary and frequently creates many new addresses for receiving coins. If both criteria are fulfilled but person uses default keypool of 100, it can happen that when rolling back to old backup some coins will be missing due to keypool of old wallet being exhausted, e.g. newer wallet "knows" more used keys than older one. Thats correct its for creating reserve addresses I was trying to get him to throw random ideas at the problem notice how i didnt format -keypool 1000 properly that was also a work of deductive arts Sherlock would be so proud, but thanks mate so this is what i have tried so far. breaking it into smaller portions., i have a total of 100 yac stuck in there. went from trying to pull 90 to 45 to 1 and still get the error. removed everything and allow to redownload block chain. still error moved wallet to windows 7 with yac client. shows the amount. but still same error. i'm out of idea |
|
|
|
Looks like we catch some orphans Those "doubles" seems to be found by different nodes/miners. Probably they have high GBT latency. 2 of them are relayed by 108.58.12.54 ohphans drunk on long island ice tea no doubt but you would think our chain would have been trusted more but anyhow i really think we need to get everyone back into the one pool again that's my ip.. is there something wrong with my pool? |
|
|
|
|
is something going on with our nodes? the last 12 or so blocks are all orphans
|
|
|
|
Same. We just found the first 2 blocks in 3 minutes.  yup sweet deal. now if we can get caish5 to come over with his 1.5 mhs rate we will be sitting pretty  |
|
|
|
My YAC node also crashed. But, if you changing network options you should also change hexes and p2p port and DELETE current share chain. I made some modifications and run my node https://github.com/Rav3nPL/p2pool-yacTry it if you want. Best way to git clone it to new directory. Changed: - payout for 12hrs - pay for up to 10 blocks - share period 10 seconds - diff retarget for 30 shares (5 minutes) - my node as seed node - p2p port 8337 - hexes to not mess another chains ok i cloned your git gonna see how this runs. so far so good no error p2pool.dsync.net:21112edit very good so far no error like before. very low doa 2% on my pool with 300 kHs |
|
|
|
ok does anyone reconize this IP 196.210.238.252 it was running fine for about 5 mins until 2013-06-12 11:03:47.881368 Processing 321 shares from 196.210.238.252:35341...
2013-06-12 11:03:49.219032 > Share check failed:
|
|
|
|
lol i just blocked running solo. me so lucky! ok i'm going try to merge our pool again to bitvolcano |
|
|
|
It seems to work ok on my end now, half errors, half hashes. I thought maybe it's a miner submitting wrong shares, but i don't know if that's possible or how to interpret these errors exactly: 2013-06-12 14:46:50.033906 > --- <exception caught here> ---
2013-06-12 14:46:50.033943 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/data.py", line 531, in attempt_verify
2013-06-12 14:46:50.033979 > share.check(self)
2013-06-12 14:46:50.034015 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/data.py", line 420, in check
2013-06-12 14:46:50.034062 > raise ValueError('''gentx doesn't match hash_link''')
2013-06-12 14:46:50.034101 > exceptions.ValueError: gentx doesn't match hash_link
2013-06-12 14:46:50.039057 > Traceback (most recent call last):
2013-06-12 14:46:50.039114 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 125, in maybeDeferred
2013-06-12 14:46:50.039154 > result = f(*args, **kw)
2013-06-12 14:46:50.039192 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/node.py", line 362, in clean_tracker
2013-06-12 14:46:50.039230 > self.set_best_share()
2013-06-12 14:46:50.039267 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/node.py", line 307, in set_best_share
2013-06-12 14:46:50.039305 > best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2013-06-12 14:46:50.039346 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/data.py", line 560, in think
2013-06-12 14:46:50.039474 > if self.attempt_verify(share):
2013-06-12 14:46:50.039520 > --- <exception caught here> ---
2013-06-12 14:46:50.039566 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/data.py", line 531, in attempt_verify
2013-06-12 14:46:50.039607 > share.check(self)
2013-06-12 14:46:50.039644 > File "/home/eule/yacpool/yacoin-p2pool/p2pool/data.py", line 420, in check
2013-06-12 14:46:50.039681 > raise ValueError('''gentx doesn't match hash_link''')
2013-06-12 14:46:50.039718 > exceptions.ValueError: gentx doesn't match hash_link
2013-06-12 14:46:50.042168 Punishing share for 'Block-stale detected! 254d3d07aa8a2a13d8618fa0f2f18173b189cd378932bae37d978bf2 < f1f0eb0dd6bc2969c9eab8b90317fc61cc7642d5684fd78e048c63a0'! Jumping from 10b03540 to bb87c541!
2013-06-12 14:46:51.310158 Handshake timed out, disconnecting from 87.98.221.175:12579
2013-06-12 14:46:51.614171 Worker YHCkUR2vbx489YDCXGGVrDTAfSKqasEc31 submitted share with hash > target:
2013-06-12 14:46:51.614284 Hash: 4bfac64144234f297f60fb5d0aa525137d3a9a1a1fbaa488fbe177089c5f
2013-06-12 14:46:51.614353 Target: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2013-06-12 14:46:51.637508 Handshake timed out, disconnecting from 192.69.192.202:12579
2013-06-12 14:46:51.910433 Worker YHCkUR2vbx489YDCXGGVrDTAfSKqasEc31 submitted share with hash > target:
2013-06-12 14:46:51.910631 Hash: 30ebf86e6b1ab899bb9729f944dcc990cd6ab050381a22fa6f191cf64f82
I think the errors begin immediately after workers begin connecting and delivering work. Pool address is http://yacpool.tk:8838. can you check your network.py share_period=15 i just saw a ealier post caish5 didn't put a block comment to change it to 15 instead of 3 |
|
|
|
looks pretty much the same to me. this is my /bitcoin/network.py nets = dict(
yacoin=math.Object(
P2P_PREFIX='d9e6e7e5'.decode('hex'),
P2P_PORT=7688,
ADDRESS_VERSION=77,
RPC_PORT=8344,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'yacoinaddress' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda target: get_subsidy(6, 100, target),
BLOCKHASH_FUNC=lambda header: pack.IntType(256).unpack(__import__('yac_scrypt').getPoWHash(header, data.block_header_type.unpack(header)['ti$
POW_FUNC=lambda header: pack.IntType(256).unpack(__import__('yac_scrypt').getPoWHash(header, data.block_header_type.unpack(header)['timestam$
BLOCK_PERIOD=60, # s
SYMBOL='YAC',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'yacoin') if platform.system() == 'Windows' else os.path.expanduser($
BLOCK_EXPLORER_URL_PREFIX='http://yacexplorer.tk/block/',
ADDRESS_EXPLORER_URL_PREFIX='http://yacexplorer.tk/address/',
SANE_TARGET_RANGE=(2**256//2**20//1000 - 1, 2**256//2**20 - 1),
),
|
|
|
|
|
Show Posts
