Portable bitcoin client downloads 1 block and stops

[theGECK]

This system (http://bitcointalk.org/index.php?topic=4868.0) used to work flawlessly for me, but now it has stopped downloading the blockchain. I hadn't opened it in awhile, so I did this morning and let it sit. When I came back to it, the client is sitting right where it started, at block 117882, 8 connections, and won't download any more blocks. I closed it, opened it up and saw it go to 117883, so I minimized the window. An hour later, it is still at that level. Each time I open the client I download 1 block and then it stops.

Edit: While typing this the client suddenly dropped connections down to 6, downloaded up to block 117903, increased connections to 8, and then stopped again. Anybody have any ideas about what is causing this?

[theymos]

See anything relevant in debug.log?

[theGECK]

Having never read debug.log before, I'm assuming that the log is written oldest to newest. Timestamps would be very helpful.

I see this once in awhile in the most recent session.

Code:

ERROR: ConnectInputs() : 354984e7d1 mapTransactions prev not found 5a8f7ac18f
ERROR: AcceptToMemoryPool() : ConnectInputs failed 354984e7d1

Also, there is a list of "already have block" from 118315-118383. Outside of that, I don't see anything odd, so let me know if there's something I should be looking for.

[dishwara]

Check the task manager if 2 or more bitcoin.exe running.
If more than one then end process all & start again from portable.
Usually with server switch or bitcoind, exit don't exit it from memory.

Also Thanks for mentioning there is a portable version. I tried & it works flawless.

[theGECK]

There was only one instance of bitcoin.exe running. It was the first thing I did when I started up the computer this morning.

The block chain did finish downloading, up to current block, but it did so in starts and stops.

[MoonShadow]

The block chain did finish downloading, up to current block, but it did so in starts and stops.

That's fairly normal.  The client downloads old blocks in groups of up to 500 at a time, and then proceeds to hash-check all of them before moving onto the next set.

[theGECK]

That's good to know. In the past, it had downloaded them one at a time, and I could see the block number going up by 1s and 2s.