CGWatcher 1.4.0, the GUI/monitor for CGMiner and BFGMiner to prevent downtime - page 10.

Tigggger

legendary

Activity: 1098

Merit: 1000

Quote from: milone on January 21, 2014, 12:44:55 PM

Quote from: greenbtc on January 21, 2014, 12:12:47 PM

I know a few other people are using this for Jupiters, but while it displays the correct "average" hashrate, if you watch cgminer and then watch the CGRemote it does not match the "current hashrate."

It's not a huge deal (it overprojects hashrate by 100-200GH/s--says my Jupiter is doing 900GH/s) but I'm curious if anyone else is having that issue?

Also, Milone, are there smtp notifications for CGRemote? I couldn't find them in the program (if they aren't, can I tack that on a wish list somewhere?)

Thanks

That's odd. If you can send me a bug report, I should be able to tell why this is happening. Click 'Report Bug' in the toolbar, then send me the report it creates.

I can help, it's looks like it's pulling the value from 1 whereas I suppose it should get the 5s value at 2

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

Quote from: greenbtc on January 21, 2014, 12:12:47 PM

I know a few other people are using this for Jupiters, but while it displays the correct "average" hashrate, if you watch cgminer and then watch the CGRemote it does not match the "current hashrate."

It's not a huge deal (it overprojects hashrate by 100-200GH/s--says my Jupiter is doing 900GH/s) but I'm curious if anyone else is having that issue?

Also, Milone, are there smtp notifications for CGRemote? I couldn't find them in the program (if they aren't, can I tack that on a wish list somewhere?)

Thanks

That's odd. If you can send me a bug report, I should be able to tell why this is happening. Click 'Report Bug' in the toolbar, then send me the report it creates.

There will be email notifications in CGRemote, and several users have asked for the ability to use their own server, so it is on the to-do list.

Quote from: stef942 on January 21, 2014, 12:26:20 PM

Quote from: milone on January 21, 2014, 12:10:10 PM

Quote from: stef942 on January 21, 2014, 11:51:30 AM

Hi Mr Milone, i cant start bfgminer with the latest version of cgwatcher, this the log file :
Huh

Have you used older versions of cgwatcher with that version of bfgminer and did it work? I don't believe I changed anything recently related to starting the miner. It looks like the miner starts and then closes immediately... are you able to launch bfgminer outside of cgwatcher using the same config settings?

yes bfgminer works perfectly alone or with version 1.3.3.2

Can you email me your config file and/or arguments? Thanks..

stef942

full member

Activity: 181

Merit: 100

Quote from: milone on January 21, 2014, 12:10:10 PM

Quote from: stef942 on January 21, 2014, 11:51:30 AM

Hi Mr Milone, i cant start bfgminer with the latest version of cgwatcher, this the log file :
Huh

Have you used older versions of cgwatcher with that version of bfgminer and did it work? I don't believe I changed anything recently related to starting the miner. It looks like the miner starts and then closes immediately... are you able to launch bfgminer outside of cgwatcher using the same config settings?

yes bfgminer works perfectly alone or with version 1.3.3.2

greenbtc

full member

Activity: 210

Merit: 100

I know a few other people are using this for Jupiters, but while it displays the correct "average" hashrate, if you watch cgminer and then watch the CGRemote it does not match the "current hashrate."

It's not a huge deal (it overprojects hashrate by 100-200GH/s--says my Jupiter is doing 900GH/s) but I'm curious if anyone else is having that issue?

Also, Milone, are there smtp notifications for CGRemote? I couldn't find them in the program (if they aren't, can I tack that on a wish list somewhere?)

Thanks

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

Quote from: stef942 on January 21, 2014, 11:51:30 AM

Hi Mr Milone, i cant start bfgminer with the latest version of cgwatcher, this the log file :
Huh

Have you used older versions of cgwatcher with that version of bfgminer and did it work? I don't believe I changed anything recently related to starting the miner. It looks like the miner starts and then closes immediately... are you able to launch bfgminer outside of cgwatcher using the same config settings?

stef942

full member

Activity: 181

Merit: 100

Hi Mr Milone, i cant start bfgminer with the latest version of cgwatcher, this the log file :

Code:

[21/01/2014 17:40:02] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/0]
[21/01/2014 17:40:04] [d] Miner.IsProcessAlive(4744) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4744 n'est pas exécuté.] (CPID4744/CMPID=4744/CBPID=0)
[21/01/2014 17:40:04] [d] Waiting for BFGMiner to initialize API. Process 4744 alive=False, minerid=4744.
[21/01/2014 17:40:05] [d] Watch for miner, expected process is 4744 (not alive).
[21/01/2014 17:40:05] [d] BFGMiner process is running using ProcessID 4744, expecting port 4028.
[21/01/2014 17:40:06] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:40:06] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:40:06] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:40:06] Start miner failed on 1st attempt. Killing any remaining processes and trying again.
[21/01/2014 17:40:06] [d] Miner.IsProcessAlive(4744) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4744 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:40:06] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/0]
[21/01/2014 17:40:07] [d] Miner.IsProcessAlive(4648) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4648 n'est pas exécuté.] (CPID4648/CMPID=4648/CBPID=0)
[21/01/2014 17:40:07] [d] Waiting for BFGMiner to initialize API. Process 4648 alive=False, minerid=4648.
[21/01/2014 17:40:08] [d] Watch for miner, expected process is 4648 (not alive).
[21/01/2014 17:40:08] [d] BFGMiner process is running using ProcessID 4648, expecting port 4028.
[21/01/2014 17:40:09] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:40:09] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:40:09] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:40:09] Start miner failed on 2nd attempt. Killing any remaining processes and trying again.
[21/01/2014 17:40:09] [d] Miner.IsProcessAlive(4648) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4648 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:40:09] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/0]
[21/01/2014 17:40:10] [d] Miner.IsProcessAlive(4400) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4400 n'est pas exécuté.] (CPID4400/CMPID=4400/CBPID=0)
[21/01/2014 17:40:10] [d] Waiting for BFGMiner to initialize API. Process 4400 alive=False, minerid=4400.
[21/01/2014 17:40:11] [d] Watch for miner, expected process is 4400 (not alive).
[21/01/2014 17:40:11] [d] BFGMiner process is running using ProcessID 4400, expecting port 4028.
[21/01/2014 17:40:12] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:40:12] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:40:12] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:40:12] Start miner failed on 3rd attempt. Killing any remaining processes and trying again.
[21/01/2014 17:40:12] [d] Miner.IsProcessAlive(4400) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4400 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:40:12] Unable to start and establish communication with BFGMiner after user clicked Start Mining button (Path="F:\bfgminer-3.10.0-win64\bfgminer.exe";Arguments="--config F:\bfgminer-3.10.0-win64\bfgminer.conf"). Ensure that the miner's path, arguments, and config file (if any) are correct.
[21/01/2014 17:40:46] [d] 1 miner instances found, 1 ignored.
[21/01/2014 17:40:48] [d] Process 4272 ignored: Unable to match to a profile or communicate with on port 4028.
[21/01/2014 17:42:44] User clicked Start Mining button. Attempting to start miner...
[21/01/2014 17:42:44] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/1]
[21/01/2014 17:42:45] [d] Miner.IsProcessAlive(3508) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 3508 n'est pas exécuté.] (CPID3508/CMPID=3508/CBPID=0)
[21/01/2014 17:42:45] [d] Waiting for BFGMiner to initialize API. Process 3508 alive=False, minerid=3508.
[21/01/2014 17:42:46] [d] Watch for miner, expected process is 3508 (not alive).
[21/01/2014 17:42:46] [d] BFGMiner process is running using ProcessID 3508, expecting port 4028.
[21/01/2014 17:42:47] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:42:47] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:42:47] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:42:47] Start miner failed on 1st attempt. Killing any remaining processes and trying again.
[21/01/2014 17:42:47] [d] Miner.IsProcessAlive(3508) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 3508 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:42:47] [d] 1 miner instances found, 1 ignored.
[21/01/2014 17:42:47] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/1]
[21/01/2014 17:42:48] [d] Miner.IsProcessAlive(1904) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 1904 n'est pas exécuté.] (CPID1904/CMPID=1904/CBPID=0)
[21/01/2014 17:42:48] [d] Waiting for BFGMiner to initialize API. Process 1904 alive=False, minerid=1904.
[21/01/2014 17:42:49] [d] Watch for miner, expected process is 1904 (not alive).
[21/01/2014 17:42:49] [d] BFGMiner process is running using ProcessID 1904, expecting port 4028.
[21/01/2014 17:42:50] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:42:50] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:42:50] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:42:50] Start miner failed on 2nd attempt. Killing any remaining processes and trying again.
[21/01/2014 17:42:50] [d] Miner.IsProcessAlive(1904) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 1904 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:42:51] [d] 1 miner instances found, 1 ignored.
[21/01/2014 17:42:51] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/1]
[21/01/2014 17:42:51] [d] Miner.IsProcessAlive(2548) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 2548 n'est pas exécuté.] (CPID2548/CMPID=2548/CBPID=0)
[21/01/2014 17:42:51] [d] Waiting for BFGMiner to initialize API. Process 2548 alive=False, minerid=2548.
[21/01/2014 17:42:52] [d] Watch for miner, expected process is 2548 (not alive).
[21/01/2014 17:42:52] [d] BFGMiner process is running using ProcessID 2548, expecting port 4028.
[21/01/2014 17:42:54] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:42:54] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:42:54] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:42:54] Start miner failed on 3rd attempt. Killing any remaining processes and trying again.
[21/01/2014 17:42:54] [d] Miner.IsProcessAlive(2548) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 2548 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:42:54] Unable to start and establish communication with BFGMiner after user clicked Start Mining button (Path="F:\bfgminer-3.10.0-win64\bfgminer.exe";Arguments="--config F:\bfgminer-3.10.0-win64\bfgminer.conf"). Ensure that the miner's path, arguments, and config file (if any) are correct.
[21/01/2014 17:42:55] [d] 1 miner instances found, 1 ignored.
[21/01/2014 17:44:17] [d] WER DontShowUI value was restored to 1.
[21/01/2014 17:44:17] CGWatcher closed by the user.
[21/01/2014 17:44:17]
[21/01/2014 17:45:35] -- Begin CGWatcher v1.3.5.2 Process -------------------------------------------------------
[21/01/2014 17:45:38] [d] WER DontShowUI value exists (1) and was set to 1 (disabled).
[21/01/2014 17:45:38] Active profile is "multipool"
[21/01/2014 17:45:38] No CGMiner instance found.
[21/01/2014 17:45:38] Preparing to launch CGMiner in 15 second(s)...
[21/01/2014 17:45:41] Monitoring is turned on at 10 second intervals.
[21/01/2014 17:45:47] [d] Monitor.CheckScheduledActions skipped due to one of the following: inside CGWatcher startup period, hardware refresh incomplete, or waiting for miner auto-launch to complete.
[21/01/2014 17:45:53] You requested I run CGMiner upon starting. Attempting to start using profile "multipool"...
[21/01/2014 17:45:53] [d] Preparing to autostart miner using (Miner=F:\bfgminer-3.10.0-win64\bfgminer.exe; Config=F:\bfgminer-3.10.0-win64\bfgminer.conf; Arguments=--config F:\bfgminer-3.10.0-win64\bfgminer.conf)
[21/01/2014 17:45:53] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/0]
[21/01/2014 17:45:55] [d] Miner.IsProcessAlive(4820) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4820 n'est pas exécuté.] (CPID4820/CMPID=4820/CBPID=0)
[21/01/2014 17:45:55] [d] Waiting for BFGMiner to initialize API. Process 4820 alive=False, minerid=4820.
[21/01/2014 17:45:56] [d] Watch for miner, expected process is 4820 (not alive).
[21/01/2014 17:45:56] [d] BFGMiner process is running using ProcessID 4820, expecting port 4028.
[21/01/2014 17:45:58] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:45:58] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:45:58] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:45:58] Start miner failed on 1st attempt. Killing any remaining processes and trying again.
[21/01/2014 17:45:58] [d] Miner.IsProcessAlive(4820) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4820 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:45:58] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/0]
[21/01/2014 17:46:00] [d] Miner.IsProcessAlive(4984) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4984 n'est pas exécuté.] (CPID4984/CMPID=4984/CBPID=0)
[21/01/2014 17:46:00] [d] Waiting for BFGMiner to initialize API. Process 4984 alive=False, minerid=4984.
[21/01/2014 17:46:01] [d] Watch for miner, expected process is 4984 (not alive).
[21/01/2014 17:46:01] [d] BFGMiner process is running using ProcessID 4984, expecting port 4028.
[21/01/2014 17:46:03] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:46:03] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:46:03] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:46:03] Start miner failed on 2nd attempt. Killing any remaining processes and trying again.
[21/01/2014 17:46:03] [d] Miner.IsProcessAlive(4984) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4984 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:46:03] [d] Miner.StartMining called. [Profile=multipool;MinerFile=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerFileUsed=F:\bfgminer-3.10.0-win64\bfgminer.exe;MinerExecutable=F:\bfgminer-3.10.0-win64\bfgminer.exe;Config=F:\CGWatcher-1.3.5\temp.conf (F:\bfgminer-3.10.0-win64\bfgminer.conf);Arguments=--config F:\CGWatcher-1.3.5\temp.conf;Anticipated Port=4028;Used Port=4028;IsBatCmd=False;BatCmdPath=F:\bfgminer-3.10.0-win64\bfgminer.exe (F:\bfgminer-3.10.0-win64\bfgminer.exe);LastKnownInstanceCount=0/0]
[21/01/2014 17:46:04] [d] Miner.IsProcessAlive(4116) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4116 n'est pas exécuté.] (CPID4116/CMPID=4116/CBPID=0)
[21/01/2014 17:46:04] [d] Waiting for BFGMiner to initialize API. Process 4116 alive=False, minerid=4116.
[21/01/2014 17:46:05] [d] Watch for miner, expected process is 4116 (not alive).
[21/01/2014 17:46:06] [d] BFGMiner process is running using ProcessID 4116, expecting port 4028.
[21/01/2014 17:46:08] BFGMiner process closed outside of CGWatcher! Use the 'Ensure miner stays running' monitor option to have CGWatcher restart the miner when this happens.
[21/01/2014 17:46:08] [d] Finish wait for miner to start, process is 0 (not alive).
[21/01/2014 17:46:08] [d] BFGMiner process 0 not alive at Miner.StartMining exit.
[21/01/2014 17:46:08] Start miner failed on 3rd attempt. Killing any remaining processes and trying again.
[21/01/2014 17:46:08] [d] Miner.IsProcessAlive(4116) returns False. [First try, test process is nothing. ex: Un processus ayant l'ID 4116 n'est pas exécuté.] (CPID0/CMPID=0/CBPID=0)
[21/01/2014 17:46:08] [d] Auto-start miner when CGWatcher starts failed to start the miner successfully. Miner.StartMining returned false.
[21/01/2014 17:46:08] BFGMiner was not launched upon starting as you requested. See debug log for more information.

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

Quote from: rebbeca on January 20, 2014, 12:35:44 PM

hi ,im new for CGWACTHER ,would you teach me how to make / write a config file for profil manager ? im using redfury for itboin mining at btcguild pool,thanks in advanced

You can use the Config File Editor in CGWatcher to create config files. Go to the Settings tab, click the "Other Tools..." button and select Config File Editor.

Quote from: Gasai Yuno on January 21, 2014, 01:37:47 AM

hey guys im having problem with cgremote. i do everything needed but it doesnt connect to my rigs.

i run my rigs with latest version of cgwatcher.

i enter passkey both cgremote and cgwatcher. also i tried local ip and public internet ip. but it doesnt connect. it says
my rigs are and cgremote in same network.

It's most likely a firewall issue. Try creating rules for the ports. I know Windows prompts you to create a program rule, but this doesn't always seem to work as expected. If you need help doing this, email me and let me know whether you're connecting to miners on the same network or over the Internet, as an additional step is necessary if over the Internet.

Chello

member

Activity: 64

Merit: 10

Lol - its not needed to hide a local IP

Are you sure thats the correct IP and port ?

Gasai Yuno

full member

Activity: 154

Merit: 100

Yukki Yukki Yukki!

hey guys im having problem with cgremote. i do everything needed but it doesnt connect to my rigs.

