Bitcoin Forum
May 09, 2024, 01:22:39 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Claymore Miner log file description  (Read 124 times)
mind_miner (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
February 19, 2020, 10:09:09 AM
 #1


Hi all,

Does eny one know if exist somewhere description of claymore's log file structure? I searched on the net and only what I've found is the documentation for claymore command line options, but nothing about log file. I'am struggling with 3-5% rejected shares. I have cellular WCDMA connection to my miner and trying to dectect the reason of these rejects - is this latency of connection or some GPU/GPU's causing rejects. Ping to the pool is ok - 60-85ms.
I did test, reduced OC to 1270 GPU Mem 2000 DPM 3 (modded bios - copied last three stripes). My rig 6x RX580 8 gb nitro. Normally is running with 34Mh/GPU, in test I reduced to 30. Nothing changed.


In logfile I see information about rejects but at first look they are telling nothing special. Does any one know the structure of buf array, (what "id" means) or what time in brackets is telling about? Examples below.


Examples of rejected shares


09:03:43:684    597fa700        buf: {"id":15,"jsonrpc":"2.0","result":false}
09:03:43:685    597fa700        ETH: Share rejected (363 ms)!
09:03:43:706    597fa700        buf: {"id":10,"jsonrpc":"2.0","result":false}
09:03:43:706    597fa700        ETH: Share rejected (384 ms)!
09:15:20:549    597fa700        buf: {"id":11,"jsonrpc":"2.0","result":false}
09:15:20:550    597fa700        ETH: Share rejected (1291 ms)!
09:19:44:012    597fa700        buf: {"id":14,"jsonrpc":"2.0","result":false}
09:19:44:012    597fa700        ETH: Share rejected (800 ms)!
09:43:05:491    597fa700        buf: {"id":14,"jsonrpc":"2.0","result":false}
09:43:05:491    597fa700        ETH: Share rejected (612 ms)!
09:44:03:852    597fa700        buf: {"id":13,"jsonrpc":"2.0","result":false}
09:44:03:853    597fa700        ETH: Share rejected (603 ms)!
09:44:03:863    597fa700        buf: {"id":13,"jsonrpc":"2.0","result":false}
09:44:03:863    597fa700        ETH: Share rejected (613 ms)!
{"id":13,"jsonrpc":"2.0","result":false}
09:45:30:793    597fa700        ETH: Share rejected (1518 ms)!
09:45:30:842    597fa700        buf: {"id":11,"jsonrpc":"2.0","result":false}
09:45:30:842    597fa700        ETH: Share rejected (1567 ms)!
10:04:53:487    597fa700        buf: {"id":11,"jsonrpc":"2.0","result":false}
10:04:53:487    597fa700        ETH: Share rejected (632 ms)!
10:09:11:661    597fa700        buf: {"id":10,"jsonrpc":"2.0","result":false}
10:09:11:661    597fa700        ETH: Share rejected (671 ms)!
10:32:54:691    597fa700        buf: {"id":12,"jsonrpc":"2.0","result":false}                                                                                                 
10:32:54:691    597fa700        ETH: Share rejected (100 ms)!                                                                                                                 




Examples of accepted shares with high times

09:07:39:045    597fa700        ETH: Share accepted (1423 ms)!
09:08:59:031    597fa700        ETH: Share accepted (1548 ms)!
09:09:20:239    597fa700        ETH: Share accepted (1294 ms)!
09:10:23:821    597fa700        ETH: Share accepted (1655 ms)!
09:13:00:334    597fa700        ETH: Share accepted (1543 ms)!
09:15:54:699    597fa700        ETH: Share accepted (1716 ms)!
09:17:10:141    597fa700        ETH: Share accepted (1680 ms)!
09:22:22:464    597fa700        ETH: Share accepted (1108 ms)!
09:24:33:657    597fa700        ETH: Share accepted (1972 ms)!
09:29:44:794    597fa700        ETH: Share accepted (1793 ms)!
09:32:30:870    597fa700        ETH: Share accepted (1373 ms)!
09:33:15:900    597fa700        ETH: Share accepted (1904 ms)!
09:33:50:372    597fa700        ETH: Share accepted (1508 ms)!
09:35:31:254    597fa700        ETH: Share accepted (1678 ms)!
09:52:11:539    597fa700        ETH: Share accepted (1635 ms)!
09:52:41:353    597fa700        ETH: Share accepted (1180 ms)!
09:56:11:120    597fa700        ETH: Share accepted (1542 ms)!
09:58:32:810    597fa700        ETH: Share accepted (1185 ms)!
10:04:16:952    597fa700        ETH: Share accepted (1157 ms)!
10:23:54:844    597fa700        ETH: Share accepted (1390 ms)!

I'll be grateful for any helpful information.


1715217759
Hero Member
*
Offline Offline

Posts: 1715217759

View Profile Personal Message (Offline)

Ignore
1715217759
Reply with quote  #2

1715217759
Report to moderator
1715217759
Hero Member
*
Offline Offline

Posts: 1715217759

View Profile Personal Message (Offline)

Ignore
1715217759
Reply with quote  #2

1715217759
Report to moderator
According to NIST and ECRYPT II, the cryptographic algorithms used in Bitcoin are expected to be strong until at least 2030. (After that, it will not be too difficult to transition to different algorithms.)
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715217759
Hero Member
*
Offline Offline

Posts: 1715217759

View Profile Personal Message (Offline)

Ignore
1715217759
Reply with quote  #2

1715217759
Report to moderator
sxemini
Member
**
Offline Offline

Activity: 1558
Merit: 69


View Profile
February 19, 2020, 11:12:48 AM
 #2

Poor connection. Thats it. Try another pool
mind_miner (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
February 19, 2020, 11:21:28 AM
 #3

Hm..., why do you think so? What does this indicate?

Information from log are not showing the rason clearly, ping is ok, rejects happens at any time during the day & night.

If I only had such possibility I would do that.

Do you know what these times are telling? Why there are rejected shares with 100ms,300ms and also are shares with 1500ms which are accepted?
There is no logic.

[EDIT]

Ok, you mean connection to the pool. I changed the pool and will see the results in one hour.
mind_miner (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
February 19, 2020, 12:38:23 PM
 #4


You were right. I chaged pool to 2miners and 100% shares accepted in 1h 15min.

Thanx.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!