581
|
Bitcoin / Mining software (miners) / Re: M's Miner (Ant/SP) Monitor v4.7: alerts,auto/mass/scheduled reboot/fast
|
on: March 24, 2015, 09:24:13 AM
|
I checked and the .dll is the right place. I decided to check your log and I see this repeated message:
3/17/2015 10:03:27 PM: Error occurred submitting MobileMiner stats: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. 3/17/2015 10:04:02 PM: Error occurred submitting MobileMiner stats: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Would this help you to determine the cause?
Thank you in advance.
That's a curious message. I may be able to figure it out. What version of IE do you have on this machine? Is it fully patched? M i primarily use FireFox. Could this be the issue?? No. My app uses "imbedded IE". That is, whatever version of IE is on your PC it's using. M
|
|
|
582
|
Bitcoin / Mining software (miners) / Re: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner
|
on: March 22, 2015, 07:42:04 PM
|
The automatic reboot function still does not appear to be functioning. I loaded the latest version (5.3b1) and attempted to auto-reboot. However, the attempt failed, as evidenced by the following log:
3/22/2015 2:04:22 PM: M's Miner Monitor v5.3b1 starting 3/22/2015 2:04:22 PM: Initiated Ant refresh 3/22/2015 2:08:09 PM: Rebooting S3:1.103 because it's been up more than the specified uptime before rebooting. 3/22/2015 2:08:09 PM: Not rebooting S3:1.103 because it is marked as Do Not Reboot 3/22/2015 2:08:09 PM: Rebooting S3: 192.168.1.108 because it's been up more than the specified uptime before rebooting. 3/22/2015 2:08:09 PM: Not rebooting S3: 192.168.1.108 because it is marked as Do Not Reboot 3/22/2015 2:08:09 PM: Rebooting S2: 192.168.1.110 because it's been up more than the specified uptime before rebooting. 3/22/2015 2:08:09 PM: Not rebooting S2: 192.168.1.110 because it is marked as Do Not Reboot
Of course, I double checked and confirmed that the "Do Not Reboot" box is not actually checked.
Any thoughts would be appreciated.
Thanks,
I have not been able to look at that yet. It's on my to do list. M
|
|
|
585
|
Bitcoin / Mining software (miners) / Re: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner
|
on: March 22, 2015, 03:04:17 PM
|
I tried with smtp gmail but not able. so i setup with other smtp provider.
I use the default SMTP object that comes with .net. In typical Microsoft fashion, it isn't "standard", which means it doesn't work with all SMTP providers. When I initially tested it, I was not able to get it to work with Verizon. I was able to get it to work Gmail. Gmail may have changed things since then. If I ever come across a more standardized library for SMTP, I'll switch to it. In the meantime I am not able to put the time into manually writing one. M
|
|
|
586
|
Bitcoin / Pools / Re: [10000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
|
on: March 22, 2015, 02:56:36 PM
|
I've been mining with Nicehash for a while now using Eligius. Eligius don't give miners the option to set difficulty but this has never been a problem until now. Suddenly my orders have all crapped out because it says the difficulty is 127.9980. 0.002 short of the minimum. Why is this? Something sounds a bit fishy? Is there an issues between Eligius & Nicehash???
EMail Nicehash/Westhash. I agree it is a bit coincidental that after I posted my message about the odd payouts that suddenly Westhash doesn't work. We've suggested before that Eligius up the minimum starting difficulty past 128, but Wiz doesn't seem to be interested in doing so. M The bot is back working as normal again. Looks like it restarted overnight. Must have been a glitch. I think Westhash fixed it. It no longer says 128 is the min difficulty, it says 127 is. M
|
|
|
587
|
Bitcoin / Pools / Re: [10000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
|
on: March 22, 2015, 11:12:39 AM
|
I've been mining with Nicehash for a while now using Eligius. Eligius don't give miners the option to set difficulty but this has never been a problem until now. Suddenly my orders have all crapped out because it says the difficulty is 127.9980. 0.002 short of the minimum. Why is this? Something sounds a bit fishy? Is there an issues between Eligius & Nicehash???
EMail Nicehash/Westhash. I agree it is a bit coincidental that after I posted my message about the odd payouts that suddenly Westhash doesn't work. We've suggested before that Eligius up the minimum starting difficulty past 128, but Wiz doesn't seem to be interested in doing so. M
|
|
|
588
|
Bitcoin / Mining software (miners) / Re: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner
|
on: March 22, 2015, 11:11:03 AM
|
Hello, i am using this nice software from two weeks ago, with v5.1 thanks the developer for it work. I detected some issues, if it can help you to develop. I have SP20 and ant S4 miners. I also have mobileminer and get info corrrectly. When a miner is offline, i just see locally a and speed avg still show last data, so i dont get an email alert !!! Same happens to mobile miner, only showing avg. speed and not detecting miner is stopped. would be nice be corrected this. I think for me and other people to be alerted when a miner is stop is one of most important . thanks Thanks for the idea. This is in line with the prior suggestion. I'll see what I can come up, but it may be a while. M
|
|
|
591
|
Bitcoin / Pools / Re: [10000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
|
on: March 21, 2015, 08:48:12 PM
|
Recently I decided to rent a very large amount of hashpower from westhash, since prices are < the cost to mine. I let it run full blast, as much as it can pour into Eligius, all pointed at a new address I never used before. Minimum hash rate is about 500 TH/s, I think peaking at 750 TH/s every so often. At that speed, my little order goes very fast, in a few hours or less.
Could you elaborate on how you managed to have Nicehash pointed at Eligius ? Currently, their "verificator" refuses this because of the following : Received mining.set_difficulty... Pool difficulty too low (provided=127.998046875, minimum=128.0) Nothing complicated. Just pointed Nicehash to it... Sometimes it doesn't like the slight less than 128 difficulty, but in most cases it works. M
|
|
|
597
|
Bitcoin / Pools / Re: [10000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
|
on: March 20, 2015, 11:56:30 PM
|
I have been mining here off and on for about 10 months. I have never been paid better then 97%. It seems to me that this is a way to get a 3% bounty for the ability to mine here. Also another thing that really irritates me is the pay out queue. The pool immediately when a block is found. But the miners can wait days to get paid. I could see a pay out once a day or after the 120 confirmations. But not this variable pay out queue that one can sit in for days or weeks.
It just does not make since to me. And is not really fair to the miners.
My slow but steady address is at 93%. My super fast but short address is at 100%. I'm waiting for Wizkid or Luke to chime in here to explain what's going on. M
|
|
|
598
|
Bitcoin / Pools / Re: [10000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
|
on: March 20, 2015, 01:27:46 AM
|
I have a question about the payout queue. I thought I understood it, but clearly I missed something along the way. I have one address that I mine to with approximately 8 TH/s. I usually get paid every few days. Right now I'm #254 in the queue. Recently I decided to rent a very large amount of hashpower from westhash, since prices are < the cost to mine. I let it run full blast, as much as it can pour into Eligius, all pointed at a new address I never used before. Minimum hash rate is about 500 TH/s, I think peaking at 750 TH/s every so often. At that speed, my little order goes very fast, in a few hours or less. Much to my surprise, later in the day I get paid from Eligius for the bulk of my earnings on that new address. Yes, you read that right, in less than 12 hours I got paid for new work that I submitted on an account that had an outstanding balance of zero (remember, the address was brand new, never used before). I did not get paid in 1 lump sum, it was 2 payments that brought to 100% shares paid. (In case you are curious, despite paying at 5% less than I'd make at 100% luck, with a 2% fee, I didn't quite get back all my investment, despite 100% of the shares being paid.) Meanwhile my 8 TH/s is still sitting in queue despite being a few days old. A week or so later, I did it again when Westhash prices dipped a little bit lower still. This time I kept the same payout address, which was at 0 with 100% shares paid (according to MyEligius). Really high hash rate - 500 to 700 TH/s - for a few hours. Within 12 hours I got paid for 100% of shares, in two payments. And my 8 TH/s address, which last paid me about 2 days ago, is still sitting in queue. So, if the payout queue is based on the age of entering the queue, why, two times in a row, did my super fast and super short work get paid well ahead of my slow but steady work? M EDIT: If you want to see it, check http://eligius.st/~wizkid057/newstats/userstats.php/1JD6k7dcAmrzWCoNEdCjGKbcwbCdXHbtsJ. EDIT #2: The first time around, it wasn't 100% of shares in two payments because of horrible luck. However, the first payment did happen extremely quickly.
|
|
|
599
|
Bitcoin / Mining software (miners) / Re: M's Miner (Ant/SP) Monitor v4.7: alerts,auto/mass/scheduled reboot/fast
|
on: March 18, 2015, 09:21:50 AM
|
I checked and the .dll is the right place. I decided to check your log and I see this repeated message:
3/17/2015 10:03:27 PM: Error occurred submitting MobileMiner stats: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. 3/17/2015 10:04:02 PM: Error occurred submitting MobileMiner stats: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Would this help you to determine the cause?
Thank you in advance.
That's a curious message. I may be able to figure it out. What version of IE do you have on this machine? Is it fully patched? M
|
|
|
|