You know, all these invalids started happening after the P2SH thing. I am making changes to the bitcoind daemons today, we'll see if that makes any difference, though I can't imagine what it could be other than bad luck.

mmbregman: What miner are you using and you say us2 and us3 are also giving you the same error?

If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.

You know, all these invalids started happening after the P2SH thing. I am making changes to the bitcoind daemons today, we'll see if that makes any difference, though I can't imagine what it could be other than bad luck.

mmbregman: What miner are you using and you say us2 and us3 are also giving you the same error?

Something is wrong with your CGminer or the configuration. "Unexpected error" isn't very helpful. One of the many reasons I dislike cgminer. It would be great if it just did simple things properly, but the lack of ability to split GPUs by miner and errors like that just turn me off to it almost completely.

If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.

No, I mean the ability to assign different workers to different GPUs. I think it's crazy to aggregate all GPUs into one worker. Then you never know if a GPU is having issues.

Again ... I presume you don't mean the -d option ...

Pretty sure he doesn't mean the -d option. If I am correct he is at least the fourth person to want to have multiple workers in one instance (as opposed to running multiple instances with -d). Either some other software does that, or cgminer isn't "better enough" (not sure which). Doesn't really affect me with my lowly one device.

No, I mean the ability to assign different workers to different GPUs. I think it's crazy to aggregate all GPUs into one worker. Then you never know if a GPU is having issues.

Again ... I presume you don't mean the -d option ...

Pretty sure he doesn't mean the -d option. If I am correct he is at least the fourth person to want to have multiple workers in one instance (as opposed to running multiple instances with -d). Either some other software does that, or cgminer isn't "better enough" (not sure which). Doesn't really affect me with my lowly one device.

Well yeah it's quite simple to do that and saying it can't is quite incorrect ...Anyway, it makes no difference if you run multiple cgminers(I'd even expect that if you are using windows and using the 'wrong' ATI drivers with the CPU bug you'd just set their affinity all to the same CPU and not lose anything from that either - no idea of course but anyone want to verify that who knows what they are talking about?)And with the API (that I wrote ) I'd expect that many people are now using some front end to monitor their mining with cgminer so running 1 or 5 of them would make no difference.

Lastly ... using a pool to decide if something is up with your mining seems a pretty bad hack IMO

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLUFreeNode IRC: irc.freenode.net channel #kano.isMajority developer of the ckpool codeHelp keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!

To those of you having problems with Poclbm - the error has been found and you need to update your poblbm. This applies to raw poclbm AND GUIMiner. It will get rid of the "Unexpected error" you've been experiencing.

If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.

Yes, I could run multiple instances, but cgminer is too heavy as far as a mining client goes to run multiple instances on some of my stripped down rigs (they already struggle with a plain poclbm and nothing else). Additionally, one of the advantages of cgminer is suppose to be the multiple GPU support built in, so not being able to split up the GPUs defeats that purpose.

I'm not saying cgminer is bad... and that web interface is nice, but it doesn't really help unless you watch it like a hawk. I would probably use it as my primary miner if it would just let me split the GPUs up by miner in once instance. I can get by without native SMS alerts

But, even then, lets say it encountered a bug like the poclbm bug that just happened... the client wouldn't even know there is a problem - it was busy hashing away at full speed, yet unable to submit shares. The pool knew, of course, and will alert if no more shares are coming in. So there are instances where the pool is better at alerting and instances where it's better for the mining client. But in either case, there's no SMS alerting built in to cgminer, sadly The webinterface is also kind of useless for people behind firewalls wanting to monitor multiple machines. Sure you can setup a bunch of firewall and port forwarding rules, but then you have to monitor each machine individually, which is impractical for large setups.

If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.