yes of course, running a second is impossible [ /quote]
What about chrooted bitcoind? Put it in jail perhaps
Why would you want two separate bitcoind's on the same machine? What problem are you trying to solve? You can run one instance for mining --without-wallet and other for coins maybe, security..
|
|
|
yes of course, running a second is impossible [/quote]
What about chrooted bitcoind? Put it in jail perhaps
|
|
|
Sun Jun 22 2014 11:59:24 GMT+0300 (EEST) 0.0489 Sun Jun 22 2014 11:56:36 GMT+0300 (EEST) 0.0662 Sun Jun 22 2014 11:53:48 GMT+0300 (EEST) 0.0334 Sun Jun 22 2014 11:51:00 GMT+0300 (EEST) 0.0242 Sun Jun 22 2014 11:48:12 GMT+0300 (EEST) 0.0162 Sun Jun 22 2014 11:45:24 GMT+0300 (EEST) 0.0175
This is getblocktemplate latency with 0.0001 fees...
.bitcoin .namecoin .devcoin .fusioncoin .ixcoin directorys are moved to a small 60gb ssd with nothing else there as mentioned earlier.
If blocks gets corrupted, its only umount /home/username/.coindir and restart client not the bootstrap project - if you have it there, then when its up to date shutdown client and cp -Rp /home/username/.coindir /mnt/.coindir remount it and restart client...
|
|
|
Can Coin Cadence P2P Bitcoin Mining Pool frontend be dowloaded , it doesnt look so "beta" to me, I think it looks great and want to try it because it has many things in one place...
|
|
|
blockprioritysize=0 prevents 0 fee transactions
On my node, I set that to 196kB out of 500kB. The fees are mainly to prevent spam, and are mainly a bonus at this point. Between 12% hardware error rate, 20% penalty for no long polling, and another 10% for slow CPU lag (probably 3 seconds), I am getting 43% local DOA though. Hard numbers?
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
Is that reliant on bitcoind only or also peers? I've been doing some tuning of bitcoind but struggle to keep it below 0.5 secs and not topping 1s. Is that a bitcoind issue or a p2pool issue? Its not p2pool issue, use ssd disk and should be able to put blockprioritysize=0 #blockminsize=2000 blockmaxsize=1000000 mintxfee=0.00001 minrelaytxfee=0.00001 With just 0.2s, with merged mining namecoin, fusioncoin, ixcoin and devcoin i'm using fc disk and large caching. I've not seen blockprioritysize=0 before. that does that do? also do you set maxconnections? If i put maxconnections over 20 bitcoind starts to upload blocks with all upload bw, so I keep it 19 blockprioritysize=0 prevents 0 fee transactions thanks, I've just set blockprioritysize and it looks like latency is down lower than its been. now around 0.2~0.3 but will monitor. ive got maxconns at 20. did you find that extra 1 really made a difference? I have a 50mbit fibre link that achieves up to 70mbit up so I don't think i'll have any bandwidth issues with maxconns. I can go with 40 (10mbit up) but hasnt found it useful, no deads with 19... Ants seems to find shares just as easy with those settings mintxfee=0.00001 minrelaytxfee=0.00001 as 0.1 so it works here just fine with lots of transactions.. In fact when setting those to 0.1 to have blocktemplate to some ms, ants starts to submit share more than once..
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
Is that reliant on bitcoind only or also peers? I've been doing some tuning of bitcoind but struggle to keep it below 0.5 secs and not topping 1s. Is that a bitcoind issue or a p2pool issue? Its not p2pool issue, use ssd disk and should be able to put blockprioritysize=0 #blockminsize=2000 blockmaxsize=1000000 mintxfee=0.00001 minrelaytxfee=0.00001 With just 0.2s, with merged mining namecoin, fusioncoin, ixcoin and devcoin i'm using fc disk and large caching. I've not seen blockprioritysize=0 before. that does that do? also do you set maxconnections? If i put maxconnections over 20 bitcoind starts to upload blocks with all upload bw, so I keep it 19 blockprioritysize=0 prevents 0 fee transactions If Your home directory is on normal hd and system runs on ssd or theres mounted an ssd on /mnt/ put this on your /etc/fstab /mnt/.bitcoin /home/usrername/.bitcoin none bind 0 0 then as root cp -Rp /home/username/.bitcoin /mnt/.bitcoin mount it mount /home/username/.bitcoin Then its on ssd
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
Is that reliant on bitcoind only or also peers? I've been doing some tuning of bitcoind but struggle to keep it below 0.5 secs and not topping 1s. Is that a bitcoind issue or a p2pool issue? Its not p2pool issue, use ssd disk and should be able to put blockprioritysize=0 #blockminsize=2000 blockmaxsize=1000000 mintxfee=0.00001 minrelaytxfee=0.00001 With just 0.2s, with merged mining namecoin, fusioncoin, ixcoin and devcoin
|
|
|
Looks very good to me, great work
|
|
|
So we should donate to an expert who makes the frontend that works and has maybe the same info as p2poolinfo once had..
|
|
|
so I was digging around and found some settings that may help with p2pool.
In cgminer and bfgminer there are options for --scan-time and --expiry also queue
I read that --scan-time 1 --expiry 1 and queue set to 0 is best for p2pool.
I managed to add these to my antminer so will monitor how it goes.
to do so you can edit \etc\init.d\cgminer and add in the PARAMS= section
e.g. PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb --api-listen --scan-time 1 --expiry 1"
queue = 0 is already in the \etc\Config\cgminer file from Bitmain.
norgan, check ./cgminer-api config , what is the value for queue there?. Ahh I was looking under \etc I'll have a look when I get back home. What should it be? on the s1 there is no cgminer-api file. (I only use cgminer on the ant, for everything else I used bfg+multiminer) Its there man, root@antMiner:/usr/bin# ls -larths 0 drwxrwxr-x 1 root root 0 Dec 2 2013 .. 9 -rwxr-xr-x 1 root root 9.1K Dec 25 13:48 lua 7 -rwxr-xr-x 1 root root 7.0K Dec 25 14:20 jshn 12 -rwxr-xr-x 1 root root 11.8K Dec 25 14:24 luci-bwc 355 -rwxr-xr-x 1 root root 354.8K Feb 6 22:57 cgminer.original 1 -rwxr-xr-x 1 root root 681 Feb 6 22:57 cgminer-monitor.original 6 -rwxr-xr-x 1 root root 6.0K Feb 6 22:57 cgminer-api
you can do it from your pc aswell if you want to, you can point cgminer-api at your S1. Just do ./cgminer-api summary IP_OF_YOUR_S1 bfgminer-rpc will work also. I was looking in \etc what am I looking for in cgminer-API? I'll check it out when I get home. Bfgminers miner.php works just great with ants1 https://forums.butterflylabs.com/blogs/ivan-frimmel/133-setting-up-bfgminer-rpc-access-miner-php-remote-status-update-windows-7-a.htmlJust needs webserver, apache and php, its fast and easy. Add rigs to $rigs = array('192.168.11.50','192.168.11.51','192.168.11.52','192.168.11.220'); or # Set $mcast to true to look for your rigs and ignore $rigs $mcast = false; to true Doa dropped with --scan-time 1 --expiry 1, thats good
|
|
|
Does anyone know of a p2pool node in Iceland?
Is the percent of orphan/dead shares "lost" between the miner and the pool or between the pool and the network?
Ive got 2,5% orphan rate last week http://p2pool.servebeer.com:9332/static/graphs.html?Week 4% last month no deads in the graphic - its so low dead rate Located in Finland
|
|
|
All make commands could go like make -j12.... if you have lets say 8 cores, it makes it alot faster that way... time is coins make -j12 -f makefile.unix
|
|
|
net-misc/cgminer-4.3.5 doesnt work with p2pool stratum, not here anyways - it falls to longpoll
|
|
|
Bitcoindqt here is 1 hour behind, node punishes all the time - what is going on? Never ending punishment 2pool.util.jsonrpc.NarrowError: -2 Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. 2014-06-15 20:51:42.276634 > ######################################## 2014-06-15 20:51:42.276732 > >>> Warning: (from bitcoind) Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. 2014-06-15 20:51:42.276794 > ######################################## The last time I saw that error, my bitcoin block chain was corrupted. Rescan didn't fix it, and I had to re-download the whole damn thing. I did that just yesterday, hardisk is going to give up then maybe, hd passed test... It takes only 5 minutes to take a backup from .bitcoin directory and many hours to do it the hard way It was corrupted perhaps because of kernel options was not up to date with systemd
|
|
|
Bitcoindqt here is 1 hour behind, node punishes all the time - what is going on? Never ending punishment 2pool.util.jsonrpc.NarrowError: -2 Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. 2014-06-15 20:51:42.276634 > ######################################## 2014-06-15 20:51:42.276732 > >>> Warning: (from bitcoind) Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. 2014-06-15 20:51:42.276794 > ########################################
|
|
|
Restart, we are going in a loop - no blocks.
|
|
|
If you ask me, this thing not submitting blocks might have something to do with overclocked miners.... Its a huge problem....
Pardon me if I'm wrong, but hardware errors are subtracted from the valid shares already. So pools are only paying for valid shares under most circumstances. Im not talkin about hardware errors, try to calculate how many over 2mbit shares you get with ant s1 overclocked to 200gh vs standard 180gh, lets say in 10 days... Melting brains is newer good for anyones health, not with alcohol or sun(heat)
|
|
|
If you ask me, this thing not submitting blocks might have something to do with overclocked miners.... Its a huge problem....
|
|
|
see after xxxx if you have those, recseck becaus 2.8-3.0 and it wont help to pull one cord off , shut down the psu ....
|
|
|
|