Author Topic: [Stratum][ESMPPS][PPLNS] TheSeven's PPCoin Pool - Official thread (Read 19282 times)

TheSeven · « **Reply #30 on:** May 18, 2013, 02:52:24 pm »

Quote from: TheSeven on May 18, 2013, 11:49:50 am

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.

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

camel · « **Reply #31 on:** May 18, 2013, 02:56:12 pm »

Nice! It looks much better!

camel · « **Reply #32 on:** May 18, 2013, 05:50:58 pm »

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.

TheSeven · « **Reply #33 on:** May 18, 2013, 07:23:34 pm »

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?

camel · « **Reply #34 on:** May 18, 2013, 07:46:04 pm »

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.

TheSeven · « **Reply #35 on:** May 18, 2013, 08:41:47 pm »

Quote from: camel on May 18, 2013, 07:46:04 pm

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.

My server is reporting this kind of stuff:

Code: [Select]

[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"}'

camel · « **Reply #36 on:** May 18, 2013, 08:51:50 pm »

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.

TheSeven · « **Reply #37 on:** May 18, 2013, 10:21:32 pm »

Quote from: camel on May 18, 2013, 08:51:50 pm

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.

camel · « **Reply #38 on:** May 18, 2013, 10:30:22 pm »

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?

ygraku · « **Reply #39 on:** May 19, 2013, 12:05:32 am »

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:

Code: [Select]

[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/%7Etheseven/pool/?PD4rreaEEJhPmKKE7eEsvoV6CNMSWqSuoe
is fixed to:

Code: [Select]

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

is it ok?

thanks

TheSeven · « **Reply #40 on:** May 19, 2013, 12:13:14 am »

Quote from: ygraku on May 19, 2013, 12:05:32 am

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:

Code: [Select]
[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"}}

That is bfgminer attempting to use some completely undocumented protocol extensions. Nothing to worry about. I'd be curious which pool server software even supports that...

Quote from: ygraku on May 19, 2013, 12:05:32 am

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

Code: [Select]
Your last payment was sent on Sat May 18 2013 23:26:10 GMT+0200 (CEST).
is it ok?

thanks

That's just your registration (i.e. connected first time) date until you receive a payout.

However, looking at the server logs and your statistics page, it seems like you didn't submit a single share yet.
Roughly how much hashrate do you have?

Edit: Shortly after typing this, you seem to have submitted your first share. Something should appear on your statistics page within the next minutes...

ygraku · « **Reply #41 on:** May 19, 2013, 12:30:11 am »

Quote from: TheSeven on May 19, 2013, 12:13:14 am

However, looking at the server logs and your statistics page, it seems like you didn't submit a single share yet.
Roughly how much hashrate do you have?

Edit: Shortly after typing this, you seem to have submitted your first share. Something should appear on your statistics page within the next minutes...

thanks for the quick reply :-)
anyway i am just experimenting using a very old computer and i have 2.0 Mh/s, and yes now i see the statistics updated,
thank you

camel · « **Reply #42 on:** May 19, 2013, 03:39:38 pm »

This morning, I awoke to both of my systems having "issues". My disconnection from the pool was not intentional. It looks like the problem started shortly after going to bed. (of course!)
I have upgraded both workers to run cgminer 3.1.1. Maybe that will help things on my end. (v3.1.1 notes: https://bitcointalk.org/index.php?topic=28402.msg2109055#msg2109055)
One cool new feature is that it shows current network difficulty, and when it changes.

TheSeven · « **Reply #43 on:** May 19, 2013, 04:32:11 pm »

Quote from: camel on May 19, 2013, 03:39:38 pm

This morning, I awoke to both of my systems having "issues". My disconnection from the pool was not intentional. It looks like the problem started shortly after going to bed. (of course!)
I have upgraded both workers to run cgminer 3.1.1. Maybe that will help things on my end. (v3.1.1 notes: https://bitcointalk.org/index.php?topic=28402.msg2109055#msg2109055)
One cool new feature is that it shows current network difficulty, and when it changes.

The disconnection time was around 3:00-4:00 UTC, which is the time frame during which my IP address changes every night. The miners probably failed to reconnect properly for some reason, I hope that the update will help with that.

(And yes, I'll need to get some better hosting for this pool once it gets bigger. Right now it doesn't pay for itself yet, so my hosting budget is fairly limited.)

camel · « **Reply #44 on:** May 19, 2013, 06:07:25 pm »

They did not seem to have that issue the night before; the last two nights, I think. I've not really had any problems with my config on any bitcoin stratum pools before, but hopefully v3.1.1 works better with your pool. Are you still seeing the weird behavior reflected in the logs now that I've restarted and upgraded?

News:

Author Topic: [Stratum][ESMPPS][PPLNS] TheSeven's PPCoin Pool - Official thread (Read 19282 times)

TheSeven

Re: New experimental stratum pool

camel

Re: New experimental stratum pool

camel

Re: New experimental stratum pool

TheSeven

Re: New experimental stratum pool

camel

Re: New experimental stratum pool

TheSeven

Re: New experimental stratum pool

camel

Re: New experimental stratum pool

TheSeven

Re: New experimental stratum pool

camel

Re: New experimental stratum pool

ygraku

Re: New experimental stratum pool

TheSeven

Re: New experimental stratum pool

ygraku

Re: New experimental stratum pool

camel

Re: New experimental stratum pool

TheSeven

Re: New experimental stratum pool

camel

Re: New experimental stratum pool