I keep getting the message "project has no tasks available" but the server stats show quite a few left. I started to get the message on a single computer at first, now it appears on others here.

---

A work unit has arrived on this machine! I hope I can finish the 30+ SIMAP units in time to crack on with it. Got a serious amount of work to do in order to catch up the place I lost in my country stats, but as the other machines are enigma only I hope it won't take too long...sleeping with ear defenders tonight :)

---

There will be short periods without work every now and then.
All the batches of workunits are manually created, often new batch brings new features and patches to the server code which take time to deploy. Also the server can only handle a limited number of workunits (and batches), if there are too many in progress the WU generator is stopped for a while.

---

M4 Project homepage
M4 Project wiki

can you give us a status on the progress of this project, the latest news are from 2008 and rather old. how much work is left to break the remaining message?

thanks in advance.

I have not had any work in weeks and I can not do a network comunication to update my computer preferences. I have resources for this project set at 25%. I am trying to up it to 50% to see if that solves the dry spell, but I cannot update my preferences.

---

I'd suggest having a project as a backup, with Enigma still active for when more work arrives. As TJM said, work has to be compiled by hand so to speak. At the moment (22/4) quite a few server programs:
http://www.enigmaathome.net/server_status
are not running, so I assume the work creation process is in hand.

---

Despite turning resourse share for this project up to 100% and updating the project I still have not recieved any work units. Should I reinstall BOINC?

Despite turning resourse share for this project up to 100% and updating the project I still have not recieved any work units. Should I reinstall BOINC?

No use doing that, we are still not getting any wu:s

/Cerwin

Have a look at the "server status" page for clues when you're not getting WUs, from any project. All of the tasks here are completed for now.

---

Click Here to see My Detailed BOINC Stats

Hi - I am trying to get work from the Enigma project, and no matter what I do, lately, I get no tasks:

1. I watch the indicator light on the main page of BOINCstats frequently, specifically for this project. Only when it is orange (low work) or green (normal work) do I pursue the matter further.
   
2. When it is orange/green, like now and 2 days ago, I pretty much kill all current cpu jobs on my machines and update, update, update. To the point where I generated a batch-file to poll (update) the server every minute for my machines.
   
3. Even 'new' machines I created as VM guests to have no track record get no work. (They do from other projects I have tested with)
   
4. The messages I get in the log(s) are:
   24-Dec-12 16:49:36 | Enigma@Home | Requesting new tasks for CPU
   24-Dec-12 16:49:41 | Enigma@Home | Scheduler request completed: got 0 new tasks
   

Based upon the log results, the server is electing to NOT issue me wu. Why?

What do I need to do to get some wu?


Thank you in advance for any advice.

---

@Raubhautz*

I think I'm having the same issue as you are, and I think I know the reason too.

Server is currently stating that there are about 3000 plus wu to be sent.

However, all of these units are classified as "high priority results"7

Footnote number 7 states : "number of workunits marked for processing on hosts with average turnaround time lower than 3 days."

I know that my recent turnaround average was just over a week, thus I say the system is doing its job and not allowing me to have these units. :(

I looked at your machines. The ones with credit all appear to have turnaround times greater than 3 days. However, for your machines without any credit and thus a 0 day turnaround time I can't explain why they would not be allowed units. Unless the system is programed to only give the high priority units to machines with a proven track record ie credits.

I've tried both reseting the project and re-attaching to the project. Still not getting any units. I've shut down every other project that I run so that the client thinks it should only be running Enigma and even that won't convince the system to get me units.

So, I think we are out of luck unless someone can tell us how to reset our turnaround times so that they are below the cut off point of 3 days.

I'd really love to get crunching Enigma again as Enigma will be the first project I get a million credits in and I am sooooo close right now.

Hope this answers your question. Sorry that I could not provide a solution.

Campion

Ahhhh, very good. That must be it. (There is no other logical reason in any case). Thanks! I'll have to see what I can do to lower that turnaround time. Probably I should start making smaller queues.


________
Added Note:

I think that perhaps the reason the Linux machines are not getting work is because they never have worked any Enigma ('Tasks = 0'); and though they have quick turnarounds on other projects, no baseline has been established. And apparently, Enigma is not giving the benefit of the doubt!!! ;)

---

Hello!

I have been watching your wu's, which are all high-priority... but they are not moving very fast... loosen the requirement to normal and I'll get right on them!!! It will also allow me to get my machines turn-around time lower... Thanks

---

Hi,

There seems to be a bug... I have one of my computers with:

"Average turnaround time 1.34 days",

as indicated by boinc, all other projects and tasks are suspended, enigma server status is indicating:

Results ready to send6 4,080
High priority results7 4,080

and here is what I can read in the log:

26/12/2012 11:17:43 | Enigma@Home | Requesting new tasks for CPU
26/12/2012 11:17:46 | Enigma@Home | Scheduler request completed: got 0 new tasks
26/12/2012 11:17:46 | Enigma@Home | No tasks sent

Any explanation????

I don't think it's a very intelligent way to send out work units. Now I've read this I understand how I got 90 work units backed up - because I kept on giving more resources to try and get through the queue.
Where the system makes complete errors is when someone goes on holiday :D and has to abandon 90 work units - and now gets a bad score on the algorithm.
I've been watching another project jam up my queue with a similar scheme, all marked "high priority" and push to the back of the cpu queue a really big WU from a third project (4228962GFLOPS), which has only two months left to finish, and will need 7 hours a day of my desktop time, which is more than it's usual use.