Topic: SEGWIT LTC.TBDICE.ORG 0.5% fee SOLO MM LTC/DGE POOL 3K+ LTC/7K+ DGE blks solved - page 21. (Read 42897 times)

Hello. I'm fairly new to mining but have setup my miner to use TBDICE and when I look at my user it shows up as a POOL user. Shouldn't it say SELF?
Here's my script
bfgminer.exe --scrypt -o stratum+tcp://tbdice.org:13333 -u MAazxdg6pP8p879FEHgUQfFTah3wWPvtHV -p diff_128   -S MLD:all --set MLD:clock=796

Thanks for any help

Yes I can PM me your TeamViewer  ID and PASS. What is you TimeZone

I am UTC+3?

I am not sure how to mess with SCP or how to access the ssh, but I do have teamviewer on my PC! Can you help me? Thanks

Hi,
Here is something like how-to

https://bitcointalksearch.org/topic/m.20414675

If you are having difficulties doing it please prepare PC with Team viewer which can access your miner via ssh. I will do rest for you
Best
Loshia

Hi Loshia, I just bought a Antrouter R1 LTC, can you help me, I have no idea how to get into the config because I know the password feel is getting truncated therefore not receiving the doge address and other parameters correctly.

Hi,
No for the moment sorry. Pool and LTC daemon needs to be updated...
I am working on SPLNS LTC + MM DOGE pool.
Like this one  (the original CK BTC pool)
https://bitcointalksearch.org/topic/ckpoolorg-closed-1876330
When i finish it i will update solo also
Best
Loshia

Hi loshia - Can I use the new LTC address format, the one that starts with "M" - thanks

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

Pool was updated and restarted. There issue was found and fixed
Mine on...
Best
Loshia
Pool OP

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
 

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

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
---------------------

Thanks to sunsetblues the issue was found and fixed. Please let me know if you do receive emails ok
Best
Loshia
Pool OP

PM sent.

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 => [email protected] 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 => [email protected] 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 =>[email protected] 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 =>[email protected] 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.....

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? 

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

Can you provide any screenshot or something? I really don't see that error on FF, it's just fine for me.

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

I had already tried FF, Edge, and Opera. I'll just move my miners until I get a reply from loshia