[Stratum][ESMPPS][PPLNS] TheSeven's PPCoin Pool - Official thread

I have yet to see a new block on the network broadcast in my mining client. (cgminer 2.10.2) Why? I assume other pools/miners are finding PPC blocks.

Hm, I’ll have to look into that. Do you happen to know how cgminer determines that a new block was broadcast on the network?
My mining rig (running MPBM) has seen ~900-ish new blocks since I last restarted it, so that seems to work fine.

[quote=“TheSeven, post:22, topic:71”]Hm, I’ll have to look into that. Do you happen to know how cgminer determines that a new block was broadcast on the network?
My mining rig (running MPBM) has seen ~900-ish new blocks since I last restarted it, so that seems to work fine.[/quote]

I don’t really know. When mining solo, I can see when new blocks are found on the network. When mining at Coinotron, it appears that new blocks are announced via longpoll.
cgminer’s author, ckolivas (https://bitcointalk.org/index.php?action=profile;u=19971) has always seemed very helpful. Maybe you could send him a PM for more technical insight into this?

[quote=“camel, post:23, topic:71”][quote=“TheSeven, post:22, topic:71”]Hm, I’ll have to look into that. Do you happen to know how cgminer determines that a new block was broadcast on the network?
My mining rig (running MPBM) has seen ~900-ish new blocks since I last restarted it, so that seems to work fine.[/quote]

I don’t really know. When mining solo, I can see when new blocks are found on the network. When mining at Coinotron, it appears that new blocks are announced via longpoll.
cgminer’s author, ckolivas (https://bitcointalk.org/index.php?action=profile;u=19971) has always seemed very helpful. Maybe you could send him a PM for more technical insight into this?[/quote]

Did that behavior change to reporting vast amounts of blocks during the last hour? I did some change to the pool server to test this…

I am not connected currently. Let me switch over and check it out…

2013-05-16 15:00:55 Statum from pool 2 detected new block
2013-05-16 15:07:01 Statum from pool 2 detected new block 8)

camel, looks like you found a block just a few minutes ago! :slight_smile:
Please note that it will take slightly more than 12 confirmations for the first few blocks to be paid out, because I will be manually verifying the payments, just to make sure that the payment system works right…

[quote=“TheSeven, post:27, topic:71”]camel, looks like you found a block just a few minutes ago! :slight_smile:
Please note that it will take slightly more than 12 confirmations for the first few blocks to be paid out, because I will be manually verifying the payments, just to make sure that the payment system works right…[/quote]

The first payouts have been sent!
Sorry if the payments don’t match the estimated amounts that were shown on the page, I had to fix some display bugs. The paid amounts are correct though.

[quote=“TheSeven, post:28, topic:71”][quote=“TheSeven, post:27, topic:71”]camel, looks like you found a block just a few minutes ago! :slight_smile:
Please note that it will take slightly more than 12 confirmations for the first few blocks to be paid out, because I will be manually verifying the payments, just to make sure that the payment system works right…[/quote]

The first payouts have been sent![/quote]
Awesome! Payout received!

~24-hour stats:
cgminer 2.10.2
Catalyst 12.8

Worker 1 (HD 7970)
avg. speed: 647.2 Mh/s
queried: 3184
accepted: 7554
rejected: 69
efficiency: 237%
best share: 239,000
5.4 shares/minute

Worker 2 (HD 7950)
avg. speed: 525.5 Mh/s
queried: 3131
accepted: 7479
rejected: 45
efficiency: 239%
best share: 402,000
5.4 shares/minute

I’m going to rework the hashrate tracking of the pool today, to make that react quicker and display more accurate estimates.
So please don’t worry if the statistics are broken or showing nonsense values while I’m working on it.

[quote=“TheSeven, post:30, topic:71”]I’m going to rework the hashrate tracking of the pool today, to make that react quicker and display more accurate estimates.
So please don’t worry if the statistics are broken or showing nonsense values while I’m working on it.[/quote]

Work on that is finished for now. The statistics still aren’t perfect, but much better than before.

Nice! It looks much better!

My hashrate dropped ~300 Mh/s about 4 hours ago in the graphs. It now hovers somewhere in the 700-900 Mh/s range, but my miners haven’t changed.

What is the hashrate that’s reported by your miners?

I uncovered another little flaw in the hashrate tracking algorithm, that I will fix now, but that doesn’t explain much of a deviation.
However, while looking at the logs, I saw your miners (you’re PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF, aren’t you?) behaving really weird and sending shares with garbage job IDs, as if they would suffer from some kind of memory corruption. You’ll probably want to restart them. Did they report a large amount of share upload failures recently?

647.4 Mh/s & 536.9 Mh/s (average), 705.8 Mh/s & 546.8 Mh/s (last 5 secs.)
They have not reported anything unusual. Accepted shares and blocks found are the only things. Occasionally, one of my workers will start submitting n/2 difficulty shares, but mostly both are submitting n/1 shares.

[quote=“camel, post:35, topic:71”]647.4 Mh/s & 536.9 Mh/s (average), 705.8 Mh/s & 546.8 Mh/s (last 5 secs.)
They have not reported anything unusual. Accepted shares and blocks found are the only things. Occasionally, one of my workers will start submitting n/2 difficulty shares, but mostly both are submitting n/1 shares.[/quote]

My server is reporting this kind of stuff:

[SyntaxError: Unexpected token ^A] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0001", "\u000f\u0005000000", "�\u0003979fd3", "842f02ce"], "id": 5660, "method": "mining.submit"}' [SyntaxError: Unexpected token ^A] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "2\u0001", "\b", "\u0002", "71fcc768"], "id": 5605, "method": "mining.submit"}' [SyntaxError: Unexpected token ^B] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "H\u00023", "��000000", "45000000", "857a4cfd"], "id": 5740, "method": "mining.submit"}' [SyntaxError: Unexpected token ^B] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0002c", "��000000", "10000000", "44d240fc"], "id": 5772, "method": "mining.submit"}' [SyntaxError: Unexpected token ^B] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0002b", "��000000", "66000000", "de1e7efd"], "id": 5817, "method": "mining.submit"}' [SyntaxError: Unexpected token ^B] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0002c", "\u0017", "6f000000", "629747fd"], "id": 5824, "method": "mining.submit"}' [SyntaxError: Unexpected token ^M] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�", "�\r000000", "\u001d\f97b12c", "d46204cb"], "id": 6055, "method": "mining.submit"}' [SyntaxError: Unexpected token ^A] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u00012", "�", "J", "148d1ff9"], "id": 6172, "method": "mining.submit"}' [SyntaxError: Unexpected token ^A] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u00016", "\u0002", "17000000", "9ca928fd"], "id": 6149, "method": "mining.submit"}' [SyntaxError: Unexpected token ^W] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "1a9", "��000000", "\u0017", "3bc3acfd"], "id": 6157, "method": "mining.submit"}' [SyntaxError: Unexpected token ^B] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0002b", "/\u0003000000", "/\u0003000000", "6c5ad368"], "id": 6297, "method": "mining.submit"}' [SyntaxError: Unexpected token ^C] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0003f", "�\u0005000000", "�\u000297bf96", "5ae609fd"], "id": 6383, "method": "mining.submit"}' [SyntaxError: Unexpected token ^C] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "^\u0003a", "\u001a", "8f000000", "4612c9fd"], "id": 6385, "method": "mining.submit"}' [SyntaxError: Unexpected token ] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�", "�\t000000", "�\t97c662", "71afcffc"], "id": 6556, "method": "mining.submit"}' [SyntaxError: Unexpected token] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�", "�\b000000", "�\b000000", "ac244d6b"], "id": 6530, "method": "mining.submit"}' [SyntaxError: Unexpected token ^A] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u0001a", "�\f000000", "�\f000000", "47df706b"], "id": 6691, "method": "mining.submit"}' [SyntaxError: Unexpected token ^A] 'attemping to parse:' '{"params": ["PS2KDRDhDt2X94yPrVnTe2rqLitunL84XF", "�\u00012", "��000000", "5d000000", "d6406cfd"], "id": 6709, "method": "mining.submit"}'

How long has that been happening? I restarted both systems about 20 hours ago, but I can do so again if you think it is necessary. I’ve not changed any of my parameters.

I’ve started noticing that today, but that log doesn’t have timestamps (yet), so I can’t tell for sure.
Restarting could help if this was a one-time hardware glitch, but if the root cause is a bug, you might want to update your cgminer version.

One of my systems had a display driver crash yesterday (memclock-related, I think). I had to hard-reset it when it happened, but just now I did a OS restart. Think that will make any difference?

hi, i am testing using bfgminer:

./bfgminer -o theseven.bounceme.net:3333 -u PD4rreaEEJhPmKKE7eEsvoV6CNMSWqSuoe -p esmpps_quick -w 128

and showing debug details i have sometimes:

[2013-05-19 00:51:20] Pushing work from pool 0 to hash queue
[2013-05-19 00:51:20] Unknown stratum msg: {"jsonrpc":"2.0","id":"txlist447","error":{"code":-32601,"message":"Method not found"}}

the statistics page
http://theseven.bounceme.net/~theseven/pool/?PD4rreaEEJhPmKKE7eEsvoV6CNMSWqSuoe
is fixed to:

Your last payment was sent on Sat May 18 2013 23:26:10 GMT+0200 (CEST).

is it ok?

thanks