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

[alphateam]

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

[milone]

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.

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.

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\<username>\Desktop

[poohbah]

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.

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]

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).

[greenbtc]

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.

[rebbeca]

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

[Gasai Yuno]

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.

[Chello]

Lol - its not needed to hide a local IP

Are you sure thats the correct IP and port ?

[milone]

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.

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.

[stef942]

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]

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

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?

[greenbtc]

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

[stef942]

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

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

[milone]

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.

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

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..

[Tigggger]

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]

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 pulling the value from 1 whereas I suppose it should get the 5s value at 2

That is definitely it. In older versions of cgminer, the total current hashrate was not reported via API so CGWatcher & CGRemote calculated it by adding all of the device's hashrates together. I believe in recent versions of cgminer or bfgminer the total current hashrate is reported. The question is then which one to use. I'm thinking the device shows the actual hashrate, and the 5s total takes into account rejects and hardware errors? Or it's a bug. I guess I should change it to only use the device sum hashrate if the total hashrate isn't available (older versions of cgminer).

[Tigggger]

That is definitely it. In older versions of cgminer, the total current hashrate was not reported via API so CGWatcher & CGRemote calculated it by adding all of the device's hashrates together. I believe in recent versions of cgminer or bfgminer the total current hashrate is reported. The question is then which one to use. I'm thinking the device shows the actual hashrate, and the 5s total takes into account rejects and hardware errors? Or it's a bug. I guess I should change it to only use the device sum hashrate if the total hashrate isn't available (older versions of cgminer).

My october jupiter is running 3.9.0 and reports correctly, like you say it's just the older ones, my november jupiter has been running sweet so never upgraded the firmware hence the older cgminer (Member of the not broke don't fix it group)

It's no biggie for me, the average is accurate enough and at some point I'll upgrade

[greenbtc]

That is definitely it. In older versions of cgminer, the total current hashrate was not reported via API so CGWatcher & CGRemote calculated it by adding all of the device's hashrates together. I believe in recent versions of cgminer or bfgminer the total current hashrate is reported. The question is then which one to use. I'm thinking the device shows the actual hashrate, and the 5s total takes into account rejects and hardware errors? Or it's a bug. I guess I should change it to only use the device sum hashrate if the total hashrate isn't available (older versions of cgminer).

My october jupiter is running 3.9.0 and reports correctly, like you say it's just the older ones, my november jupiter has been running sweet so never upgraded the firmware hence the older cgminer (Member of the not broke don't fix it group)

It's no biggie for me, the average is accurate enough and at some point I'll upgrade

Makes sense now. I didn't have my October Jupiter in the software yet, so didn't have that comparison. Like I said, it wasn't a huge deal for me either since the average showed up correctly, it was just something I noticed. (and yeah, both my Nov. jupiters do over 680GH/s out of the box, so haven't upgraded them at all either...)

[stef942]

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.

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

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..

this my config file :

Code:

{
"pools" : [
	{
		"url" : "stratum+tcp:/bitcointalk.org:3333",
		"user" : "stef942",
		"pass" : "btc",
		"pool-priority" : "1"
	},
{
		"url" : "bitcointalk.org:3333",
		"user" : "stef942",
		"pass" : "btc",
		"pool-priority" : "2"
	},
{
		"url" : "stratum+tcp://bitcointalk.org:3333",
		"user" : "stef942",
		"pass" : "btc",
		"pool-priority" : "0"
	}
]
,
"intensity" : "12,12",
"vectors" : "1,1",
"worksize" : "256,256",
"kernel" : "scrypt,scrypt",
"lookup-gap" : "0,0",
"thread-concurrency" : "4096,7200",
"shaders" : "1024,1440",
"gpu-engine" : "1000,800",
"gpu-fan" : "0-85,0-85",
"gpu-memclock" : "1200,0-0",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "0,0",
"gpu-vddc" : "0.000,0.000",
"temp-overheat" : "85,85",
"api-mcast-port" : "4028",
"api-port" : "4028",
"auto-fan" : true,
"expiry" : "120",
"expiry-lp" : "3600",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"log" : "5",
"no-pool-disable" : true,
"no-show-processors" : true,
"no-show-procs" : true,
"no-unicode" : true,
"queue" : "1",
"scan-time" : "60",
"scrypt" : true,
"skip-security-checks" : "0",
"submit-stale" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "C:\\Program Files\\BFGMiner\\/share/bfgminer",
"scan" : "opencl:auto"

}

thanks

[milone]

stef942, can you try it without the kernel-path setting? I do remember adding some additional escaping for some reason (can't remember exactly at the moment) and I wonder if this is tripping it up. If it works after removing this setting then I at least know what to fix. Thanks.