BURST BASH!!!!! 48 HOURS Starting Monday 18:00 CET

[tross]

Come to my pool and mine plus 3k burst will be sent to the pool every +- 3 hours!

[IceBurst]

Hey Tross, I'm getting something odd with this Pool, typically the first block goes through fine but then I get "strange results" in out blocks. See the screen shot, this is using JMiner 4.4.

I have 5 months mining on Burst-Team without this issue, same everything. Let me know if you need me to run a specific test.

-IceBurst

[tross]

I have no idea! I used jminer beore but never seen this lol show your conf!

[IceBurst]

@tross

plotPaths=Z:/plots,D:/plots,H:/plots
poolMining=true
numericAccountId=8176504108164725152
poolServer=http://burstpool.ddns.net
listPlotFiles=true
connectionTimeout=20000
walletServer=
winnerRetriesOnAsync=
winnerRetryIntervalInMs=
devPool=
devPoolCommitsPerRound=
soloServer=http://localhost:8125
passPhrase=
targetDeadline=2592000
platformId=0
deviceId=0
restartInterval=120
chunkPartNonces=320000
refreshInterval=120
readerThreads=2

[tross]

@IceBurst try TargetDeadline =4000000,

[IceBurst]

I'll let you know, I also updated my jminer to 4.5

• It appears I don't get confirms from the pool on any block accept for the first

• All drives are local to my LAN, H:\ and Z:\ are both net mapped locally (1GB connection)

[tross]

@IceBurst Ok thanks ! I also seen you have a drive z: is that cloud storage? Updated miner should help! You could try the client jminer and see if same.

[tross]

There are still 10 hours left at http://burstpool.ddns.net/#!!!

[IceBurst]

Very interesting, I always wondered about sloppy graphics now I have my own to submit. Here is a clean run, with values as requested on the new JMiner 4.5. See how Block #1 on the start works fine and then I don't get confirms from any future blocks?

[tross]

@IceBurst The difficulty is high almost double your tb. To be honest I dont know and I dont see why you cant mine successfully here. I used jminer 1 year ago with an HD 5850 and seen some of the same but also had some good deadlines. I also see you are getting deadlines recorded in all shares. There are others that use jminer but never heard anything bad.

[RichBC]

@IceBurst Very strange. Do you know if the nonces that say submitted are actually appearing at the pool and it's just the confirmation that is missing?

I am using jminer 0.4.4, as the changes in 4.5 were not important to me, with no confirmation problems. You could try 0.4.4 and see if that fixes things?

Rich

[IceBurst]

It's is odd, I was able to confirm with the pool GUI that the "confirmed" submissions are reported correctly. I have tried with both jminer 4.4 and 4.5 with the same result. Back a couple of months ago when Tomahawker(sp?) setup a server based on the same preliminary code base I saw a similar issue but did not address it. It appears that others might be having the same issue and not be aware based on the provided information below.

F7LM-N3BR-2943-HFYHR	114174 years	
VAX9-BFZ6-XSX5-CW2EN	71531 years	
2XFL-Q586-AM6F-7BQZX	142775 years	

For the good of the community
-IceBurst

[tross]

Part 2 of our Burst Bash starts in 20 min at http://burst.lexitoshi.uk/#

[RichBC]

@tross Is that the format to use in the configuration with the # or does it need a port number?

Rich

[tross]

@RichBC leave the # off sorry!

[RichBC]

@tross OK all set and nearly there, just need another confirmation, but we need some more miners.

Rich

[tross]

Go to http://burst.lexitoshi.uk/# for another 24hr of fun! People are still going to my pool ! Go to lexicon pool and get free burst!

[luxe]

@IceBurst said in BURST BASH!!!!! 48 HOURS Starting Monday 18:00 CET:

Very interesting, I always wondered about sloppy graphics now I have my own to submit. Here is a clean run, with values as requested on the new JMiner 4.5. See how Block #1 on the start works fine and then I don't get confirms from any future blocks?

@IceBurst In jminer 4.5 the 'strange dl' stuff is only logged if you enable 'debug=true' in jminer.properties. If not it will just not confirm. The 'strange dl' is not necessary related to a pool, i also get it on solo from time to time, may indicate a partly corrupted plotfile, i'm not sure why in some cases the calculated dl by miner does not match with calculated from wallet. (But thats why this shows up) It may be just a read issue ... i fixed some of this by replotting the affected plotfiles ... but i'm getting lazy these days, so i just live with it if it appears from time to time. If you enable debug, you may notice, that it is the same plotfile causing this in most cases.

Edit: Your drive may also be the issue, check SMART status or/and try chkdsk on it.

[IceBurst]

@luxe Thanks @luxe as you can see in my properties file I do have debug=true. It's very odd that it happens consistently after the first block and only on this one pool, I switched back to Burst-Team today and the issue never showed up again. If my drives are failing I'm in big trouble as this machine isn't even a year old yet or my office raid array is failing which would be even worse! If I find time to look at it some more I will but I think for the time being I'm marking this as, "Closed" - "Over Come By Events"

-IceBurst

[Lexicon]

sending another 3k shortly just waiting for my wallet to start up