"No work available to Process"

Message boards : Questions and problems : "No work available to Process"
Message board moderation

To post messages, you must log in.

AuthorMessage
Craig

Send message
Joined: 30 Mar 18
Posts: 3
United Kingdom
Message 85551 - Posted: 30 Mar 2018, 9:11:02 UTC

Hi,
I just started using BOINC a couple of days ago (vers. 7.8.3 (x64)). I have two laptops, both running Win 10. On the first one, everything seems to be working fine. But yesterday I tried installing BOINC on the second. Again everything seemed to install without error. I logged in using the same account details as the first. But after connecting with the same project (LHC@home) BOIC only ever shows "No work available to process". I looked at the event log, and it doesn't show anything unusual - no errors. I looked at my project task list. The first laptop is the only one that appears to have completed work successfully. The second laptop shows a list of tasks, but all display the comment "Error while computing".

I have tried uninstalling using the Windows control panel, but clearly a full uninstall is not being completed, leaving some residual files somewhere, because when I reinstall, it automatically completes the login with my previous details and preferences. And I get the same issues.

Regarding whether BOINC is installed as a service, I have no idea what this means. I followed the procedure outlined on the LHC@home website.

Any ideas?

Thanks,
Craig.
ID: 85551 · Report as offensive
floyd
Help desk expert

Send message
Joined: 23 Apr 12
Posts: 77
Message 85554 - Posted: 30 Mar 2018, 12:31:36 UTC - in response to Message 85551.  

You haven't looked close enough if you think your first computer is working fine. It completed SixTrack tasks sucessfully, as the other one would probably do if they hadn't run out. BOTH computers show 100% error rate for VirtualBox tasks, and the error messages suggest something is wrong with hardware support. My first action would be to check the BIOS settings regarding virtualization. For other options, please wait for somebody else to step up.
ID: 85554 · Report as offensive
Craig

Send message
Joined: 30 Mar 18
Posts: 3
United Kingdom
Message 85565 - Posted: 30 Mar 2018, 21:08:55 UTC - in response to Message 85554.  

You haven't looked close enough if you think your first computer is working fine. It completed SixTrack tasks sucessfully, as the other one would probably do if they hadn't run out. BOTH computers show 100% error rate for VirtualBox tasks, and the error messages suggest something is wrong with hardware support. My first action would be to check the BIOS settings regarding virtualization. For other options, please wait for somebody else to step up.


Thanks. I hadn't noticed that. Below is an example of the errors in Virtual Box:

Runtime error opening 'C:\ProgramData\BOINC\slots\0\boinc_26c29e8c79bd585e\boinc_26c29e8c79bd585e.vbox' for reading: -103 (Path not found.).
F:\tinderbox\win-5.2\src\VBox\Main\src-server\MachineImpl.cpp[741] (long __cdecl Machine::i_registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
ID: 85565 · Report as offensive
Dr Who Fan
Avatar

Send message
Joined: 10 May 07
Posts: 1328
United States
Message 85569 - Posted: 31 Mar 2018, 5:15:53 UTC - in response to Message 85565.  

A www search on "MachineWrap" found this: https://forums.virtualbox.org/viewtopic.php?f=6&t=85485

Not sure if this will fix your problem but it is worth looking at.

You might want to post at the LHC https://lhcathome.cern.ch/lhcathome/forum_index.php forums about your problem referencing this thread since it is a LHC VBox app having problems.
ID: 85569 · Report as offensive
Craig

Send message
Joined: 30 Mar 18
Posts: 3
United Kingdom
Message 85575 - Posted: 1 Apr 2018, 14:29:44 UTC

Thanks to all who helped. I think I have them fixed now. As suggested, it was a BIOS enable issue. Enabled in BIOS and re-installed software. Everything now seems to be working.

Thanks!
Craig.
ID: 85575 · Report as offensive
Ritchie

Send message
Joined: 18 Apr 18
Posts: 2
New Zealand
Message 85928 - Posted: 18 Apr 2018, 17:51:35 UTC

I have been crunching SETI data thru BOINC for 15 perhaps 20 yrs now, for months now nothing has been happening and I get the message "No work available to process."
The info in the other threads on this subject is over my head.
I actually find this rather annoying and want to know what's going on?!
ID: 85928 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 85932 - Posted: 18 Apr 2018, 21:30:23 UTC - in response to Message 85928.  

Mind we're not the Seti forums, so we cannot check your systems (under your name).

So we do not know what kind of system you have, Windows, Linux, Android, Mac, other?

We also don't know what you set in the project preferences that you want to run, just Seti v8 tasks or Astropulse. Astropulse are not available every day, so if you set just to run AP, that would account for not getting any work.

We also don't know if you run stock - by the project - supplied applications, or that you set up an anonymous platform app_info.xml file with specific applications in them. Perhaps that these are no longer in use. Seti Multibeam tasks require v8 applications, Astropulse v7. Any older applications no longer get work.

We also don't know if you're using a GPU and whether it's got the correct drivers installed. Getting wrong drivers installed may also not get you any work.

The best thing to do would be to post the first 40 lines or so from your BOINC start-up messages. That gives us a lot of information.
Try to get a scheduler request in there with the messages, to show us what the rest of them say.
ID: 85932 · Report as offensive

Message boards : Questions and problems : "No work available to Process"

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.