Claymore Miner Log Files | Bitcointalksearch.org

UMICHStatistican

newbie

Activity: 7

Merit: 0

Thanks. I'll give that a shot. I did notice, shortly after posting this message, that the log files get created much more frequently right after restarting. For example, I rebooted last night, and noticed I had about 10 log files in the span of about 10 minutes, but then I had only 1 for the next 5 hours until I checked on the server and rebooted.

It seems to me like there is something that causes an issue when it first begins executing, but the behavior stops after a bit. I'd like to dig into this more. Is there anywhere I should be looking in the log files (or perhaps elsewhere?) to dig into this a bit more to get to root cause of the issue?

Thanks again!

chohav

sr. member

Activity: 251

Merit: 250

Every new log you see means the miner has restarted and created new one. So you should find the reason why it restarts, in most cases the clocks are too high, try lowering a little.
For the DAG error you can try adding option -eres 3 to your bat file and see if that helps.

UMICHStatistican

newbie

Activity: 7

Merit: 0

I have just brought my first rig online using Claymore Miner (dual mining ETH and sia), so I'm a bit of a newb and trying to find me way here a bit.

My question is about log files with Claymore miner:

Background:
I am running 6 ASUS GTX 1070 8GB OC cards on an MSI Z170A Gaming Pro Carbon motherboard and I'm getting really good hashrates nearly 32/Mhs on each card for ETH (188.936 Mh/s total). I have set up Claymore miner to run as a background service in Windows 10. While it runs it outputs log files to the standard Claymore miner directory. What I am trying to figure out is this: I have noticed that ever few minutes or so a new log files is kicked out. I've reviewed the log files and many look normal and end like this:

Code:

01:38:03:492 18d8 parse packet: 242
01:38:03:492 18d8 ETH: job is the same
01:38:03:492 18d8 new buf size: 0

and start with the standard log file header when the service begins:

Code:

01:20:15:017 14c8 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
01:20:15:017 14c8 º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.7 º
01:20:15:033 14c8 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼
01:20:15:033 14c8
01:20:15:252 14c8 ETH: 5 pools are specified
01:20:15:252 14c8 Main Ethereum pool is eth-us-east1.nanopool.org:9999
01:20:15:252 14c8 SC: 5 pools are specified
01:20:15:267 14c8 Main Siacoin pool is sia-us-east1.nanopool.org:7777
01:20:15:611 14c8 OpenCL platform: NVIDIA CUDA
01:20:15:611 14c8 AMD OpenCL platform not found
01:20:16:314 14c8 CUDA initializing...
01:20:16:314 14c8 NVIDIA Cards available: 6
01:20:16:314 14c8 CUDA Driver Version/Runtime Version: 9.0/8.0
01:20:16:314 14c8 GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1
01:20:16:330 14c8 GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1
01:20:16:330 14c8 GPU #2: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1
01:20:16:330 14c8 GPU #3: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1
01:20:16:330 14c8 GPU #4: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1
01:20:16:346 14c8 GPU #5: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1

Occassionally, I see things like this is the logs, but certainly not all of them:

Code:

01:33:13:730 12cc CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
01:33:13:761 59c server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...
01:33:13:761 1208 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
01:33:13:870 cd8 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
01:33:13:870 160c CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
01:33:14:621 2424 GPU 2, GpuMiner cu_kd failed 73 (0), an illegal instruction was encountered
01:33:14:621 2424 GPU 2, Calc DAG failed!
01:33:14:714 1b30 GPU 3, GpuMiner cu_kd failed 73 (0), an illegal instruction was encountered
01:33:14:714 1b30 GPU 3, Calc DAG failed!

Question:
So, given this, my quesitons are:

is it normal to see these log files being produced at a rate of about 1 every 10 minute or so? If not, how can I fix this?
Also, should I be concerned about the occasional message CUDA error messages/cannot allocate big buffer for DAG messages I see in my log files? If so, how can I resolve the issue?
Is there any documentation on how to read the these log files? I can guess at what much of what is in there, but I was hoping there might be something written that describes the logging in detail

Thank you!

Topic: Claymore Miner Log Files (Read 1230 times)