I have slightly different issue with a long running WU. The unit is almost 6 hours in and only progressed .06% Currently the manager is telling me it will take 368 days to complete. It is running on client 4.2 application 4.75. The id is H1_00052.9_0053.3_0.1_T26_Test02_2. It is the only WU that computer currently has, so I will let it run for awhile to see what happens.
I have three other machines using the same client and application number that are running just fine.
Hopefully it's just a glitch, but I though I would report it.
> > It is running on client 4.2 application 4.75.
>
> Hm - which client? 4.62?
>
> BM
> BM, Rom Walton released a new Alpha build a couple days ago. It is the successor to 4.66. Below is his response to questions about why he named it 4.20.
hope this helps
tony
Rom Walton
Forum moderator
Project developer
Joined: Apr 27, 2000
Posts: 279
ID: 85465
Posted: 10 Feb 2005 1:22:38 UTC
Basically we were going to be throwing away quite a few potential version numbers.
Minor versions have to be two characters otherwise there is potential for bad things to happen, plus the major versions have to be in sync between the client and server, otherwise the server will ignore the client, and the client will reset all the projects.
So if we kept going, we would have only been allowed 25 or so updates to the client before changing the logic of the client and server completely around, or forcing in mass all the projects to update.
For those who are running CPDN, it would have been a very painful experience.
Since 4.5x and 4.6x were never officially released to the public, we could reclaim those version numbers and hold off any potential compatibility bugs that might result because of a version number scheme change.
I would love to switch over to the windows version number scheme where versions are selected based on feature changes, and the build number is incremented for each new build, but I haven’t been able to sell it to David successfully yet. I’m still working on it.
It has been scheduled 12 times since Jan 23rd (last 02/12/05) and never get any successful completion. I had to restart project to cancel this endless WU.
Boinc 4.19 & E@H 4.75. Working also on CPDN, LHC & SETI.
Thanks for all the reports (and uploads etc.). That issue should not occur with the newest apps anymore, so no need to report and upload files for this error if it happens with apps earlier then 4.78. If you see such a WU, wait until it finishes if you have the patience, reset the project if not to get the new apps right away.
Well this seems to still be an on going problem. I'm running the new 4.79 app's and just noticed 2 WU's at 21 & 22 hr's CPU Time. I also just aborted one WU that showed only 9 Min's running time with 70 hr's to go yet.
That WU would just keep jumping back and forth between 6:30 & 7:00 hr's to run, I watched it for awhile & just decided to abort it because there was no way of telling how long it was going to hang like that...
Another WU that is not
)
Another WU that is not finishing
H1_0344.4__0344.5_0.1_T06_Test02_0
I will reset project and download the new aplication
Running Boinc 4.19 and E@H 4.72
I have slightly different
)
I have slightly different issue with a long running WU. The unit is almost 6 hours in and only progressed .06% Currently the manager is telling me it will take 368 days to complete. It is running on client 4.2 application 4.75. The id is H1_00052.9_0053.3_0.1_T26_Test02_2. It is the only WU that computer currently has, so I will let it run for awhile to see what happens.
I have three other machines using the same client and application number that are running just fine.
Hopefully it's just a glitch, but I though I would report it.
[img]http://www.boincstats.com/stats/banner.php? cpid=19ffeb205afac117477975798c4ada3f[/img]
> It is running on client 4.2
)
> It is running on client 4.2 application 4.75.
Hm - which client? 4.62?
BM
BM
> > It is running on client
)
> > It is running on client 4.2 application 4.75.
>
> Hm - which client? 4.62?
>
> BM
>
BM, Rom Walton released a new Alpha build a couple days ago. It is the successor to 4.66. Below is his response to questions about why he named it 4.20.
hope this helps
tony
Rom Walton
Forum moderator
Project developer
Joined: Apr 27, 2000
Posts: 279
ID: 85465
Posted: 10 Feb 2005 1:22:38 UTC
Basically we were going to be throwing away quite a few potential version numbers.
Minor versions have to be two characters otherwise there is potential for bad things to happen, plus the major versions have to be in sync between the client and server, otherwise the server will ignore the client, and the client will reset all the projects.
So if we kept going, we would have only been allowed 25 or so updates to the client before changing the logic of the client and server completely around, or forcing in mass all the projects to update.
For those who are running CPDN, it would have been a very painful experience.
Since 4.5x and 4.6x were never officially released to the public, we could reclaim those version numbers and hold off any potential compatibility bugs that might result because of a version number scheme change.
I would love to switch over to the windows version number scheme where versions are selected based on feature changes, and the build number is incremented for each new build, but I haven’t been able to sell it to David successfully yet. I’m still working on it.
----- Rom
BOINC Development Team, U.C. Berkeley
Another WU endless and still
)
Another WU endless and still rescheduled...
H1_0295.9__0296.2_0.1_T00_Test02_4
It has been scheduled 12 times since Jan 23rd (last 02/12/05) and never get any successful completion. I had to restart project to cancel this endless WU.
Boinc 4.19 & E@H 4.75. Working also on CPDN, LHC & SETI.
Regards,
Etienne
Gex - France
I too have a stuck work unit
)
I too have a stuck work unit running boinc 4.19 & einstein 4.72
it stopped at 100% and will not progress to the next unit
stuck unit ref:
H1_0332.9__0333.2_0.1_T00_Test02_1
it has currently run for 19+ hours and should take only 5hrs 41 mins
Hope this info is useful
PS I'm running a 2.8Ghz Barton or windows XP SP2 including latest hotfixes this february
Thanks for all the reports
)
Thanks for all the reports (and uploads etc.). That issue should not occur with the newest apps anymore, so no need to report and upload files for this error if it happens with apps earlier then 4.78. If you see such a WU, wait until it finishes if you have the patience, reset the project if not to get the new apps right away.
Thanks for participating in this beta test.
BM
BM
Well this seems to still be
)
Well this seems to still be an on going problem. I'm running the new 4.79 app's and just noticed 2 WU's at 21 & 22 hr's CPU Time. I also just aborted one WU that showed only 9 Min's running time with 70 hr's to go yet.
That WU would just keep jumping back and forth between 6:30 & 7:00 hr's to run, I watched it for awhile & just decided to abort it because there was no way of telling how long it was going to hang like that...
PoorBoy, can you tell the
)
PoorBoy,
can you tell the Result IDs or names?
BM
BM
> PoorBoy, > > can you tell
)
> PoorBoy,
>
> can you tell the Result IDs or names?
>
> BM
=========
This WU & This WU both took approximately 22 Hr's to complete, their both v4.79 Applications WU's ...
This WU I aborted because it was hung on 70 Hr's to completion with only 9 Min's CPU Time showing ...