Quote from: hipaulshi on June 29, 2011, 10:53:54 PM

try to update to latest version now

Code:

Current database version is 2. Attempting migration to version 3.

Migrating 2 -> 3 ...

The work_data.data column cannot be shrunk because that would result in duplicate primary key values. Please truncate the work_data table and try migrating again.

Final database version: 2.

Database migration did not fully complete. Correct the errors displayed above and try again.

EDIT: I fixed it by deleting the whole database and import a fresh database and load backup to my worker/worker_pool/pool

You could have just done what it suggested: TRUNCATE TABLE work_data;

Quote from: Grinder on June 29, 2011, 10:28:11 PM

Quote from: wyze on June 25, 2011, 06:25:10 AM

EDIT: I have a workable solution. I was able to successfully submit work with the proxy to MultiPool.
I will discuss the fix further with cdhowie in the morning and see how he wants to go about implementing it.

Did you get anywhere with this?

Multipool is currently down, so I haven't been able to review the problem and proposed fix.

Quote from: kripz on June 30, 2011, 01:25:15 AM

So no problems with getworks and the like? One card solves something and the others some how knows to getwork again?

I'm not sure what you mean. The mining software is responsible for determining how to allocate work to the various devices it supports. My proxy doesn't know or care how many GPUs you have.