Error during mining on Burstcoin-jminer-0.4.7-SNAPSHOT
-
Dear Burstonians,
Recently I notice that during mining thru jminer-0.4.7-SNAPSHOT I am receiving below error message every couple of blocks ( these are 3 examples):
Error: Failed to submit nonce to pool: java.io.EOFException: HttpConnectionOverHTTP@71e3991a(l:/192.168.1.3:60225 <-> r:burst.lexitoshi.uk/192.99.181.231:8124,closed=false)=>HttpChannelOverHTTP@e614664(exchange=HttpExchange@4b6060e9 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@5ccbe99d(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@6a52f88e{s=START}],recv=HttpReceiverOverHTTP@6e04c1c6(rsp=CONTENT,failure=null)[HttpParser{s=CLOSED,66 of -1}]]<-SocketChannelEndPoint@262b83c7{burst.lexitoshi.uk/192.99.181.231:8124<->/192.168.1.3:60225,ISHUT,fill=-,flush=-,to=27635/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@71e3991a(l:/192.168.1.3:60225 <-> r:burst.lexitoshi.uk/192.99.181.231:8124,closed=false)=>HttpChannelOverHTTP@e614664(exchange=HttpExchange@4b6060e9 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@5ccbe99d(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@6a52f88e{s=START}],recv=HttpReceiverOverHTTP@6e04c1c6(rsp=CONTENT,failure=null)[HttpParser{s=CLOSED,66 of -1}]]
Error: Failed to submit nonce to pool: java.io.EOFException: HttpConnectionOverHTTP@20b010b4(l:/192.168.1.3:56109 <-> r:burst.lexitoshi.uk/192.99.181.231:8124,closed=false)=>HttpChannelOverHTTP@145be08b(exchange=HttpExchange@3e50562d req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@744fb299(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@63c73d9d{s=START}],recv=HttpReceiverOverHTTP@2853d6d6(rsp=CONTENT,failure=null)[HttpParser{s=CLOSED,68 of -1}]]<-SocketChannelEndPoint@148e1ccf{burst.lexitoshi.uk/192.99.181.231:8124<->/192.168.1.3:56109,ISHUT,fill=-,flush=-,to=25609/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@20b010b4(l:/192.168.1.3:56109 <-> r:burst.lexitoshi.uk/192.99.181.231:8124,closed=false)=>HttpChannelOverHTTP@145be08b(exchange=HttpExchange@3e50562d req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@744fb299(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@63c73d9d{s=START}],recv=HttpReceiverOverHTTP@2853d6d6(rsp=CONTENT,failure=null)[HttpParser{s=CLOSED,68 of -1}]]
b.j.c.n.task.NetworkSubmitPoolNonceTask : Error: Failed to submit nonce to pool: java.io.EOFException: HttpConnectionOverHTTP@4024c65e(l:/192.168.1.3:49502 <-> r:burst.lexitoshi.uk/192.99.181.231:8124,closed=false)=>HttpChannelOverHTTP@45cc294d(exchange=HttpExchange@c632f15 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@7a33c4fd(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@6b3f4373{s=START}],recv=HttpReceiverOverHTTP@4f9d9918(rsp=CONTENT,failure=null)[HttpParser{s=CLOSED,66 of -1}]]<-SocketChannelEndPoint@5a131c79{burst.lexitoshi.uk/192.99.181.231:8124<->/192.168.1.3:49502,ISHUT,fill=-,flush=-,to=31287/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@4024c65e(l:/192.168.1.3:49502 <-> r:burst.lexitoshi.uk/192.99.181.231:8124,closed=false)=>HttpChannelOverHTTP@45cc294d(exchange=HttpExchange@c632f15 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@7a33c4fd(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@6b3f4373{s=START}],recv=HttpReceiverOverHTTP@4f9d9918(rsp=CONTENT,failure=null)[HttpParser{s=CLOSED,66 of -1}]]
Is it something to do we the recent issues with the network or is it something on my side/pool side?
The only thing a can notice are 3 different forwarding ports (60225,56109,49502)from my side and port 8124 that was set up for http://burst.lexitoshi.uk/I think @Lexicon might givee some advise.
Ip85
-
whats your burst address?
-
BURST-TRJM-KG32-29MD-7V3EN
-
@Ip85 Try increase 'connectionTimeout' setting in jminer.properties (AIO client will overwrite this setting, so you need to start jminer manually with run script in same folder)
-
@luxe Changed it to "connectionTimeout=500000" from 360000. Let's wait a bit if the error pops out again.
-
360000 is quite high already ... a request should not take 6 minutes ... maybe that is the problem ... if connection do not get interrupted by connectionTimeout ... you could also try use just 30sec or something so 30000.
-
@luxe Done
-
@luxe After changing timeout to 30000 the error occurs even more:

-
@Ip85 ok i was just guessing ... and on increase? maybe you should try if another pool works better for you ... do you have issues with other miners? (just in case you tried one)
-
@luxe The thing is lex's pool gives me the best payouts from several others I've tried. I will try to tweak connection timeout a little bit more. The first miner I was using was Blagos but the reading times were around 26Mb/s so bit to slow :). So I am forced to use Jminer with openCL. I have only integrated GPU and "energy efficient" CPU ( TDP: 6W). Unless you have any advise?
-
@Ip85 have you tried creepsky's miner yet? i quite like that one for the interface it gives. i personally use blagos and dont have much of an issue.
it depends how much your mining with. if its small amounts <10tb i wouldnt worry to much
-
@Lexicon I have played a little bit with timeout and for now it is set on connectionTimeout=65000 and error is occurring only 1 per 10 block or so. I mine with 20TB and more in the future. My reading times on Jminer are around 18s and with Blagos it is a 60s at best. What are your speeds at Blagos and what CPU you have?
i might have a go on Creepsky's.
-
