Topic: CGWatcher 1.4.0, a GUI/monitor for CGMiner & BFGMiner to help minimize downtime - page 11. (Read 402549 times)

same problem here no profile switching only one time after restart

Is there any reference to the scheduler in the log? I dont think i changed anything as far as the schedule goes other than performing a few additional checks to make sure things run as expected. I'll go over it again to see if i missed something. keep in mind if you create an action to switch to most profitable profile and the most profitable profile is the profile you're already using.. nothing will happen. It should create a log entry if an action is skipped/ignored, successful, or fails.

But this could be a bug somewhere... I'll go over it tonight. Any relevant log entries related to the scheduler not working would be helpful and appreciated.

I, like many others, am also having issues with the scheduler using version 1.3.4.5

I've setup a scheduler to switch to the most profitable profile (adjusted) every 5 minutes. It will run once when I just startup CGwatcher for the first time, but then will not run anymore.

Up until today, I was using 1.3.3 with the exact same settings and it worked fine.

I'm getting errors in CGWatcher on just 1 of my 3 machines. They are all running Win7 64-bit. Can anyone help me with this?

When I go to Settings > Manage Profiles, I get this unhandled exception: http://imgur.com/eclfS90,KK6ok8u,2jSmdIK#2 . If I click Continue, it just closes that dialog, but doesn't let me manage my profiles.

If I unzip the zip for the first time, then launch it and click Yes to setup the profile, I get this error 438: http://imgur.com/eclfS90,KK6ok8u,2jSmdIK#1

If I click OK and try to save a new profile, I get: http://imgur.com/eclfS90,KK6ok8u,2jSmdIK#0

I tried uninstalling and reinstalling the .NET framework 4.0 from the page, and also 4.5. I also tried a .NET cleanup tool. I also tried copying the whole directory from a working machine.

 

I'm curious as to what is causing it to not work until a CGRemote restart. After the refresh fails, does clicking on the Refresh button do anything? If the miner goes to "unavailable" status, it should still try to refresh if you click the Refresh button, and it should still auto-refresh if auto-refresh is enabled, it just may auto-refresh less often until it is available again. A lot of "shoulds" there, so maybe there are some issues that are preventing that from happening.

As for the hostname, it stores the IP address the hostname was last resolved to. Then if it tries to connect and fails, it *should* try to resolve it again to see if a new IP address is returned. I think there is still some improvements to be made here.

It's been a busy couple weeks but I think I have fixed the CGWatcher issues with the latest update yesterday and am looking forward to diving back into CGRemote. But it may be another day or two before I can really devote some time to it. I've already added the ability to submit bugs inside of CGRemote, and I'm in the process of creating a webpage allowing me to also add bugs/suggestions/feature request that will use the same database so I can stay organized when going through the bajillion emails I wake up to each day.

Justin you got me wrong. It just breaks once a day and nothing will bring it back. It is showing (Unavailable, wrong passkey?), but obviously passkey is correct.
Only thing to do is close program, launch it and works like a charm again.

Edit: Just happened again, but this time it wont resolve the hostname even after restart. I did add the same miner 2nd time and it connected fine. From the debug I found out that cgremote was trying to use old ip address to connect.

Thanks, I presume json is easiest for you, still working on my complete list of coins and profits once I'm happy will put something together and email you the details so you can test at your leisure.

Hmm, is it coz I'm using a modified cgminer 3.7.2 (middlecoin fork) that the temp is not displayed on the status page (in the graph)? Even tho it reports it under devices (correct)?

Are the not responding fixes in the newer version? Or should I wait for another update?

The update is now available. The in-app update (check for update & auto-update) will not be triggered for this update until I make sure I didn't break anything new. Working on my notebook is messing my routine up. So you'll have to go to the website to download it.

Among the changes (that I remembered to write down):

- Fixed 'restart miner if hashrate below X' monitor option not triggering if sha256 cutoff hashrate was set to zero.
- Fixed 'decrease font size' and 'increase font size' for main window (still experimental, changes not saved)
- Reduced minimum height of main window to 460 to accommodate that one guy running 640x480 resolution
- Config File Editor skips quantity check for GPU settings if "device" setting is used.
- Message box after saving profile removed.
- Profile and coin (if applicable) added to title bar
- Diff1 accepted and rejected share counts for bfgminer are sum of device counts to hopefully provide a more accurate number.
- CGWatcher executable path added to About tab to help differentiate multiple instances
- Profile and coin added to tray icon tooltip
- Fixed profiles & variables data file errors if the path they were set to is no longer valid (CGWatcher folder moved)
- Fixed config file load/save errors if a setting had a \ character.

Check in Settings to see if the refresh interval for unavailable miners is enabled. If it is, this interval will override individual miner refresh intervals. For example, you add a miner and set its refresh interval to 60 seconds. The refresh interval for unavailable miners is 5 minutes. If this miner becomes unavailable, it will refresh every 5 minutes instead of every 60 seconds. This is to reduce unnecessary refreshes for miners that are down, as they require intervention to get running again so no point in checking them constantly. Likewise, there is a setting for refresh interval while computer is idle, so if the CGRemote computer is idle, you can reduce the number of refreshes since theoretically nobody is there to watch anyway. This setting may be removed once the monitor and scheduling options are added to CGRemote.


