Export the relevant miner log, keep an untouched private original, and make a separate redacted copy for sharing. Remove secrets and unnecessary identifiers from the copy, but preserve error messages, event order and the technical context needed to investigate. A clean-looking screenshot is not enough if its attached archive still contains the original sensitive files.
This guide is for owners preparing an Antminer support log or public troubleshooting excerpt. It covers collection, redaction and handover—not a diagnosis, a firmware installation procedure or evidence that a particular unit passed testing. The checklist below is LeedMiner's suggested workflow, distinct from the manufacturer's export instructions.
Collect evidence before changing the machine
Start with the exact model, firmware version, observed symptom and capture time, including the time zone. Give the machine a neutral case identifier such as UNIT-A. Keep the connection between that identifier and your actual asset record privately. A product family name alone may leave support unsure which hardware and interface you used.
BITMAIN's malfunction reporting guidance asks for a kernel log together with miner-status and overview screenshots during operation. Capture those views only when the machine is safe to operate; preserving evidence is not a reason to continue running equipment showing a dangerous electrical or thermal condition.
Record any recent restart, configuration change or interrupted connection. If your question concerns a rate discrepancy, use the miner-versus-pool hashrate comparison guide to establish comparable intervals first. This article instead addresses what happens to the resulting files before another person receives them.
Choose the export route that matches the interface
BITMAIN documents both older System / Kernel Log navigation and newer Miner Log interfaces. Menu names therefore need checking against the installed software, rather than guessing from a different machine's screenshot. The kernel-log navigation article describes the older route. Sign in using your existing device credentials; do not put those credentials in your support attachment.
For the interface covered by BITMAIN's current-log download instructions, open Miner Log, choose Download Log, select the current date and download the package. Its separate text-copy and history-log guide distinguishes current from historical records and explains copying the entire selected log into a text file. Check that the saved text includes both the beginning and end.
These routes describe supported interfaces, not a promise that every Antminer exposes identical buttons. If the controls differ, record the version and ask support which export they need. Avoid installing another firmware merely to make the menu match; the firmware download checklist covers that separate compatibility decision.
Keep an original and a sharing copy
Store the original export in a restricted location. Work on a duplicate, with an obvious filename such as UNIT-A-log-redacted.txt. Do not overwrite the original or label an edited excerpt as a raw export. A later investigation may need context that was removed from the public copy.
Make a short manifest listing the capture time, covered interval, source interface, filenames and any omitted sections. If the device clock is wrong, record the observed offset rather than silently rewriting every timestamp. For public discussion, an excerpt may be sufficient; for manufacturer support, ask which complete records are required and use its verified support channel.
A manufacturer may request identifying details to associate a ticket with a unit. That is different from publishing those details in a forum. The receiving channel and the question being investigated determine which identifiers are necessary.
Review fields by purpose, not just by appearance
OWASP's logging guidance identifies passwords, access tokens and other sensitive information as data to exclude or protect, and recommends considering masking or pseudonymization. The following miner-specific review is our editorial application of that principle, not a claim that every firmware writes all these fields.
| Field to inspect if present | Public sharing copy | Preserve privately or clarify with support |
|---|---|---|
| Passwords, access tokens, session cookies, private keys | Remove completely; a shortened secret is still a secret | Store credentials outside the support package; rotate exposed credentials through the relevant service |
| Pool account, worker name or payout address | Replace unnecessary identity with stable labels | Retain the device-to-worker mapping in the private case record |
| IP address, MAC address, hostname or rack location | Mask identifying values where the diagnostic question permits | Keep network relationships clear; support may need particular addressing details |
| Serial number, order reference or customer information | Remove from public excerpts and filenames | Supply required identifiers only through the verified private case |
| Error code, chain index, firmware version and units | Retain unless there is a specific sensitivity concern | These help distinguish events and equipment; explain any removal |
Do not delete every line containing an address or the word “user.” Such broad editing can erase the connection failure being investigated. Replace the value, preserve the surrounding event, and state that replacement occurred. If a network question requires distinguishing two destinations, use POOL-A and POOL-B consistently instead of collapsing both into one label.
Preserve the diagnostic story
A useful redacted copy still answers four questions: which equipment state was observed, what happened, in what order, and over which interval. Keep error spelling, numerical readings, units and board identifiers intact where appropriate. Do not turn an intermittent event into a continuous fault by removing the intervening successful entries without explanation.
For a public excerpt, label its boundaries and mention that the complete original exists privately. For a requested full support log, preserve the requested scope and discuss sensitive fields with the recipient. Neither format should be presented as an independently verified performance test.
Use this review worksheet before sending:
| Review step | Pass condition | If it fails |
|---|---|---|
| Identity consistency | UNIT-A means the same machine in the log, screenshots and note | Correct the mapping before sharing |
| Timeline | Time zone, interval and known clock offset are stated | Add the missing context without inventing timestamps |
| Redaction | Replacement labels are consistent and secrets are absent | Review the copy again, including filenames |
| Diagnostic continuity | The relevant error and surrounding sequence remain understandable | Restore necessary context from the private original |
| Attachment contents | Every file in the actual outgoing package has been reviewed | Rebuild the package from reviewed copies only |
Check the outgoing package, not only the visible text
An archive can contain more than the file you opened first. Inspect its file list and review the contents intended for sharing. Check screenshot edges, browser tabs, address bars and account menus for unrelated details. Inspect filenames too: a name containing an internal address or customer name can disclose information even when the text was edited.
For image-based redaction, verify the exported flattened result rather than trusting an editable overlay. For text, reopen the final saved file and search for the original sensitive values locally. Automated matching helps locate candidates; it does not establish that every secret or identifying context has been removed. Have a second reviewer check a sensitive case when practical.
Send a concise question with the package: model, firmware, symptom, time window, previous actions and the decision you need help with. If coordinating through LeedMiner support, start with the model and a description of the issue, then agree the appropriate private channel for any required records. A listing such as the Antminer S21 XP identifies a catalog product, not the identity or condition of your individual machine.
