 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
Getting other strange errors instead  [22:24:16] New Block: df739d3e11737cea607de1d6d1abf12243475b547cce964c0000006d00000000
[22:24:16] Block Owner bitclockers
Announcing: *** New Block {bitclockers} - df739d3e11737cea607de1d6d1abf12243475b547cce964c0000006d00000000
New Block: {bitclockers} - df739d3e11737cea607de1d6d1abf12243475b547cce964c0000006d00000000
Server selected: bitclockers
[22:24:16] Setting Block Owner bitclockers:df739d3e11737cea607de1d6d1abf12243475b547cce964c0000006d00000000
Clean Up...
[22:24:16] LP triggered serving miner
[22:24:16] LP triggered serving miner
[22:24:16] LP triggered serving miner
[22:24:16] LP triggered serving miner
[22:24:16] LP Call http://pool.bitclockers.com:8332/LP
Disconnected...
Connecting...
Connect returned
Connecting...
Disconnected...
[22:24:27] RPC request [e37ba000] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [73fef000] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:27] RPC request [getwork] submitted to btcpool24_pps
[22:24:29] RPC request [97a05000] submitted to btcpool24_pps
[22:24:32] RPC request [b8b5a000] submitted to btcpool24_pps
[22:24:36] RPC request [getwork] submitted to btcpool24_pps
Connecting...
Disconnected...
[22:24:37] RPC request [getwork] submitted to btcpool24_pps
[22:24:38] RPC request [getwork] submitted to btcpool24_pps
[22:24:40] RPC request [9af33000] submitted to btcpool24_pps
[22:24:41] RPC request [4733b000] submitted to btcpool24_pps
[22:24:43] RPC request [1517a000] submitted to btcpool24_pps
Connecting...
Disconnected...
[22:24:47] RPC request [getwork] submitted to btcpool24_pps
[22:24:48] RPC request [getwork] submitted to btcpool24_pps
[22:24:48] RPC request [getwork] submitted to btcpool24_pps
[22:24:50] RPC request [9ef1b000] submitted to btcpool24_pps
[22:24:50] RPC request [2850d000] submitted to btcpool24_pps
[22:24:51] RPC request [6f222000] submitted to btcpool24_pps
[22:24:52] RPC request [e5723000] submitted to btcpool24_pps
[22:24:52] RPC request [cd350000] submitted to btcpool24_pps
[22:24:56] RPC request [1a8a1000] submitted to btcpool24_pps
[22:24:56] RPC request [53aa6000] submitted to btcpool24_pps
Connecting...
Disconnected...
[22:24:58] RPC request [getwork] submitted to btcpool24_pps
[22:24:58] RPC request [getwork] submitted to btcpool24_pps
[22:24:59] RPC request [getwork] submitted to btcpool24_pps
[22:25:04] writing to database
I did a Reset Scheduler, Reset Shares and a Reload Config because it was mining a 55% pool, and this happened. [22:33:57] User forced configuration reload
[22:33:57] bclc: 1805702 481.9gh/s
[22:33:57] Error in pool api for bclc
[22:33:57] slush: 3188133 1858.9gh/s 120min.
[22:33:57] Error in pool api for slush
[22:33:58] swepool: 4275231 5.7gh/s 28682min.
[22:33:58] Error in pool api for swepool
[22:33:58] deepbit: 1805849 5666.0gh/s
[22:33:58] Error in pool api for deepbit
[22:33:58] btcserv: 1182024
[22:33:58] Error in pool api for btcserv
[22:33:58] mtred: 1750283 65.8gh/s
[22:33:58] Error in pool api for mtred
[22:33:58] digbtc: 944779
[22:33:58] Error in pool api for digbtc
[22:33:58] btcworld: 2393821
[22:33:58] Error in pool api for btcworld
[22:33:58] triple: 5888418
[22:33:58] Error in pool api for triple
[22:33:58] eligius: 1953976
[22:33:58] Error in pool api for eligius
[22:33:58] bitclockers: 2974953 177.1gh/s
[22:33:58] Error in pool api for bitclockers
[22:33:58] polmine: 3062234 153.2gh/s 1333min.
[22:33:58] Error in pool api for polmine
[22:33:58] btcpool24_pps: 2377859
[22:33:58] Error in pool api for btcpool24_pps
[22:33:58] arsbitcoin: 1514402
[22:33:58] Error in pool api for arsbitcoin
[22:33:58] btcpool24_prop: 2377859
[22:33:58] Error in pool api for btcpool24_prop
[22:33:58] bcpool: 2813 187.6gh/s 1min.
[22:33:58] Setting Block Owner bcpool:df739d3e11737cea607de1d6d1abf12243475b547cce964c0000006d00000000
[22:33:58] Error in pool api for bcpool
[22:33:58] btcg: 1806133 1796.0gh/s
[22:33:58] Error in pool api for btcg
[22:33:59] RPC request [1f114000] submitted to digbtc
[22:33:59] RPC request [getwork] submitted to digbtc
[22:33:59] btcmonkey: 4104500 2.1gh/s
[22:33:59] Error in pool api for btcmonkey
[22:33:59] ozco: 1161611 69.7gh/s 606min.
[22:33:59] Error in pool api for ozco
[22:33:59] unitedminers:842278
[22:33:59] Error in pool api for unitedminers
[22:34:00] RPC request [458fa000] submitted to digbtc
[22:34:00] RPC request [832f1000] submitted to digbtc
[22:34:01] RPC request [ccf0b000] submitted to digbtc
[22:34:04] RPC request [bea87000] submitted to digbtc
[22:34:04] writing to database
Connecting...
Disconnected...
[22:34:05] RPC request [getwork] submitted to digbtc
[22:34:07] RPC request [getwork] submitted to digbtc
[22:34:09] RPC request [getwork] submitted to digbtc
[22:34:11] RPC request [d4530000] submitted to digbtc
Connecting...
Disconnected...
[22:34:16] RPC request [ffaa6000] submitted to digbtc
[22:34:16] RPC request [getwork] submitted to digbtc
[22:34:17] RPC request [getwork] submitted to digbtc
[22:34:20] New Block: fe38f61b8b0316e92c6ea67133fcb3429bcb2d85399cef8f0000084500000000
[22:34:20] Block Owner bitclockers
Announcing: *** New Block {bitclockers} - fe38f61b8b0316e92c6ea67133fcb3429bcb2d85399cef8f0000084500000000
Clean Up...
[22:34:21] RPC request [getwork] submitted to digbtc
[22:34:21] RPC request [getwork] submitted to digbtc
[22:34:21] RPC request [getwork] submitted to digbtc
Connecting...
Disconnected...
[22:34:27] RPC request [getwork] submitted to digbtc
[22:34:27] RPC request [getwork] submitted to digbtc
[22:34:27] RPC request [getwork] submitted to digbtc
[22:34:28] RPC request [getwork] submitted to digbtc
[22:34:28] RPC request [getwork] submitted to digbtc
[22:34:29] RPC request [getwork] submitted to digbtc
[22:34:30] RPC request [getwork] submitted to digbtc
Connecting...
Disconnected...
[22:34:38] RPC request [getwork] submitted to digbtc
[22:34:38] RPC request [abec1000] submitted to digbtc
[22:34:39] RPC request [getwork] submitted to digbtc
[22:34:41] RPC request [getwork] submitted to digbtc
[22:34:42] RPC request [32c2d000] submitted to digbtc
[22:34:43] RPC request [1fd35000] submitted to digbtc
[22:34:44] RPC request [8484c000] submitted to digbtc
Connecting...
Disconnected...
[22:34:47] RPC request [537be000] submitted to digbtc
[22:34:48] RPC request [getwork] submitted to digbtc
[22:34:50] RPC request [getwork] submitted to digbtc
[22:34:52] RPC request [a95de000] submitted to digbtc
[22:34:52] RPC request [getwork] submitted to digbtc
[22:34:52] RPC request [f58da000] submitted to digbtc
[22:34:53] RPC request [c93f0000] submitted to digbtc
Connecting...
Disconnected...
[22:34:55] RPC request [0c07d000] submitted to digbtc
[22:34:56] RPC request [f016e000] submitted to digbtc
[22:34:59] RPC request [getwork] submitted to digbtc
[22:35:00] RPC request [getwork] submitted to digbtc
[22:35:02] RPC request [getwork] submitted to digbtc
[22:35:03] RPC request [87b29000] submitted to digbtc
[22:35:04] writing to database
[22:35:05] slush: 3213434 1855.9gh/s 121min.
[22:35:05] Error in pool api for slush
[22:35:05] Error in pool api for swepool
[22:35:05] bclc: 1813261 481.9gh/s
[22:35:05] Error in pool api for bclc
Traceback (most recent call last):
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/bitHopper.py", line 267, in <module>
main()
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/bitHopper.py", line 263, in main
reactor.run()
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1165, in run
self.mainLoop()
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1174, in mainLoop
self.runUntilCurrent()
--- <exception caught here> ---
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 796, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/pool.py", line 415, in update_api_server
self.bitHopper.scheduler.update_api_server(server)
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/scheduler.py", line 637, in update_api_server
if info['role'] in ['info', 'disable'] and info['slice'] > 0:
exceptions.KeyError: 'slice'
Connecting...
Disconnected...
[22:35:06] triple: 5888592
[22:35:06] Error in pool api for triple
[22:35:06] deepbit: 1896408 5657.0gh/s
[22:35:06] Error in pool api for deepbit
[22:35:08] Error in pool api for digbtc
[22:35:09] polmine: 3064949 152.2gh/s 1341min.
[22:35:09] Error in pool api for polmine
Traceback (most recent call last):
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/bitHopper.py", line 267, in <module>
main()
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/bitHopper.py", line 263, in main
reactor.run()
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1165, in run
self.mainLoop()
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1174, in mainLoop
self.runUntilCurrent()
--- <exception caught here> ---
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 796, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/pool.py", line 415, in update_api_server
self.bitHopper.scheduler.update_api_server(server)
File "/home/bithopper/bin/bitHopper/bitHopper_2011_08_19_2205/scheduler.py", line 637, in update_api_server
if info['role'] in ['info', 'disable'] and info['slice'] > 0:
exceptions.KeyError: 'slice'
Are those ^Connecting|Disconnected related to the --p2pLP? con/dis started after a new block was detected anyway, bitclockers is in info-mode Shares are not updated, only rejects. No user is in the list, but at the top the "pool @xxxxMHash" correct Restarted bh and now no dis/con after a block was detected, got vote info instead. |
|
|
|
Tried a newer version(commit bbe980b1d7fa3284c6b6e02cbe0297789c31e5fd was the latest at the time) and now no API-errors  Just tried out the latest git, lots of API-errors. [16:10:14] Updating Difficulty
[16:10:19] 1805700.8361937
[16:10:19] Updating NameCoin Difficulty
[16:10:25] 94037.96
[16:10:25] Checking Database
[16:10:25] writing to database
[16:10:25] Selecting scheduler: AltSliceScheduler
[16:10:25] [scheduler-altslice] Initializing AltSliceScheduler...
[16:10:25] [scheduler-altslice] - Min Slice Size: 60
[16:10:25] [scheduler-altslice] - Slice Size: 180
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] Server change to btcpool24_pps
[16:10:25] Starting p2p LP
Connecting...
[16:10:25] bclc: 1805712 493.5gh/s
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] swepool: 4245274 4.2gh/s 28298min.
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] slush: 654984 1866.9gh/s 25min.
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] LP Call http://bitcoins.lc:8080/LP
[16:10:25] btcserv: 1159784
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] triple: 5824275
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] LP Call http://pit.deepbit.net:8332/listenChannel
[16:10:25] LP Call http://swepool.net:8337/LP
[16:10:25] LP Call http://su.mining.eligius.st:8337/LP
[16:10:25] deepbit: 1806047 5520.0gh/s
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] LP Call http://min.btcpool24.com:8338/LP
[16:10:25] LP Call http://min.btcpool24.com:8338/LP
[16:10:25] LP Call http://btcworld.de:8332/LP
Connect returned
[16:10:26] eligius: 3714571
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] LP Call http://arsbitcoin.com:8344/LP
[16:10:26] LP Call http://bitcoinmonkey.com:8332/LP
[16:10:26] bitclockers: 2279465 190.3gh/s
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] btcworld: 2378671
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] LP Call http://mtred.com:8837/LP
[16:10:26] LP Call http://uscentral.btcguild.com:8332/LP
[16:10:26] polmine: 2094070 146.0gh/s 956min.
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] LP Call http://pool.bitclockers.com:8332/LP
[16:10:26] btcpool24_prop: 2240063
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] btcpool24_pps: 2240063
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] digbtc: 573727
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] [scheduler-altslice] digbtc sliced to 180.00
[16:10:26] Server change to digbtc
[16:10:26] Error in pool api for digbtc
[16:10:26] LP Call http://digbtc.net:8332/LP
[16:10:26] mtred: 876616 196.5gh/s
[16:10:26] Error in pool api for mtred
[16:10:26] arsbitcoin: 206292
[16:10:26] Error in pool api for arsbitcoin
[16:10:26] LP Call http://pool.unitedminers.com:8332/LP/
[16:10:26] LP Call http://pool.bitminersunion.org:8341/LP
[16:10:26] btcmonkey: 4093595 2.1gh/s
[16:10:26] Error in pool api for btcmonkey
[16:10:26] RPC request [fb29d000] submitted to digbtc
[16:10:26] bcpool: 2813 187.6gh/s 1min.
[16:10:26] Error in pool api for bcpool
[16:10:26] LP Call http://ozco.in:8332/LP
[16:10:26] btcg: 1806228 2160.0gh/s
[16:10:26] Error in pool api for btcg
[16:10:27] ozco: 653252 212.2gh/s 222min.
[16:10:27] [scheduler-altslice] Re-Slicing...
[16:10:27] [scheduler-altslice] digbtc sliced to 95.83
[16:10:27] [scheduler-altslice] ozco sliced to 84.17
[16:10:27] Error in pool api for ozco
[bunch of works cut out]
[16:12:25] bclc: 1819610 497.3gh/s
[16:12:25] Error in pool api for bclc
[16:12:25] slush: 699186 1866.2gh/s 27min.
[16:12:25] Error in pool api for slush
[16:12:25] RPC request [f1aa5000] submitted to digbtc
[16:12:25] RPC request [411be000] submitted to digbtc
[16:12:25] swepool: 4245385 4.2gh/s 28300min.
[16:12:25] Error in pool api for swepool
[16:12:26] btcserv: 1159862
[16:12:26] Error in pool api for btcserv
[16:12:26] triple: 5824678
[16:12:26] Error in pool api for triple
[16:12:26] deepbit: 1960109 5504.0gh/s
[16:12:26] Error in pool api for deepbit
[16:12:26] Error in pool api for btcworld
[16:12:26] eligius: 3729500
[16:12:26] Error in pool api for eligius
[16:12:26] bitclockers: 2288996 190.0gh/s
[16:12:26] Error in pool api for bitclockers
[16:12:26] Error in pool api for digbtc
[16:12:26] Error in pool api for digbtc
[16:12:26] polmine: 2098468 146.0gh/s 956min.
[16:12:26] Error in pool api for polmine
[16:12:26] btcpool24_pps: 2240710
[16:12:26] Error in pool api for btcpool24_pps
[16:12:27] Error in pool api for mtred
[16:12:27] Error in pool api for mtred
[16:12:27] Error in pool api for arsbitcoin
[16:12:27] Error in pool api for arsbitcoin
[16:12:27] RPC request [1fbc5000] submitted to digbtc
[16:12:27] RPC request [getwork] submitted to digbtc
[16:12:27] bcpool: 8484 187.6gh/s 1min.
[16:12:27] Error in pool api for bcpool
[16:12:27] Error in pool api for bcpool
[16:12:27] RPC request [getwork] submitted to digbtc
[16:12:27] btcg: 1866963 2155.0gh/s
[16:12:27] Error in pool api for btcg
[16:12:27] btcg: 1866977 2155.0gh/s
|
|
|
|
|
I don't understand the details on how LP works.
Is it only the server that one has sent a LP-request to that sends a LP-reply when it has a new block, but it doesn't say it's name?
Or is there some kind of broadcast involved?
|
|
|
|
Just tried out the latest git, lots of API-errors. [16:10:14] Updating Difficulty
[16:10:19] 1805700.8361937
[16:10:19] Updating NameCoin Difficulty
[16:10:25] 94037.96
[16:10:25] Checking Database
[16:10:25] writing to database
[16:10:25] Selecting scheduler: AltSliceScheduler
[16:10:25] [scheduler-altslice] Initializing AltSliceScheduler...
[16:10:25] [scheduler-altslice] - Min Slice Size: 60
[16:10:25] [scheduler-altslice] - Slice Size: 180
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] Server change to btcpool24_pps
[16:10:25] Starting p2p LP
Connecting...
[16:10:25] bclc: 1805712 493.5gh/s
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] swepool: 4245274 4.2gh/s 28298min.
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] slush: 654984 1866.9gh/s 25min.
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] LP Call http://bitcoins.lc:8080/LP
[16:10:25] btcserv: 1159784
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] triple: 5824275
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] LP Call http://pit.deepbit.net:8332/listenChannel
[16:10:25] LP Call http://swepool.net:8337/LP
[16:10:25] LP Call http://su.mining.eligius.st:8337/LP
[16:10:25] deepbit: 1806047 5520.0gh/s
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] [scheduler-altslice] Re-Slicing...
[16:10:25] No servers to slice, picking a backup...
[16:10:25] LP Call http://min.btcpool24.com:8338/LP
[16:10:25] LP Call http://min.btcpool24.com:8338/LP
[16:10:25] LP Call http://btcworld.de:8332/LP
Connect returned
[16:10:26] eligius: 3714571
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] LP Call http://arsbitcoin.com:8344/LP
[16:10:26] LP Call http://bitcoinmonkey.com:8332/LP
[16:10:26] bitclockers: 2279465 190.3gh/s
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] btcworld: 2378671
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] LP Call http://mtred.com:8837/LP
[16:10:26] LP Call http://uscentral.btcguild.com:8332/LP
[16:10:26] polmine: 2094070 146.0gh/s 956min.
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] LP Call http://pool.bitclockers.com:8332/LP
[16:10:26] btcpool24_prop: 2240063
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] btcpool24_pps: 2240063
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] No servers to slice, picking a backup...
[16:10:26] digbtc: 573727
[16:10:26] [scheduler-altslice] Re-Slicing...
[16:10:26] [scheduler-altslice] digbtc sliced to 180.00
[16:10:26] Server change to digbtc
[16:10:26] Error in pool api for digbtc
[16:10:26] LP Call http://digbtc.net:8332/LP
[16:10:26] mtred: 876616 196.5gh/s
[16:10:26] Error in pool api for mtred
[16:10:26] arsbitcoin: 206292
[16:10:26] Error in pool api for arsbitcoin
[16:10:26] LP Call http://pool.unitedminers.com:8332/LP/
[16:10:26] LP Call http://pool.bitminersunion.org:8341/LP
[16:10:26] btcmonkey: 4093595 2.1gh/s
[16:10:26] Error in pool api for btcmonkey
[16:10:26] RPC request [fb29d000] submitted to digbtc
[16:10:26] bcpool: 2813 187.6gh/s 1min.
[16:10:26] Error in pool api for bcpool
[16:10:26] LP Call http://ozco.in:8332/LP
[16:10:26] btcg: 1806228 2160.0gh/s
[16:10:26] Error in pool api for btcg
[16:10:27] ozco: 653252 212.2gh/s 222min.
[16:10:27] [scheduler-altslice] Re-Slicing...
[16:10:27] [scheduler-altslice] digbtc sliced to 95.83
[16:10:27] [scheduler-altslice] ozco sliced to 84.17
[16:10:27] Error in pool api for ozco
[bunch of works cut out]
[16:12:25] bclc: 1819610 497.3gh/s
[16:12:25] Error in pool api for bclc
[16:12:25] slush: 699186 1866.2gh/s 27min.
[16:12:25] Error in pool api for slush
[16:12:25] RPC request [f1aa5000] submitted to digbtc
[16:12:25] RPC request [411be000] submitted to digbtc
[16:12:25] swepool: 4245385 4.2gh/s 28300min.
[16:12:25] Error in pool api for swepool
[16:12:26] btcserv: 1159862
[16:12:26] Error in pool api for btcserv
[16:12:26] triple: 5824678
[16:12:26] Error in pool api for triple
[16:12:26] deepbit: 1960109 5504.0gh/s
[16:12:26] Error in pool api for deepbit
[16:12:26] Error in pool api for btcworld
[16:12:26] eligius: 3729500
[16:12:26] Error in pool api for eligius
[16:12:26] bitclockers: 2288996 190.0gh/s
[16:12:26] Error in pool api for bitclockers
[16:12:26] Error in pool api for digbtc
[16:12:26] Error in pool api for digbtc
[16:12:26] polmine: 2098468 146.0gh/s 956min.
[16:12:26] Error in pool api for polmine
[16:12:26] btcpool24_pps: 2240710
[16:12:26] Error in pool api for btcpool24_pps
[16:12:27] Error in pool api for mtred
[16:12:27] Error in pool api for mtred
[16:12:27] Error in pool api for arsbitcoin
[16:12:27] Error in pool api for arsbitcoin
[16:12:27] RPC request [1fbc5000] submitted to digbtc
[16:12:27] RPC request [getwork] submitted to digbtc
[16:12:27] bcpool: 8484 187.6gh/s 1min.
[16:12:27] Error in pool api for bcpool
[16:12:27] Error in pool api for bcpool
[16:12:27] RPC request [getwork] submitted to digbtc
[16:12:27] btcg: 1866963 2155.0gh/s
[16:12:27] Error in pool api for btcg
[16:12:27] btcg: 1866977 2155.0gh/s
|
|
|
|
|
Here are my mine_deepbit stats using the AltSliceScheduler:
(full command line: --scheduler=AltSliceScheduler --altslicesize=180 --startLP --p2pLP)
Bitcoins.lc: 339
BTCGuild.com: 0
DeepBit: 17
PolMine.pl: 1369
Total Shares during the same period: 129.000
Version: no idea, how does one check? it's from the git 4 days ago
|
|
|
|
|
A "simple" and crude way would just involve a share-counter that would reset when bh detects that the pool has a new block.
This wouldn't work reliable over restarts of bh though.
|
|
|
|
|
Feature Request: presentation on the stats-page of sharestats of the current round and not just totals
|
|
|
|
Low tech would be placing a cd-rom drive which the tray will open and hit the reset button.
Someone please do a thing like that and make a video  |
|
|
|
i recommend to remove bitcoinpool from the rotation. its obvious that they fake their shares as decoy and then even demand a fee. also they are so unprofessional in every way.. avoid!
Don't use json on them, that is why it changed to grabbing their webpage instead, update your pools.cfg |
|
|
|
Isn't it just hopping between, and not doing multiple shares from multiple pools simultaneously? At least that is how I read Keninishna's question. best way is to always take the pool with lowest round shares. The Pools hashrates are important variables here? |
|
|
|
A crazy idea just popped up while I was messing around with some bash-scripts. Would it be possible to have bh running multiple pools simultaneously? And splitting the getwork requests of those based on a on-every-X-getwork. If one sets a pool to 'on-every-X-getwork: 10' it would do a getwork every 10th getwork, getting 10% of the total hashspeed. Why would anyone want something crazy like that? Direct a constant portion of ones hashingpower towards a pool that one might like to support despite hopping or whatever reason. Getting bh to re-read the user.cfg either by command or by internal filechange-checking would be a nice, but not required, addition to this. Another idea came up while writing this post, but it can be shot down quickly if someone has the data: Would it be favorable to mine, for example, two(things change if there are more?) sub 10%shares pools simultaneously, instead of one until it reaches the threshold and then jump to one of the others, if it/they are still below threshold, or is it better to try and get lucky as early on in a round as possible? I'm not quite sure how the hopping is determined atm. Will bh constantly try and find the pool with the lowest share-count and then jump to it? or will it stay with a pool it has jumped to until the threshold is reached, then jump to the pool with the lowest share-count? I'm guessing "--altslicesize" has a part in this, but I don't understand what a "slice" is, is it shares? (The more I add to this post, the more confusing it gets, so I will just press "Post" now) |
|
|
|
|
I think I have read about the "DoS-like appearance" in some other thread before, can't remember where though.
But I don't think I have seen invalid shares being part of it, aggressive pulling/getwork I think it was when I read about it before.
The big question, is the massive amount of invalid shares only occurring on the ABCpool?
|
|
|
|
BTW, Slush with "mine_slush" with penalty at 0.5 FTW !!  I have found 0.5 to work quite nice as well |
|
|
|
What happens ? : Yesterday between. 21:46 und 22:50 0.05BTC instead of 0.00002647BTC where paid per PPS Share.
Ouch, that's some 50BTC for each and every 1000 shares, or 1BTC for every 20 shares  Wouldn't want to experience the feeling you got when you noticed the issue, and then later, the cause of it. Happy to hear that most BTC have found their way back, this is something I doubt would happen on the very large pools. |
|
|
|
Stats on their webpages gives a much higher round shares, yes. |
|
|
|
|
If using linux, code a script that checks for GPU-hungs, if a hung is detected, it sets the default overclock on that card to 5MHz lower than the current MHz(you might want to set some thresholds here so you don't end up with a GPU that is running at clocks like 200MHz), then coldreboot.
At the same time this scripts lowers the clocks if the temperature go over predefined limits, and raises the clocks again as it gets cooler. Use other temperature sensors(such as the motherboard) to trigger presets.
|
|
|
|
|
If you want to try linux, here are some hints...
Using WiFi (Cheap Router & Adapters)
Not sure what the pricing or coverage is like in your region, but using a mobile broadband(3G or what ever might be available) as a backup/fail over connection might be of interest if your internet connection have any history of not being reliable.
No UPS
Set the bios to "Start" if power is lost and then restored.
Summer
Code a watcher script that downclocks the card as temperatures go above predefined values, and overclocks in steps or full when temperature is within safe levels.
You might want to go extreme and use the motherboard temperature as an indicator of the room temperature so that it doesn't hang the GPU almost directly after startup if too aggressive overclocking is applied at start.
No Config to continue correctly if system reboots
Create a simple startup-script
No One to check on it
Code a simple monitor script that checks for GPUs that are hung etc, and coldreboots the rig if hungs are detected.
If your motherboards support IPMI or similar, then the rigs can monitor each other, and take action accordingly, such as reboot etc.
A managed PDU could be interesting as well, have the rigs monitor each other, if problems occur or a dead response and the system doesn't want to reboot, the other rig tells the PDU to power-cycle the troubling rig.
No Communication
same as above
No Access to a computer
same as above
|
|
|
|
|
Here are two more:
EVGA 680i SLI (122-CK-NF68-A1)
EVGA 680i SLI (122-CK-NF68-T1)
|
|
|
|
I tried cgminer on a couple of my boxes last night and woke up to find 3/4 GPU marked as DEAD on one and 2/4 DEAD on another. Trying to restart the DEAD GPU doesnt seem to do anything on either machine (restarting the ones still running did seem to restart them OK). Both boxes have been running for weeks using poclbm without errors. Running the 1.5.3 binary on Ubuntu (3xHD5870 and HD6310).
Anyone else seeing problems with DEAD GPU that won't recover unless cgminer is restarted?
BB.
Restart dead GPUs does not work for me too. Win7 64bit, Catalyst 11.7 Me too. LinuxCoin beta final In my testing, under Fedora14, SDK2.4, restart GPU works in 100% of my 5xxx series cards, and 0% of my 6xxx series cards. restart GPU works even if the GPU is hung due to things like overheat-lockup? I simply have a monitoring script that checks for serious lockups and coldreboots the rig if it is triggered, not pretty, but all GPU are at least up and mining again within a minute. Will probably add that corespeed controlled by temperature levels script(it down clocks the core if temperature gets too high) I saw in some thread on the forum a few days ago. Summertime is a bitch when it comes to mining  |
|
|
|
|
