Topic: Windows mining monitoring tool - v2-BETA [OPEN BETA] - page 43. (Read 104806 times)
The monitor has stopped unless I manually start start-http-only.bat manually. It appears the startmonitor.bat is not starting the http now. It really stopped working when I used the updater.bat.
The config is OK, and everything works well .... exept that the second rig clock is wrong.
So the monitor page think that the last update are 1 hour ago.
Just change the clock on the second rig to match your local time and the monitoring page should display well
LolSo the monitor page think that the last update are 1 hour ago.
Just change the clock on the second rig to match your local time and the monitoring page should display well
http://imgdepo.com/id/i9239710
Thanks!!
@happytorn
As you can see : http://i.imgur.com/eTlcPQ5.jpg
When I debug it in the javascript console of Chrome browser and simulate that the time in the json is good.
The page display well on your monitor page.
edit : It's strange bacause the two output are displayed with a time that seems to be good.
But the timestamp of the 2 rigs are not synchronized
See how they are displayed for me when I look at the timestamps your rig have set in the mining-info.json.
So I defenitivly thinks that is a clock problem or timezone of the second rig
As you can see : http://i.imgur.com/eTlcPQ5.jpg
When I debug it in the javascript console of Chrome browser and simulate that the time in the json is good.
The page display well on your monitor page.
edit : It's strange bacause the two output are displayed with a time that seems to be good.
But the timestamp of the 2 rigs are not synchronized
See how they are displayed for me when I look at the timestamps your rig have set in the mining-info.json.
So I defenitivly thinks that is a clock problem or timezone of the second rig
Code:
Rig 1 --> new Date(1463062544000)
Thu May 12 2016 16:15:44 GMT+0200 (Paris, Madrid (heure d’été))
Rig 2 --> new Date(1463058926000)
Thu May 12 2016 15:15:26 GMT+0200 (Paris, Madrid (heure d’été))
The config is OK, and everything works well .... exept that the second rig clock is wrong.
So the monitor page think that the last update are 1 hour ago.
Just change the clock on the second rig to match your local time and the monitoring page should display well
So the monitor page think that the last update are 1 hour ago.
Just change the clock on the second rig to match your local time and the monitoring page should display well
http://imgdepo.com/id/i9238525
First rig:
192.168.1.3
config:
"http://95.37.153.222:9511/mining-infos.json",
"http://95.37.153.222:9512/mining-infos.json"
Second rig:
192.168.1.5
config:
"http://192.168.1.5:9510/mining-infos.json"
NAT:
http://imgdepo.com/id/i9238523
What am I doing wrong?
First rig:
192.168.1.3
config:
"http://95.37.153.222:9511/mining-infos.json",
"http://95.37.153.222:9512/mining-infos.json"
Second rig:
192.168.1.5
config:
"http://192.168.1.5:9510/mining-infos.json"
NAT:
http://imgdepo.com/id/i9238523
What am I doing wrong?
Use only the external link, because when you acces it from internet localhost is not available.
And when you are accessing it from localhost, you will see the rig two times.
{
"rigs":[
"http://molitar.no-ip.org:9510/mining-infos.json"
]
}
Will works event on your LAN
And when you are accessing it from localhost, you will see the rig two times.
{
"rigs":[
"http://molitar.no-ip.org:9510/mining-infos.json"
]
}
Will works event on your LAN
Wow this is a very nice utility. Be nice if it could alert or monitor if a rig goes down. But thanks for this great utility.
Now I have a problem when I had a friend try to browse it he gets this error.
Ok I partially solved this problem but now I have one that always reports the same error. What I did was setup rigs as...
{
"rigs":[
"http://localhost:9510/mining-infos.json",
"http://molitar.no-ip.org:9510/mining-infos.json"
]
}
Is this the only way to make it work for both local and external access or can this be edited differently? I also tried other ports for each one but that made it fail to work completely.
Now I have a problem when I had a friend try to browse it he gets this error.
Ok I partially solved this problem but now I have one that always reports the same error. What I did was setup rigs as...
{
"rigs":[
"http://localhost:9510/mining-infos.json",
"http://molitar.no-ip.org:9510/mining-infos.json"
]
}
Is this the only way to make it work for both local and external access or can this be edited differently? I also tried other ports for each one but that made it fail to work completely.
1- I can't be certain to have the exact order of GPU as the miner display it. And it also a well known problem of the Claymore miner.
Because I'm using what OpenhardwareMonitor are listing, and the miner is using what the AMD SDK is listing ... whick can be also different of the order of the GPU in driver interface or MSI AfterBurner.
But I can display the ID of the GPU in the PCI-E port, wich can help to identify wich card is monitored.
For exemple on my motherbord with 7 PCI-E ports, the cards are on PCI-E 0 and 6.
2- I don't understand this one. You want a shortcut to edit the miner .bat file ?
3- Start/Stop so you can just stop mining but let the monitoring tool and http server run ?
4- I'll try to do that
5- Why not. But I have to change and rewrite a lot of thing to store the values over time. I'll try to think about that for a next version
Because I'm using what OpenhardwareMonitor are listing, and the miner is using what the AMD SDK is listing ... whick can be also different of the order of the GPU in driver interface or MSI AfterBurner.
But I can display the ID of the GPU in the PCI-E port, wich can help to identify wich card is monitored.
For exemple on my motherbord with 7 PCI-E ports, the cards are on PCI-E 0 and 6.
2- I don't understand this one. You want a shortcut to edit the miner .bat file ?
3- Start/Stop so you can just stop mining but let the monitoring tool and http server run ?
4- I'll try to do that
5- Why not. But I have to change and rewrite a lot of thing to store the values over time. I'll try to think about that for a next version
Did you have some feature you want me to try to add on the monitoring tool ?
Hello! Thank you for your work with miner monitor!
About featuses:
1. Wrote near "AMD Radeon HD 7800 Series" number of GPU in miner. For example -"GPU0 - AMD Radeon HD 7800 Series"
Because list of GPU not equal number of GPU in miner
2. Editor Start.bat - file
3. Start/stop Start.bat (or other miner start file)
4. Add button with manual refresh stats
5. Maybe add Graphs, gpu temp, number shares/s or other
Thanks, and with the updater script it will be easier to update the tool without having to download and manually unzip and replace the file etc ...
Did you have some feature you want me to try to add on the monitoring tool ?
Did you have some feature you want me to try to add on the monitoring tool ?
No, everything is ok. Even stopped disappear hashrate when updating monitoring on any Rig. Super, very well.
A small mistake in index.html "Miner outpout" -> Miner output, I correct myself
A small mistake in index.html "Miner outpout" -> Miner output, I correct myself
th00ber
v1.4.1 is super!
P.S. There is one feature DCR >1000 displays "1000. Mh/s"
Does it introduce a wrong calculation of the sum ?v1.4.1 is super!
P.S. There is one feature DCR >1000 displays "1000. Mh/s"
I'll try to reproduce this on my own rig and fix the display on a v1.4.2
@Abcederian, do you see the advantage of using Claymore vs ethOS? I am using ethOS right now so just curious.
Also i am building a native iOS app for monitoring ether mining rigs, i am starting with ethOS since it's what i am using. I wanna get some input on how other mining rigs using diff software are being monitored. I would love to add that to the app i am building so it can serve more users. is there like an API that can be used? or a web panel that has JSON formatted info? here is a WIP of the iOS app:
https://www.dropbox.com/s/bjnl5ol3ucbf6s2/thumb_IMG_6351_1024.jpg?dl=0
Also i am building a native iOS app for monitoring ether mining rigs, i am starting with ethOS since it's what i am using. I wanna get some input on how other mining rigs using diff software are being monitored. I would love to add that to the app i am building so it can serve more users. is there like an API that can be used? or a web panel that has JSON formatted info? here is a WIP of the iOS app:
https://www.dropbox.com/s/bjnl5ol3ucbf6s2/thumb_IMG_6351_1024.jpg?dl=0
th00ber
v1.4.1 is super!
P.S. There is one feature DCR >1000 displays "1000. Mh/s"
v1.4.1 is super!
P.S. There is one feature DCR >1000 displays "1000. Mh/s"
First solution
To see the values from the internet, you have to have every rig accessible from the internet (with port forward) and use the forwarded IP+port in the config.
(ex: public 10.25.67.201:8095 -> local 192.168.1.10:9510. The config should contains 10.25.67.201:8095, not the local IP because it will not be accessible from the internet. And the config.json are accessed from the browser with javascript, not with server-side code, so if the statuspage displayed from your public IP cannot access the json file, nothing is displayed). If you add a rule for every rig in your internet router and have a correct rig list in the master config file, I will works
Second solution
You have a linux server accessible on internet and you can publish the json from every rig to this PC (that is what I do, i publish from my rig + desktop to my vps cloud machine).
But it could have been a linux server or rapsberry PI on your LAN and so you only have one port forward to do.
To see the values from the internet, you have to have every rig accessible from the internet (with port forward) and use the forwarded IP+port in the config.
(ex: public 10.25.67.201:8095 -> local 192.168.1.10:9510. The config should contains 10.25.67.201:8095, not the local IP because it will not be accessible from the internet. And the config.json are accessed from the browser with javascript, not with server-side code, so if the statuspage displayed from your public IP cannot access the json file, nothing is displayed). If you add a rule for every rig in your internet router and have a correct rig list in the master config file, I will works
Second solution
You have a linux server accessible on internet and you can publish the json from every rig to this PC (that is what I do, i publish from my rig + desktop to my vps cloud machine).
But it could have been a linux server or rapsberry PI on your LAN and so you only have one port forward to do.
Hello,
Thank you for your advice now that everything is OK.
Just got poslendí question can somehow set up so I can watch even from the Internet.
So far, I see the value in your home network?
Screenshot: http://www.jpeg.cz/images/2016/05/10/3J4w8.jpg
Thank you for your advice now that everything is OK.
Just got poslendí question can somehow set up so I can watch even from the Internet.
So far, I see the value in your home network?
Screenshot: http://www.jpeg.cz/images/2016/05/10/3J4w8.jpg
The other PC that is the "master" and display all the rigs has to run the HTTP server that is in the v1.4+ to display the name.
If this PC is not a rig, you could just run the HTTP server on it not all the monitoring tool.
When all the rigs and the "master" are updated every rigs will have his name displayed
If this PC is not a rig, you could just run the HTTP server on it not all the monitoring tool.
When all the rigs and the "master" are updated every rigs will have his name displayed
Hello,
that's how it goes but only on one PC.
When I look at another PC so everything except the name indicates Miner.
I forward the picture how it looks and how do I set values on another PC so I could watch all Miner.
Screenshot:
http://www.jpeg.cz/images/2016/05/10/o3zDl.jpg
http://www.jpeg.cz/images/2016/05/10/hgrGO.jpg
It's online, can you run the updater and test the v1.4.1 ?
I have remove the loop and replace it instead with a warning if after at the end of the setup OHM is still not running.
In your case we will see if it better like that
I have remove the loop and replace it instead with a warning if after at the end of the setup OHM is still not running.
In your case we will see if it better like that
Ok, I'll remove this feature and patch the v1.4 so you could test and update.
It will be ok in a few minutes
It will be ok in a few minutes
Jump to: