Invalid WU's
log in |
Message boards : Number crunching : Invalid WU's
1 · 2 · Next
Author | Message |
---|---|
I started three computers on this project and two are working just fine. The third, with computer ID: 5522, keeps getting marked "Completed, marked as invalid". | |
ID: 245 · Rating: 0 · rate: / Reply Quote | |
I tried a few of the newest WU's and got the same messages again. Can anyone help me figure this out? | |
ID: 288 · Rating: 0 · rate: / Reply Quote | |
I had something like this on a remote computer and my two home Windows computers, I found that the Anti Virus programme I am running had blocked the WU when it had been updated and the file version name changed from 1.37 to 1.38. | |
ID: 289 · Rating: 0 · rate: / Reply Quote | |
I tried a few of the newest WU's and got the same messages again. Can anyone help me figure this out? Which distribution did you use? Did you use SELinux? I will try to reproduce the problem. ____________ | |
ID: 290 · Rating: 0 · rate: / Reply Quote | |
This machine is running Debian linux I will get the exact details when I get home tonight and let you know what they are. I do know it is a very recent version of Debian. | |
ID: 292 · Rating: 0 · rate: / Reply Quote | |
OK, A few more details, The OS and kernel that are failing is Debian Sid and either kernel 2.6.32-trunk-686 (Debian 2.6.32-5) or 2.6.32-5-686 (Debian 2.6.32-20), both were used at various time and I'm not sure which was used when. Now this machine is running the 2.6.32-5-686-bigmem kernel so I will enable this project again and see what it does. | |
ID: 293 · Rating: 0 · rate: / Reply Quote | |
I installed Debian Sid 32bits in Virtual machine. | |
ID: 295 · Rating: 0 · rate: / Reply Quote | |
Started running WUs again and got the same error messages. This machine is running Debian sid and Linux kernel 2.6.32-5-686-bigmem. So there is something different about this machine that causes problems. Are there any ports that this application uses that I could be blocking that could cause this problem? | |
ID: 298 · Rating: 0 · rate: / Reply Quote | |
The application uses the same port as the BOINC Manager (31416) telnet 127.0.0.1 31416
<get_cc_status> You should obtain
____________ | |
ID: 300 · Rating: 0 · rate: / Reply Quote | |
Here is the result of the Telnet command: | |
ID: 301 · Rating: 0 · rate: / Reply Quote | |
I modify the application
You should restart the BOINC client. ____________ | |
ID: 302 · Rating: 0 · rate: / Reply Quote | |
Ca marche! | |
ID: 303 · Rating: 0 · rate: / Reply Quote | |
All I can say is that it is a friggen waste of computer time to have a work unit trudge along just to find out that after 12 hours of run time to have it come up as invalid. Again a friggen waste of my computer time. Can I get a rebate on my electric bill, Please! | |
ID: 308 · Rating: 0 · rate: / Reply Quote | |
Yes | |
ID: 309 · Rating: 0 · rate: / Reply Quote | |
YES, a complete waste of my time. | |
ID: 310 · Rating: 0 · rate: / Reply Quote | |
All I can say is that it is a friggen waste of computer time to have a work unit trudge along just to find out that after 12 hours of run time to have it come up as invalid. Again a friggen waste of my computer time. Can I get a rebate on my electric bill, Please! Well, considering that these work units are non-cpu intensive their impact on your electric bill is quite minimal, to say the least. What other CPU projects were you running at that time on this computer? Consider yourself lucky you that you never ran an Orbit work unit for 12 days and then have it come up invalid. | |
ID: 311 · Rating: 0 · rate: / Reply Quote | |
I ran 3 Orbit Wu and all three crashed. Must be Orbit's std MOD. They're off my radar for that. lol. | |
ID: 312 · Rating: 0 · rate: / Reply Quote | |
The work unit doesn't get done when the computer is off and dumbfoundly when you do turn off your computer off in the middle of a work unit and you pass that 12 hour mark the result is sent in no matter hou far along you got the previous day. So -- power on uses electricity and the work unit trudges along to completion after 12 hours work. Hopefully it passes muster and you get your 25 credits. The same power/electricity is being used for 12 hours only to get an "INVALID" upon completion. Anyway you read it, the computer was powered up for those 12 hours of time that went down the drain. A total waste of the computers processing time and electricity. | |
ID: 313 · Rating: 0 · rate: / Reply Quote | |
The work unit doesn't get done when the computer is off and dumbfoundly when you do turn off your computer off in the middle of a work unit and you pass that 12 hour mark the result is sent in no matter hou far along you got the previous day. So -- power on uses electricity and the work unit trudges along to completion after 12 hours work. Hopefully it passes muster and you get your 25 credits. The same power/electricity is being used for 12 hours only to get an "INVALID" upon completion. Anyway you read it, the computer was powered up for those 12 hours of time that went down the drain. A total waste of the computers processing time and electricity. Please don't tell me this computer was turned on for the sole purpose of crunching work units here. | |
ID: 314 · Rating: 0 · rate: / Reply Quote | |
I'm not sure what mscharmack is talking about but the machine I was having problems with was running 6 other projects. So the fact that this projects WUs were coming back invalid did not bother me in the least, and I did not consider it a waste of electricity in the least. (OK it bothered me enough to try to find out why they were coming back invalid and fix the problem.) | |
ID: 315 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Number crunching :
Invalid WU's