I know, this here is E@H and not P@H, but maybe it's interesting for you. I have posted this message in the P@H forum:
on one of my boxes I have a mfoldB125 4.22 that does nothing with the WU. It sit's there and it is doing nothing. CoreClient says running, but the box is really idle
Normally the box switches between the boinc applications every 60 minutes; I have watched that it didn't switch for several hours.
Oh, I have set "leave application in memory" and it has worked fine since cc 4.x has been released.
I have restarted the whole client, no change.
I don't have an idea wheather it's a problem of the CC or the application.
I let it sit as it is for quite a while; let's see what happens.
If developers are interested: I have made a copy of the whole boinc-directory. (It has packed 450 MB ! ) If you are interested, send me an e-mail and I will tell where you can download this zip-file.
Yeti
PS.: WIN 2000 Prof, CC 4.19
Copyright © 2024 Einstein@Home. All rights reserved.
WU not running
)
Try to run only P@H, after you have finished E@H WU`s detach from Project, if you want no more work set the time to 0,1. If this not work try the other client 4.62. Make a backup before upgrade! My mfold125 4.22 works fine here on 4.19 everytime but now Iam only running P@H.
> Try to run only P@H, after
)
> Try to run only P@H, after you have finished E@H WU`s detach from Project, if
> you want no more work set the time to 0,1. If this not work try the other
> client 4.62. Make a backup before upgrade! My mfold125 4.22 works fine here on
> 4.19 everytime but now Iam only running P@H.
>
No, I won't detach from any project !
I think, it is a problem that will be interesting for BOINC-developers and / or for Predictor-Team. It's important to find out what is happening to find and fix this bug.
I have ran hundreds or thousands of WUs from predictor / einstein / and more. I could easily reset the project, detach / reattach or uninstall / install the client and I'm shure I will get him to work again. But I think, at this time it is much more important to find out what is causing the client to act as it does than to easily solve the problem on the box.
Supporting BOINC, a great concept !
I had the same thing happen
)
I had the same thing happen with a CPDN WU last night. Nothing happening, yet BOINC says the WU is running. CPU temp also showed me that nothing was processing.
I rebooted, and all was well.
I have encountered 2 such
)
I have encountered 2 such units, both from predictor, both last week. There must be something wrong.
I just aborted that WU (running 4.62) and new ones seem to crunch ok.
Administrator
Message@Home
Okay, I've got it: MFOLD
)
Okay, I've got it:
MFOLD had a fortran-error, because I'm running BOINC 4.19 as a service, it was not able to open a message-box and show the fortran error.
Supporting BOINC, a great concept !