milone, hi!
I can`t find CGWatcher 1.3.3.2 on your site
Topic: CGWatcher 1.4.0, the GUI/monitor for CGMiner and BFGMiner to prevent downtime - page 15. (Read 180485 times)
December 09, 2013, 05:24:56 AM
December 08, 2013, 06:48:58 PM
Some suggestions:
1. Instead of emailing from your server, how about sending email through the user's server?
2. You already allow switching of coins based on profitability, could you add the ability to switch to the next profitable coin if no results are being generated or if there is some other problem preventing money from being made on a given coin? Sort of like coin failover?
3. Ability to disable a profile so it is not mined on, even if it is most profitable.
Thanks,
tejsei
1. Instead of emailing from your server, how about sending email through the user's server?
2. You already allow switching of coins based on profitability, could you add the ability to switch to the next profitable coin if no results are being generated or if there is some other problem preventing money from being made on a given coin? Sort of like coin failover?
3. Ability to disable a profile so it is not mined on, even if it is most profitable.
Thanks,
tejsei
December 06, 2013, 07:58:15 PM
Eboman - when this happens (while it is stuck), can you please go to the Tests tab and click the 'Create Debug Report' button. Email the report to my email address at the top of Readme.txt. If you can also attach cgwatcher.log, that may be helpful.
Is cgminer running correctly when this occurs? Typically CGWatcher should wait approximately 30-60 seconds for the miner to start, depending on settings. The only time it will wait indefinitely is if you have not specified any pools, which means you type in your pool manually when prompted by cgminer.
The more info you can provide when this happens, the better.
codegnome - I'll try to get this into the next update. A field will be added in the 'Coins' tab of coin manager allowing you to adjust coins individually.
Is cgminer running correctly when this occurs? Typically CGWatcher should wait approximately 30-60 seconds for the miner to start, depending on settings. The only time it will wait indefinitely is if you have not specified any pools, which means you type in your pool manually when prompted by cgminer.
The more info you can provide when this happens, the better.
codegnome - I'll try to get this into the next update. A field will be added in the 'Coins' tab of coin manager allowing you to adjust coins individually.
December 06, 2013, 07:52:21 PM
I would like to customize the profitability totals from CoinWarz. Say add 500% to LTC and subtract 100% from TAG. For example to compensate for stales.
Adjust profitability is a feature in MultiMiner - I am able to adjust the profitability by addition or multiplication. Multiminer no longer supports CGMiner so I am trying to move my rigs to CGWatcher.
I will investigate the custom field and see if that will work for me. Thanks!
Adjust profitability is a feature in MultiMiner - I am able to adjust the profitability by addition or multiplication. Multiminer no longer supports CGMiner so I am trying to move my rigs to CGWatcher.
I will investigate the custom field and see if that will work for me. Thanks!
December 06, 2013, 07:44:27 PM
I have been running CGWatcher for a few days now and can't say enough good things about it.
I went away for Thanksgiving and came home only to find out my miner software had "crashed" about 3 hours after I left the house (CGMiner). So, instead of 5 days of Litecoin mining in the bank, I only had 3 hours (not to mention the power bill for running the computer with nothing to show for it). That prompted me to get CGWatcher up and running and I wish I had done it months ago.
But here's a odd thing that's happened three times so far and I'm not sure if there's something I can do to make it not happen anymore.
Sometimes when I check on the miner rig, CGWatcher says it's restarting CGMiner. But here's the problem -- Right now, I'm 13,136 seconds into the "restart process". Is there a way to have it do something other than get "stuck" waiting for the restart to happen?? Like maybe cancel the current restart action and try it again? Or restart the computer?? Under the "monitor" tab, I have every option checked.
What I've been doing is manually restarting CGWatcher and CGMiner to get it "unstuck". But that sort of defeats the purpose of CGWatcher.
Any ideas or help would be greatly appreciated.
Thanks everyone!!!
Eboman
I went away for Thanksgiving and came home only to find out my miner software had "crashed" about 3 hours after I left the house (CGMiner). So, instead of 5 days of Litecoin mining in the bank, I only had 3 hours (not to mention the power bill for running the computer with nothing to show for it). That prompted me to get CGWatcher up and running and I wish I had done it months ago.
But here's a odd thing that's happened three times so far and I'm not sure if there's something I can do to make it not happen anymore.
Sometimes when I check on the miner rig, CGWatcher says it's restarting CGMiner. But here's the problem -- Right now, I'm 13,136 seconds into the "restart process". Is there a way to have it do something other than get "stuck" waiting for the restart to happen?? Like maybe cancel the current restart action and try it again? Or restart the computer?? Under the "monitor" tab, I have every option checked.
What I've been doing is manually restarting CGWatcher and CGMiner to get it "unstuck". But that sort of defeats the purpose of CGWatcher.
Any ideas or help would be greatly appreciated.
Thanks everyone!!!
Eboman
December 06, 2013, 07:37:04 PM
I'm not sure what you mean. You may be able to use the coin custom field for what you're asking, but I'm not sure what you're asking. Can you give an example? Otherwise, it may be better to ask the guys at CoinChoose or CoinWarz - whichever you're using to get this data.
To create a custom field in CGWatcher:
Go to Settings tab -> click 'Other Tools...' button -> select Manage Coins. In Coin Manager window, click 'Custom Field' tab. Here you can create your own formula using the data variables on the right and mathematical functions (in the drop-down list). An IF(expression,true,false) function is also available, so you can have conditional values. Once you've created your custom expression, test it on a coin at the bottom.
If you open the Coin Profitability window, each time you save your custom field expression the coin data will be updated, so you can check the value of this field for all coins at once.
You can then schedule CGWatcher to switch profiles based on the highest or lowest custom field value, as well as ranked values (2nd highest, 4th lowest, etc).
To create a custom field in CGWatcher:
Go to Settings tab -> click 'Other Tools...' button -> select Manage Coins. In Coin Manager window, click 'Custom Field' tab. Here you can create your own formula using the data variables on the right and mathematical functions (in the drop-down list). An IF(expression,true,false) function is also available, so you can have conditional values. Once you've created your custom expression, test it on a coin at the bottom.
If you open the Coin Profitability window, each time you save your custom field expression the coin data will be updated, so you can check the value of this field for all coins at once.
You can then schedule CGWatcher to switch profiles based on the highest or lowest custom field value, as well as ranked values (2nd highest, 4th lowest, etc).
December 06, 2013, 07:29:04 PM
Is it possible to adjust profitability on a per coin basis?
November 27, 2013, 02:22:13 PM
I'll look into what would cause the freeze when saving settings. There is a drop-down list in the 'Debug Reports & Utilities' section in the Tests tab where you can select 'Remove all CGWatcher autorun entries' and click Run. I would suggest doing this before moving CGWatcher to another folder, but it is a recent addition and is my fault for not adding this to the readme yet. I will make changes for CGWatcher to record where it saves an autorun entry to so that if it is moved, it can remove the correct (old) entry. Many miners (myself included) use multiple instances of CGWatcher to watch multiple miner instances so it will only remove entries that match its current path, which means once you move it the old autorun entry gets abandon (unless you run the 'Remove all CGWatcher autorun entries' as mentioned above).
So if I am following you correctly you have the issue resolved, and are just bringing it to my attention? Or is there something not working correctly still? Either way, I appreciate the feedback and will look into this.
So if I am following you correctly you have the issue resolved, and are just bringing it to my attention? Or is there something not working correctly still? Either way, I appreciate the feedback and will look into this.
November 27, 2013, 04:24:36 AM
Hi milone
I just found a bug (if it hasn't already been reported) happening on Win8, win 8.1 and server 2012 (all x64)
Using previously version 1.3.2 and now 1.3.3, saving settings.
initially the path fot cgwatcher.exe was "d:\miner\cgwatcher-1.3.2\cgwatcher.exe"
I did configure some profile, everything was running smooth.
I then update to 1.3.3, and the path to cgwtcher changed to "d:\miner\cgwatcher\cgwatcher.exe" to simplify further updates.
The program did not launch any more when I started Windows (I then put a link in the startup menu folder and it did the job).
And then when I click on save settings, cgwatcher hangs (not responding), forcing me to kill it via process manager.
after that, when I launch cgwatcher again, settings were saved correctly.
I tries to run it as administrator but with no more luck,
I had to manually modify the run key to correct path, and now, it doesn'thang any more and did run smooth, no more hanging on saving settings...
If you have any question, do ask
And thanks a lot for your helpfull software
I just found a bug (if it hasn't already been reported) happening on Win8, win 8.1 and server 2012 (all x64)
Using previously version 1.3.2 and now 1.3.3, saving settings.
initially the path fot cgwatcher.exe was "d:\miner\cgwatcher-1.3.2\cgwatcher.exe"
I did configure some profile, everything was running smooth.
I then update to 1.3.3, and the path to cgwtcher changed to "d:\miner\cgwatcher\cgwatcher.exe" to simplify further updates.
The program did not launch any more when I started Windows (I then put a link in the startup menu folder and it did the job).
And then when I click on save settings, cgwatcher hangs (not responding), forcing me to kill it via process manager.
after that, when I launch cgwatcher again, settings were saved correctly.
I tries to run it as administrator but with no more luck,
I had to manually modify the run key to correct path, and now, it doesn'thang any more and did run smooth, no more hanging on saving settings...
If you have any question, do ask
And thanks a lot for your helpfull software
November 18, 2013, 02:38:19 PM
New in version 1.3.3 (most significant changes)
- CoinWarz added as optional coin data provider (API key required, see http://coinwarz.com/v1/api for more info)
I just came to the thread to ask about this, THANK YOU!!
November 17, 2013, 10:18:26 PM
New in version 1.3.3 (most significant changes)
- CoinWarz added as optional coin data provider (API key required, see http://coinwarz.com/v1/api for more info)
- Do not show CGRemote ads if user is using CGRemote.
- Drop-down list of coins in Coin Manager -> Custom Field -> Test sorted.
- Coin algorithm added to custom field value expression variables. Returns 1 for sha256, 2 for scrypt.
- On Status tab, Efficiency replaced with custom stat. You can leave it at Efficiency, select a different statistic, or create your own statistic.
- Fixed "when highest/lowest custom field value changes" event description not displaying correctly in scheduled actions list.
- Added "Device elapsed" to GPU and USB devices as added in miner API 1.32.
- Unrecognized remote commands will be tested by being sent to miner (if running) rather than just reporting that the command is unrecognized. This will allow new miner API commands to be used manually without necessarily requiring a CGWatcher update.
- Fixed "Manage Pools" button opening temporary config file instead of actual profile config file.
- Fixed causing "Switch Profile" in CGRemote to not start miner using new profile.
- Add "log" and "report" commands for CGRemote to get log and report data.
- Add "New Block average (seconds)" and "Found Block average (seconds)" values for custom profitability formula field and custom value expression.
- Add "Utility" and "Work Utility" values for custom profitability formula field.
- Current and average hashrates added to window title bar.
- Fixed icarus-timing option incorrectly mirroring usb option in Config File Editor.
- Tests tab reorganized, additional debug reports and utilities moved to drop-down list.
- 'Clear all Windows autorun entries' in Tests tab (drop-down) will remove all CGWatcher entries from Windows startup as a way to get a clean slate. It also disables the "Run when Windows starts" setting, which can be re-enabled afterward.
- Chart on Status tab now shows mining devices only, including FPGA/ASIC devices that report temperature.
- Setting created to ensure CGWatcher & miner are relaunched automatically after CGWatcher-initiated computer restart.
- "Restart CGWatcher" scheduled action created, which may help in situations where CGWatcher stops responding or crashes after running for X consecutive days on low memory computers. This has only been reported once, and I often check for memory leaks, but this is a simple alternative (temporary) solution.
- "Restart CGWatcher" command added for CGRemote.
- Miner auto-launch delay setting added to UI (Monitor -> Other -> Continuous Mining)
- Displayed hashrate formatting improved for consistency.
- CGRemote command to have CGWatcher automatically check and update itself added.
- Other minor fixes and improvements.
November 15, 2013, 05:13:19 PM
Thanks for the feedback, I'll look into this. I think I have an idea what the problem is... I just have to track it down.
I'm working on CGRemote and CGWatcher right now... should have updates for both sometime this weekend.
Edit: Loft: as a temporary fix until I can pinpoint the cause of your problem, CGWatcher 1.3.3 should automatically re-launch itself when it encounters an unhandled exception as it did according to your log. Even if I do fix what caused your issue, I'll probably leave this to protect against any unhandleable unhandled exceptions in the future where CLR is terminating.
You can think of it as CGWatcher dying, but as it takes its last breath it reaches up from the floor and double-clicks the shortcut to launch a new CGWatcher process... then dies, a hero.
I'm working on CGRemote and CGWatcher right now... should have updates for both sometime this weekend.
Edit: Loft: as a temporary fix until I can pinpoint the cause of your problem, CGWatcher 1.3.3 should automatically re-launch itself when it encounters an unhandled exception as it did according to your log. Even if I do fix what caused your issue, I'll probably leave this to protect against any unhandleable unhandled exceptions in the future where CLR is terminating.
You can think of it as CGWatcher dying, but as it takes its last breath it reaches up from the floor and double-clicks the shortcut to launch a new CGWatcher process... then dies, a hero.
November 15, 2013, 03:01:06 AM
Hello Milone!
I have a problem with CGWather. It is closed for some reason. An excerpt of the log here.
You know what the problem is?
I have a problem with CGWather. It is closed for some reason. An excerpt of the log here.
Code:
[14.11.2013 17:55:53] Active profile changed from "WORLDCOIN" to "TagCoin".
[14.11.2013 17:55:53] CGRemote requested miner restart...
[14.11.2013 17:55:53] [d] Miner.Restart begin.
[14.11.2013 17:55:53] Because the active profile has changed, I will attempt to stop and then start the miner so the new active profile's settings are used...
[14.11.2013 17:55:53] [d] Miner.PerformStopStartRestart called. (Profile=TagCoin;Miner=M:\cgminer-3.3.1-windows\cgminer.exe;HasFullAPIAccess=True;Initiator=CGRemote;Reason=#NAME# was successfully restarted using the "#PROFILE#" profile.)
[14.11.2013 17:55:53] [d] Miner.StopMining called: Miner=M:\cgminer-3.3.1-windows\cgminer.exe;ProcessID=1500 (True);BatchProcessID=0 (False);Config=M:\CGWatcher-1.2.0.1\temp.conf;Arguments=--config M:\cgminer-3.3.1-windows\MULTY_WDC_MNC_PXC_LTC.conf;HasFullAPIAccess=True;KillOnReadOnlyAccess=True;IsBatCmdFile=False;ProcessID=1500;.
[14.11.2013 17:55:56] [d] Miner.IsProcessAlive(1500) returns False. [First try, test process is nothing. ex: Process with an Id of 1500 is not running.] (CPID0/CMPID=0/CBPID=0)
[14.11.2013 17:55:56] [d] Miner.StartMining (for restart) called. [Profile=TagCoin;MinerFile=M:\cgminer-3.3.1-windows\cgminer.exe;MinerFileUsed=M:\cgminer-3.3.1-windows\cgminer.exe;MinerExecutable=M:\cgminer-3.3.1-windows\cgminer.exe;Config=M:\CGWatcher-1.2.0.1\temp.conf (M:\cgminer-3.3.1-windows\TAGCOIN.conf);Arguments=--config M:\CGWatcher-1.2.0.1\temp.conf;Anticipated Port=4028;Used Port=4028;HasFullAPIAccess=False;IsBatCmd=False;BatCmdPath=M:\cgminer-3.3.1-windows\cgminer.exe (M:\cgminer-3.3.1-windows\cgminer.exe);LastKnownInstanceCount=0/0]
[14.11.2013 17:55:56] [d] Miner.IsProcessAlive(3632) returns True. [First try, process is alive.] (CPID3632/CMPID=3632/CBPID=0)
[14.11.2013 17:55:56] [d] Waiting for CGMiner to initialize API. Process 3632 alive=True, minerid=3632.
[14.11.2013 17:55:57] [d] Watch for miner, expected process is 3632 (alive).
[14.11.2013 17:55:57] [d] CGMiner process is running using ProcessID 3632, expecting port 4028.
[14.11.2013 17:56:02] [d] CGMiner running and API initialized on port 4028, process matched to profile TagCoin.
[14.11.2013 17:56:02] [d] Finish wait for miner to start, process is 3632 (alive).
[14.11.2013 17:56:02] CGMiner was successfully restarted using the "TagCoin" profile.
[14.11.2013 17:56:02] [d] Miner.Restart end.
[14.11.2013 17:56:03] [d] Unhandled Exception: System.InvalidOperationException: The Undo operation encountered a context that is different from what was applied in the corresponding Set operation. The possible cause is that a context was Set on the thread and not reverted(undone). at System.Threading.SynchronizationContextSwitcher.Undo() at System.Threading.ExecutionContextSwitcher.Undo() at System.Threading.ExecutionContext.runFinallyCode(Object userData, Boolean exceptionThrown) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteBackoutCodeHelper(Object backoutCode, Object userData, Boolean exceptionThrown) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.ContextAwareResult.Complete(IntPtr userToken) at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
[14.11.2013 18:21:39] -- Begin CGWatcher v1.3.1.1 Process -------------------------------------------------------
[14.11.2013 18:21:56] [d] WER DontShowUI value exists (1) and was set to 1 (disabled).
[14.11.2013 18:21:57] [d] Miner.IsProcessAlive(3632) returns True. [First try, process is alive.] (CPID3632/CMPID=3632/CBPID=0)
[14.11.2013 18:21:57] Running miner detected: CGMiner, a miner I launched.
[14.11.2013 18:21:57] Active profile is "TagCoin"
[14.11.2013 18:21:57] CGMiner instance found.
[14.11.2013 18:21:58] The miner running is the last miner I launched and monitored.
[14.11.2013 18:21:58] The current running miner's profile is "TagCoin".
[14.11.2013 18:21:58] CGMiner was already running so I did not launch it upon starting as requested.
[14.11.2013 18:21:59] Monitoring is turned on at 10 second intervals.
November 05, 2013, 02:07:52 PM
Kaspersky responded today:
There is a good chance the false-positive will be back in the next update. I'll try to submit new versions before they're released so by the time they're released the false-positive has been fixed... but sometimes I make changes often so this becomes a PITA.
Quote
Hello,
Sorry, it was a false detection. It will be fixed in the next update.
Thank you for your help.
Best regards,
Herman Moskalenko
39A/3 Leningradskoe Shosse, Moscow, 125212, Russia Tel./Fax: + 7 (495) 797 8700 http://www.kaspersky.com http://www.viruslist.com
Sorry, it was a false detection. It will be fixed in the next update.
Thank you for your help.
Best regards,
Herman Moskalenko
39A/3 Leningradskoe Shosse, Moscow, 125212, Russia Tel./Fax: + 7 (495) 797 8700 http://www.kaspersky.com http://www.viruslist.com
There is a good chance the false-positive will be back in the next update. I'll try to submit new versions before they're released so by the time they're released the false-positive has been fixed... but sometimes I make changes often so this becomes a PITA.
November 05, 2013, 03:05:04 AM
I've upgraded to version 1.2.0.1 with no complaints from Kaspersky 2012. I'll try to upgrade to the current version in a couple of days. Thanks.
November 04, 2013, 10:52:30 PM
I'm not sure which Kaspersky software you're using, but I did find a few guides:
PURE 2.0: http://support.kaspersky.com/7913
Internet Security 2013: http://support.kaspersky.com/us/8742#block2
I stopped submitting false positive reports because they would only whitelist the version I sent, meaning the false positive was back for the next version - no matter what or how little I changed. I'll submit a false-positive report again for the current version. They check it, whitelist it, update their definition file, then you have to make sure you update your definition file. This usually takes a day or two.
They were not able to tell me why it is being flagged, and it is a heuristic false-positive meaning no malicious code was found but it may share characteristics of some malware (what that is I have no idea). They also didn't respond to why they couldn't fix the false-positive for the program instead of only each version as Symantec was able to do a few months back when something triggered a heuristic false-positive with Norton. It may be the language barrier with Kaspersky support, but they aren't very helpful. At any rate, the program has been manually checked out by Symantec and Kaspersky (several times)... and the false-positive has been confirmed and fixed each time... so hopefully that attests that it is doing nothing malicious.
PURE 2.0: http://support.kaspersky.com/7913
Internet Security 2013: http://support.kaspersky.com/us/8742#block2
I stopped submitting false positive reports because they would only whitelist the version I sent, meaning the false positive was back for the next version - no matter what or how little I changed. I'll submit a false-positive report again for the current version. They check it, whitelist it, update their definition file, then you have to make sure you update your definition file. This usually takes a day or two.
They were not able to tell me why it is being flagged, and it is a heuristic false-positive meaning no malicious code was found but it may share characteristics of some malware (what that is I have no idea). They also didn't respond to why they couldn't fix the false-positive for the program instead of only each version as Symantec was able to do a few months back when something triggered a heuristic false-positive with Norton. It may be the language barrier with Kaspersky support, but they aren't very helpful. At any rate, the program has been manually checked out by Symantec and Kaspersky (several times)... and the false-positive has been confirmed and fixed each time... so hopefully that attests that it is doing nothing malicious.
November 04, 2013, 09:09:42 PM
I tried to update to version 1.3.2 but Kaspersky is detecting the 'false positive' on cgwatcher.exe. I've played around with setting exclusions but no success. Has anyone had success setting an exclusion and if so what were the settings or will this be reported as a false positive?
November 04, 2013, 04:23:03 PM
auth100488: I'd suggest checking CGWatcher's memory usage in Task Manager when you start it, then checking after 24 or 48 hours, etc. to see if it continues growing at a rate that would cause problems with your system. Memory usage may grow a little over the first few hours it runs, but then level off. The fact you're having less problems at higher refresh intervals makes me thing this could be the problem, but like I said it hasn't been reported before and I have instances that have been running for several weeks. I wouldn't suggest going below 10 seconds on the refresh interval simply because it's not necessary and there is no need to bother the miner that often with requests for info. Setting a very low refresh interval would also increase the odds that cgminer and CGWatcher try to get ADL device info at the same time... which I'm not certain would cause a problem since CGWatcher is only reading it but it might... I'm not sure how ADL would handle this.
roadsterreplica: CGWatcher doesn't support cudaminer. The two should have nothing to do with each other except the possibility that cudaminer might also uses NVAPI to get Nvidia GPU info (temperature, fan speed, clock speeds, etc) which CGWatcher also does for Nvidia cards.
As far as scrypt mining, CGWatcher doesn't care which type of coin you are mining. It is merely providing a GUI for the miner, and monitoring things to ensure it is working properly. If you are using cgminer 3.6.6-1 or newer, there are known issues for scrypt mining: https://bitcointalksearch.org/topic/m.3477780 If you are using a version newer than 3.6.6, you should downgrade to 3.6.6. or older. I'm currently using cgminer 3.5.0 for scrypt and there are no problems.
CGWatcher is a portable application. Removing it will change nothing other than deleting its folder and files. Whether you close CGWatcher or delete it, there would be no difference to what cgminer is doing. Here is essentially all CGWatcher does:
- Sends requests to cgminer for info, gets response back. Checks/displays the info.
- Sends commands to cgminer when the user tells it to, or restarts cgminer if a problem is found.
- Uses ADL (AMD) and NVAPI (Nvidia) to get GPU info (cgminer also uses ADL). These are APIs from the GPU manufacturers to help get GPU info.
- Uses OpenCL to get OpenCL device information because cgminer uses OpenCL. It only does this at startup.
- Launches or closes the miner if necessary or scheduled.
- Writes/reads from the files in the CGWatcher folder occasionally.
CGWatcher is only launching the miner for you using the config settings you provide. It doesn't do anything else to the miner while mining that would cause the problems you're describing. The problems you're having are more likely related to recent cgminer scrypt issues. If you can provide more information on specific problems, I'd be happy to help you troubleshoot them. I'm not implying CGWatcher is perfect or there isn't room for improvement... it's a constantly evolving project that interacts with two other projects in active development.. so there could be changes to cgminer's or bfgminer's API that need changed in CGWatcher, but I try to keep up with this. But the problems you're describing and the solutions you think you've found are technically unfeasible. It is much more likely to be coincidence that deleting CGWatcher had any effect whatsoever.
roadsterreplica: CGWatcher doesn't support cudaminer. The two should have nothing to do with each other except the possibility that cudaminer might also uses NVAPI to get Nvidia GPU info (temperature, fan speed, clock speeds, etc) which CGWatcher also does for Nvidia cards.
As far as scrypt mining, CGWatcher doesn't care which type of coin you are mining. It is merely providing a GUI for the miner, and monitoring things to ensure it is working properly. If you are using cgminer 3.6.6-1 or newer, there are known issues for scrypt mining: https://bitcointalksearch.org/topic/m.3477780 If you are using a version newer than 3.6.6, you should downgrade to 3.6.6. or older. I'm currently using cgminer 3.5.0 for scrypt and there are no problems.
Even running cgminer or bfgminer on its own is giving issues (lots of block found messages, no accepted share messages) Removing CGwatcher and the system starts working again.
CGWatcher is a portable application. Removing it will change nothing other than deleting its folder and files. Whether you close CGWatcher or delete it, there would be no difference to what cgminer is doing. Here is essentially all CGWatcher does:
- Sends requests to cgminer for info, gets response back. Checks/displays the info.
- Sends commands to cgminer when the user tells it to, or restarts cgminer if a problem is found.
- Uses ADL (AMD) and NVAPI (Nvidia) to get GPU info (cgminer also uses ADL). These are APIs from the GPU manufacturers to help get GPU info.
- Uses OpenCL to get OpenCL device information because cgminer uses OpenCL. It only does this at startup.
- Launches or closes the miner if necessary or scheduled.
- Writes/reads from the files in the CGWatcher folder occasionally.
CGWatcher is only launching the miner for you using the config settings you provide. It doesn't do anything else to the miner while mining that would cause the problems you're describing. The problems you're having are more likely related to recent cgminer scrypt issues. If you can provide more information on specific problems, I'd be happy to help you troubleshoot them. I'm not implying CGWatcher is perfect or there isn't room for improvement... it's a constantly evolving project that interacts with two other projects in active development.. so there could be changes to cgminer's or bfgminer's API that need changed in CGWatcher, but I try to keep up with this. But the problems you're describing and the solutions you think you've found are technically unfeasible. It is much more likely to be coincidence that deleting CGWatcher had any effect whatsoever.
November 04, 2013, 06:21:31 AM
Update:
Settings:
Restart Cgminer Every 1hours of running time
120 sec status refresh
Not a single crash in 24h... hmmm
As for the application log part,
There if nothing there aout cgwatcher, i'd have to make it crash and make sure the exact time, i might do that next weekend!
Thanks for your answer! you are awesome!
(yes i am familiar with it as i work as an It Specialist
)
Thx again! keep on the good work!
Settings:
Restart Cgminer Every 1hours of running time
120 sec status refresh
Not a single crash in 24h... hmmm
As for the application log part,
There if nothing there aout cgwatcher, i'd have to make it crash and make sure the exact time, i might do that next weekend!
Thanks for your answer! you are awesome!
(yes i am familiar with it as i work as an It Specialist
)Thx again! keep on the good work!
November 04, 2013, 03:51:43 AM
Here is my crazy bug. Maybe you can help me figure it out.
1) When running CGWatcher and then trying to run cudaminer, the cards won't hash. The only way I can get them to hash again is to delete the CGwatcher from my computer.
2) CGWatcher and scrypt, seems to be a bit porked. When CGWatcher is on the computer, the scrypt coins aren't showing any positive hash rates. Even running cgminer or bfgminer on its own is giving issues (lots of block found messages, no accepted share messages) Removing CGwatcher and the system starts working again.
Thanks for looking into this.
1) When running CGWatcher and then trying to run cudaminer, the cards won't hash. The only way I can get them to hash again is to delete the CGwatcher from my computer.
2) CGWatcher and scrypt, seems to be a bit porked. When CGWatcher is on the computer, the scrypt coins aren't showing any positive hash rates. Even running cgminer or bfgminer on its own is giving issues (lots of block found messages, no accepted share messages) Removing CGwatcher and the system starts working again.
Thanks for looking into this.
Jump to: