Hi,

I've looked on the server screen and it lists lots of WU's available (over 4k), but I have nothing running from Enigma. Are you purposefully limiting the tasks or is there a problem. I have 2 other projects on this computer and I frequently find that I have run out of Enigma WU's. When I hit Update It seems to send a message saying 0 work units requested when manually hit, but even when it automatically tries to fetch a job I still get "Scheduler request completed: got 0 new tasks"

Frustrated. It seems to have started about 4 days ago!

---

No issues getting WU's here, I've got over 20 tasks from Enigma ready to go....

Mike Doerner

I've just got a new pc and managed to get a workunit on it last night to test, but since i have completed the work units on my old pc and set it not to pick up new ones, and requested work on the new pc i've not got any work units?

has anyone else run out of work?

Occasionally I find I can't connect to the server to upload work units. I would imagine if you are waiting for work units you would get the same thing. I find it usually goes back to normal after a 10-15 minutes.

I have reset the project and seems to be working now! :D an overclocked core2 churning away now

I guess it's a feeder problem, but I'm not sure, because it's very hard to trace. It started around the time when I upgraded the server to revision 18xxx.
Today the feeder got stuck and the shmem work queue was empty. I think I'll gather some data and then post it to boinc_projects mailing list, because I see at least 3 separate problems here and I have no idea what to do to fix them:

- sometimes the client requests work, but it doesn't get any without any reason. Nothing unusual in scheduler log, just the info that work was not sent.

- or the client requests work, but for some strange reason it requests 0 seconds, so it does not get anything. This happens frequently and in some cases the only solution is to completely reinstall the client.

- from time to time scheduler says that shmem is empty, while show_shmem shows clearly a huge list of results ready to be sent.

And now there's also problem related to feeder, which occasionally gets stuck for a while...

---

M4 Project homepage
M4 Project wiki

The folks at BOINC just released 6.6.31 w/o telling anyone. I was not having good results with 6.6.29 (symptoms described above). 6.6.20 ran like a champ on Linux (I've heard there were issues on the Windows side) for weeks w/o a hiccup.

If I start seeing a bunch of errors on 6.6.31 I'll go back to 6.6.20. If that doesn't work, I'll let you know.

Mike Doerner

---

I have reset the project and seems to be working now! :D an overclocked core2 churning away now

What frequency are you running? Just curious.

Mike Doerner

---

Its currently running a E6600 at 3020Mhz, should be able to get more out of it (new secondhand for £300) but need to quieten down the watercooling first so i can have it running at night...might even drop a 45nm quad in it in the future.

everything has been running fine since i reset the project and copied the optimised apps back over.

seem to be doing hceyz72_2 workunits in ~40 mins...beats my X2 4800+ into the ground!

I've heard you can get a Q6600 up to about 3.4GHz on air cooling.I'd think you can do the same frequency on the dual-core (should be 1/2 of a quad, right?!? ;-) )

Mike Doerner

---

seems hung again...

Upload and download, or maybe it's just me.

I seem to be having some problems uploading completed units. It started around 1700 this evening, and says "internet access OK, project servers may be down". I'll try installing the client on another machine and see what happens.

working again here.

Well, there's less error messages with 6.6.31, but it looks like the errors I'm getting are on the server side now....

Sun 31 May 2009 07:55:11 AM EDT Enigma@Home Finished upload of hceyz72_0_6285521_r0_1_0
Sun 31 May 2009 08:05:11 AM EDT Enigma@Home Sending scheduler request: To fetch work.
Sun 31 May 2009 08:05:11 AM EDT Enigma@Home Reporting 4 completed tasks, requesting new tasks
Sun 31 May 2009 08:05:16 AM EDT Enigma@Home Scheduler request completed: got 0 new tasks
Sun 31 May 2009 08:05:16 AM EDT Enigma@Home Message from server: (Project has no jobs available)
Sun 31 May 2009 08:08:22 AM EDT Enigma@Home Sending scheduler request: To fetch work.
Sun 31 May 2009 08:08:22 AM EDT Enigma@Home Requesting new tasks
Sun 31 May 2009 08:08:27 AM EDT Enigma@Home Scheduler request completed: got 0 new tasks
Sun 31 May 2009 08:08:27 AM EDT Enigma@Home Message from server: (Project has no jobs available)
Sun 31 May 2009 08:11:29 AM EDT Enigma@Home Sending scheduler request: To fetch work.
Sun 31 May 2009 08:11:29 AM EDT Enigma@Home Requesting new tasks
Sun 31 May 2009 08:11:34 AM EDT Enigma@Home Scheduler request completed: got 0 new tasks
Sun 31 May 2009 08:11:34 AM EDT Enigma@Home Message from server: (Project has no jobs available)
Sun 31 May 2009 08:14:41 AM EDT Enigma@Home Sending scheduler request: To fetch work.
Sun 31 May 2009 08:14:41 AM EDT Enigma@Home Requesting new tasks
Sun 31 May 2009 08:14:46 AM EDT Enigma@Home Scheduler request completed: got 0 new tasks
Sun 31 May 2009 08:14:46 AM EDT Enigma@Home Message from server: (Project has no jobs available)
Sun 31 May 2009 08:17:51 AM EDT Enigma@Home Sending scheduler request: To fetch work.
Sun 31 May 2009 08:17:51 AM EDT Enigma@Home Requesting new tasks
Sun 31 May 2009 08:17:56 AM EDT Enigma@Home Scheduler request completed: got 0 new tasks
Sun 31 May 2009 08:17:56 AM EDT Enigma@Home Message from server: (Project has no jobs available)

---

The problem with file upload handler is fixed.
The 'project has no jobs available' is harder to trace, so far I couldn't find anything helpful in log files. I think that I'll try to update feeder and scheduler to the latest revision to see if that will help, there were no database updates since revision 18067 so I think that both daemons should be compatible.

---

M4 Project homepage
M4 Project wiki

The problem with file upload handler is fixed.

Seems to be back. (Sorry, didn't see this thread until after I started one of my own in the Bug Reports.).

---

"Verloren ist nur, wer sich selbst aufgibt."

Here's the latest bugfixes in BOINC....If you can bump up to 6.6.33 you probably should....

Change Log for 6.6.32 (not released or on any download list!)

- Mac MGR: Eliminate erroneous references to wxMac-2.8.7 in XCode (now building with wxMac-2.8.10).

- SS: Add new optional boolean xml tag <default_ss_first>; if true, then launch default screensaver graphics app first, else run science graphics first.

- MGR: Remove references to ViewNews, it won't appear in this release.

- fix display problem when talking to old clients

- lib: return proper error codes from boinc_rename() and boinc_mkdir()

- client: Haiku support (from Urias McCullough?)

- client: include plan class in other_result list in sched request

- client: unify code for writing soft link files

- Mac MGR: Fix per-thread-locale logic on Mac; weak-link sqlite3 for OS 10.3.9 compatibility.

- client: if scheduler request didn't request work, don't report 0 tasks

- MGR: In Async RPC logic, change calling order for wxCondition and wxMutex to match examples in literature

Change log for 6.6.33

- Mac: delete source files ViewNews.cpp, ViewNews.h from XCode Project

- client: include plan class in other_result list in sched request (for resource-specific jobs-in-progress limit)

- client: show "est. delay" correctly in work fetch debug msgs

- client: show times correctly in rr_sim debug msgs

- client: in "requesting new tasks" msg, say what resources we're requesting (if there's more than CPU)

- client: estimated delay was possibly being calculated incorrectly because of roundoff error

- client: add a 1e-6 slop factor in deciding if a resource is fully utilized.

---

I think that the 'Project has no work available' bug is fixed now. Looks like if I restart the BOINC server (or feeder alone), I also have to kill all the fastcgi schedulers (can be done easily with 'apachectl -k restart' or 'killall cgi'). Before restart 'old' scheduler instances are unable to see the tasks inside shared memory segment for some reason.
I noticed that yesterday after upgrading scheduler from 18087 to the latest SVN, I did some requests from browser and I noticed, that 95% of the requests are still beeing handled by old schedulers.

The problem with file upload handler is fixed.

Seems to be back. (Sorry, didn't see this thread until after I started one of my own in the Bug Reports.).

It's fixed again.

---

M4 Project homepage
M4 Project wiki

I have reset the project and seems to be working now! :D an overclocked core2 churning away now

I hated resetting the project (lost my little project graph), but having seen the less and less work running (and daily averages dropping)I had to do something. I had tried many times over half the day to update. I saw lots of work was on the server, so that wasn't the issue. 17 tasks downloaded after resetting, so things are now running again. Thanks.

7/2/2009 12:22:55 AM|Enigma@Home|Sending scheduler request: To fetch work. Requesting 43200 seconds of work, reporting 0 completed tasks
7/2/2009 12:23:00 AM|Enigma@Home|Scheduler request completed: got 0 new tasks
7/2/2009 12:23:00 AM|Enigma@Home|Message from server: No work sent

Ran all day fine, now it's not getting any work. Server status says it's got plenty of WUs ready to go, any ideas why it won't give me any? Details on my machine says 133/day per CPU and I've only gone through 46.

PS: This is KWSNs project of the month, so if we broke it earlier by all of us joining around the same time and then requesting a ton of work... sorry hehe. Lots of users having issues with the project though, wish we could sort it out.

Edit: After looking through my task log I noticed I started getting download errors too, but weird ones. Never seen this before:
7/1/2009 11:38:59 PM|Enigma@Home|Started download of yqwk__0
7/1/2009 11:39:00 PM|Enigma@Home|Giving up on download of yqwk__0: file not found