i usually start 'em all using addnode, these getblock-lags just happened quite often lately, so i tried using the connect-switch,
here's a screeny* of 2 nodes seem to be connected to forwarded-node,  both show only 1 connection, the higher blockcount is, the lower isn't, it sometimes even tells me, drops to 0connections for a sec, then back to 1, but still doesnt get any new blocks.

same happens when both are addnode'd and showing 8connections, connections drop below 8 and no more blocks are downloaded, mining doesnt stop though, lots of wasted energy, at least it's green.

* from front to back
- GPU mining to (addnode'd) remote node (not on screen)
- HD-miner-node -connect=<ip> (idle)
- a random node -connect=<ip> (idle, running in VM)

about half an hour after the shot was taken, the random node still hasnt loaded any blocks,
it's not that it's always the VM that lags blocks though, sometimes it's the other way around.

yeah, i also noticed that some blocks need some time to show up,
i already restarted bitcoin, hoping it might materialize somehow, 
but it didn't.

first time i noticed this, hopefully the last too.

The block won't show up. This happens when the network discovered block just after last request for work by the miner. This is the drawback of the pull manner in which getwork... works. The probability for this to happen is 1/60 with ask rate of 10 seconds and 1/120 with ask rate of 5 seconds. It will be better if work is provided in 'push' manner, but I didn't want to complicate the client with separate server thread.

I was generating some blocks today on a 5970 and I noticed that both instances of the the miner claimed to have found the same block (see attached image) The main bitcoin client only counts them once (as it should.)  Does anyone know what is happening?  I am running with default settings and -f 30.

Sorry guys, I screwed it with the update to SVN 170. There is a bug in getwork patch that makes poclbm useless with more than a single instance. Until this is fixed anyone using more than one instance should use previous version of the patch (against SVN 166). Win32 binary bitcoin-getwork-svn166-win32.7z

Just fixed problem with getwork (different miners were showing same results). Updated to SVN 173. See for windows build in first post.

Wow, zipslack, that's almost as much as I get on my GTS 250!

I was on Bitcoin client 3.08 beta and now have also installed and tried 3.14 beta.  My bitcoin.conf file is located in directory "c:\Users\<my Windows user name>\AppData\Roaming\Bitcoin"

It contains 2 lines with syntax : rcpuser=<my unique user name>
 rcppassword=<my unique password>

I am running poclbm from a windows command line with syntax:
poclbm.exe --user=<username> --pass=<password>

It recognizes my CPU and GPU, then when I choose one, I get the "Unable to communicate with bitcoin RPC"

Thank you in advance for any help.

Like BitLex told, I think it's the getwork-patch. Just replace the old bitcoin.exe by the one from the getwork and it should work. Enjoy your Bitcoin !

Malouin

Got my new 5970 and it's only showing half performance it should. I'm on Linux with SDK 2.1 and catalyst drivers 10.10. I know others have seen this problem, but I don't know whether I've seen a resolution. Does anyone know how to fix it?