Page 1 of 2
FIXED: Error: Not an unsigned 32-bit number
Posted: Sat May 18, 2019 4:26 pm
by foldy
When I want to check returned work units status I see
Error: Not an unsigned 32-bit number
https://apps.foldingathome.org/wu?p=117 ... =2637&g=36
Maybe this is because of beta project so you can move it beta forum section.
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sat May 18, 2019 5:21 pm
by Joe_H
It should not have anything to do with whether the project is in beta status or not. The lookup is working for other WU's I have tested it with. I will pass this on to the person who maintains this page.
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sat May 18, 2019 6:48 pm
by foldy
Another issue on the list of returned work units: I wish to see if the work unit was OK or BAD in the list.
https://apps.foldingathome.org/cpu?q=
Currently I have to click each work unit to see its state OK or BAD.
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sun May 19, 2019 4:24 am
by Theodore
I've noticed a few of those as well.
Some are bad units, some are not.
It can only be seen from the client log, matching the time stamp (in my case converting it to local time).
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sun May 19, 2019 9:33 am
by toTOW
I think the tool to check individual WUs is completely broken, it returns the error for every WU I tried ...
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sun May 19, 2019 10:44 am
by foldy
It is working for project 14180 but fails also for 14214
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Mon May 20, 2019 12:44 pm
by Joe_H
This should be fixed now. An update to the software that handles these queries to the database was put in place Thursday, a bug was identified and fixed last night.
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Mon May 20, 2019 2:41 pm
by foldy
Confirm it is working again. What about adding an additional column work unit code OK or BAD?
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Mon May 20, 2019 10:06 pm
by MeeLee
Confirmed works.
Yes, Foldy's idea is great!
No more clicking on each WU date. It would save us time, and FAH server bandwidth.
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Fri May 24, 2019 8:41 pm
by toTOW
I think the CPUID column is still broken, it shows the same value for all entries ...
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Fri May 24, 2019 8:47 pm
by bruce
toTOW wrote:I think the CPUID column is still broken, it shows the same value for all entries ...
What PRCG values are you using to see that issue?
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sat May 25, 2019 7:47 am
by foldy
CPUID is working for me. You know it shows the same value for same PC?
By the way how do I calculate the CPUID on my PC manually? Or can it be found in the fah logfile?
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sat May 25, 2019 5:17 pm
by bruce
The CPUID is calculated from the USERID which was assigned to FAHClient when it first connected to the FAH servers and the slot number is added to that value. On the server it is stored in "reverse ascii" and when it is displayed in a web transaction, it is not displayed correctly. Each byte is in reversed order and a few bit have been truncated. The least significant bits include the slot number and the most significant bits (sign?) are zero.
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Sun May 26, 2019 7:40 pm
by toTOW
bruce wrote:toTOW wrote:I think the CPUID column is still broken, it shows the same value for all entries ...
What PRCG values are you using to see that issue?
All WUs I tested returned 2540BE3FF for CPUID ... and the same value is also returned for every entry when a WU is attempted multiple times ...
This is also the value I see when I use the link provided in first post of this topic ...
Re: Returned WU Status shows Error: Not an unsigned 32-bit n
Posted: Mon May 27, 2019 2:48 am
by bruce
toTOW wrote:bruce wrote:This is also the value I see when I use the link provided in first post of this topic ...
How many machines do you have? If that's >1, did you do a fresh install on each machine or was your OS cloned.
How many slots do you have on each one.
It would really help if you followed the instructions and posted the configurations of each one found in the first couple of screen-fulls on the log.