CGWatcher 1.4.0, the GUI/monitor for CGMiner and BFGMiner to prevent downtime

[techman05]

I'll look over the code that displays the coin at the top. Keep in mind that for multi-coin pools (auto-switching pools), I can only report the coin if they give it to me. The data hashco.ws provided me has been down for quite some time and I have not heard back from them about fixing it. Multipool was working last I checked. Middlecoin refused to provide which coin they are mining. Other than that, it should display the coin the current profile is linked to... unless there is something I need to fix. Also, for multi-coin pools it may take up to 5 minutes for the coin to be updated because I didn't want to overload them with requests. With new auto-switching pools popping up frequently, this is something I'm going to need to revisit as soon as I get a chance. I already have some ideas on how to improve it.


techman05: I'm not sure what you're asking regarding devices. For profitability mining, you can assign a coin to a profile. A profile consists of a miner and a config file and/or arguments. You do not need to create a new config file for each profile. For example, you can create a config file that has no pools, then assign the pools for each profile in the arguments. You can also use cgminer/bfgminer's "include" setting to include one config file inside of another. I realize this may seem more complicated than just assigning a coin to a pool... mining has changed a lot since CGWatcher was created (this ability is available in CGRemote), but many users create profiles for each coin they mine, and the profile consists of multiple pools - all for that same coin as failover. That way when they select (or CGWatcher selects) a coin to mine, they know it is mining that coin and didn't just failover to the next pool, which may not be that coin.

With my devices isssue at least with drillbit some devices like to run faster than others and with the option to see that a device is not hashing presuming the overclock settings are not to its likeing I'd hope a way to say treat this differently so right from there I could pull its id number(serial number) and set it do a different overclock setting.

I kind of thought profitability monitoring meant that it would jump around to those profiles on its own so If it detected my default bitcoin profile was lacking it would go to a different coin like "dodge vs litecoin? ".
 ---found the scheduling setting though now I have to see if there's a further way to check for current profitability.
 
You already saved me a night of babysitting my miners, so cgwatcher is still better than leaving my mineing software to its problems. Maybe all I need from cgwatcher from now is a toggle "Miner is crashing alot enable logging for user" option.

[1715121619]

1715121619

[1715121619]

1715121619

[1715121619]

1715121619

[1715121619]

1715121619

[kimocoin]

Today was the first time since my previous post that I had the problem again.
The problem happened about an hour before I got home. When I got home I noticed it was more quiet than "normally".  All gpu fans were running @ low rpm's.
Both cgminer 3.7.2 & cgwatcher 1.3.4.6 were frozen with empty windows.
When I closed the cgminer window, cgwatcher unfroze and it restarted cgminer, after which the cgwatcher overheat protection kicked in with fans @ 100%, as my gpu's were @ 90 Celsius.
Haven't rebooted this miner since it happened. But everything appears to be normal.

If you haven't already, please download the latest version (1.3.5.2) as it should have some additional handling for a blank miner window.

I've been using 1.3.5.2 for a couple of days. Just now I had another blank window problem.

[milone]

Octopuss: I do plan on supporting sgminer, but I have not had a chance to look at any API changes or additions it has compared to cgminer. It seems to be the most popular GPU fork so I'll do whatever is needed to support it. Just keep in mind things are very busy for me right now trying to maintain two projects and move so feel free to let me know of any changes it requires and have patience with me getting them made. I'll try to do it as quickly as possible though.

As for the Config File Editor... a few other users have asked for something similar. I can't make any promises until I look more into it... the table is part of the .NET framework so I'll have to see how much I can manipulate it.



techman05: The device functionality you're talking about would require quite a bit of work... so I cannot say how soon I'd be able to get to it. If it's something that helps then I have no problem putting it on the to-do list... but it is quite a long list. Usually things that will help the most miners get priority, followed by requests from donators, followed by the order in which things were requested. I'd recommend posting this to the "requested features" section of the new CoinMyne support forum (http://minerremote.com/support).

As for profitability mining, yes, CGWatcher can monitor profitability and switch which profile is being mined. How often it checks is up to you... you create a scheduled action to switch profiles to whatever you'd like (using an existing profitability field or creating your own) and set it to check at a set interval or at specific times/days.

You can find more information at http://manotechnology.blogspot.com/2013/07/profitability-mining-in-cgwatcher.html


kimocoin: This is a blank screen that occurs right after the miner is started... correct? What is CGWatcher doing during this? For example, is it still waiting for the miner to start? Or has it passed that point to where it is monitoring?

[kimocoin]

kimocoin: This is a blank screen that occurs right after the miner is started... correct? What is CGWatcher doing during this? For example, is it still waiting for the miner to start? Or has it passed that point to where it is monitoring?

I'm not sure. But when it happens, I think cgwatcher is waiting for the miner to start.
I was looking at cgwatcher.log and miner.log.
This morning I noticed a frozen cgminer screen. This was not an empty cgminer window as before, but all data was frozen. At 6:43 I closed the frozen cgminer window.
This is from cgwatcher.log:
[2-2-2014 23:00:24]          The computer is now idle (30 min, 5 sec since last activity, 30 min requirement).
[3-2-2014 6:31:42]           The computer is no longer idle. <=== Here I turned the monitor on after I woke up.
[3-2-2014 6:43:00]           CGMiner process closed outside of CGWatcher! <=== Clearly I wasn't awake yet  , here I closed the frozen cgminer window
[3-2-2014 6:43:00]       [d] Monitor.EnsureMinerRunning found miner stopped; I will wait at least 15 seconds to ensure miner is running...
[3-2-2014 6:43:00]           The miner is closed outside of CGWatcher and you've requested for me to ensure it stays running. Attempting to start...
[3-2-2014 6:43:00]       [d] Miner.IsProcessAlive(2896) returns False. [First try, test process is nothing.  ex: Process with an Id of 2896 is not running.] (CPID0/CMPID=0/CBPID=0)
[3-2-2014 6:43:00]       [d] Miner.StartMining called. [Profile=Digger;MinerFile=C:\cgminer-3.7.2-windows\cgminer.exe;MinerFileUsed=C:\cgminer-3.7.2-windows\cgminer.exe;MinerExecutable=C:\cgminer-3.7.2-windows\cgminer.exe;Config=C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf (C:\cgminer-3.7.2-windows\cgminer.conf);Arguments=--config C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=C:\cgminer-3.7.2-windows\cgminer.exe (C:\cgminer-3.7.2-windows\cgminer.exe);LastKnownInstanceCount=0/0]
[3-2-2014 6:43:00]       [d] Miner.IsProcessAlive(4580) returns True. [First try, process is alive.] (CPID4580/CMPID=4580/CBPID=0)
[3-2-2014 6:43:00]       [d] Waiting for CGMiner to initialize API. Process 4580 alive=True, minerid=4580.
[3-2-2014 6:43:01]       [d] Watch for miner, expected process is 4580 (alive).
[3-2-2014 6:43:01]       [d] CGMiner process is running using ProcessID 4580, expecting port 4028.
[3-2-2014 6:43:08]       [d] CGMiner running and API initialized on port 4028, process matched to profile Digger.
[3-2-2014 6:43:08]       [d] Finish wait for miner to start, process is 4580 (alive).
[3-2-2014 6:43:08]           CGMiner started successfully.
[3-2-2014 6:43:13]           Restart miner if share totals do not change for 5 minute(s) enabled.
[3-2-2014 6:43:18]       [d] Monitor.Check skipped due to being within 30 seconds of miner start.
[3-2-2014 6:43:21]           Number of minutes without total shares increase set to 10.
[3-2-2014 6:43:28]       [d] Monitor.Check skipped due to being within 30 seconds of miner start.
[3-2-2014 7:13:37]           The computer is now idle (30 min, 7 sec since last activity, 30 min requirement).
[3-2-2014 9:07:41]           Accepted shares have not changed for 10,11667 minutes, longer than the threshold of 10 minutes. Attempting to restart...
[3-2-2014 9:07:41]       [d] Miner.Restart begin.
[3-2-2014 9:07:41]           Restart CGMiner was requested, preparing to stop then start the miner to make sure its configuration settings are reloaded...
[3-2-2014 9:07:41]       [d] Miner.PerformStopStartRestart called. (Profile=Digger;Miner=C:\cgminer-3.7.2-windows\cgminer.exe;HasFullAPIAccess=True;Initiator=Monitor;Reason=#NAME# was successfully restarted.)
[3-2-2014 9:07:41]       [d] Miner.StopMining called: Miner=C:\cgminer-3.7.2-windows\cgminer.exe;ProcessID=4580 (True);BatchProcessID=0 (False);Config=C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf;Arguments=--config C:\cgminer-3.7.2-windows\cgminer.conf;HasFullAPIAccess=True;KillOnReadOnlyAccess=True;IsBatCmdFile=False;ProcessID=4580;.
[3-2-2014 9:07:42]           CGMiner process closed outside of CGWatcher!
[3-2-2014 9:07:42]       [d] Miner.IsProcessAlive(4580) returns False. [First try, test process is nothing.  ex: Process with an Id of 4580 is not running.] (CPID0/CMPID=0/CBPID=0)
[3-2-2014 9:07:42]       [d] Miner.StartMining (for restart) called. [Profile=Digger;MinerFile=C:\cgminer-3.7.2-windows\cgminer.exe;MinerFileUsed=C:\cgminer-3.7.2-windows\cgminer.exe;MinerExecutable=C:\cgminer-3.7.2-windows\cgminer.exe;Config=C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf (C:\cgminer-3.7.2-windows\cgminer.conf);Arguments=--config C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;HasFullAPIAccess=False;IsBatCmd=False;BatCmdPath=C:\cgminer-3.7.2-windows\cgminer.exe (C:\cgminer-3.7.2-windows\cgminer.exe);LastKnownInstanceCount=0/0]
[3-2-2014 9:07:43]       [d] Miner.IsProcessAlive(2968) returns True. [First try, process is alive.] (CPID2968/CMPID=2968/CBPID=0)
[3-2-2014 9:07:43]       [d] Waiting for CGMiner to initialize API. Process 2968 alive=True, minerid=2968.
[3-2-2014 9:07:44]       [d] Watch for miner, expected process is 2968 (alive).
[3-2-2014 9:07:44]       [d] CGMiner process is running using ProcessID 2968, expecting port 4028.
[3-2-2014 10:55:31]          CGMiner process closed outside of CGWatcher! <=== Here I close the empty cgminer window
[3-2-2014 10:55:31]      [d] Finish wait for miner to start, process is 0 (not alive).
[3-2-2014 10:55:31]      [d] CGMiner process 0 not alive at Miner.StartMining exit.
[3-2-2014 10:55:31]          Start miner failed on 1st attempt. Killing any remaining processes and trying again.
[3-2-2014 10:55:31]      [d] Miner.IsProcessAlive(2968) returns False. [First try, test process is nothing.  ex: Process with an Id of 2968 is not running.] (CPID0/CMPID=0/CBPID=0)
[3-2-2014 10:55:31]          The computer is no longer idle.
[3-2-2014 10:55:31]      [d] Miner.StartMining (for restart) called. [Profile=Digger;MinerFile=C:\cgminer-3.7.2-windows\cgminer.exe;MinerFileUsed=C:\cgminer-3.7.2-windows\cgminer.exe;MinerExecutable=C:\cgminer-3.7.2-windows\cgminer.exe;Config=C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf (C:\cgminer-3.7.2-windows\cgminer.conf);Arguments=--config C:\Users\Digger\Downloads\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;HasFullAPIAccess=False;IsBatCmd=False;BatCmdPath=C:\cgminer-3.7.2-windows\cgminer.exe (C:\cgminer-3.7.2-windows\cgminer.exe);LastKnownInstanceCount=0/0]
[3-2-2014 10:55:32]      [d] Miner.IsProcessAlive(2876) returns True. [First try, process is alive.] (CPID2876/CMPID=2876/CBPID=0)
[3-2-2014 10:55:32]      [d] Waiting for CGMiner to initialize API. Process 2876 alive=True, minerid=2876.
[3-2-2014 10:55:33]      [d] Watch for miner, expected process is 2876 (alive).
[3-2-2014 10:55:33]      [d] CGMiner process is running using ProcessID 2876, expecting port 4028.
[3-2-2014 10:55:38]      [d] CGMiner running and API initialized on port 4028, process matched to profile Digger.
[3-2-2014 10:55:38]      [d] Finish wait for miner to start, process is 2876 (alive).
[3-2-2014 10:55:38]          CGMiner was successfully restarted.


I hope this helps in finding my bug.

[techman05]

Yeah I've got at least my cgwatcher set to give a half hour a day for now to your donate pool as long as I hope its working , though there is no way to track who's cgwatcher is doing what (crap another request).

I would have just hoped that when it gets it info on the device to show that and on the bottom below put a box that says "current commands followed for this device" and then go from there with any changes "hey your changing things that might affect x same devices" and then jump to those devices in some sort of order. I only have drillbit devices, soon to be replaced eroupters and some antminers , so if when you get to me on the list those are at the top for me right now ( at least the drillbit device driver/s have command to control by it serial number and its posted on cgminer startup).

[D.Khaled]

Hi milone,

First of all, thank you very much for creating this GUI tool, it really helps me schedule different mining tasks!
I would like to know if it is possibl to use CGWatcher to start multiple instances of CGminer for multi GPU machines, each mining a different coin. If so, how can I do it? Thanks!

[Shenrox]

Hi,

Wonderfull app, just one thing though...
It sometime cause one of the cards to show that it's mining at 25-400Mhs!! lol
I then have to restart the miner, can you please add a funtion like when it drops below a threshold that it restarts, also the otherway around... if it goes too high it also restarts...

Thanks

[gsrcrxsi]

so to confirm, cgwatcher still doesnt support sgminer? i thought i read that 1.3.5.2 added it.

i downloaded 1.3.5.3 yesterday, but when it calls sgminer, the whole computer locks up and intermittently flashes between a black screen and a frozen desktop, and becomes totally unresponsive (needs a reboot). but running sgminer standalone works fine.

[Thomza]

I have one question.

Is it possible to define a range of IPs in the api-allow line. My cgremote is on computer that changes IP every day so every time i need to change api-allow ip.
Or is there any other solution?

Thank you

[techman05]

get a dyndns account and set your computer to static to point to it through your router(Its easier than I make it and its only 20 dollars a year). CGRemotes at some point is going to be a solution but its not available [I think] without being on the same network as devices and I'm not sure what devices work with it (though its not in the google play store).

[Ntrain2k]

Might have found a little bug.

I tried to use the setting to change the intensity once the computer is idle for XX min.

My card is rock solid at an intensity of 19 at the set clocks.

Changed my bat to an intensity of 14 and set up CGwatcher to change it to 19 after idle.

It changes and the card begins ramping up but cgminer locks up before it settles in at the new intensity. I have to lower my GPU and MEM clocks 25+ for it to not freeze cgminer up.

Any ideas or suggestions?

[milone]

kimocoin: I'm still looking into this. I have it narrowed down to a small area of code... I just don't understand what exactly is happening. It's as if CGWatcher just freezes right along with cgminer.


techman05: I appreciate the donation mining. I'm not ruling out adding this functionality in the future... but I'm not sure how soon I'll be able to get to it. I don't have any drillbit devices so I'd be flying blind... but I'll look into getting one in order to work on this.


D.Khaled:  I'm not sure what you mean. You can run multiple instances of CGWatcher on the same computer if you need to run mutliple miner instances (you can find how to set this up here). If you want to control multiple computers from one program, you would use CGRemote.


Shenrox:  In the Monitor tab you can already set it to restart the miner or computer if the hashrate falls below a certain threshold. There isn't an option yet for restarting if it exceeds a threshold.


gsrcrxsi:  I haven't had a chance to look at sgminer to see if any changes were made that would break CGWatcher's support for it. Being a fork of cgminer, I assume that the existing API and settings would remain intact at least in the short-term, but it looks like there may have already been changes made that require CGWatcher to be updated. My guess is CGWatcher is using a config setting that sgminer no longer supports. The support it has right now was only regarding the name - so mostly cosmetic. As soon as I get a chance I'm going to switch my desktop over to it. On a related note, we've released compiled SGMiner Windows binaries available at: http://coinmyne.proboards.com/thread/24/sgminer-compiled-version-download. Scott (from CoinMyne) compiled it, so I haven't personally used it yet... but this will make it much easier for me to switch over to it.

Thomza:  You can separate IP addresses in the api-allow using a comma. Precede any IP address with W: to give it full API access. For example:

"api-allow" : "W:127.0.0.1,W:192.168.1.10,W:192.168.1.11"

or

"api-allow" : "W:127.0.0.1,W:192.168.1/24"


Ntrain2k:  So it works if you start mining at intensity 19, but if you start it at 14 and set it to increase to 19 during idle it locks up? If I'm understanding you correctly, it's difficult to say... CGWatcher is simply sending a command to cgminer telling it to change the intensity. It sounds like more of a cgminer issue, but since cgminer no longer supports GPUs I'd suggest looking at sgminer, which is a cgminer fork focusing on GPU mining. As I mentioned above, you can download Windows binaries here: http://coinmyne.proboards.com/thread/24/sgminer-compiled-version-download


Edit:
techman05: With CGRemote you can monitor miners on the same local network or over the Internet. The web and mobile apps are not finished, so you won't see them on the Play Store yet. I want to release the desktop application first, then devote all of my time to the web and mobile apps.

[Ntrain2k]

Ntrain2k:  So it works if you start mining at intensity 19, but if you start it at 14 and set it to increase to 19 during idle it locks up? If I'm understanding you correctly, it's difficult to say... CGWatcher is simply sending a command to cgminer telling it to change the intensity. It sounds like more of a cgminer issue, but since cgminer no longer supports GPUs I'd suggest looking at sgminer, which is a cgminer fork focusing on GPU mining. As I mentioned above, you can download Windows binaries here: http://coinmyne.proboards.com/thread/24/sgminer-compiled-version-download

Yes Sir, that's correct. If I fire it off at 19 it runs fine.

I'll give sgminer a shot.

Thank you.

[Shenrox]

Shenrox:  In the Monitor tab you can already set it to restart the miner or computer if the hashrate falls below a certain threshold. There isn't an option yet for restarting if it exceeds a threshold.

Hi, yes i found it and it works great, but sometimes my display driver "crashes and recovers...." (what is says in the bottom of the screen) and then cgminer and cgwatcher will both show that my hash-rate is going up exponentially. (First time found it displaying 700Mhs) Would it be possible to add the feature for when it exceeds XXX hash-rate that it also restarts, or if it could detect that the display driver has crashed.

I'm running 2 @ Gigabyte R9 280X's undervolted to 1.075V as opposed to 1.2V because i get higher hash-rates (more stable) and it runs about 20 Degrees Celsius cooler.
When i used 1 card it ran perfect for hours on end, but when i added the second it would crash and recover randomly, sometimes a few minutes, other times a few hours. (This only happens while mining, but hasn't happened yet while gaming). Sorry, now i feel like i'm hijacking this thread...

Thanks for the awesome program

[tthieu24]

i chose "restart computer if gpu sick or dead", my gpu is sick, but cgminer closed and computer do not re start. I have to manual restart. please help.

[Ntrain2k]

FYI for all, give SGminer a shot. I was able to clock my card quite a bit higher with it than with cgminer. Seems to be more stable than CGminer.

[kimocoin]

kimocoin: I'm still looking into this. I have it narrowed down to a small area of code... I just don't understand what exactly is happening. It's as if CGWatcher just freezes right along with cgminer.

I have 2 rigs, one with 3x XFX R9 290's, and one with 1 Asus R9 290.
Note: All 3 cards are elevated from the mobo by riser cables pcieX1 to pcieX16.
The rig with 3 cards is the one that is giving me these frozen miner windows. One day everything is fine, mining the whole day into the next. Then another day it freezes up to a couple of times. I just can't seem to figure out what could be causing this. Perhaps a new cgminer process is starting too soon after killing the previous cgminer.exe  I'm just guessing here.
The single card rig hasn't had any problems at all mining under cgwatcher supervision.

Just now another failed cgminer restart, this is from cgwatcher.log:

[8-2-2014 15:24:33]          Accepted shares have not changed for 5,033333 minutes, longer than the threshold of 5 minutes. Attempting to restart...
[8-2-2014 15:24:33]      [d] Miner.Restart begin.
[8-2-2014 15:24:33]          Restart CGMiner was requested, preparing to stop then start the miner to make sure its configuration settings are reloaded...
[8-2-2014 15:24:33]      [d] Miner.PerformStopStartRestart called. (Profile=Digger;Miner=C:\cgminer-3.7.2-windows\cgminer.exe;HasFullAPIAccess=True;Initiator=Monitor;Reason=#NAME# was successfully restarted.)
[8-2-2014 15:24:33]      [d] Miner.StopMining called: Miner=C:\cgminer-3.7.2-windows\cgminer.exe;ProcessID=4728 (True);BatchProcessID=0 (False);Config=C:\cgminer-3.7.2-windows\cgminer.conf;Arguments=--config C:\cgminer-3.7.2-windows\cgminer.conf;HasFullAPIAccess=True;KillOnReadOnlyAccess=True;IsBatCmdFile=False;ProcessID=4728;.
[8-2-2014 15:24:34]          CGMiner process closed outside of CGWatcher!
[8-2-2014 15:24:34]      [d] Miner.StartMining (for restart) called. [Profile=Digger;MinerFile=C:\cgminer-3.7.2-windows\cgminer.exe;MinerFileUsed=C:\cgminer-3.7.2-windows\cgminer.exe;MinerExecutable=C:\cgminer-3.7.2-windows\cgminer.exe;Config=C:\CGWatcher-1.3.5\temp.conf (C:\cgminer-3.7.2-windows\cgminer.conf);Arguments=--config C:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;HasFullAPIAccess=False;IsBatCmd=False;BatCmdPath=C:\cgminer-3.7.2-windows\cgminer.exe (C:\cgminer-3.7.2-windows\cgminer.exe);LastKnownInstanceCount=0/0]
[8-2-2014 15:24:35]      [d] Miner.IsProcessAlive(4792) returns True. [First try, process is alive.] (CPID4792/CMPID=4792/CBPID=0)
[8-2-2014 15:24:35]      [d] Waiting for CGMiner to initialize API. Process 4792 alive=True, minerid=4792.
[8-2-2014 15:24:36]      [d] Watch for miner, expected process is 4792 (alive).
[8-2-2014 15:24:36]      [d] CGMiner process is running using ProcessID 4792, expecting port 4028.
[8-2-2014 15:26:15]          CGMiner process closed outside of CGWatcher!
[8-2-2014 15:26:15]      [d] Finish wait for miner to start, process is 0 (not alive).
[8-2-2014 15:26:15]      [d] CGMiner process 0 not alive at Miner.StartMining exit.
[8-2-2014 15:26:15]          Start miner failed on 1st attempt. Killing any remaining processes and trying again.
[8-2-2014 15:26:15]      [d] Miner.IsProcessAlive(4792) returns False. [First try, test process is nothing.  ex: Process with an Id of 4792 is not running.] (CPID0/CMPID=0/CBPID=0)
[8-2-2014 15:26:15]      [d] Miner.StartMining (for restart) called. [Profile=Digger;MinerFile=C:\cgminer-3.7.2-windows\cgminer.exe;MinerFileUsed=C:\cgminer-3.7.2-windows\cgminer.exe;MinerExecutable=C:\cgminer-3.7.2-windows\cgminer.exe;Config=C:\CGWatcher-1.3.5\temp.conf (C:\cgminer-3.7.2-windows\cgminer.conf);Arguments=--config C:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;HasFullAPIAccess=False;IsBatCmd=False;BatCmdPath=C:\cgminer-3.7.2-windows\cgminer.exe (C:\cgminer-3.7.2-windows\cgminer.exe);LastKnownInstanceCount=0/0]
[8-2-2014 15:26:16]      [d] Miner.IsProcessAlive(4340) returns True. [First try, process is alive.] (CPID4340/CMPID=4340/CBPID=0)
[8-2-2014 15:26:16]      [d] Waiting for CGMiner to initialize API. Process 4340 alive=True, minerid=4340.
[8-2-2014 15:26:17]      [d] Watch for miner, expected process is 4340 (alive).
[8-2-2014 15:26:17]      [d] CGMiner process is running using ProcessID 4340, expecting port 4028.
[8-2-2014 15:26:22]      [d] CGMiner running and API initialized on port 4028, process matched to profile Digger.
[8-2-2014 15:26:22]      [d] Finish wait for miner to start, process is 4340 (alive).
[8-2-2014 15:26:22]          CGMiner was successfully restarted.

[milone]

Shenrox:  I put this option on the to-do list. I'll try to get it in one of the next few updates.


Ntrain2k:  Yeah this seems more like a cgminer issue than a cgwatcher issue. If the miner runs fine when started at 19 but crashes when started at a lower intensity and then changed to 19 (all cgwatcher is doing is sending the 'intensity' command with the new value), it would be a problem with cgminer changing intensity while mining. I haven't experienced this myself... maybe try an older version of cgminer? I use 3.5.0 myself. I don't know of any GPU-related improvements between 3.5 and 3.7.2 that you'd be missing out on. As someone who write software, I'd almost always recommend using the latest versions of software. But cgminer has been focused on ASICs for quite some time... so if you find an older version that works, you might as well stick with it (unless you move to a project with active GPU development like sgminer).


tthieu24:  Were there any other windows open? Did it look like Windows was trying to shut down (e.g. it closed other open programs)? I've made a change to CGWatcher to kill itself after it initiates the shutdown, rather than waiting for Windows to close it. This may help if CGWatcher was causing the hold up... but if this was the case I think it would have been reported before. This change will be in the next update.


kimocoin:  I just wanted to let you know I'm still hunting this down. I'm moving to LA in a few days (driving from Ohio so will be on the road a few days), so it may be a week or two before I can really spend time on it. But I will get it fixed, even if it kills me.

[Shenrox]

Shenrox:  I put this option on the to-do list. I'll try to get it in one of the next few updates.

  Thanks, will send something ur way when i exchange next time.
This driver issue is really killing my hahsrate, by as much as 50% 

[brao]

Hi guys
I need your help

My rig
Intel MB ASROCK H77 Pro4/M, Celeron CPU, 8GB RAM, 3x SAPPHIRE R9 280X TOXIC

My config
--scrypt  -o stratum+tcp://vtc.poolz.net:3333 -u XXX -p XXX -v 1 -w 256 -I 13 -g 2 --lookup-gap 2 --gpu-powertune -20,-20  --temp-overheat 89,89 --temp-cutoff 90,90 --gpu-memclock 1500,1500 --gpu-engine 1000,1000 --thread-concurrency 8193

I'm mining vertcoin where is necessary modified CGMINER (see http://vertcoin.org/)


I've got two problems with my rig I cannot get on
1. After first start, automatic or manual restart of CGWATHER one card has different gpu-memclock and gpu-engine values like other two,  like it's defined by config, it gets gpu 1150 mem 1600 and therefore  it runs lower Hashrate. After I correct it in CGWATHER GUI the card start working fine. After restart it happens again.

2. Time to time I found my rig not mining and when I start it one card cannot start. It shows 0 hash rate and after another restart it marked the card sick. This can be easily solved by automatic rig restart, but after that it runs lower hash rate due to issue #1.

btw my log https://gofile.me/24UHK/Nsar3pWa

Guys, any advice appreciated!