X11 Worker Not Displaying In Earnings Page

locohammerhead
Archived posts: 5
Joined: Apr 27, 2017

X11 Worker Not Displaying In Earnings Page

by locohammerhead · · Post #5500

Hello,

Been mining scrypt with prohashing for a little while now. Very happy with it. I'm glad to see you added X11 but I seem to be having a problem getting the site to display that the worker is even connected, let alone hashing. The site shows shows my scrypt miner. My mining software shows connected and hashing at around 9 mhs. Any suggestions?

Thanks
locohammerhead
locohammerhead
Archived posts: 5
Joined: Apr 27, 2017

Re: X11 Worker Not Displaying In Earnings Page

by locohammerhead · · Post #5515

I am for scrypt. I do see two connections but they are both showing as scrypt and I only have 1 worker set to scrypt. I dont see anything on the earnings page that would constitute a connection. I see the live balances and everything else for scrypt but X11 is entirely missing, not even showing shares for X11. Below is a log from my mining software. I created a new account in which my scrypt miner isn't connected. It shows as mining scrypt instead of X11 but can't calculate hashrate.

image of the x11 worker showing as mining scrypt
http://imgur.com/a/SR38f

[2017-04-27 09:35:03] prohashing.com:3333 x11 block 3126178
[2017-04-27 09:35:03] prohashing.com:3333 x11 block 1650513
[2017-04-27 09:35:03] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:35:28] GPU #0: GeForce GTX 1060 6GB, 9039.29 kH/s
[2017-04-27 09:35:53] GPU #0: GeForce GTX 1060 6GB, 9048.00 kH/s
[2017-04-27 09:36:04] prohashing.com:3333 x11 block 1467203
[2017-04-27 09:36:04] GPU #0: GeForce GTX 1060 6GB, 9047.87 kH/s
[2017-04-27 09:36:05] prohashing.com:3333 x11 block 46547
[2017-04-27 09:36:05] GPU #0: GeForce GTX 1060 6GB, 9056.28 kH/s
[2017-04-27 09:36:10] prohashing.com:3333 x11 block 1650514
[2017-04-27 09:36:11] GPU #0: GeForce GTX 1060 6GB, 9042.05 kH/s
[2017-04-27 09:36:11] prohashing.com:3333 x11 block 1671973
[2017-04-27 09:36:11] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:36:12] prohashing.com:3333 x11 block 1650514
[2017-04-27 09:36:12] GPU #0: GeForce GTX 1060 6GB, 9064.98 kH/s
[2017-04-27 09:36:37] GPU #0: GeForce GTX 1060 6GB, 9038.57 kH/s
[2017-04-27 09:36:38] prohashing.com:3333 x11 block 1650515
[2017-04-27 09:36:38] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:37:03] GPU #0: GeForce GTX 1060 6GB, 9050.18 kH/s
[2017-04-27 09:37:21] prohashing.com:3333 x11 block 1650516
[2017-04-27 09:37:21] GPU #0: GeForce GTX 1060 6GB, 8972.70 kH/s
[2017-04-27 09:37:37] prohashing.com:3333 x11 block 1467204
[2017-04-27 09:37:38] GPU #0: GeForce GTX 1060 6GB, 8995.79 kH/s
[2017-04-27 09:37:39] prohashing.com:3333 x11 block 1650517
[2017-04-27 09:37:39] GPU #0: GeForce GTX 1060 6GB, 9023.37 kH/s
[2017-04-27 09:38:04] GPU #0: GeForce GTX 1060 6GB, 9033.14 kH/s
[2017-04-27 09:38:29] GPU #0: GeForce GTX 1060 6GB, 9002.83 kH/s
[2017-04-27 09:38:54] GPU #0: GeForce GTX 1060 6GB, 9026.93 kH/s
[2017-04-27 09:39:19] GPU #0: GeForce GTX 1060 6GB, 9023.37 kH/s
[2017-04-27 09:39:44] GPU #0: GeForce GTX 1060 6GB, 9003.19 kH/s
[2017-04-27 09:40:08] GPU #0: GeForce GTX 1060 6GB, 9025.12 kH/s
[2017-04-27 09:40:33] GPU #0: GeForce GTX 1060 6GB, 9028.79 kH/s
[2017-04-27 09:40:38] prohashing.com:3333 x11 block 514975
[2017-04-27 09:40:38] GPU #0: GeForce GTX 1060 6GB, 9032.78 kH/s
[2017-04-27 09:40:50] prohashing.com:3333 x11 block 514976
[2017-04-27 09:40:50] GPU #0: GeForce GTX 1060 6GB, 9030.85 kH/s
[2017-04-27 09:41:12] prohashing.com:3333 x11 block 1650517
[2017-04-27 09:41:12] GPU #0: GeForce GTX 1060 6GB, 9033.55 kH/s
[2017-04-27 09:41:13] prohashing.com:3333 x11 block 514977
[2017-04-27 09:41:13] GPU #0: GeForce GTX 1060 6GB, 8961.68 kH/s
[2017-04-27 09:41:18] prohashing.com:3333 x11 block 1650517
[2017-04-27 09:41:18] GPU #0: GeForce GTX 1060 6GB, 9007.87 kH/s
[2017-04-27 09:41:43] GPU #0: GeForce GTX 1060 6GB, 9020.04 kH/s
[2017-04-27 09:42:06] prohashing.com:3333 x11 block 1467206
[2017-04-27 09:42:06] GPU #0: GeForce GTX 1060 6GB, 9030.45 kH/s
[2017-04-27 09:42:09] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:09] prohashing.com:3333 x11 block 1671977
[2017-04-27 09:42:09] GPU #0: GeForce GTX 1060 6GB, 9024.12 kH/s
[2017-04-27 09:42:09] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:09] GPU #0: GeForce GTX 1060 6GB, 8972.63 kH/s
[2017-04-27 09:42:15] prohashing.com:3333 x11 block 1671977
[2017-04-27 09:42:15] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:15] GPU #0: GeForce GTX 1060 6GB, 9032.01 kH/s
[2017-04-27 09:42:16] prohashing.com:3333 x11 block 1671977
[2017-04-27 09:42:17] GPU #0: GeForce GTX 1060 6GB, 9029.20 kH/s
[2017-04-27 09:42:18] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:18] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:42:43] GPU #0: GeForce GTX 1060 6GB, 9028.43 kH/s
[2017-04-27 09:43:08] GPU #0: GeForce GTX 1060 6GB, 9017.60 kH/s
[2017-04-27 09:43:30] prohashing.com:3333 x11 block 1671979
[2017-04-27 09:43:30] GPU #0: GeForce GTX 1060 6GB, 9023.70 kH/s
[2017-04-27 09:43:34] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:43:34] GPU #0: GeForce GTX 1060 6GB, 9018.47 kH/s
[2017-04-27 09:43:59] GPU #0: GeForce GTX 1060 6GB, 9018.68 kH/s
[2017-04-27 09:44:24] GPU #0: GeForce GTX 1060 6GB, 9015.43 kH/s
[2017-04-27 09:44:25] prohashing.com:3333 x11 block 1650519
[2017-04-27 09:44:25] GPU #0: GeForce GTX 1060 6GB, 9031.15 kH/s
JKDReaper
Archived posts: 99
Joined: Mar 31, 2017

Re: X11 Worker Not Displaying In Earnings Page

by JKDReaper · · Post #5518

If I connect 1 rig that hashes with 2 workers I have the same problem if I use "n=". Both workers will hash on my end, but only one will show on worker status and based on the rate of pay, only that one is credited. However, after some trial and error today I figured out that not naming eliminated the issue and both showed and were crediting. Just noticed this today
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: X11 Worker Not Displaying In Earnings Page

by Steve Sokolowski · · Post #5519

JKDReaper wrote:If I connect 1 rig that hashes with 2 workers I have the same problem if I use "n=". Both workers will hash on my end, but only one will show on worker status and based on the rate of pay, only that one is credited. However, after some trial and error today I figured out that not naming eliminated the issue and both showed and were crediting. Just noticed this today
Are you using the same name for both workers, or is "n=" different for each of them?