Documentation
No Statistics Data
Explains why hashrate, online, and chart data may not appear in Custom Management when a customer server previously installed the official build or another CID custom build, and whether fee configuration is affected.
No Statistics Data
If a customer server first installed the official RustMinerSystem build, or first installed a custom build that belongs to another CID, and then later installs your custom build, statistics may still be reported to the version that was installed first.
In this situation, your Custom Management backend may not show statistics for that server, including hashrate statistics, online statistics, client counts, and chart data.
Impact Scope
| Item | Impact |
|---|---|
| Hashrate statistics | May not appear in your Custom Management backend. |
| Online statistics | May not be counted under your custom build. |
| Statistics charts | Coin hashrate, online trend, client trend, and similar charts may have no data. |
| External wallet fee configuration | Not affected. It can still be pushed to the corresponding client normally. |
Why This Happens
After the RustMinerSystem client establishes a statistics ownership relationship on a server, statistics continue to prefer the reporting relationship created by the earliest installed version. In other words, if the server first connected through the official build or another CID custom build, later installing your custom build may not move the statistics ownership to your backend.
Therefore, no statistics in the backend does not mean the client is not running, and it does not mean the inside fee configuration from Service Management was not delivered.
Does Configuration Still Work?
The core inside fee configuration feature is not affected by this issue. You can still maintain the corresponding CID, coin, ratio, device name, pool address, port, and protocol configuration in Custom Management, and the backend can still push those settings to the corresponding client.
The limitation is visibility: you may be able to confirm configuration delivery and client behavior, but you may not see complete hashrate, online status, fee hashrate, or chart data in the current Custom Management backend. The inside fee configuration itself should still be checked from Edit Fee Rate in Service Management.
Troubleshooting Suggestions
- Confirm whether the customer server previously installed the official build or another CID custom build.
- If the backend has no statistics but configuration can be delivered normally, treat it first as a statistics ownership issue under the earliest installed version.
- When explaining it to the customer, clarify that this is a statistics reporting ownership issue and does not affect the core inside fee configuration feature.
- For new servers, ask customers to install the custom build that should own the statistics first, so the statistics ownership does not attach to another version.