loshia1974
Jr. Member
 Offline
Activity: 52
Merit: 29
|
 |
December 28, 2017, 05:43:13 PM |
|
Hintsal, You got a PM  Please PM me your user (LTC) address so i can check logs and try to figure out what is really going on Best Loshia |
|
|
|
|
Hintsal
Newbie
Offline
Activity: 42
Merit: 0
|
|
December 29, 2017, 02:07:26 PM |
|
Hi. I can't pm back cause I'm not a paid member and km limited to 2 pm a day. When I got home and hour ago I started the miner and it stopped after about 20 minutes. I just closed bfgminer and restarted it. It has been running since. If it stops before I go to sleep I'll message here as I can't pm. I'll leave the miner on all night connected even if it stops running.
|
|
|
|
|
Hintsal
Newbie
Offline
Activity: 42
Merit: 0
|
|
December 29, 2017, 03:31:18 PM |
|
Hintsal, You got a PM Please PM me your user (LTC) address so i can check logs and try to figure out what is really going on Best Loshia Just stopped working a few minutes ago. Bfgminer is only recording new block detections by stratum. I'll leave it running all night. Sucks that it's just sitting idle though. |
|
|
|
|
kapnmike2009
Newbie
Offline
Activity: 2
Merit: 0
|
|
December 30, 2017, 02:46:18 PM |
|
Can someone assist. Tried both ports with nicehash Notice: Pool verificator may not be 100% accurate and may report pool being compatible while in fact it is not compatible or vice versa. Always discuss with pool operator if you encounter any issues with the pool verificator. Pool host: tbdice.org Pool port: 13334 Pool user: LW4JKc4LvFAPnN6GeMgZ5kb3yTrEJbb2b4 Pool pass: x:D8BkjGc32BiMqxz4er7huqowQkxVfq7jQv Algorithm: Scrypt Resolving pool host tbdice.org... OK Establishing connection with proxy... OK Establishing connection with pool 195.85.215.220:13334... OK Sending mining.subscribe... OK Sending mining.authorize... OK Received mining.notify subscription... OK Received authorization result... OK Received mining.set_difficulty... Pool difficulty too low (provided=16384, minimum=131072) Waiting for pool to send higher difficulty. Received mining.notify work... OK Received mining.notify work... OK Error: Difficulty too low. Your pool is shown as incompatible therefore we encourage you to contact pool operator to make sure that the pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners), please send them link to our FAQ on this topic: https://www.nicehash.com/index.jsp?p=faq#faqb3. Thank you! |
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
December 30, 2017, 10:19:15 PM
Last edit: December 30, 2017, 10:33:31 PM by loshia1974 |
|
Can someone assist. Tried both ports with nicehash Notice: Pool verificator may not be 100% accurate and may report pool being compatible while in fact it is not compatible or vice versa. Always discuss with pool operator if you encounter any issues with the pool verificator. Pool host: tbdice.org Pool port: 13334 Pool user: LW4JKc4LvFAPnN6GeMgZ5kb3yTrEJbb2b4 Pool pass: x:D8BkjGc32BiMqxz4er7huqowQkxVfq7jQv Algorithm: Scrypt Resolving pool host tbdice.org... OK Establishing connection with proxy... OK Establishing connection with pool 195.85.215.220:13334... OK Sending mining.subscribe... OK Sending mining.authorize... OK Received mining.notify subscription... OK Received authorization result... OK Received mining.set_difficulty... Pool difficulty too low (provided=16384, minimum=131072) Waiting for pool to send higher difficulty. Received mining.notify work... OK Received mining.notify work... OK Error: Difficulty too low. Your pool is shown as incompatible therefore we encourage you to contact pool operator to make sure that the pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners), please send them link to our FAQ on this topic: https://www.nicehash.com/index.jsp?p=faq#faqb3. Thank you! Hi, Just change Pool pass: x:D8BkjGc32BiMqxz4er7huqowQkxVfq7jQv to: Pool pass: diff_131072:D8BkjGc32BiMqxz4er7huqowQkxVfq7jQv replace x with diff_131072 this will do the trick According to: https://www.nicehash.com/pool-operators bottom of the page Scrypt diff should be >= 524288 so if diff_131072 is not making nicehash happy then use diff_524288 instead |
|
|
|
|
|
Xardas2014
|
|
January 25, 2018, 10:38:41 PM |
|
My worker is not showing up on the worker page. I've PM'd loshia without response. The workers page give me this popup error: DataTables warning: table id=workers - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1When I try the steps in the provided link I am stopped at: The network panel will show all of the requests made by Chrome to load the page. Click the XHR option at the bottom of the window to reduce the requests to just the Ajax (XHR) requests. Double click the Ajax request made by DataTables<----------no requests made Using latest Chrome, Win10 Pro. |
|
|
|
|
|
crypto_curious
|
|
January 25, 2018, 10:54:25 PM |
|
My worker is not showing up on the worker page. I've PM'd loshia without response. The workers page give me this popup error: DataTables warning: table id=workers - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1When I try the steps in the provided link I am stopped at: The network panel will show all of the requests made by Chrome to load the page. Click the XHR option at the bottom of the window to reduce the requests to just the Ajax (XHR) requests. Double click the Ajax request made by DataTables<----------no requests made Using latest Chrome, Win10 Pro. I am using Firefox on Win10 right now, and workers page is running just fine. Try different browser/system. |
|
|
|
|
|
Xardas2014
|
|
January 25, 2018, 11:32:02 PM |
|
My worker is not showing up on the worker page. I've PM'd loshia without response. The workers page give me this popup error: DataTables warning: table id=workers - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1When I try the steps in the provided link I am stopped at: The network panel will show all of the requests made by Chrome to load the page. Click the XHR option at the bottom of the window to reduce the requests to just the Ajax (XHR) requests. Double click the Ajax request made by DataTables<----------no requests made Using latest Chrome, Win10 Pro. I am using Firefox on Win10 right now, and workers page is running just fine. Try different browser/system. I had already tried FF, Edge, and Opera. I'll just move my miners until I get a reply from loshia |
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
January 26, 2018, 08:37:52 AM |
|
Hi, You just got PM Let me know how it goes. About invalid son response Data tables issue it happens very really. I know what is causing it. For the moment let us pretend it is not happening as long as we can live with that. If you or someone else thinks it is anoying please let me know and i will try to fix it Best Loshia |
|
|
|
|
|
crypto_curious
|
|
January 26, 2018, 12:32:55 PM |
|
My worker is not showing up on the worker page. I've PM'd loshia without response. The workers page give me this popup error: DataTables warning: table id=workers - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1When I try the steps in the provided link I am stopped at: The network panel will show all of the requests made by Chrome to load the page. Click the XHR option at the bottom of the window to reduce the requests to just the Ajax (XHR) requests. Double click the Ajax request made by DataTables<----------no requests made Using latest Chrome, Win10 Pro. I am using Firefox on Win10 right now, and workers page is running just fine. Try different browser/system. I had already tried FF, Edge, and Opera. I'll just move my miners until I get a reply from loshia Can you provide any screenshot or something? I really don't see that error on FF, it's just fine for me. |
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
January 26, 2018, 05:53:08 PM |
|
It is hard to make screen shoot as long it is happening very rare. Any way i will explain...If you are refreshing stats page like "crasy" and in the same time pool dumps users/worker stats to file to be served by web server and sent to your browser browser will get corrupted json and will alert the error:) We are talking for less than a second in each minute Other option is in between "crazy" page refreshes web server (nginx) to reset your tcp connection... Best Loshia |
|
|
|
|
sunsetblues
Member
Offline
Activity: 154
Merit: 12
Live life to the fullest and focus on the positive
|
|
February 02, 2018, 04:17:42 AM |
|
I've been mining for a week at TBdice without any problems. I have pool notifications set to type=51 so I get notices. Of course when I restart my ASIC I get an email notice that says "Worker has been authorized" and this is expected so all is working correctly.
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
|
Have faith in humanity and never lose hope.
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
February 02, 2018, 09:41:44 PM
Last edit: February 02, 2018, 09:54:25 PM by loshia1974 |
|
I've been mining for a week at TBdice without any problems. I have pool notifications set to type=51 so I get notices. Of course when I restart my ASIC I get an email notice that says "Worker has been authorized" and this is expected so all is working correctly.
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
Hi, This seems odd. Can you PM me mail message headers to investigate this case further? 10X Best Loshia PS: Some logs and all seems good [2018-02-02 01:55:07.956] Authorised client 4821322 Lbwrx...... [2018-02-02 01:55:07.966] Authorised client 4821321 Lbwrx...... [2018-02-02 22:19:25.386] Authorised client 4834871 Lbwrx...... [2018-02-02 22:51:28.929] Authorised client 4835425 Lbwrx...... And two mails sent around /var/log/exim4/mainlog.1:2018-02-02 01:56:04 1ehOi1-0003HS-TO => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... /var/log/exim4/mainlog.1:2018-02-02 01:56:04 1ehOi2-0003HW-04 => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... /var/log/exim4/mainlog:2018-02-02 22:21:05 1ehhpW-00047i-RM => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... /var/log/exim4/mainlog:2018-02-02 22:53:04 1ehiKV-0004Nx-0X => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... |
|
|
|
|
sunsetblues
Member
Offline
Activity: 154
Merit: 12
Live life to the fullest and focus on the positive
|
|
February 05, 2018, 10:05:50 PM |
|
I've been mining for a week at TBdice without any problems. I have pool notifications set to type=51 so I get notices. Of course when I restart my ASIC I get an email notice that says "Worker has been authorized" and this is expected so all is working correctly.
Today without restarting my miner I got two notices that said "Worker has been authorized" for worker 1 & 2, but I hadn't restarted my miner it was running just fine. It happened at the exact time when Pool Block 1361150 hit (think that's the correct number). What makes this really weird is the two emails I received included two additional email addresses I've never seen before. You can find my workers with Lbwrx.
Bug maybe?
Hi, This seems odd. Can you PM me mail message headers to investigate this case further? 10X Best Loshia PS: Some logs and all seems good [2018-02-02 01:55:07.956] Authorised client 4821322 Lbwrx...... [2018-02-02 01:55:07.966] Authorised client 4821321 Lbwrx...... [2018-02-02 22:19:25.386] Authorised client 4834871 Lbwrx...... [2018-02-02 22:51:28.929] Authorised client 4835425 Lbwrx...... And two mails sent around /var/log/exim4/mainlog.1:2018-02-02 01:56:04 1ehOi1-0003HS-TO => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... /var/log/exim4/mainlog.1:2018-02-02 01:56:04 1ehOi2-0003HW-04 => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... /var/log/exim4/mainlog:2018-02-02 22:21:05 1ehhpW-00047i-RM => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... /var/log/exim4/mainlog:2018-02-02 22:53:04 1ehiKV-0004Nx-0X => teaxxxxxrt@goxxxxs.org R=dnslookup T=remote_smtp H=smtp.gxxxxs.org [xxx.xxx.xxx.xxx] X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=US..... PM sent. |
Have faith in humanity and never lose hope.
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
February 06, 2018, 02:36:36 PM |
|
Thanks to sunsetblues the issue was found and fixed. Please let me know if you do receive emails ok
Best
Loshia
Pool OP
|
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
February 28, 2018, 06:17:16 AM
Last edit: February 28, 2018, 06:32:02 AM by loshia1974 |
|
Hello,
There are a series of rejected DOGE blocks recently
I am investigating pool logs and let you know what is going on.
My guess is that
Pool LOG
[2018-02-28 05:10:15.034] Possible AUX block 2115362 solve diff 456952590219.086548 > 58632474940.824486(58691166106.931419)!
[2018-02-28 05:10:15.043] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-28 05:10:15.043] Submitted, but had AUX block 2115362 rejected
Doge LOG
UpdateTip: new best=f22560d3ee0674e77a05fbdd93aa9fc2498b079bc5108b59a25c0c79c6198360 height=2115362 log2_work=69.785573 tx=34656924 date=2018-02-28 05:09:22 progress=1.000000 cache=41.6MiB(15165tx)
As you see that block was submitted almost a minute later and became stale
If someone from big miners can answer me if you were upgrading your proxies or mining software lately?
Thanks
Best
Loshia
PS: However i will dig into it and will watch it closely .
More updates are on the way....
-----------------------
[2018-02-27 07:47:49.951] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-27 07:47:49.951] Submitted, but had AUX block 2114018 rejected
[2018-02-27 10:43:30.655] Possible AUX block 2114179 solve diff 51750974512.521477 > 47578295133.653755(47625921054.708466)!
[2018-02-27 10:43:30.661] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-27 10:43:30.661] Submitted, but had AUX block 2114179 rejected
[2018-02-27 13:58:58.084] Possible AUX block 2114372 solve diff 81975431999.216431 > 76941469121.388428(77018487608.997421)!
[2018-02-27 13:58:58.089] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-27 13:58:58.090] Submitted, but had AUX block 2114372 rejected
[2018-02-27 14:12:02.196] Possible AUX block 2114389 solve diff 376559022888.440857 > 120942612138.498917(121063675814.313232)!
[2018-02-27 14:12:02.203] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-27 14:12:02.203] Submitted, but had AUX block 2114389 rejected
[2018-02-27 22:08:37.172] Possible AUX block 2114840 solve diff 128009409178.024292 > 79358860107.239059(79438298405.644699)!
[2018-02-27 22:08:37.177] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-27 22:08:37.178] Submitted, but had AUX block 2114840 rejected
[2018-02-28 03:37:23.907] Possible AUX block 2115162 solve diff 625178572652.954956 > 124676011361.433975(124800812173.607590)!
[2018-02-28 03:37:23.913] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-28 03:37:23.914] Submitted, but had AUX block 2115162 rejected
[2018-02-28 07:10:15.034] Possible AUX block 2115362 solve diff 456952590219.086548 > 58632474940.824486(58691166106.931419)!
[2018-02-28 07:10:15.043] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-28 07:10:15.043] Submitted, but had AUX block 2115362 rejected
---------------------
|
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
February 28, 2018, 09:42:21 AM |
|
UP:
Pool was restarted ....Sorry for short interruption. I will wait a little bit to see what will happen with next DOGE Blocks
Best
Loshia
|
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
February 28, 2018, 05:07:39 PM |
|
The issue with DOGE still continues....
Pool
[2018-02-28 18:56:27.885] Possible AUX block 2116044 solve diff 66345692652.530006 > 64019457257.128250(64083540797.926178)!
[2018-02-28 18:56:27.897] SUBMIT AUX BLOCK RETURNED: bad-cb-height
[2018-02-28 18:56:27.898] Submitted, but had AUX block 2116044 rejected
Doge
2018-02-28 16:56:38 UpdateTip: new best=ed88a005d0b96a47b8662d045df689330febfea2f6c335eb857384f16dafbcb8 height=2116044 log2_work=69.792006 tx=34693364 date=2018-02-28 16:56:37 progress=1.000000 cache=3.1MiB(1093tx)
2018-02-28 16:57:14 UpdateTip: new best=b59d194e521d48552b7ac063c88d6e02b1e861c68949f6e17bde1470a0fdb233 height=2116044 log2_work=69.792006 tx=34693495 date=2018-02-28 16:56:13 progress=0.999999 cache=3.1MiB(1099tx)
That is our last rejected block...Something wired is going on with DOGE network..Any way i have restarted both doge daemons and we will have to wait again
Sorry folks
Best
Loshia
|
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
February 28, 2018, 07:22:01 PM |
|
Pool was updated and restarted. There issue was found and fixed
Mine on...
Best
Loshia
Pool OP
|
|
|
|
|
loshia1974
Jr. Member
Offline
Activity: 52
Merit: 29
|
|
March 01, 2018, 04:52:57 AM |
|
Update...
After pool code change all is good both LTC and DOGE are accepted and there will be no more issues with doge blocks
[2018-03-01 06:32:15.284] Possible LTC block solve diff 5679774376160.954102 > 329546263335.884216(329876139475.359558)!
[2018-03-01 06:32:15.284] Submitting block data!
[2018-03-01 06:32:15.324] LTC BLOCK ACCEPTED!
[2018-03-01 06:32:15.324] Solved and confirmed block 1377123 by LLY......DK8L1.CoolJ
[2018-03-01 06:32:15.325] Possible AUX block 2116721 solve diff 5679774376160.954102 > 141825048628.479614(141967015644.123749)!
[2018-03-01 06:32:15.332] AUX BLOCK ACCEPTED!
[2018-03-01 06:32:15.333] Solved and confirmed AUX block 2116721 by LLY......DK8L1.CoolJ
Best
Loshia
|
|
|
|
|
|
