[ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool

[Bhuz]

got them too, after restart and compilling new from source, it is now fixed

I tryed to restart it but nothing changed. I'm on win7 64bit and I don't really know which depencies I need for compiling from source...

@xolokram: can you help me with this?

Code: [Select]

[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
hashmeter      0 khash/s


[xolokram]

sorry, i was working on the pool
it should be fine now

/edit:
if the automatic reconnect doesnt work, please reconnect manually
i'm sorry for the inconvenience

[vortexfoto]

xolokram, i have a problem, after a while i got this error all the time:

[STATS] 2013-11-09 13:38:42 | hashmeter 5.962389 hashs/min
VL: 5 (83.3%), RJ: 1 (16.7%), ST: 0 (0.0%)
Found Hash 000130f96cd1607fa9d57916d2efb61376a2794d6f4c40ef812682629953d216
[MASTER] submitted share -> SHARE
[STATS] 2013-11-09 13:41:11 | hashmeter 6.307057 hashs/min
VL: 6 (85.7%), RJ: 1 (14.3%), ST: 0 (0.0%)
[MASTER] submitted share -> SHARE
[STATS] 2013-11-09 13:41:11 | hashmeter 6.307057 hashs/min
VL: 7 (87.5%), RJ: 1 (12.5%), ST: 0 (0.0%)
Found Hash 02579ccca7f5e657d83b8b80f1ced28db699165358a2ea0e86a78d016f86ee9d
Found Hash 004bec3dc3baacebe91d224c77ae411e6d64e0feec7f1462862aa33c331aa69e
force reconnect if possible!
connecting to 54.201.26.128:1337
Found Hash 03af8ccd3c70b8dfb1241633fb67850bfc697d39ba33d724f42298695d3af065
Found Hash 0041d0a43eb7c5ddcb225ef8a813f713b27f96de6f12b5bdc8fb33506cf58ae4
Found Hash 03ba4c9d5129c3eaeb9d213d5dd36a8a8c7137187f485efd51364e0968de4bcc
Found Hash 0ed32dfb3503b5dd2ee096cae5674f9b0452b159659e0b2c6f1bb61b7ea7d5c5
Found Hash 0e25f20614ce9e5ba1cc488c7f5a6cee9b2229ef0757b51d4512fee8142ea30b
Found Hash 08f07d1f97d841d1d2dc96ea0ccd40dd82a714b19f6e65ee3952129781eb5206
Found Hash 07e0a35da5768339d1417207b3f628b0483094f7ce260a8015eb60c2d9821f90

does that force reconnect if possible cause any problems?

[m6450]

    

I can't go to the pool

[vortexfoto]

got them too, after restart and compilling new from source, it is now fixed

[Bhuz]

Hello guys!
Can someone tell me why I'm getting these, and how to fix it?
Thanks!

Code: [Select]

[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[MASTER] work received - target: 0fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
hashmeter      0 khash/s


[xolokram]

the payout script is already running and everything looks ok
there's just a delay, because i only pay for confirmed blocks (confirmations needed: 120)
check the payouts info page

[vortexfoto]

ok tnx ill download new one in one hour, hope old client is still working

[smith88]

hashrate counter is buggy in the old commit, it's now fixed on github
backend got stuck (check the height value on the webpage), that's fixed too now

- xolokram

that's great, i see my miners are running again.  thanks. as for payout, is this still be developed?
again, thank you for the work.

[xolokram]

hashrate counter is buggy in the old commit, it's now fixed on github
backend got stuck (check the height value on the webpage), that's fixed now too

- xolokram

[vortexfoto]

huh, i see offline, any info about low hashrate, i have 4 rigs 8 cores each ald 12gb ram, but i got till now just sth like this:

Found Hash 0f5c792a2f6e5a41d89ee286177195ab71614da6af813dd124a1ee2136a60daf
[MASTER] submitted share -> SHARE
[STATS] 2013-11-09 09:00:17 | hashmeter 1.574343 hashs/min
VL: 23 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)



strange its slow, on some machines vl gets till 45


oh can you post how to update to miner v 0.2 please i have 0.1

[xolokram]

pool backend has a bug
the pool will be back in a few minutes
i'm working on it

(blocks&payouts are save)

ok i deployed a workaround, i'll look into that issue later today

/edit:

AND i fixed the hashrate counter fix (yes, i guess i need some sleep.......)
commithash = 48d62e8f95

[smith88]

you bet.   too much tea...
yes, looks like I am using this in my startup file:
ptsminer.exe -poolip=ptsmine.beeeeer.org -poolport=1337 -poolpassword=x -pooluser=*** -genproclimit=3. systems are 64 bit Win so running multi instances has not been a problem.  no issues as of yet.

[xolokram]

please use the "edit" button instead of double posting

if you are using v0.2 then everything should be fine

as long as you're also using:
-poolip=ptsmine.beeeeer.org -poolport=1337
 

ps. i just pushed the hashrate counter fix (or i hope it's finally fixed now ) to github: linux users pull the latest source from github (commit = 48d62e8f95..)

[smith88]

i just checked my logs on the pool, you should definitely switch to the new miner, the old one (incl. the original pts client) ist just bad regarding rejection rates (stale blocks)
looks like there were no issues (except for a restart on the web frontend sometime last night)



btw if a payout states "reward = 0" (e.g. here), that specific block is an orphan unfortunately --- just fyi before someone asks
everyone who is/was mining on my old xpm pool should be aware of the gorgeous payout-info pages

- xolokram

perfect, thanks xolokram

BTW looks like I am using v.2 so should be good, yes?