Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 349. (Read 837101 times)
November 06, 2011, 10:23:09 AM
November 06, 2011, 10:16:21 AM
DOH. 
November 06, 2011, 10:15:39 AM
Anyone else showing "?" for all shares in shift history? 
Looks like you are logged out
? November 06, 2011, 10:10:15 AM
Anyone else showing "?" for all shares in shift history?
November 06, 2011, 06:59:58 AM
It was a cold night over here but i'm glad, that all is back to normal 
November 06, 2011, 03:37:21 AM
You can create custom miners and still connect to BitMinter with CGMiner...which is what should be done.
Thats what I meant, why he switched to bitminter client (not the pool). With a farm like that, cgminer seems like an obvious choice.
November 06, 2011, 03:31:43 AM
Pretty much how I HAD mine setup, but I redid everything when I started using the bitminter client.. I got lazy and didn't setup anything to start up on reboot
I would so much like to start bitminter from the command line
Just curious, why did you switch to bitminter? As much as I like the app for tech unsavvy users who want to run a miner on their everyday desktops without having to struggle to get anything running, I dont see the point of running it on headless dedicated machines. Particularly when you have a farm as big as yours, I wouldnt dream of not using cgminer with failover pools.
You can create custom miners and still connect to BitMinter with CGMiner...which is what should be done.
November 06, 2011, 03:30:52 AM
Pretty much how I HAD mine setup, but I redid everything when I started using the bitminter client.. I got lazy and didn't setup anything to start up on reboot
I would so much like to start bitminter from the command line
Just curious, why did you switch to bitminter? As much as I like the app for tech unsavvy users who want to run a miner on their everyday desktops without having to struggle to get anything running, I dont see the point of running it on headless dedicated machines. Particularly when you have a farm as big as yours, I wouldnt dream of not using cgminer with failover pools.
November 05, 2011, 11:36:03 PM
SS is Stale Shares discarded (work completed but not submitted because already stale - just as bad as rejected)
When merged mining this is a bad idea. The proof of work may not be valid on the bitcoin chain, but it could still be valid on the namecoin chain. One might potentially throw away a proof of work that would have been able to create a namecoin block.
By the way, it is now possible to enter an NMC cash out address on the website and collect your namecoins. More website updates coming soon.
Some of us have pointed this out and the author is working on an updated version of cgminer which doesn't assume blocks are stale unless it receives an LP.
I believe this change has been pushed to the git tree at least, so anyone that builds from source can pull, rebuild and relaunch.
November 05, 2011, 10:53:11 PM
There we go, finally an NMC block created again. Thanks for finishing that, teflone.
Obviously the number of proofs for block #60 looks ridiculous because of the bug. Hopefully no more problems with merged mining going forward. *knock on wood*
Obviously the number of proofs for block #60 looks ridiculous because of the bug. Hopefully no more problems with merged mining going forward. *knock on wood*
Ill take that bit cent thank you!
Just saw the extra options on the site for name coin addy..
Good job, keep it up..
November 05, 2011, 10:39:39 PM
There we go, finally an NMC block created again. Thanks for finishing that, teflone.
Obviously the number of proofs for block #60 looks ridiculous because of the bug. Hopefully no more problems with merged mining going forward. *knock on wood*
Obviously the number of proofs for block #60 looks ridiculous because of the bug. Hopefully no more problems with merged mining going forward. *knock on wood*
November 05, 2011, 09:34:45 PM
I also lost the tip of a finger tonight when I stuck it into the fan of a 6970 while trying to power cycle a machine 
Ouch.
I would so much like to start bitminter from the command line
Automation options (like auto start mining when the program starts) will be coming soon. I'll work on the miner after a few more NMC-related updates on the website + doing the dynamic banners.
I just restarted the pool server process again. I fixed a bug that would tell you your password was wrong if the credential checking code was unable to get your hashed worker password from the database. I also fixed a bug in creating the so-called auxiliary proof of work that allows you to create an NMC block even though you were mining BTC.
This was a bug that caused NMC block creation to fail when the BTC block it was mined with contained many transactions. Of course that rarely happens on the testnet - you don't see a lot of transactions there.
Perhaps I should take the time to create my own testnet with transaction activity to mimic the real net. But I really have enough to do just implementing what's necessary. Merged mining was a lot of work.
I so hate to see something fail in a production system. Thank you very much for your patience, I really appreciate it.
November 05, 2011, 09:27:01 PM
All fixed! now to play some BF3... I noticed that bitminter and BF3 seem to work ok together... left it running by mistake and was kinda surprised the system didn't hang or something. November 05, 2011, 09:02:07 PM
I use linuxcoin w/ usb drive and a script to launch cgminer on boot. If miners stop mining I just powercycle them and 99% of the time that solves everything. I can tell if the rig launches cgminer just by sounds. Power on .... wait 45 seconds or so for linuxcoin to launch ... wait for it. VRRRROOOOOOMMM gpu fans kick up to 70% and I know it is back hashing.
Pretty much how I HAD mine setup, but I redid everything when I started using the bitminter client.. I got lazy and didn't setup anything to start up on reboot
I also lost the tip of a finger tonight when I stuck it into the fan of a 6970 while trying to power cycle a machine
I would so much like to start bitminter from the command line
November 05, 2011, 08:38:06 PM
I was wondering why it was getting so cold in here.. I have the miners setup to heat the house!
Well I guess I know what im doing tonight! damn headless miners!
Well I guess I know what im doing tonight! damn headless miners!
I use linuxcoin w/ usb drive and a script to launch cgminer on boot (everything is set from config file). If miners stop mining I just powercycle them and 99% of the time that solves everything. I can tell if the rig launches cgminer just by sounds. Power on .... wait 45 seconds or so for linuxcoin to launch ... wait for it. VRRRROOOOOOMMM gpu fans kick up to 70% and I know it is back hashing.
November 05, 2011, 08:29:55 PM
I was wondering why it was getting so cold in here.. I have the miners setup to heat the house!
Well I guess I know what im doing tonight! damn headless miners!
Well I guess I know what im doing tonight! damn headless miners!
November 05, 2011, 08:09:12 PM
Your bitminter just asked for a password, and quite effectively killed all the pools hashs..
Im loging back in on all my machines...
Im loging back in on all my machines...
Damnit. Very sorry for this. A bug decided to return 401 Unauthorized instead of 500 Internal error. Looks like that was enough to knock half the miners off the pool.
Working on that one too.
November 05, 2011, 07:56:11 PM
Yes, I just saw in the logs something is going wrong with NMC block creation. Sorry guys.
Difficulty is so high on NMC testnet it's not easy to test merged mining well. After a full day of no errors and 7 created NMC blocks, it looked pretty stable.
Sorry for short downtime just now, I was restarting the pool backend.
Working on fixing this now..
Difficulty is so high on NMC testnet it's not easy to test merged mining well. After a full day of no errors and 7 created NMC blocks, it looked pretty stable.
Sorry for short downtime just now, I was restarting the pool backend.
Working on fixing this now..
I figured. Don't feel too bad every pool that implemented merged mining had more than one "glitch". Slush founds some issues with the back end resulting in less than expected block generation. Not sure what he found but that was like a week into merged mining.
As great of an idea as merged mining is they certainly took an asstastic route to implementation. Buggy code, difficulty testing, incomplete docs.
November 05, 2011, 07:47:38 PM
Your bitminter just asked for a password, and quite effectively killed all the pools hashs..
Im loging back in on all my machines...
Im loging back in on all my machines...
November 05, 2011, 07:44:48 PM
Yes, I just saw in the logs something is going wrong with NMC block creation. Sorry guys.
Difficulty is so high on NMC testnet it's not easy to test merged mining well. After a full day of no errors and 7 created NMC blocks, it looked pretty stable.
Sorry for short downtime just now, I was restarting the pool backend.
Working on fixing this now..
Difficulty is so high on NMC testnet it's not easy to test merged mining well. After a full day of no errors and 7 created NMC blocks, it looked pretty stable.
Sorry for short downtime just now, I was restarting the pool backend.
Working on fixing this now..
Jump to: