Hello Guys,
SOLVED - I accidentally turned on a API key
I have quite problem, on all of my miners start appear read error: "end of file" . Everything was working great on all of my PC´s until restart.
I also try upgrade XMRig to the newest version but without any change. thank´s a lot !!!
config :
{
"api": {
"id": null,
"worker-id": null
},
"http": {
"enabled": false,
"host": "127.0.0.1",
"port": 0,
"access-token": null,
"restricted": true
},
"autosave": true,
"background": false,
"colors": true,
"title": true,
"randomx": {
"init": -1,
"init-avx2": -1,
"mode": "auto",
"1gb-pages": false,
"rdmsr": true,
"wrmsr": true,
"cache_qos": false,
"numa": true,
"scratchpad_prefetch_mode": 1
},
"cpu": {
"enabled": true,
"huge-pages": true,
"huge-pages-jit": false,
"hw-aes": null,
"priority": null,
"memory-pool": false,
"yield": true,
"asm": true,
"argon2-impl": null,
"astrobwt-max-size": 550,
"astrobwt-avx2": false,
"argon2": [0, 1, 2, 3],
"astrobwt": [0, 1, 2, 3],
"cn": [
[1, 0],
[1, 1],
[1, 2]
],
"cn-heavy": [
[1, 0],
[1, 1]
],
"cn-lite": [
[1, 0],
[1, 1],
[1, 2],
[1, 3]
],
"cn-pico": [
[2, 0],
[2, 1],
[2, 2],
[2, 3]
],
"cn/upx2": [
[2, 0],
[2, 1],
[2, 2],
[2, 3]
],
"ghostrider": [
[8, 0],
[8, 1],
[8, 2]
],
"rx": [0, 1, 2],
"rx/wow": [0, 1, 2, 3],
"cn-lite/0": false,
"cn/0": false,
"rx/arq": "rx/wow",
"rx/keva": "rx/wow"
},
"opencl": {
"enabled": false,
"cache": true,
"loader": null,
"platform": "AMD",
"adl": true,
"cn-lite/0": false,
"cn/0": false
},
"cuda": {
"enabled": false,
"loader": null,
"nvml": true,
"cn-lite/0": false,
"cn/0": false
},
"log-file": null,
"donate-level": 1,
"donate-over-proxy": 1,
"pools": [
{
"algo": "rx/0",
"coin": "XMR",
"url": "prohashing.com:3359",
"user": "adabob",
"pass": "a=randomx,c=monero,n=PC5",
"rig-id": null,
"nicehash": false,
"keepalive": false,
"enabled": true,
"tls": false,
"tls-fingerprint": null,
"daemon": false,
"socks5": null,
"self-select": null,
"submit-to-origin": false
}
],
"retries": 5,
"retry-pause": 5,
"print-time": 60,
"health-print-time": 60,
"dmi": true,
"syslog": false,
"tls": {
"enabled": false,
"protocols": null,
"cert": null,
"cert_key": null,
"ciphers": null,
"ciphersuites": null,
"dhparam": null
},
"dns": {
"ipv6": false,
"ttl": 30
},
"user-agent": null,
"verbose": 0,
"watch": true,
"pause-on-battery": false,
"pause-on-active": false
}
read error: "end of file"
Forum rules
Welcome to the mining rig and connectivity support forum!
This forum is for discussing issues with mining rigs and connectivity issues with experienced PROHASHING miners. This is a great place to ask questions about connecting specific hardware to PROHASHING.
Remember, PROHASHING employees do not closely monitor the forums like we do the official support channels, so this forum's purpose is to connect you with other PROHASHING miners who have experience with similar hardware/issues. If you have connectivity issues you are unable to resolve here on the forum, please submit a ticket through the official support channels.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Welcome to the mining rig and connectivity support forum!
This forum is for discussing issues with mining rigs and connectivity issues with experienced PROHASHING miners. This is a great place to ask questions about connecting specific hardware to PROHASHING.
Remember, PROHASHING employees do not closely monitor the forums like we do the official support channels, so this forum's purpose is to connect you with other PROHASHING miners who have experience with similar hardware/issues. If you have connectivity issues you are unable to resolve here on the forum, please submit a ticket through the official support channels.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
read error: "end of file"
Last edited by adabob on Wed Dec 22, 2021 2:05 pm, edited 2 times in total.
-
- Posts: 7
- Joined: Wed Dec 01, 2021 9:28 pm
Re: read error: "end of file"
I would save your config as a backup and try to start it with a fresh file. If it works then it was something in your configuration so you can add settings back one by one to see what the problem was.