Search content
Sort by
Showing 20 of 30 results by iLLNiSS
Re: PhoenixMiner 5.4c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Anyone know why I get error 137 when trying to set the cclock and mclock on a 3080 with latest nvidia drivers? OCing works fine in MSI Afterburner but I'm unable to do it with PhoenixMiner.
Re: lolMiner 1.11: AMD Miner for Ethash / BEAM / GRIN / Ae / Tube / Equihash & more
Is anyone able to get this working with the pool MaxHash for ETH?
Alternatively by letting lolminer decide the stratum it just hangs:
lolMiner.exe -p eth-us.maxhash.org:13011 -u 0xWallet.miner -a ETHASH --tls 1
...........................
Connecting to pool...
Connected to eth-us.maxhash.org:13011 (TLS enabled)
TLS Handshake success
Set Ethash stratum mode: EthereumStratum/1.0.0
Subscribed to stratum server
Pool responded in ETHPROXY format to EthereumStratum/1.0.0 login request. Changing to stratum mode ETHPROXY.
This happens with SSL and non SSL. It does not seem to have an issue working for me on pools that are not using ethproxy.
Code:
lolMiner.exe -p eth-us.maxhash.org:13011 -u 0xWallet.miner -a ETHASH --tls 1 --ethstratum ETHPROXY
......................
Connecting to pool...
Connected to eth-us.maxhash.org:13011 (TLS enabled)
TLS Handshake success
Set Ethash stratum mode: Ethereum Proxy
[b]Property Tree error: conversion of data to type "bool" failed[/b]
......................
Connecting to pool...
Connected to eth-us.maxhash.org:13011 (TLS enabled)
TLS Handshake success
Set Ethash stratum mode: Ethereum Proxy
[b]Property Tree error: conversion of data to type "bool" failed[/b]
Alternatively by letting lolminer decide the stratum it just hangs:
lolMiner.exe -p eth-us.maxhash.org:13011 -u 0xWallet.miner -a ETHASH --tls 1
...........................
Connecting to pool...
Connected to eth-us.maxhash.org:13011 (TLS enabled)
TLS Handshake success
Set Ethash stratum mode: EthereumStratum/1.0.0
Subscribed to stratum server
Pool responded in ETHPROXY format to EthereumStratum/1.0.0 login request. Changing to stratum mode ETHPROXY.
This happens with SSL and non SSL. It does not seem to have an issue working for me on pools that are not using ethproxy.
Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Hi all,
I have just published the 2.2_development_2 version. This version includes, amongst other things, the ability to reset rigs via Wemo or TP-Link smart plugs through user defined rules.
If you want to test it then you can download it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2
This link appears to only have the readme file included.
Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Would you mind if I add this to future release packages? Of course I'll add the necessary info and license about the author
I didnt create the script, it was sourced from here:
https://tech.scargill.net/grafana-and-influxdb/
If thats what youre referring to.
Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.
Hi Sergey,
you can find the instructions here: https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/
Thank you!
I use a script to simplify the influx and grafana install for raspberry pi (tested on raspbian stretch) if you're having any trouble installing them.
Code:
# Create InfluxDB and Grafana 4.4.3 (latest)
source /etc/os-release
OPSYS=${ID^^}
curl -sL https://repos.influxdata.com/influxdb.key | sudo apt-key add -
test $VERSION_ID = "8" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
test $VERSION_ID = "9" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
curl https://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv6"* ]] && echo "deb https://dl.bintray.com/fg2it/deb-rpi-1b jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv7l"* ]] && echo "deb https://dl.bintray.com/fg2it/deb jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
sudo apt-get -y $AQUIET remove --purge grafana grafana-data
sudo apt-get -y $AQUIET autoremove
sudo apt-get -y update && sudo apt-get install -y apt-transport-https curl influxdb grafana
sudo systemctl daemon-reload
sudo systemctl enable influxdb
sudo systemctl start influxdb
sudo systemctl enable grafana-server
sudo systemctl start grafana-server
source /etc/os-release
OPSYS=${ID^^}
curl -sL https://repos.influxdata.com/influxdb.key | sudo apt-key add -
test $VERSION_ID = "8" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
test $VERSION_ID = "9" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
curl https://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv6"* ]] && echo "deb https://dl.bintray.com/fg2it/deb-rpi-1b jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv7l"* ]] && echo "deb https://dl.bintray.com/fg2it/deb jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
sudo apt-get -y $AQUIET remove --purge grafana grafana-data
sudo apt-get -y $AQUIET autoremove
sudo apt-get -y update && sudo apt-get install -y apt-transport-https curl influxdb grafana
sudo systemctl daemon-reload
sudo systemctl enable influxdb
sudo systemctl start influxdb
sudo systemctl enable grafana-server
sudo systemctl start grafana-server
And if you're looking to set up rig monitor as a system service, here is a systemctl service file you can create (/lib/systemd/system/grm.service). Just make sure to set the execstart and workingdirectory to where your grm files are. If you do not set the workingdirectory grm will error out that it can't locate your config file even if you specify the location with -config.
Code:
[Unit]
Description=Rig Monitor
After=multi-user.target
[Service]
Type=idle
WorkingDirectory=/opt/grm
ExecStart=/opt/grm/grm
[Install]
WantedBy=multi-user.target
Description=Rig Monitor
After=multi-user.target
[Service]
Type=idle
WorkingDirectory=/opt/grm
ExecStart=/opt/grm/grm
[Install]
WantedBy=multi-user.target
After creating the file do a daemon-reload, enable the service and start the service.
Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
About the timeout, I think we need to rule out a grm issue as I have been running it on a raspberry PI 1 for almost days without issues.
Could you PM you config file, I'll set up my simulator to see if everything checks out.
Also, what's the command you are using to start grm? and are you running it as a service or from the command line?
I'll. take a look at the Nvidia output and provide you a fix.
Could you PM you config file, I'll set up my simulator to see if everything checks out.
Also, what's the command you are using to start grm? and are you running it as a service or from the command line?
I'll. take a look at the Nvidia output and provide you a fix.
With 2.1.0 it has stopped crashing on me and has now been running for 13 hours, so that's good
With 2.1.1 the fanspeed issue is resolved on my end. Good work. Your efforts are much appreciated.
Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
Hi all,
version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.
rodneymo
version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.
rodneymo
Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.
I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.
HTML output:
https://pastebin.com/JYRwbNbS
Grafana just lists all 3 cards as 0 for fanspeed/temps.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings. Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas?
Nah, on an RPI.
Try to increase the influx write interval eg 30s.
If that doesnt work then send me a trace together with the influx log
Below is after increasing to 30s in the rig-monitor conf.
Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1
rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM
As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings. Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas?
Nah, on an RPI.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
I can fire the app back up and it runs fine. Any ideas?
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas?
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Try version 2.1.d15
Thanks! I'll respond with an update if an incorrect pops up again.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
That was the case originally, but I've since added another card to it.
Here is the html output from phoenix:
https://pastebin.com/m4WEtyrR
Here is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config:
https://pastebin.com/Y6UkYAkZ
The only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay).
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
On my cell now so its hard to read the traces.
So is phoenixminer working properly now?
Wrt the config, do you have a , after the end of each rig line? Could you send me your config?
So is phoenixminer working properly now?
Wrt the config, do you have a , after the end of each rig line? Could you send me your config?
It's working properly, but only with 3 rigs. Any more and it throws errors.
I've tried with and without the "," after the last rig line and all others have a "," after them.
Forgot to mention, I sent a link to my config via PM.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Check the config file. You probably have 2 "[" at the end.
should have only one. It was a typo on the release.
should have only one. It was a typo on the release.
I removed the second ] before I was even getting any errors. There is no second ] at the end like in the original config on your release.
Here is a trace without the index flag set:
https://pastebin.com/srpaxU1X
Here is a trace with the index set to 4 to match the 4 in the config:
https://pastebin.com/xEkZHLur
It seems as though despite specifying the index to allow the program to run without error, it doesn't actually do anything after.
As I was typing this and verifying all my ducks were in a row before submitting, I found the issue. The 'riglist = [ ]' section throws an error when I have 4 rigs added. Removing 1 and the app runs just fine.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.
I need to improve that error handling.
I need to improve that error handling.
Oh sweet. This error occurs just by launching the program, but manually setting the rig index (in my case -r -4) the program appears to run. Will have to setup again as I purged grafana and influx already.
About hat error, theres a double square bracket at the end. Its a typo. If you delete one of them then it fixes it.
In my case that isn't the problem. I removed that when I first edited the conf, but the app still throws the error. With the double square it throws this error:
Code:
pi@raspberrypi:~/grm $ ./grm-2.1.d12
INFO: 2018/05/20 20:30:38 main.go:33: Starting rig-monitor...
INFO: 2018/05/20 20:30:38 main.go:50: Commmand line arguments: -config
INFO: 2018/05/20 20:30:38 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/20 20:30:38 config.go:92: Reading configuration file...
ERROR: 2018/05/20 20:30:38 config.go:100: Couldn't load config: While parsing config: (97, 2): unexpected token
INFO: 2018/05/20 20:30:38 main.go:33: Starting rig-monitor...
INFO: 2018/05/20 20:30:38 main.go:50: Commmand line arguments: -config
INFO: 2018/05/20 20:30:38 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/20 20:30:38 config.go:92: Reading configuration file...
ERROR: 2018/05/20 20:30:38 config.go:100: Couldn't load config: While parsing config: (97, 2): unexpected token
Currently I'm no longer able to see any data populated to the phoenixminer dashboard in 2.1.d.12. I think it has to do somehow with being forced to launch with the -r -4 flag as I never had issues with that prior.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.
I need to improve that error handling.
I need to improve that error handling.
Oh sweet. This error occurs just by launching the program, but manually setting the rig index (in my case -r -4) the program appears to run. Will have to setup again as I purged grafana and influx already.
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey
It seems to be picking up the info, but still not parsing it correctly.
Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that up.
Could you also send me the html output? Please make sure its complete and with the html tags.
This is direct from an 8 GPU rig. https://pastebin.com/qkjGq8JR
I dumped you file in my simulator and is running fine.
Code:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:165: Miner(PhoneixMiner) response from rig07:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:169: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:170: Eth speed: 238.965 MH/s, shares: 9508/0/0, time: 114:54
TRACE: 2018/05/19 17:53:25 phoenixminer.go:173: GPUs: 1: 30.173 MH/s (1203) 2: 30.180 MH/s (1218) 3: 29.105 MH/s (1182) 4: 30.175 MH/s (1217) 5: 29.105 MH/s (1132) 6: 30.034 MH/s (1226) 7: 30.176 MH/s (1187) 8: 30.016 MH/s (1143)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:174: Eth: Average speed (5 min): 239.036 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:175: Eth: Maximum difficulty of found share: 37.8 TH (!!!)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:176: Eth: Effective speed: 229.84 MH/s; at pool: 229.84 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 1
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[1] Model: Radeon RX 570 Series (pcie 1)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[1] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[1] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[1] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 2
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[2] Model: Radeon RX 570 Series (pcie 2)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[2] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[2] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[2] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 3
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[3] Model: Radeon RX 570 Series (pcie 3)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[3] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[3] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[3] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 4
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[4] Model: Radeon RX 570 Series (pcie 4)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[4] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[4] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[4] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 5
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[5] Model: Radeon RX 570 Series (pcie 5)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[5] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[5] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[5] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 6
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[6] Model: Radeon RX 570 Series (pcie 6)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[6] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[6] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[6] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 7
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[7] Model: Radeon RX 570 Series (pcie 8)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[7] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[7] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[7] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 8
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[8] Model: Radeon RX 570 Series (pcie 9)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[8] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[8] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[8] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:187: PhoenixMiner line to parse: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:317: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[0] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[0] fan: 44
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[1] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[1] fan: 47
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[2] temperature: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[2] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[3] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[3] fan: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[4] temperature: 58
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[4] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[5] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[5] fan: 55
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[6] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[6] fan: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[7] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[7] fan: 54
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:169: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:170: Eth speed: 238.965 MH/s, shares: 9508/0/0, time: 114:54
TRACE: 2018/05/19 17:53:25 phoenixminer.go:173: GPUs: 1: 30.173 MH/s (1203) 2: 30.180 MH/s (1218) 3: 29.105 MH/s (1182) 4: 30.175 MH/s (1217) 5: 29.105 MH/s (1132) 6: 30.034 MH/s (1226) 7: 30.176 MH/s (1187) 8: 30.016 MH/s (1143)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:174: Eth: Average speed (5 min): 239.036 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:175: Eth: Maximum difficulty of found share: 37.8 TH (!!!)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:176: Eth: Effective speed: 229.84 MH/s; at pool: 229.84 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 1
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[1] Model: Radeon RX 570 Series (pcie 1)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[1] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[1] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[1] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 2
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[2] Model: Radeon RX 570 Series (pcie 2)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[2] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[2] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[2] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 3
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[3] Model: Radeon RX 570 Series (pcie 3)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[3] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[3] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[3] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 4
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[4] Model: Radeon RX 570 Series (pcie 4)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[4] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[4] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[4] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 5
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[5] Model: Radeon RX 570 Series (pcie 5)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[5] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[5] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[5] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 6
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[6] Model: Radeon RX 570 Series (pcie 6)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[6] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[6] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[6] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 7
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[7] Model: Radeon RX 570 Series (pcie 8)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[7] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[7] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[7] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 8
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[8] Model: Radeon RX 570 Series (pcie 9)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[8] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[8] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[8] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:187: PhoenixMiner line to parse: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:317: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[0] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[0] fan: 44
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[1] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[1] fan: 47
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[2] temperature: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[2] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[3] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[3] fan: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[4] temperature: 58
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[4] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[5] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[5] fan: 55
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[6] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[6] fan: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[7] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[7] fan: 54
Which version are you running? try with the latest 2.1.d.12
This was with 2.1.d.12.
I'm at a standstill now. I can't even run the app anymore. For whatever reason when I kill the app with ctrl+c, it refuses to run again. This seems to require me a wipe of everything to start over which is quite time consuming. I only get one chance to run it before it throws this error after killing it:
Code:
panic: runtime error: index out of range
goroutine 25 [running]:
go-rig-monitor/miner.loadPhoenixMinerData(0xc4200c6140, 0x9150c0, 0xc42014e0c0, 0xc4200a5c80, 0x1)
/Users/ramf/go/src/go-rig-monitor/miner/phoenixminer.go:141 +0x28d0
go-rig-monitor/miner.Monitor(0x9150c0, 0xc42014e0c0, 0xc4200a5e60, 0xc4200a5c80)
/Users/ramf/go/src/go-rig-monitor/miner/rig-monitor.go:57 +0x611
created by main.main
/Users/ramf/go/src/go-rig-monitor/main.go:153 +0xcd2
goroutine 25 [running]:
go-rig-monitor/miner.loadPhoenixMinerData(0xc4200c6140, 0x9150c0, 0xc42014e0c0, 0xc4200a5c80, 0x1)
/Users/ramf/go/src/go-rig-monitor/miner/phoenixminer.go:141 +0x28d0
go-rig-monitor/miner.Monitor(0x9150c0, 0xc42014e0c0, 0xc4200a5e60, 0xc4200a5c80)
/Users/ramf/go/src/go-rig-monitor/miner/rig-monitor.go:57 +0x611
created by main.main
/Users/ramf/go/src/go-rig-monitor/main.go:153 +0xcd2
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey
It seems to be picking up the info, but still not parsing it correctly.
Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that up.
Could you also send me the html output? Please make sure its complete and with the html tags.
This is direct from an 8 GPU rig. https://pastebin.com/qkjGq8JR
Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey
It seems to be picking up the info, but still not parsing it correctly.
Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.
Finally got around to testing (had a burst pipe in the basement). It seems as though it's not picking up all the details for all rigs. It shows the hashrates fine for all the rigs, but it is only reporting the gpu temp and fanspeed for one of the rigs.
Ok. Please send me a trace and Ill take a look at it.
https://pastebin.com/6McV8M08
At a quick glance I notice an error with parsing the GPU info. It's listing all the temperatures for all GPUs (line 43, 104 & 256) in the first GPU1 line instead of the standard GPU name info. The next parse with the hashrate (GPUs) is correct so that would explain why hashrates are working.