Take the 2-minute tour ×
Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It's 100% free, no registration required.

I have used Bitcoin previously via Windows GUI miners, but never faced an issue like this before. I am now running Ubuntu 12.04 amd64 and using an updated 0.7.1 Satoshi client.

The sync looks like it is working, but the first block never loads. I have had the wallet synchronizing, but it is forever stuck at zero. My Internet connection is fine and have cleared the bitcoin directory and rebooted with no change.

While I am writing this I am watching my other rig drop blocks fine and its running Mint 13 with about a third of the resources I have on the computer giving the issues.

Any help will be greatly appreciated. Thanks.

Specs:

  • UBUNTU 12.04 updated
  • AMD Phenom IIx4
  • 4 GB ddr3
  • Nvidia EVGA 9800GTX
share|improve this question
1  
Can you telnet to a fallback node? e.g., $ telnet 62.75.216.13 8333 If you get a connection then the problem is with Bitcoin. If you don't then the problem is with your Ubuntu networking or your firewall. - bitcoin.it/wiki/Fallback_Nodes –  Stephen Gornick Nov 9 '12 at 10:43
    
Worst case scenario you could do -connect= and connect to the other node, on your LAN. –  Stephen Gornick Nov 9 '12 at 10:45
    
Can you examine/post the log file? It's usually located in ~/.bitcoin/debug.log –  Juraj Dec 2 '12 at 22:12
    
Adding a -debug to the command line adds important information about what bitcoind does. –  cdecker Jan 16 '13 at 8:59
add comment

1 Answer

Do you have the exact same configuration on your other rig? If you do, copy the configuration exactly. Sometimes if you don't have long-polling turned on and using the correct port, in some rare cases you will keep going if you are using the wrong protocol for a said port.

In general, if you are doing Bitcoin mining on a Phenom of your type, and you are doing SHA256D hashes, you should wait around 5 minutes.

If it doesn't immediately say long-polling activated, you've got a problem and need to configure your mining application to do so.

From the time you get the Long-Polling started message, anywhere from 30 seconds to 5 minutes is normal.

I have my scan time set for 1 second, by default it's set for 5 seconds but depending on your hardware and the pool you're in they might tell you to set it for 10 to 30 seconds.

Are you using Slush's Mining Proxy too? I know that can stall out if you're not using the correct configuration for that too.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.