Username would be exactly what is shown on the manage workers screen, like:
eleuthria_mediacenter
Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 401. (Read 903217 times)
March 15, 2012, 02:56:50 PM
March 15, 2012, 02:22:07 PM
Do you mind telling me why I get: Unable to get work from pool 0, No servers were found that could be used to get work from.
thanks!
Would a username look like this: xxxxx_x
or
this: xxxxx_xxxxx_x
Im going to go try the first setup that may be where im going wrong
thanks!
Would a username look like this: xxxxx_x
or
this: xxxxx_xxxxx_x
Im going to go try the first setup that may be where im going wrong
March 12, 2012, 10:42:48 AM
ignore me, it was on my side 
You have been promptly ignored
. Glad to hear you sorted it out. March 12, 2012, 07:45:35 AM
ignore me, it was on my side
March 11, 2012, 10:25:02 AM
been playing with my miners today, noticed that my worker mh/s isn't working but the miner is getting shares.
Could this be an issue on my side ?
Thanks
Could this be an issue on my side ?
Thanks
March 09, 2012, 02:24:02 PM
With the network growing again after the large slump last fall, I have enabled a server for miners in Europe, located in Germany. Some miners are still using the old address and have already started using it [sorry to those miners who had some connection issues earlier while I was changing the DNS].
If you're in Europe or Asia, you should try the new server out: de.btcguild.com (port 8332 as usual).
If you're in Europe or Asia, you should try the new server out: de.btcguild.com (port 8332 as usual).
March 07, 2012, 04:57:12 PM
Pool down temporarily. Major problem caused by bitcoin v6 and BIP16 being enforced before its supposed to.
EDIT: Pool back online. One of the nodes had not restarted with '-paytoscripthashtime=1333238400', causing it to be working on a hard chain fork.
EDIT: Pool back online. One of the nodes had not restarted with '-paytoscripthashtime=1333238400', causing it to be working on a hard chain fork.
March 05, 2012, 03:22:01 PM
Problem seems to be fixed for Smoov. Everybody using GUIMiner should update to the latest version (released 2/19/12). Link to the thread here: https://bitcointalksearch.org/topic/gui-mining-updated-dec-3-with-7970-bugfix-also-supports-stratum-3878
The versions over the last few months have had a bug with the poclbm miner (default miner of GUIMiner).
Yep... updated the ATI SDK to 2.6 afterwards since I was tinkering anyways.The versions over the last few months have had a bug with the poclbm miner (default miner of GUIMiner).
My miners for BTCG are behaving nicely on one core, but my backup miners (-f256) for solo mining when BTCG is down, for some reason still pegs out the core at 100% full time (and now, even prevents the BTCG miners from ramping up, when before I upgraded, it wasn't an issue) (besides the 100% core).
So, I just put them on different cores.
Seems odd tho since they're all using podbm, with only the -f flag different.
Oh well, I can live with it and am happy now, thnxy Eleuthria o/
-- Smoov
March 05, 2012, 11:14:05 AM
I've had this as the IRC message for a while, but realized I have not posted it in the forums yet:
I have been running some special reports every few days to help detect malicious users [likely botnets]. When a user pops up that has many of the signs of a botnet, they are banned. This has had a fairly significant impact on the pool performance in the last two weeks, as the amount of work/connections being run through the pool have decreased by roughly 40%, even though speed has been fairly constant.
For a user banned in this way, it's as if their account does not exist when they try to log in. The number of accounts banned this way has been decreasing with each subsequent wave, which is good since it looks like those types of people are leaving the servers and not coming back. If you ever have a problem logging in, please contact me with your username and I will look into it/remove the ban. All of your data is still there, just inaccessible until the ban is removed.
The process has been manual so far, but it is very close to becoming automated. I've been waiting to see if any false positives show up, but so far not a single legitimate user has come forward as a result of a banned account.
I have been running some special reports every few days to help detect malicious users [likely botnets]. When a user pops up that has many of the signs of a botnet, they are banned. This has had a fairly significant impact on the pool performance in the last two weeks, as the amount of work/connections being run through the pool have decreased by roughly 40%, even though speed has been fairly constant.
For a user banned in this way, it's as if their account does not exist when they try to log in. The number of accounts banned this way has been decreasing with each subsequent wave, which is good since it looks like those types of people are leaving the servers and not coming back. If you ever have a problem logging in, please contact me with your username and I will look into it/remove the ban. All of your data is still there, just inaccessible until the ban is removed.
The process has been manual so far, but it is very close to becoming automated. I've been waiting to see if any false positives show up, but so far not a single legitimate user has come forward as a result of a banned account.
March 05, 2012, 09:58:32 AM
Problem seems to be fixed for Smoov. Everybody using GUIMiner should update to the latest version (released 2/19/12). Link to the thread here: https://bitcointalksearch.org/topic/gui-mining-updated-dec-3-with-7970-bugfix-also-supports-stratum-3878
The versions over the last few months have had a bug with the poclbm miner (default miner of GUIMiner).
The versions over the last few months have had a bug with the poclbm miner (default miner of GUIMiner).
March 05, 2012, 09:41:09 AM
Is there any reason why the web site wouldn't be keeping track of the work from one of my miners?
My Account page shows one miner for one CPU hasn't shown any shares submitted for over 20 hours now, although it is still chugging along, and isn't showing any connection errors.
My other CPU is shown having submitted a share just 14 seconds ago.
-- Smoov
My Account page shows one miner for one CPU hasn't shown any shares submitted for over 20 hours now, although it is still chugging along, and isn't showing any connection errors.
My other CPU is shown having submitted a share just 14 seconds ago.
-- Smoov
No, there is no reason for that. But I can't do much without knowing your username.
Kinda odd they happened 20 hours apart from each other...
-- Smoov
March 05, 2012, 09:28:38 AM
Try running a traceroute next time you get it. My uptime monitors [Pingdom & Uptime Robot] are reading 100% on the website since 2/22/12 [the date I started monitoring]. Doesn't mean it can't occasionally have a one-off loading error [does a second reload bring the page up?]
Hmm, ok I shall do that. Today it seems to have worked on the very first refresh try. Typically this issue happens when I leave the tab (website) idle for a while and don't refresh it. It basically happened every single time I would refresh the page after a period of inactivity. A second try would successfully reload the page. But I just found it weird how the page load error occurred on such a regular basis.
March 05, 2012, 09:21:18 AM
Is there any reason why the web site wouldn't be keeping track of the work from one of my miners?
My Account page shows one miner for one CPU hasn't shown any shares submitted for over 20 hours now, although it is still chugging along, and isn't showing any connection errors.
My other CPU is shown having submitted a share just 14 seconds ago.
-- Smoov
My Account page shows one miner for one CPU hasn't shown any shares submitted for over 20 hours now, although it is still chugging along, and isn't showing any connection errors.
My other CPU is shown having submitted a share just 14 seconds ago.
-- Smoov
No, there is no reason for that. But I can't do much without knowing your username.
March 05, 2012, 01:37:05 AM
Is there any reason why the web site wouldn't be keeping track of the work from one of my miners?
My Account page shows one miner for one CPU hasn't shown any shares submitted for over 20 hours now, although it is still chugging along, and isn't showing any connection errors.
My other CPU is shown having submitted a share just 14 seconds ago.
-- Smoov
My Account page shows one miner for one CPU hasn't shown any shares submitted for over 20 hours now, although it is still chugging along, and isn't showing any connection errors.
My other CPU is shown having submitted a share just 14 seconds ago.
-- Smoov
March 03, 2012, 11:01:18 PM
Try running a traceroute next time you get it. My uptime monitors [Pingdom & Uptime Robot] are reading 100% on the website since 2/22/12 [the date I started monitoring]. Doesn't mean it can't occasionally have a one-off loading error [does a second reload bring the page up?]
March 03, 2012, 10:44:43 PM
Any reason why once in a whle I get this error when trying to refresh my stats page:
This webpage is not available
The webpage at https://www.btcguild.com/my_account.php might be temporarily down or it may have moved permanently to a new web address.
This webpage is not available
The webpage at https://www.btcguild.com/my_account.php might be temporarily down or it may have moved permanently to a new web address.
March 02, 2012, 11:51:57 AM
General jist of it all: 8 different BTC related businesses using Linode as a VPS lost over 40K in BTC (the day before / yesterday). Nearly $200K in USD stolen through some backdoor in the host's system.
Just to add:
Link to the General Discussion thread: https://bitcointalksearch.org/topic/hacked-linode-coins-stolen-to-1nry8gbx56mymbhdym-66916
Source of the problem:
Like all VPS providers I'm aware of, there is the ability to reset the root password through the VPS control panel. This is just like booting a dedicated server into rescue/emergency mode if you lock yourself out. The feature has to be there otherwise it would be possible for a server to be completely inaccessible with no way of recovering it if the owner screws something up.
What happened yesterday was somebody managed to get access to a customer service account. This meant they had Super Admin privileges, and could reset the password on the VPS for customers of Linode. Unfortunately, Linode will likely never admit how the actual attack occurred (rogue sys admin, open helpdesk session, or a lack of whitelist-only access to Customer Service logins).
March 02, 2012, 11:44:46 AM
General jist of it all: 8 different BTC related businesses using Linode as a VPS lost over 40K in BTC (the day before / yesterday). Nearly $200K in USD stolen through some backdoor in the host's system.
March 02, 2012, 11:31:09 AM
Sorry been under a rock for a day or so. What's this hacking you speak of?
Take a look in the general discussion area. Several threads about the major hacking of Linode hosted Bitcoin businesses today. 
March 02, 2012, 11:23:52 AM
Sorry been under a rock for a day or so. What's this hacking you speak of?
Jump to: