How to get your miner's logs
Where miner logs live, how to turn on file logging, how to find the first error yourself, and what to send when you ask for help with a rig.
Why should you get the log first?
The log turns guessing into knowing. It records the exact error, when it happened and what the miner was doing.
A support request that starts with a log skips a day of back-and-forth. Save the log before you change anything, so the evidence of the problem is kept.
How do you turn on file logging?
Most miners always print their log to the console, the window the miner runs in. They write it to a file only when you ask.
- Open your start script in a text editor.
- Add the miner's log-file flag.
- Point the flag at a file next to the miner.
- Save the script and start the miner.
The exact flag name is in each miner's own documentation. From then on, every session adds to that same file, restart or not.
How do you read the log yourself?
Do not start at the last line. Scroll to the first ERROR or WARN line after the problem started.
The first error is usually the cause. Everything after it is a consequence.
Lines about the pool connection show whether the problem is the rig or the network. Look for these:
- Connecting to the pool.
- Logging in.
- Shares accepted, or rejected with a reason.
Reject reasons are printed word for word, so you can read exactly why a share failed.
What should you send when you ask for help?
Copy the log from a minute before the problem to a minute after. Send it with these details:
- The miner name and version.
- The GPU models and the driver version.
- The exact start command, with your wallet address shortened.
- What you changed most recently.
Send the text, not screenshots. A screenshot of a scrolled console is worse than the text itself.