4 days without downloading blocks...

[dree12]

So, my bitcoin client has ran out of connections recently. The debug file is full of IRC this and IRC that, but there hasn't been any nodes connecting even once to my client. I tried running it with the "addnode=", but all that does is start bitcoin with 0 connections, without even an error message. I'm running 0.5.2 on Windows 7. Can someone help me with this?

[1714193199]

1714193199

[1714193199]

1714193199

[1714193199]

1714193199

[Revalin]

That sounds like a firewall - software on your PC, your home router, or your ISP - is blocking Bitcoin.  Have you checked those?

[Revalin]

Try going here and test port 8333 :  http://www.firebind.com/webclient.php

[dree12]

Yeah, the exception for bitcoin-qt is still there (I had to correct that from bitcoin.exe a while ago). All outgoing ports are open on my router (for security reasons, I think most incoming ports are blocked). As for ISP, I hope they're not blocking it; that would ruin the decentralized nature of Bitcoin.

Just to make sure, I tested it on that link anyways:

Code:

Firebind Ports:8333


Status: 100.0% 

Passed: 8333

Result: Test Successful.   None of the tested ports are blocked.

[Revalin]

OK, next try running bitcoin with -debug .  That will generate a debug.log file.  Let it run for a bit then post the log here.  Hopefully it will have some clues.

[Revalin]

Actually no need for -debug.  Just delete your debug.log (it's probably huge), then restart Bitcoin.  Let it run for a bit and post the log.  That should have enough without the full debug info.

[dree12]

As I mentioned in the OP, the debug file is full of IRC this and IRC that. Here is a freshly generated one:

Code:

Bitcoin version 0.5.2-beta
Default data directory C:\Users\<redacted>\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open strLogDir=C:\Users\<redacted>\AppData\Roaming\Bitcoin/database strErrorFile=C:\Users\<redacted>\AppData\Roaming\Bitcoin/db.log
Loaded 111056 addresses
 addresses              1728ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000000000007f407fd  height=165105
 block index            7192ms
Loading wallet...
nFileVersion = 50200
fGenerateBitcoins = 0
nTransactionFee = 0
fMinimizeToTray = 1
fMinimizeOnClose = 1
fUseProxy = 0
addrProxy = 127.0.0.1:9050
fUseUPnP = 0
 wallet                  141ms
Done loading
mapBlockIndex.size() = 165127
nBestHeight = 165105
setKeyPool.size() = 100
mapWallet.size() = 85
mapAddressBook.size() = 43
Bound to port 8333
02/03/12 02:45 RandAddSeed() 236236 bytes
02/03/12 02:45:21 sending: version (85 bytes)
addrLocalHost = 192.168.1.108:8333
ThreadIRCSeed started
ThreadDNSAddressSeed started
ThreadSocketHandler started
Loading addresses from DNS seeds (could take a while)
ThreadMessageHandler started
ThreadOpenConnections started
AddAddress(78.46.244.171:8333)
AddAddress(108.40.82.240:8333)
IRC :irc.lechat.ir NOTICE AUTH :*** Looking up your hostname...
trying connection 174.97.136.86:8333 lastseen=65541.0hrs lasttry=-368954.8hrs
IRC :irc.lechat.ir NOTICE AUTH :*** Found your hostname
IRC SENDING: NICK x75187980

IRC SENDING: USER x75187980 8 * : x75187980

IRC :irc.lechat.ir 001 x75187980 :Welcome to the LFNet Internet Relay Chat Network x75187980
IRC :irc.lechat.ir 002 x75187980 :Your host is irc.lechat.ir[193.107.204.22/6667], running version hybrid-7.2.3
IRC :irc.lechat.ir 003 x75187980 :This server was created Jun 29 2011 at 17:30:40
IRC :irc.lechat.ir 004 x75187980 irc.lechat.ir hybrid-7.2.3 CDGabcdfgiklnorsuwxyz biklmnopstveI bkloveI
AddAddress(76.178.146.91:8333)
AddAddress(146.229.116.229:8333)
AddAddress(81.43.251.160:8333)
AddAddress(62.78.44.253:8333)
AddAddress(94.125.248.245:8333)
AddAddress(69.246.253.155:8333)
AddAddress(74.207.231.186:8333)
IRC SENDING: USERHOST x75187980

66 addresses found from DNS seeds
ThreadDNSAddressSeed exiting
IRC :irc.lechat.ir 302 x75187980 :x75187980=+x75187980@99.236.60.25 
GetIPFromIRC() got userhost 99.236.60.25
GetIPFromIRC() returned 99.236.60.25
IRC SENDING: NICK u6cbyJzEGSa4qJC

IRC SENDING: JOIN #bitcoin64

IRC SENDING: WHO #bitcoin64

IRC got join
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(108.211.237.163:8333)
IRC got new address: 108.211.237.163:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(84.49.105.149:8333)
IRC got new address: 84.49.105.149:8333
IRC got who
AddAddress(80.1.160.194:8333)
IRC got new address: 80.1.160.194:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(83.160.111.199:8333)
IRC got new address: 83.160.111.199:8333
IRC got who
AddAddress(2.120.228.144:8333)
IRC got new address: 2.120.228.144:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(68.230.212.139:8333)
IRC got new address: 68.230.212.139:8333
IRC got who
IRC got who
AddAddress(108.208.208.23:8333)
IRC got new address: 108.208.208.23:8333
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(180.183.188.191:8333)
IRC got new address: 180.183.188.191:8333
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
IRC got who
AddAddress(70.176.200.53:8333)
IRC got new address: 70.176.200.53:8333
IRC got who
AddAddress(78.108.106.180:8333)
IRC got new address: 78.108.106.180:8333
IRC got who
IRC got who
AddAddress(113.170.37.47:8333)
IRC got new address: 113.170.37.47:8333
IRC got who
IRC got who
IRC got who
AddAddress(66.68.10.240:8333)
IRC got new address: 66.68.10.240:8333
IRC got who
IRC got who
IRC got who
AddAddress(128.113.152.79:8333)
IRC got new address: 128.113.152.79:8333
connection timeout
trying connection 89.253.186.190:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 70.245.188.82:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 98.247.166.0:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 60.242.242.214:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
IRC got join
connection timeout
trying connection 188.27.201.67:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 184.145.154.137:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 69.251.191.143:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 218.212.75.155:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.134.93.44:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 98.235.160.96:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.23.198.59:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 24.229.80.54:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 196.209.225.4:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 108.12.78.239:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 79.232.109.153:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 188.2.62.21:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 69.166.26.247:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 88.206.160.2:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 24.14.215.107:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 81.101.6.185:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 99.252.0.73:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 68.115.73.64:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 98.19.59.47:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.180.27.189:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 109.197.69.58:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 92.247.106.5:8333 lastseen=65540.8hrs lasttry=-368954.8hrs
connection timeout
trying connection 75.82.107.221:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 94.217.231.140:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 87.104.14.134:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 208.125.16.50:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 208.88.251.119:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 110.168.89.194:8333 lastseen=65540.9hrs lasttry=-368954.8hrs
connection timeout
trying connection 46.237.78.6:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 94.19.74.20:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 195.218.190.37:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout
trying connection 92.255.237.79:8333 lastseen=65540.7hrs lasttry=-368954.8hrs
connection timeout

The one I had previously is very big, and also full of these connection timeout things.

[Revalin]

All the nodes you got from IRC aren't accepting connections (which isn't that abnormal; most nodes are behind a firewall).

What node did you try adding?  Can you try:   -dns -addnode=bitcoin.es

Also, if you're behind a firewall and on a reasonably secure LAN, can you try turning off the Windows firewall briefly just to test?

[dree12]

I tried addnode=46.182.18.245, the first on on fallback which was supposedly up.

The issue is resolved now! The -dns -addnode=bitcoin.es resolved it:


Thanks for your help!

(edit): Though, I sort of feel uneasy about having only one connection. Isn't this an attack vector for the one person I'm connecting to?

[jake262144]

There is no risk, your client will verify the whole block chaianyway, no matter where it gets it from.
Looks to me like there's some serious networking issue on your end. Are you able to browse the web with that machine at all?

[dree12]

There is no risk, your client will verify the whole block chaianyway, no matter where it gets it from.
Looks to me like there's some serious networking issue on your end. Are you able to browse the web with that machine at all?

Yes, I am able to browse the web with that machine. And I'm not talking about a block chain attack, but an isolation attack.

[DeathAndTaxes]

Yeah running with one node does leave you vulnerable to an isolation attack.

I am not sure what would be cause your client to not connect to other clients.  When adding the node bitcoin.es the first thing that node would have done if share with you a list of all nodes it knows about.  Your client then should have attempted to connect to them.

One of the .dat files contains data on all the nodes the client is aware of.   Maybe it has gotten corrupt?

[jake262144]

And I'm not talking about a block chain attack, but an isolation attack.

Ah, understood. Yeah, that would make you somewhat vulnerable.

Something weird is going on, have you tried reinstalling the client?
Make sure you download it from homepage and not some random site.

[Pieter Wuille]

The "lastseen" value of the nodes your client knows about is 65000 hours in the future. My guess is that your system clock is set to somewhere in 2005.

Still, the client should warn you about this instead of having this erratic behavior.

[dree12]

Can someone verify the following steps are safe?

• Uninstall Bitcoin
• Delete addr.dat
• Reinstall Bitcoin
• Run bitcoin with addnode=bitcoin.es

[Revalin]

As long as you save your wallet.dat you're safe.

Also check the time on your PC.

[jake262144]

I second that. Make sure your system date and time are ok first.

Make sure you have not disabled NTP time checking in your OS.
Should the date unexpectedly be a few years off, likely the motherboard battery is to blame and needs replacing.

[dree12]

Thanks for all the help guys. Bitcoin is running smooth again!


That's 8 connections!

I don't what exactly fixed it, but it was either the reinstall or the addr.dat corruption.

[Red Emerald]

addnode and connect work similarly, but are not the same.

if you did connect=bitcoin.es then you would only talk to them.

if you do addnode=bitcoin.es then you talk to them and then find peers through them.  If bitcoin.es was malicious, I guess they could isolate you even with addnode, but it would be harder.