i run my rigs with latest version of cgwatcher.

i enter passkey both cgremote and cgwatcher. also i tried local ip and public internet ip. but it doesnt connect. it says
my rigs are and cgremote in same network.

rebbeca

newbie

Activity: 3

Merit: 0

hi ,im new for CGWACTHER ,would you teach me how to make / write a config file for profil manager ? im using redfury for itboin mining at btcguild pool,thanks in advanced

greenbtc

full member

Activity: 210

Merit: 100

I'm a bit new to the software but I'm loving it--is there somewhere to setup smtp notifications for miners/devices? Not sure if I'm just missing it it somewhere in the settings, or if it's something that's not there.

Thanks for all your hard work.

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

I made changes in CGWatcher and CGRemote that should allow UNC paths. I'll release the CGWatcher update today, but since it's a minor update it won't trigger the auto-update (unless you use the "Include beta builds when checking for and auto-updating CGWatcher" option in the Settings -> Updates tab.)

I am trying to get a CGRemote update released before the Bitcoin conference in Miami (Jan 25-26).

poohbah

newbie

Activity: 59

Merit: 0

I'm quoting myself below from the newbie thread, as I have a related minor issue. I didn't even realize there were two threads...

Similar to my issue below, which you (milone) have already stated will be fixed in the next release, I've discovered that on a Win8 machine, I am unable to use any mapped drives. Cgwatcher behaves as if the drives don't exist, so I am unable to map the common conf files to the network drive.

Quote from: poohbah on January 18, 2014, 12:53:03 PM

Is there a way to (easily) use UNC paths for mining profiles? I'm trying to centralize management with variables and common conf files, but it seems cgwatcher doesn't like unc paths - it wants a drive letter or a URL.

I'd rather use \\server\profiles than x:\profiles, is there a way to do this on a local network?

What's odd, is that I can force the unc path by editing the profiles.dat file, and it seems to work fine unless I go into the profile manager. The cgwatcher UI seems to allow for unc paths and everything (except profile manager) works, including the config file editor. When a unc path is specified and the profile manager is opened, it defaults back to cgminer.conf in the cgminer folder.

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

Quote from: ?? on ??

I see you are keeping up with alternative miners. Thumbs up for that. I was worried whether veox's fork would work, especially since he said he didn't use the API and so it was not tested. Nice!

Could you make a decision to keep only one thread btw? It's kinda confusing.

This is the main/official thread... I just created a newbie thread back when I was a newbie and kept it so anyone else new to the forum could get help.

Quote from: GunPowder on January 17, 2014, 04:18:11 AM

milone,

I've got an interesting issue

After some time of running , one of my rigs just stops (it's a quit usual event) and CGWatcher doesn't do anything to restart cgminer or reboot PC, although all checks in the "monitor" tab are on.
Also last records in the log say nothing about cgminer was stoped.

What can I do about it?

Thank you

If you can send me a debug report (go to Tests tab and click Create Debug Report button) and the file called cgwatcher.log from your CGWatcher folder I'll try to find what is going wrong.

Quote from: alphateam on January 17, 2014, 06:58:24 PM

Hi milone, i have an issue too

It seems that the pool priority won't update when i change it.

For exemple, if in the .conf i put in 0:pool1 and in 1:pool2, and i want to change in 0:pool2 and 1:pool1 via the manage pool and save it, it doesnt take effect.

I need to directly change it in the conf file.

Ps : 1.3.5.2 administrator mode or not, same thing. Win 8 x64

Thx

I'm unable to reproduce this problem in Windows 7 and Windows 8.1. If you also can send me cgwatcher.log from your CGWatcher folder I may be able to find errors that occurred and caused this. I would normally say to make sure CGWatcher is able to write to the folder where the config file is located, but running as Administrator should have fixed that... to be clear you're not storing config files in any of the following?:

C:\Program Files
C:\Program Files (x86)
C:\ProgramData
C:\Windows
C:\Users\\Desktop

alphateam

hero member

Activity: 1036

Merit: 531

Hi milone, i have an issue too

It seems that the pool priority won't update when i change it.

For exemple, if in the .conf i put in 0:pool1 and in 1:pool2, and i want to change in 0:pool2 and 1:pool1 via the manage pool and save it, it doesnt take effect.

I need to directly change it in the conf file.

Ps : 1.3.5.2 administrator mode or not, same thing. Win 8 x64

Thx

GunPowder

full member

Activity: 168

Merit: 100

milone,

I've got an interesting issue

After some time of running , one of my rigs just stops (it's a quit usual event) and CGWatcher doesn't do anything to restart cgminer or reboot PC, although all checks in the "monitor" tab are on.
Also last records in the log say nothing about cgminer was stoped.

What can I do about it?

Thank you

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

Gelbstich: CGWatcher is designed to ensure mining stays running... not improve mining performance. However, there are many monitoring options that allow you to set thresholds that if not met, will take the action you specify.

If you're using AMD cards, CGWatcher doesn't disable them due to overheat - it leaves this to the miner. The only part where CGWatcher steps in for AMD cards is that when the miner does disable a GPU due to overheating, it is usually unsuccessful when it tries to re-enable it. So CGWatcher will try to detect when this happens and restart the GPU. I'm not sure where "dead" and "rest" come from... when CGWatcher detects that the miner has disabled a GPU it will list it as "disabled". If it is saying "rest" this is new to me so perhaps newer versions of cgminer/bfgminer handle this differently. I cannot immediately keep up with every change cgminer and bfgminer make. For Nvidia cards, the miners do not detect things like temperature, so CGWatcher does this. CGWatcher's overheat protection for these cards is to throttle intensity until they cool, or disable if they exceed temp-cutoff.

As for your GPU's performance dropping, there are monitoring options that would detect this and restart the miner when this occurs. Perhaps the readme would be a good place to start rather than coming to this thread just to post how pointless this software is... which, by the way, is now running on 45000+ computers. Apparently some people find it useful.

fruor: Sorry, this information is not something that is currently available in CGWatcher. You could possibly try to use the time logged to a specific block, but I don't think it will be 100% accurate. It's something I'll add to the to-do list, which at this point needs to be separated into chapters... so I cannot promise how soon I'll be able to get to it.

Octopuss: Yes, there will be a one-time price for the CGRemote desktop application. It will be at or above the current minimum donation required to join the beta. In other words, it will only cost more once it is released. The idea was not to charge for early access, but to give a discount to those who donated before it was finished and am trusting that I will finish it. Anyone participating in the beta will get the released product free for up to 5 miners. There will be a small fee if additional miners or instances are needed. (Instances meaning you need to run multiple instances at the same time from the same account).

CGRemote has received very positive feedback and I feel that the ultimate price will be more than fair considering what it is/will be capable of.

kimocoin: Thanks

kimocoin

newbie

Activity: 16

Merit: 0

My (CG)miner has been running very smoothly for the past two days with CGwatcher 1.3.4.6 monitoring it's activity. No restarts, or reboots. Cool

As promised: Time to make a donation!
Mining for you as i'm writing this.

Thank you for this awesome piece of code you compiled Milone! Wink

milone

sr. member

Activity: 434

Merit: 251

CGWatcher & CGRemote

Quote from: ?? on ??

milone, is this caused by CGWatcher??

A service was installed in the system.

Service Name: WinRing0_1_2_0
Service File Name: C:\TEMP\tmpB1B9.tmp
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:

My EventLog is full of that stuff. I had an unpleasant experience with some malware in recent hours, and thought I had a rootkit in my system, but this seems to populate EventLog once CGWatcher starts mining.

Yes, this is CGWatcher. Specifically it is the library CGWatcher uses to get hardware information. If I remember correctly, I have to open, retrieve hardware info, then close... otherwise it interferes with the miner if I just leave it open.

fruor

member

Activity: 78

Merit: 13

I have found several blocks the last days while connected to pools, but they don't show up on the pool.
Pool admins are not very helpful, so I wanted to ask if you could see the block number of the found blocks anywhere?

Didn't find any information in cgwatcher data_output.txt which I set to log the column found blocks as well and they did increase but not show additional info nor in my miner.log which only shows these lines:

[16.01.2014 15:15:05] CGMiner (4852): Congratulations, you found 1 blocks!

Topic: CGWatcher 1.4.0, the GUI/monitor for CGMiner and BFGMiner to prevent downtime - page 10. (Read 180484 times)