Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts)

[Lexicon]

the Pending Payments tab is back.

it now updates every 30 minutes

its also looking like yesterday someone attempted to DDOS the pool.

didnt take down the service though

[Lexicon]

Guys,

was up all weekend writing a connector for the pool that basically uses multiple wallets.

[Burstde]

@Lexicon That's beautiful

[Propagandalf]

@Lexicon Is this intended for miners, or pool admins?

[manfromafar]

@Propagandalf said in Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts):

@Lexicon Is this intended for miners, or pool admins?

Admins. Its so if one wallet messes up on the pool is just switched to another

[Lexicon]

almost fully synced.

ive tested this locally but not sure how its going to contend with 760 miners.

[Lexicon]

just switched on the load balancer already noticed a great decrease in submission time

rebroadcasting is working well.

downside. due to the severe decrease in submission time current roundshares has caused browsers to hang and crash. so for now ive disabled it. and if anyone wants to check it try using index3.html.

this inturn has caused the time to bug out in the corner so will work on fixs for this soon

[Pon]

Hi, i changed to this pool yesterday....everything seems to working perfect except that its the first time i see "Not Confirmed DLs".

While most of my DLs get confirmed there are a few that they dont. Since i'm generally new to mining and at the previous pool never got that type of error i wanted to ask if this is normal and if its because the pool is stressed or i have to change something in my settings ??

thanks in advanced !

[Lexicon]

@Pon said in Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts):

Hi, i changed to this pool yesterday....everything seems to working perfect except that its the first time i see "Not Confirmed DLs".

While most of my DLs get confirmed there are a few that they dont. Since i'm generally new to mining and at the previous pool never got that type of error i wanted to ask if this is normal and if its because the pool is stressed or i have to change something in my settings ??

thanks in advanced !

got any details on the deadlines that are not confirming? if they are recent enough i can check now to see if the pool has received them

[Pon]

wow that's a super fast reply !! i ll try to get a screenshot when i see the next unconfirmed dl. thanks again !!

[Lexicon]

@Pon its no problem. even when you get an unconfirmed deadline the pool will always receive it.

that said we have had a load of really fast blocks recently and when these happen it doesn't give enough time for the miner to respond back. before the next round starts so it severs the connection :)

get info failed is nothing to worry about either. thats only failing because the wallet its looking at for winner info hasnt caught up to the rest of the chain.

[Pon]

@Lexicon i really appreciate the support man !!.

here's a screenshot (fresh...like 5mins ago)

http://imgur.com/a/oM8t0

and a second one, 2mins after.
http://imgur.com/a/pZxf5

still if you say its common then i don't really mind

[Lexicon]

@Pon

heres your info :)

so round 372725 you got no conform.

the pools tells me on that round you got a deadline for
{
"accountId": "13556499195252515745",
"baseTarget": "676884",
"height": "372725",
"share": 3.382630843326631,
"deadline": 1920839,
"lastUpdate": 1497868941098
},

so it looks fine. all confirmed :) it even got the one before

"13556499195252515745": {
      "id": 0,
      "capacity": 15429,
      "currentRoundShare": {
        "accountId": "13556499195252515745",
        "baseTarget": "583581",
        "height": "372728",
        "share": 27.74271527126743,
        "deadline": 271650,
        "lastUpdate": 1497869180514
      },
      "prevRoundShare": [
        {
          "accountId": "13556499195252515745",
          "baseTarget": "602445",
          "height": "372727",
          "share": 19.763896179619127,
          "deadline": 369377,
          "lastUpdate": 1497869129744
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "685590",
          "height": "372726",
          "share": 11.78767110187024,
          "deadline": 619319,
          "lastUpdate": 1497869078784
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "676884",
          "height": "372725",
          "share": 3.382630843326631,
          "deadline": 1920839,
          "lastUpdate": 1497868941098
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "671775",
          "height": "372724",
          "share": 13.84076672646035,
          "deadline": 473016,
          "lastUpdate": 1497868830759
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "677713",
          "height": "372722",
          "share": 387.18991531621043,
          "deadline": 17280,
          "lastUpdate": 1497868632852
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "657343",
          "height": "372723",
          "share": 15.633253663564732,
          "deadline": 427975,
          "lastUpdate": 1497868620460
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "697083",
          "height": "372721",
          "share": 8.472472716303105,
          "deadline": 765956,
          "lastUpdate": 1497868523232
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "669695",
          "height": "372720",
          "share": 37.03984212046611,
          "deadline": 177302,
          "lastUpdate": 1497868417529
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "644682",
          "height": "372719",
          "share": 0,
          "deadline": -1,
          "lastUpdate": 1497868363751
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "635009",
          "height": "372718",
          "share": 87.39930544564517,
          "deadline": 78056,
          "lastUpdate": 1497868322909
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "659438",
          "height": "372717",
          "share": 11.53954851151497,
          "deadline": 577959,
          "lastUpdate": 1497867958907
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "634287",
          "height": "372716",
          "share": 2.8564320226763256,
          "deadline": 2427449,
          "lastUpdate": 1497867890727
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "610519",
          "height": "372715",
          "share": 290.7917164990521,
          "deadline": 24773,
          "lastUpdate": 1497867642334
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "584712",
          "height": "372714",
          "share": 20.824802473631753,
          "deadline": 361191,
          "lastUpdate": 1497867497761
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "572188",
          "height": "372713",
          "share": 0,
          "deadline": -1,
          "lastUpdate": 1497867358067
        },
        {
          "accountId": "13556499195252515745",
          "baseTarget": "552350",
          "height": "372712",
          "share": 183.81335526420523,
          "deadline": 43318,
          "lastUpdate": 1497867308360
        }
      ],
``

[Pon]

@Lexicon again all i can do is thank you for your time mate !! cheers :)

[Lexicon]

new bug fix.

hopefully this stops the blocks jumping backward and forwards. theres basically a small delay on round start where a few of the wallets are on the prior block so miners are switching between these wallets with different block numbers..

with any luck this issue is now resolved.

[beast0crypt]

@Lexicon said in Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts):

new bug fix.

hopefully this stops the blocks jumping backward and forwards. theres basically a small delay on round start where a few of the wallets are on the prior block so miners are switching between these wallets with different block numbers..

with any luck this issue is now resolved.

a fresh log :

18:41:46 New block 372803, baseTarget 367294, netDiff 49892 Tb
18:41:48 Winner: 73s by FCP4-FNTE-5CSK-DHGC4 (tstsk8dood)
18:41:48 Winner's pool: LBQ2-XLPT-S2S8-64ZG5 (all.poolofd32th.club)

18:41:48 New block 372802, baseTarget 365589, netDiff 50125 Tb
18:41:50 [13902634915633307503] found DL: 196546
18:41:51 [13902634915633307503] sent DL: 196546 2d 06:35:46
18:42:01 Thread "X:\Burst\plots" @ 12.4 sec (74.8 MB/s) CPU 57.95%
18:42:01 Thread "Z:\Burst\plots" @ 12.5 sec (74.7 MB/s) CPU 57.72%
WINNER: Get info failed: 10060

18:42:05 New block 372803, baseTarget 367294, netDiff 49892 Tb
18:42:13 [13902634915633307503] found DL: 1390638
18:42:13 [13902634915633307503] sent DL: 1390638 16d 02:17:18
18:42:18 Thread "Z:\Burst\plots" @ 12.3 sec (75.8 MB/s) CPU 57.43%
18:42:18 Thread "X:\Burst\plots" @ 12.3 sec (75.8 MB/s) CPU 57.44%
18:42:36 [13902634915633307503] sent DL: 1390638 16d 02:17:18
18:42:43 [13902634915633307503] confirmed DL: 1390638 16d 02:17:18
18:42:53 Thread "Y:\Burst\plots" @ 47.9 sec (19.5 MB/s) CPU 15.42%

[beast0crypt]

