 Show Posts
|
|
Pages: [1]
|
Well, my things are going from bad to worse. This is what my AM dashboard is showing right now. Both miners are spending more time idling than working.  EDIT: Just upgraded to the latest Dev version - both, the monitoring PC as well as both remote clients on the miners. No change, still restarting both miners at the exact same time every 15-20 minutes. Thucar, can you give us some more details as to what you are mining? What coin, what algo, what mining software, what pool, etc? Are you using a regular Managed Miner or a Profit Miner? If Profit Miner, then what service(s) are you using? If you stop your miner and right-click it and select Diagnostics, can you post that here? This is my original problem description: I've been using AM for a month now and I'm absolutely loving it. However, after the latest update (v4.3.2) my miners restart very often. Their Uptimes used to be in hours and even days, whereas now it's a rare occasion to see them reach one full hour.
Specifics:
Running Profit Miners with MPH as the only pool selected. Only allowing two algo's(cryptonight and equihash) And it's not that they would switch between the algos when they restart. They just stop mining Equihash and then start at it again.
I'm facing the same problem, but for me the miners restart exactly every 2.5 minutes and it would happen to all running miners at the same time (GPU and CPU). It's like something is forcing the miners to restart. Profit switching still works though at the interval that I have set. So the restarts every 2.5 minutes is not due to switching to a different algorithm. Even with profit switching is off and miners setup to mine one coin only, it would behave the same way. The general answer first: A later version of Awesome Miner often includes later versions of the mining software as well and these kind of crashes that happens after a while has often very little to do with Awesome Miner. To troubleshoot, is it a specific software like EWBF or Claymore Cryptonight that is crashing? Is it the only software that is instable, or what about the others? I did see your previous post that you could see this for both CPU and GPU mining. I would recommend to take a look at the rules you have in Awesome Miner. Also, is this on a remote computer via Remote Agent? I also noticed few lines of the log file in a previous post, but it was a little too short of information what happend just before those lines. Was it a crash that Awesome Miner detected and simply restarted the mining software? Was it a rule that triggered and forced a restart? I see pythus got his issue resolved, unfortunately for me it seems to be a different cause. I'm only using Claymore Zcash miner and Claymore Cryptonight miner. I have two dedicated mining rigs managed over the Remote Manager. They both get stopped/started at the same time. Looking at the log file, it seems to be happening just around the time Awesome Miner does profitability calculations. 18.01.2018 4:08:10.932 [031] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:16.049 [030] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:16.049 [020] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:21.150 [033] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:21.150 [037] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:26.236 [011] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:26.236 [010] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:28.030 [025] [S]Managed Profit Switching. Profile: AMD GPU - Miner1, type: Single
18.01.2018 4:08:28.030 [025] [S] Enabled mining software: ZecClayMiner,CnClayMiner
18.01.2018 4:08:28.030 [025] [S]PoolServiceManager.GetAsPools, pools: 99
18.01.2018 4:08:28.077 [025] [S]PoolServiceManager.GetAllEnabledPools, pools: 42
18.01.2018 4:08:28.077 [025] [S]PoolServiceManager.GetAllEnabledPools, SinglePoolCM predefined count: 116
18.01.2018 4:08:28.077 [025] [S] Enabled pools: count: 42, EnabledPools: Zpool, MiningPoolHub
18.01.2018 4:08:28.092 [025] [S]Profitability information:
MiningPoolHub [Equihash] [Zclassic (ZCL)], Url: stratum+tcp://europe.equihash-hub.miningpoolhub.com:17023, Profit: 0,00072000414218971, Priority: 0
Zpool [Equihash], Url: stratum+tcp://equihash.mine.zpool.ca:2142, Profit: 0,00056390852, Priority: 0
MiningPoolHub [CryptoNight], Url: stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:17024, Profit: 0,0003396555888, Priority: 0
18.01.2018 4:08:28.092 [025] [S]Managed Profit Switching processing: Miner-1, IsRunning: False
18.01.2018 4:08:28.092 [025] [S] Profitability, poolChanged: False, Algorithm: Equihash -> Equihash, EngineType: ZecClayMiner ->ZecClayMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath: Diagnostics of one of the miners: Starting Diagnostics. Awesome Miner version: 4.3.4
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: ZecClayMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Miner\AppData\Roaming\AwesomeMinerService\ZecMiner64_1\Claymore's ZCash AMD GPU Miner v12.6\ZecMiner64.exe
C:\Users\Miner\AppData\Roaming\AwesomeMinerService\ZecMiner64_1\Claymore's ZCash AMD GPU Miner v12.6\ZecMiner64.exe -wd 1 -r -1 -mport 4028 -logfile C:\Users\Miner\AppData\Local\AwesomeMinerService\claylog.txt (WindowMode: ConsoleFormat, EngineType: ZecClayMiner, IsProfitMiner: True)
Configuration:
POOL: stratum+tcp://equihash.mine.zpool.ca:2142, WALLET: xxx.Miner-1, PSW: c=BTC, ALLPOOLS: 1
POOL: stratum+tcp://europe.equihash-hub.miningpoolhub.com:17023, WALLET: thucar.Miner-1, PSW: x, ALLPOOLS: 1
Mining Engine Process started, PID: 3928
====================================================================================================
05:10:50:208 8ac args: -wd 1 -r -1 -mport 4028 -logfile C:\Users\Miner\AppData\Local\AwesomeMinerService\claylog.txt
05:10:50:208 8ac
05:10:50:208 8ac ����������������������������������������������������������������ͻ
05:10:50:208 8ac � Claymore's ZCash AMD GPU Miner v12.6 �
05:10:50:208 8ac ����������������������������������������������������������������ͼ
05:10:50:208 8ac
05:10:50:411 8ac ZEC: 2 pools are specified
05:10:50:411 8ac Main ZCash pool is equihash.mine.zpool.ca:2142
05:10:51:752 8ac OpenCL platform: AMD Accelerated Parallel Processing
05:10:51:752 8ac OpenCL initializing...
05:10:51:768 8ac driver 10, 0, 1912, 5
05:10:51:768 8ac AMD Cards available: 4
05:10:51:768 8ac GPU #0: Pitcairn, 3072 MB available, 20 compute units
05:10:51:768 8ac GPU #0 recognized as Radeon 270/270X
05:10:51:768 8ac GPU #1: Pitcairn, 2048 MB available, 20 compute units
05:10:51:768 8ac GPU #1 recognized as Radeon 270/270X
05:10:51:768 8ac GPU #2: Pitcairn, 2048 MB available, 20 compute units
05:10:51:768 8ac GPU #2 recognized as Radeon 270/270X
05:10:51:768 8ac GPU #3: Pitcairn, 2048 MB available, 20 compute units
05:10:51:768 8ac GPU #3 recognized as Radeon 270/270X
05:10:51:768 8ac POOL version
05:10:51:768 8ac b571
05:10:51:768 8ac Platform: Windows
05:10:51:877 8ac start building OpenCL program for GPU 0...
05:10:51:877 8ac done
05:10:52:095 8ac start building OpenCL program for GPU 1...
05:10:52:095 8ac done
05:10:52:314 8ac start building OpenCL program for GPU 2...
05:10:52:314 8ac done
05:10:52:532 8ac start building OpenCL program for GPU 3...
05:10:52:532 8ac done
05:10:52:782 8ac GPU #0 algorithm ASM, intensity 6
05:10:52:829 8ac GPU #1 is going to use too high intensity (6), not enough GPU memory, intensity value reduced (4)
05:10:52:829 8ac GPU #1 algorithm ASM, intensity 4
05:10:52:860 8ac GPU #2 is going to use too high intensity (6), not enough GPU memory, intensity value reduced (4)
05:10:52:860 8ac GPU #2 algorithm ASM, intensity 4
05:10:52:907 8ac GPU #3 is going to use too high intensity (6), not enough GPU memory, intensity value reduced (4)
05:10:52:907 8ac GPU #3 algorithm ASM, intensity 4
05:10:52:907 8ac Total cards: 4
05:11:05:870 e1c ZEC: Stratum - connecting to 'equihash.mine.zpool.ca' <149.56.122.76> port 2142 (unsecure)
05:11:05:948 8ac Watchdog enabled
05:11:05:948 8ac Remote management is enabled on port 4028
05:11:05:948 8ac Warning: use negative -mport option value (read-only mode) or disable remote management entirely if you think that you can be attacked via this port!
05:11:05:948 8ac
05:11:06:011 e1c send: {"id": 1, "method": "mining.subscribe", "params": ["equihashminer", null, "equihash.mine.zpool.ca", "2142"]}
05:11:06:011 e1c send: {"id": 2, "method": "mining.authorize", "params": ["xxx.Miner-1","c=BTC"]}
05:11:06:011 e1c send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
05:11:06:026 e1c ZEC: Stratum - Connected (equihash.mine.zpool.ca:2142) (unsecure)
05:11:06:759 e1c got 188 bytes
05:11:06:759 e1c buf: {"id":1,"result":[[["mining.set_target","0001fffe00000000000000000000000000000000000000000000000000000000"],["mining.notify","63633cf7513f10485e657dde778ce477"]],"81009f08"],"error":null}
05:11:06:759 e1c parse packet: 187
05:11:06:759 e1c new buf size: 0
====================================================================================================
Stopping miner process ...
Stopping Mining Software
Diagnostics completed I've now installed AM on each miner, locally. Both have been running without any restart for over 8 hours. |
|
|
|
Well, my things are going from bad to worse. This is what my AM dashboard is showing right now. Both miners are spending more time idling than working. EDIT: Just upgraded to the latest Dev version - both, the monitoring PC as well as both remote clients on the miners. No change, still restarting both miners at the exact same time every 15-20 minutes. Thucar, can you give us some more details as to what you are mining? What coin, what algo, what mining software, what pool, etc? Are you using a regular Managed Miner or a Profit Miner? If Profit Miner, then what service(s) are you using? If you stop your miner and right-click it and select Diagnostics, can you post that here? This is my original problem description: I've been using AM for a month now and I'm absolutely loving it. However, after the latest update (v4.3.2) my miners restart very often. Their Uptimes used to be in hours and even days, whereas now it's a rare occasion to see them reach one full hour.
Specifics:
Running Profit Miners with MPH as the only pool selected. Only allowing two algo's(cryptonight and equihash) And it's not that they would switch between the algos when they restart. They just stop mining Equihash and then start at it again.
I'm facing the same problem, but for me the miners restart exactly every 2.5 minutes and it would happen to all running miners at the same time (GPU and CPU). It's like something is forcing the miners to restart. Profit switching still works though at the interval that I have set. So the restarts every 2.5 minutes is not due to switching to a different algorithm. Even with profit switching is off and miners setup to mine one coin only, it would behave the same way. The general answer first: A later version of Awesome Miner often includes later versions of the mining software as well and these kind of crashes that happens after a while has often very little to do with Awesome Miner. To troubleshoot, is it a specific software like EWBF or Claymore Cryptonight that is crashing? Is it the only software that is instable, or what about the others? I did see your previous post that you could see this for both CPU and GPU mining. I would recommend to take a look at the rules you have in Awesome Miner. Also, is this on a remote computer via Remote Agent? I also noticed few lines of the log file in a previous post, but it was a little too short of information what happend just before those lines. Was it a crash that Awesome Miner detected and simply restarted the mining software? Was it a rule that triggered and forced a restart? I see pythus got his issue resolved, unfortunately for me it seems to be a different cause. I'm only using Claymore Zcash miner and Claymore Cryptonight miner. I have two dedicated mining rigs managed over the Remote Manager. They both get stopped/started at the same time. Looking at the log file, it seems to be happening just around the time Awesome Miner does profitability calculations. 18.01.2018 4:08:10.932 [031] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:16.049 [030] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:16.049 [020] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:21.150 [033] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:21.150 [037] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:26.236 [011] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:26.236 [010] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:28.030 [025] [S]Managed Profit Switching. Profile: AMD GPU - Miner1, type: Single
18.01.2018 4:08:28.030 [025] [S] Enabled mining software: ZecClayMiner,CnClayMiner
18.01.2018 4:08:28.030 [025] [S]PoolServiceManager.GetAsPools, pools: 99
18.01.2018 4:08:28.077 [025] [S]PoolServiceManager.GetAllEnabledPools, pools: 42
18.01.2018 4:08:28.077 [025] [S]PoolServiceManager.GetAllEnabledPools, SinglePoolCM predefined count: 116
18.01.2018 4:08:28.077 [025] [S] Enabled pools: count: 42, EnabledPools: Zpool, MiningPoolHub
18.01.2018 4:08:28.092 [025] [S]Profitability information:
MiningPoolHub [Equihash] [Zclassic (ZCL)], Url: stratum+tcp://europe.equihash-hub.miningpoolhub.com:17023, Profit: 0,00072000414218971, Priority: 0
Zpool [Equihash], Url: stratum+tcp://equihash.mine.zpool.ca:2142, Profit: 0,00056390852, Priority: 0
MiningPoolHub [CryptoNight], Url: stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:17024, Profit: 0,0003396555888, Priority: 0
18.01.2018 4:08:28.092 [025] [S]Managed Profit Switching processing: Miner-1, IsRunning: False
18.01.2018 4:08:28.092 [025] [S] Profitability, poolChanged: False, Algorithm: Equihash -> Equihash, EngineType: ZecClayMiner ->ZecClayMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath: Diagnostics of one of the miners: Starting Diagnostics. Awesome Miner version: 4.3.4
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: ZecClayMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Miner\AppData\Roaming\AwesomeMinerService\ZecMiner64_1\Claymore's ZCash AMD GPU Miner v12.6\ZecMiner64.exe
C:\Users\Miner\AppData\Roaming\AwesomeMinerService\ZecMiner64_1\Claymore's ZCash AMD GPU Miner v12.6\ZecMiner64.exe -wd 1 -r -1 -mport 4028 -logfile C:\Users\Miner\AppData\Local\AwesomeMinerService\claylog.txt (WindowMode: ConsoleFormat, EngineType: ZecClayMiner, IsProfitMiner: True)
Configuration:
POOL: stratum+tcp://equihash.mine.zpool.ca:2142, WALLET: xxx.Miner-1, PSW: c=BTC, ALLPOOLS: 1
POOL: stratum+tcp://europe.equihash-hub.miningpoolhub.com:17023, WALLET: thucar.Miner-1, PSW: x, ALLPOOLS: 1
Mining Engine Process started, PID: 3928
====================================================================================================
05:10:50:208 8ac args: -wd 1 -r -1 -mport 4028 -logfile C:\Users\Miner\AppData\Local\AwesomeMinerService\claylog.txt
05:10:50:208 8ac
05:10:50:208 8ac ����������������������������������������������������������������ͻ
05:10:50:208 8ac � Claymore's ZCash AMD GPU Miner v12.6 �
05:10:50:208 8ac ����������������������������������������������������������������ͼ
05:10:50:208 8ac
05:10:50:411 8ac ZEC: 2 pools are specified
05:10:50:411 8ac Main ZCash pool is equihash.mine.zpool.ca:2142
05:10:51:752 8ac OpenCL platform: AMD Accelerated Parallel Processing
05:10:51:752 8ac OpenCL initializing...
05:10:51:768 8ac driver 10, 0, 1912, 5
05:10:51:768 8ac AMD Cards available: 4
05:10:51:768 8ac GPU #0: Pitcairn, 3072 MB available, 20 compute units
05:10:51:768 8ac GPU #0 recognized as Radeon 270/270X
05:10:51:768 8ac GPU #1: Pitcairn, 2048 MB available, 20 compute units
05:10:51:768 8ac GPU #1 recognized as Radeon 270/270X
05:10:51:768 8ac GPU #2: Pitcairn, 2048 MB available, 20 compute units
05:10:51:768 8ac GPU #2 recognized as Radeon 270/270X
05:10:51:768 8ac GPU #3: Pitcairn, 2048 MB available, 20 compute units
05:10:51:768 8ac GPU #3 recognized as Radeon 270/270X
05:10:51:768 8ac POOL version
05:10:51:768 8ac b571
05:10:51:768 8ac Platform: Windows
05:10:51:877 8ac start building OpenCL program for GPU 0...
05:10:51:877 8ac done
05:10:52:095 8ac start building OpenCL program for GPU 1...
05:10:52:095 8ac done
05:10:52:314 8ac start building OpenCL program for GPU 2...
05:10:52:314 8ac done
05:10:52:532 8ac start building OpenCL program for GPU 3...
05:10:52:532 8ac done
05:10:52:782 8ac GPU #0 algorithm ASM, intensity 6
05:10:52:829 8ac GPU #1 is going to use too high intensity (6), not enough GPU memory, intensity value reduced (4)
05:10:52:829 8ac GPU #1 algorithm ASM, intensity 4
05:10:52:860 8ac GPU #2 is going to use too high intensity (6), not enough GPU memory, intensity value reduced (4)
05:10:52:860 8ac GPU #2 algorithm ASM, intensity 4
05:10:52:907 8ac GPU #3 is going to use too high intensity (6), not enough GPU memory, intensity value reduced (4)
05:10:52:907 8ac GPU #3 algorithm ASM, intensity 4
05:10:52:907 8ac Total cards: 4
05:11:05:870 e1c ZEC: Stratum - connecting to 'equihash.mine.zpool.ca' <149.56.122.76> port 2142 (unsecure)
05:11:05:948 8ac Watchdog enabled
05:11:05:948 8ac Remote management is enabled on port 4028
05:11:05:948 8ac Warning: use negative -mport option value (read-only mode) or disable remote management entirely if you think that you can be attacked via this port!
05:11:05:948 8ac
05:11:06:011 e1c send: {"id": 1, "method": "mining.subscribe", "params": ["equihashminer", null, "equihash.mine.zpool.ca", "2142"]}
05:11:06:011 e1c send: {"id": 2, "method": "mining.authorize", "params": ["xxx.Miner-1","c=BTC"]}
05:11:06:011 e1c send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
05:11:06:026 e1c ZEC: Stratum - Connected (equihash.mine.zpool.ca:2142) (unsecure)
05:11:06:759 e1c got 188 bytes
05:11:06:759 e1c buf: {"id":1,"result":[[["mining.set_target","0001fffe00000000000000000000000000000000000000000000000000000000"],["mining.notify","63633cf7513f10485e657dde778ce477"]],"81009f08"],"error":null}
05:11:06:759 e1c parse packet: 187
05:11:06:759 e1c new buf size: 0
====================================================================================================
Stopping miner process ...
Stopping Mining Software
Diagnostics completed |
|
|
|
Well, my things are going from bad to worse. This is what my AM dashboard is showing right now. Both miners are spending more time idling than working. EDIT: Just upgraded to the latest Dev version - both, the monitoring PC as well as both remote clients on the miners. No change, still restarting both miners at the exact same time every 15-20 minutes. |
|
|
|
Is the timing always the same? what time is it happening at?
Scheduled event? Local network?
Have you noticed if the gui is functional during one of these times?
The timing seems to be related to the profit calculations. Whenever I look up the time, when the miners restarted in the log file, i see profit calculation update just before it. |
|
|
|
...
Adding a screenshot of my dashboard. You can see what's happening with my two miners. Has to be on the main Awesome Miner side for the restarts to be in sync like that.  screenshot not working No image when you click on it?  |
|
|
|
...
Adding a screenshot of my dashboard. You can see what's happening with my two miners. Has to be on the main Awesome Miner side for the restarts to be in sync like that. EDIT: second try -  |
|
|
|
I've been using AM for a month now and I'm absolutely loving it. However, after the latest update (v4.3.2) my miners restart very often. Their Uptimes used to be in hours and even days, whereas now it's a rare occasion to see them reach one full hour.
Specifics:
Running Profit Miners with MPH as the only pool selected. Only allowing two algo's(cryptonight and equihash) And it's not that they would switch between the algos when they restart. They just stop mining Equihash and then start at it again.
I'm facing the same problem, but for me the miners restart exactly every 2.5 minutes and it would happen to all running miners at the same time (GPU and CPU). It's like something is forcing the miners to restart. Profit switching still works though at the interval that I have set. So the restarts every 2.5 minutes is not due to switching to a different algorithm. Even with profit switching is off and miners setup to mine one coin only, it would behave the same way. The general answer first: A later version of Awesome Miner often includes later versions of the mining software as well and these kind of crashes that happens after a while has often very little to do with Awesome Miner. To troubleshoot, is it a specific software like EWBF or Claymore Cryptonight that is crashing? Is it the only software that is instable, or what about the others? I did see your previous post that you could see this for both CPU and GPU mining. I would recommend to take a look at the rules you have in Awesome Miner. Also, is this on a remote computer via Remote Agent? I also noticed few lines of the log file in a previous post, but it was a little too short of information what happend just before those lines. Was it a crash that Awesome Miner detected and simply restarted the mining software? Was it a rule that triggered and forced a restart? I see pythus got his issue resolved, unfortunately for me it seems to be a different cause. I'm only using Claymore Zcash miner and Claymore Cryptonight miner. I have two dedicated mining rigs managed over the Remote Manager. They both get stopped/started at the same time. Looking at the log file, it seems to be happening just around the time Awesome Miner does profitability calculations. 18.01.2018 4:08:10.932 [031] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:16.049 [030] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:16.049 [020] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:21.150 [033] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:21.150 [037] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:26.236 [011] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.109:9630
18.01.2018 4:08:26.236 [010] [E]ChannelManagerBase: ProtocolException for channel: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService, 192.168.32.106:9630
18.01.2018 4:08:28.030 [025] [S]Managed Profit Switching. Profile: AMD GPU - Miner1, type: Single
18.01.2018 4:08:28.030 [025] [S] Enabled mining software: ZecClayMiner,CnClayMiner
18.01.2018 4:08:28.030 [025] [S]PoolServiceManager.GetAsPools, pools: 99
18.01.2018 4:08:28.077 [025] [S]PoolServiceManager.GetAllEnabledPools, pools: 42
18.01.2018 4:08:28.077 [025] [S]PoolServiceManager.GetAllEnabledPools, SinglePoolCM predefined count: 116
18.01.2018 4:08:28.077 [025] [S] Enabled pools: count: 42, EnabledPools: Zpool, MiningPoolHub
18.01.2018 4:08:28.092 [025] [S]Profitability information:
MiningPoolHub [Equihash] [Zclassic (ZCL)], Url: stratum+tcp://europe.equihash-hub.miningpoolhub.com:17023, Profit: 0,00072000414218971, Priority: 0
Zpool [Equihash], Url: stratum+tcp://equihash.mine.zpool.ca:2142, Profit: 0,00056390852, Priority: 0
MiningPoolHub [CryptoNight], Url: stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:17024, Profit: 0,0003396555888, Priority: 0
18.01.2018 4:08:28.092 [025] [S]Managed Profit Switching processing: Miner-1, IsRunning: False
18.01.2018 4:08:28.092 [025] [S] Profitability, poolChanged: False, Algorithm: Equihash -> Equihash, EngineType: ZecClayMiner ->ZecClayMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath: |
|
|
|
|
I've been using AM for a month now and I'm absolutely loving it. However, after the latest update (v4.3.2) my miners restart very often. Their Uptimes used to be in hours and even days, whereas now it's a rare occasion to see them reach one full hour.
Specifics:
Running Profit Miners with MPH as the only pool selected. Only allowing two algo's(cryptonight and equihash) And it's not that they would switch between the algos when they restart. They just stop mining Equihash and then start at it again.
|
|
|
|
|