If the miner won't connect at all and always shows as unavailable, it is a firewall issue, or a port-forwarding issue (if connecting to miners over the Internet). There are occasionally messages that fail, in which case it tries again... but if it never connects that indicates a problem outside of CGWatcher/CGRemote.

I am considering your idea... in fact it's something I already have on the to-do list so I guess it's past considering. Tigggger also suggested some additional coin features, which I'll also be adding. Right now I'm implementing the same coin features CGWatcher has into CGRemote, so you'll be able to select CoinWarz or CoinChoose. Then there will be an additional feature where you can have CGRemote get data from CoinWarz/CoinChoose and send it to all CGWatchers connected to it, saving you api calls.

Check the email I sent for more information on setting up CGRemote. Windows prompts you to allow programs through your firewall, and creates a program rule. But you may also need to create port rules. I'm not sure why this is... maybe a known issue with Windows Firewall. If you're connecting to miners over the Internet, you'll also want to enable edge traversal on incoming firewall rules, as this allows for unsolicited connections coming in from over the Internet (which CGRemote will be).



Tigggger: If you want to create a standard for coin data, I'll implement it (no guarantee on how soon). Maybe we can even get the websites to use it.

I get the same problem, on a local network. I just figured it's a bug to be fixed, or CGWatcher was too busy to allow the connection.

Milone, I don't need an ETA but I would like to know if you're considering my solution to be able to combine Coinwarz and Coinchoose data.

Cgremote is wroking fine for me except once a day it gives me "miner unavailable" and I have to restart the program to make it work.

It is possible that my external IP changes when this occurs. Still I am using no-ip domain service to connect.

yes

I'm using the latest version. I'm trying to use CGRemote to connect to my miners on different networks in a remote location, but it seems that this feature is broken. I'm pretty sure I set up the port forwarding correctly.

Has anyone successfully connected to a computer not on the same network?

Thank you for your reply, I'm running a 7950 on that one but I think I fixed my problem by making cgminer write a config and make cgwatcher use that one.

I currently have most profitable coin profile switching !

it shows failed to switch to most profitable adjusted schedule

CGWatcher reads information from ADL and NVAPI, but it doesn't change anything. So when you set clock speeds, fan speeds, voltages, etc. in your config, the only thing actually changing those things is the miner. Same thing if you change these values in the Devices tab in CGWatcher - it is just passing that request on to the miner. I did it this way to prevent clashes between CGWatcher and the miner, and because I want CGWatcher to just be a layer on top of the miner.

Overclocking done by cgminer/bfgminer should not persist through restarts.

i set everything up and had it running for some time i did some cablemanagement in my pc and had to reposition the gpu from PCI_E2 to PCI_E4 (MSI A970 G46 mainboard).
after that i had (the pc crashed several times) to use afterburner to OC it to wanted values (what cgwatcher did previously through the config file).
is cgwatcher further down in the "OC-access-order" or will the OC stay trough reboots (provided i shut down correctly)?

Tigggger:  All great ideas. I'm trying to get a minor update out quick, so these ideas won't be included. I don't want to rush them and potentially break something. I'll make sure they're in the next major update.


chickenthr33:  Yeah there were some problems with the text resizing. I already fixed it so it should work in the next update. It is still considered experimental so it does not save font sizes, so they will need reapplied each time CGWatcher is opened for now.


duz: CGWatcher gets stats from the miner, so if you want to zero them you can send the miner the "zero" command (you can do this in the Tests tab). Alternatively, you could restart mining obviously.


MineRock:  I'm not sure what prompt you're referring to. When you modify the active profile while mining and are asked if you want to restart the miner, I got rid of the messagebox that would show the results of whether the miner restarted successfully or not. Instead it shows a notification in the main window, which does not need clicked on. When you modify the config file in use, it asks you if you want to restart to use the new config file because I imagine sometimes the user may want to finish out the current config file then use the new one next time it is restarted. If you can give me more detail on which prompt I'll get it removed or make a setting to remove it.


TheUniporn:  Which cards are you running? And when you say "reopening cgminer", do you mean CGWatcher restarting it? If so, make sure the setting "Kill miner process during restart instead of sending 'quit' command" is enabled (you have to click Save Settings to save anything in the Settings tab.) I don't think it is CGWatcher that is freezing your PC... it is the miner. CGWatcher just launches the miner, and the miner is what sets your GPU clock speeds, fan speeds, voltage, etc. based on your config settings.


MineRock:  Efficiency is defined as number of shares returned/work item. This was dropped from cgminer's UI, which means it probably no longer provides useful information and perhaps was not updated to reflect changes in mining over the past 6 months. This is why I chose this stat to be replaced by a custom stat if you wish.


tangmonkey:  You can create scheduled actions to trigger when a specified program starts or stops running.


If anyone emails me and I don't get back to you within a week, please don't hesitate to email me again. Users for both CGWatcher and CGRemote have grown significantly over the past couple months and it's possible that occasionally something gets lost in the pile (except for donations for CGRemote, which I do stay on top of). Thanks for your patience, and I assure you I am trying my hardest to get every fix and feature made as soon as possible. I may or may not have some exciting news in the next two weeks regarding both of these projects.

Any way you could add a feature that watches for processes to open such as bf4.exe and pauses the miner, then starts again once bf4.exe closes? I'd really like this feature.