Wow , no wonder my pending payment is up only 5 burst since this morning :(

19:35:30 New block 372816, baseTarget 377080, netDiff 48597 Tb
19:35:35 [13902634915633307503] found DL: 2096408
19:35:35 [13902634915633307503] sent DL: 2096408 24d 06:20:08
19:35:40 [13902634915633307503] found DL: 1629743
19:35:40 [13902634915633307503] sent DL: 1629743 18d 20:42:23
19:35:43 Thread "Z:\Burst\plots" @ 12.4 sec (74.9 MB/s) CPU 57.01%
19:35:43 Thread "X:\Burst\plots" @ 12.8 sec (72.8 MB/s) CPU 58.12%
19:35:47 [13902634915633307503] confirmed DL: 1629743 18d 20:42:23
19:35:48 [13902634915633307503] 2096408 > 1629743 discarded
19:36:18 Thread "Y:\Burst\plots" @ 48.0 sec (19.4 MB/s) CPU 15.54%
WINNER: Get info failed: 10060

19:40:05 New block 372817, baseTarget 385922, netDiff 47484 Tb
19:40:17 [13902634915633307503] found DL: 756974
19:40:18 [13902634915633307503] sent DL: 756974 8d 18:16:14
19:40:18 Thread "Z:\Burst\plots" @ 12.8 sec (73.0 MB/s) CPU 55.44%
19:40:18 Thread "X:\Burst\plots" @ 13.0 sec (71.9 MB/s) CPU 56.57%
WINNER: Get info failed: 10060

19:40:37 New block 372818, baseTarget 367068, netDiff 49923 Tb
19:40:40 Winner: 286s by JAWS-KNAW-BFX9-H7SB9 (>--^-:> Patrol_/.\o/./_Shar
k <:-^--<)
19:40:40 Winner's pool: E925-FACX-C2X8-49772 (poolofd32th.club Main Wallet)

19:40:40 New block 372817, baseTarget 385922, netDiff 47484 Tb
19:40:44 Winner: no info yet

19:40:44 New block 372818, baseTarget 367068, netDiff 49923 Tb
WINNER: Get info failed: 10060

19:40:57 New block 372818, baseTarget 367068, netDiff 49923 Tb
19:41:10 Thread "X:\Burst\plots" @ 12.4 sec (75.1 MB/s) CPU 57.57%
19:41:10 Thread "Z:\Burst\plots" @ 12.5 sec (74.6 MB/s) CPU 57.66%
19:41:45 Thread "Y:\Burst\plots" @ 48.0 sec (19.4 MB/s) CPU 15.62%
19:45:33 Winner: no info yet

19:45:33 New block 372819, baseTarget 376948, netDiff 48614 Tb
19:45:35 Winner: 33s by JEQM-5MVL-SC4U-HT9N8 (Foise)
19:45:35 Winner's pool: RNMB-9FJW-3BJW-F3Z3M (Burst Mining Club Pool Wallet)

19:45:35 New block 372818, baseTarget 367068, netDiff 49923 Tb
19:45:47 Thread "Z:\Burst\plots" @ 12.7 sec (73.5 MB/s) CPU 57.74%
19:45:48 Thread "X:\Burst\plots" @ 12.8 sec (72.6 MB/s) CPU 58.44%
WINNER: Get info failed: 10060

[Lexicon]

@beast0crypt said in Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts):

Wow , no wonder my pending payment is up only 5 burst since this morning :(

19:35:30 New block 372816, baseTarget 377080, netDiff 48597 Tb
19:35:35 [13902634915633307503] found DL: 2096408
19:35:35 [13902634915633307503] sent DL: 2096408 24d 06:20:08
19:35:40 [13902634915633307503] found DL: 1629743
19:35:40 [13902634915633307503] sent DL: 1629743 18d 20:42:23
19:35:43 Thread "Z:\Burst\plots" @ 12.4 sec (74.9 MB/s) CPU 57.01%
19:35:43 Thread "X:\Burst\plots" @ 12.8 sec (72.8 MB/s) CPU 58.12%
19:35:47 [13902634915633307503] confirmed DL: 1629743 18d 20:42:23
19:35:48 [13902634915633307503] 2096408 > 1629743 discarded
19:36:18 Thread "Y:\Burst\plots" @ 48.0 sec (19.4 MB/s) CPU 15.54%
WINNER: Get info failed: 10060

19:40:05 New block 372817, baseTarget 385922, netDiff 47484 Tb
19:40:17 [13902634915633307503] found DL: 756974
19:40:18 [13902634915633307503] sent DL: 756974 8d 18:16:14
19:40:18 Thread "Z:\Burst\plots" @ 12.8 sec (73.0 MB/s) CPU 55.44%
19:40:18 Thread "X:\Burst\plots" @ 13.0 sec (71.9 MB/s) CPU 56.57%
WINNER: Get info failed: 10060

19:40:37 New block 372818, baseTarget 367068, netDiff 49923 Tb
19:40:40 Winner: 286s by JAWS-KNAW-BFX9-H7SB9 (>--^-:> Patrol_/.\o/./_Shar
k <:-^--<)
19:40:40 Winner's pool: E925-FACX-C2X8-49772 (poolofd32th.club Main Wallet)

19:40:40 New block 372817, baseTarget 385922, netDiff 47484 Tb
19:40:44 Winner: no info yet

19:40:44 New block 372818, baseTarget 367068, netDiff 49923 Tb
WINNER: Get info failed: 10060

19:40:57 New block 372818, baseTarget 367068, netDiff 49923 Tb
19:41:10 Thread "X:\Burst\plots" @ 12.4 sec (75.1 MB/s) CPU 57.57%
19:41:10 Thread "Z:\Burst\plots" @ 12.5 sec (74.6 MB/s) CPU 57.66%
19:41:45 Thread "Y:\Burst\plots" @ 48.0 sec (19.4 MB/s) CPU 15.62%
19:45:33 Winner: no info yet

19:45:33 New block 372819, baseTarget 376948, netDiff 48614 Tb
19:45:35 Winner: 33s by JEQM-5MVL-SC4U-HT9N8 (Foise)
19:45:35 Winner's pool: RNMB-9FJW-3BJW-F3Z3M (Burst Mining Club Pool Wallet)

19:45:35 New block 372818, baseTarget 367068, netDiff 49923 Tb
19:45:47 Thread "Z:\Burst\plots" @ 12.7 sec (73.5 MB/s) CPU 57.74%
19:45:48 Thread "X:\Burst\plots" @ 12.8 sec (72.6 MB/s) CPU 58.44%
WINNER: Get info failed: 10060

the discards are fine thats basically saying that you have submitted a better deadline so it discards the worse one. unsure on why the block numbers keep pinging back and forth. im guessing its due to delayed getmininginfo querys so ill seperate these out from the rest. ive disabled the other wallets until i find a fix. shouldnt take to long

[beast0crypt]

19:35:30 New block 372816, baseTarget 377080, netDiff 48597 Tb
19:35:35 [13902634915633307503] found DL: 2096408
19:35:35 [13902634915633307503] sent DL: 2096408 24d 06:20:08
19:35:40 [13902634915633307503] found DL: 1629743
19:35:40 [13902634915633307503] sent DL: 1629743 18d 20:42:23
19:35:43 Thread "Z:\Burst\plots" @ 12.4 sec (74.9 MB/s) CPU 57.01%
19:35:43 Thread "X:\Burst\plots" @ 12.8 sec (72.8 MB/s) CPU 58.12%
19:35:47 [13902634915633307503] confirmed DL: 1629743 18d 20:42:23
19:35:48 [13902634915633307503] 2096408 > 1629743 discarded
19:36:18 Thread "Y:\Burst\plots" @ 48.0 sec (19.4 MB/s) CPU 15.54%
WINNER: Get info failed: 10060

Isn't this the best DL ? Found , sent , confirmed and then discarded

And I just got this :

00:05:41 New block 372879, baseTarget 577661, netDiff 31723 Tb
00:05:41 [13902634915633307503] found DL: 303904
00:05:42 [13902634915633307503] sent DL: 303904 3d 12:25:04
00:05:52 [13902634915633307503] found DL: 153470
00:05:52 [13902634915633307503] sent DL: 153470 1d 18:37:50
00:05:54 Thread "X:\Burst\plots" @ 12.4 sec (75.1 MB/s) CPU 56.71%
00:05:54 Thread "Z:\Burst\plots" @ 12.7 sec (73.6 MB/s) CPU 57.60%
00:06:21 [13902634915633307503] confirmed DL: 303904 3d 12:25:04
00:06:29 Thread "Y:\Burst\plots" @ 48.3 sec (19.3 MB/s) CPU 16.00%
WINNER: Get info failed: 10060

It confirms the longer deadline and the shorter one just vanishes ?

[Lexicon]

@beast0crypt said in Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts):

19:35:48 [13902634915633307503] 2096408 > 1629743 discarded

19:35:30 New block 372816, baseTarget 377080, netDiff 48597 Tb
19:35:35 [13902634915633307503] found DL: 2096408
19:35:35 [13902634915633307503] sent DL: 2096408 24d 06:20:08
19:35:40 [13902634915633307503] found DL: 1629743
19:35:40 [13902634915633307503] sent DL: 1629743 18d 20:42:23
19:35:43 Thread "Z:\Burst\plots" @ 12.4 sec (74.9 MB/s) CPU 57.01%
19:35:43 Thread "X:\Burst\plots" @ 12.8 sec (72.8 MB/s) CPU 58.12%
19:35:47 [13902634915633307503] confirmed DL: 1629743 18d 20:42:23 <- best DL confirmed
19:35:48 [13902634915633307503] 2096408 > 1629743 discarded < worse DL Discarded
19:36:18 Thread "Y:\Burst\plots" @ 48.0 sec (19.4 MB/s) CPU 15.54%

2096408 is greater than 1629743 so its discarded.. it could be blagos rebroadcast feature trying to rebroadcast the deadline.

all the deadlines confirm if you can message me as soon as they happen i can extract your share data to show you the deadline was received. like ive done before. the server takes priority on taking incoming connections overe outgoing on submit nonce.

the block changing should now be sorted. load balancer is switched on.

the reason for this new connector is because i go on holiday to Portugal this weekend for a week so access to the internet will be very limited. so i need to ensure uptime is optimal.

due to the block switching error i had to switch back to using a single wallet so this would of caused dl submissions to get much worse.

about 9 hours ago i think i fixed the block skipping issue in the load balancer. and switched these over. please let me know if you see it again :)