jobs are not getting dispatched

Message boards : Server programs : jobs are not getting dispatched
Message board moderation

To post messages, you must log in.

AuthorMessage
dharasty

Send message
Joined: 29 Jul 14
Posts: 4
United States
Message 55126 - Posted: 29 Jul 2014, 18:30:17 UTC

I'm new to BOINC; I'm using the "Quick start" BOINC server, as per: http://boinc.berkeley.edu/trac/wiki/QuickStart

I seem to have everything installed and running: I can connect to my test project with 3 different clients (Windows, Android, Ubuntu). HOWEVER: no jobs are getting dispatched: all clients report "the server says there is no work", and yet, I see results/workunits in the server ops pages. (I've enqueued both the example_app jobs, and some of my own for a sample Windows client.)

What is my next step to figure out why jobs are not getting dispatched?
ID: 55126 · Report as offensive
ChristianB
Volunteer developer
Volunteer tester

Send message
Joined: 4 Jul 12
Posts: 321
Germany
Message 55157 - Posted: 30 Jul 2014, 16:18:19 UTC

Try to set a higher debug level on the server and activate additional log flags like debug_send* and debug_version_select. Than look into the server logfiles. The client sometimes also prints in the message log why no work was sent.

see: http://boinc.berkeley.edu/trac/wiki/ProjectOptions#Logging
ID: 55157 · Report as offensive
dharasty

Send message
Joined: 29 Jul 14
Posts: 4
United States
Message 55166 - Posted: 30 Jul 2014, 21:10:42 UTC - in response to Message 55157.  
Last modified: 30 Jul 2014, 21:12:27 UTC

Thank you for the input... but I still have so many questions. Any help is appreciated.

1) Where should I be looking (in the file system or DB) for the results? I honestly can't figure out where to look. (I'd like to confirm that the "results directory" -- wherever that is -- is empty.)

2) My feeder.log as these lines in it:

2014-07-30 14:33:08.9219 [debug] result [RESULT#1] already in array
2014-07-30 14:33:08.9220 [debug] result [RESULT#2] already in array
2014-07-30 14:33:08.9221 [debug] result [RESULT#3] already in array
2014-07-30 14:33:08.9221 [debug] result [RESULT#4] already in array
2014-07-30 14:33:08.9221 [debug] result [RESULT#5] already in array
2014-07-30 14:33:08.9221 [debug] result [RESULT#6] already in array
2014-07-30 14:33:08.9221 [debug] result [RESULT#7] already in array
2014-07-30 14:33:08.9221 [debug] result [RESULT#8] already in array
2014-07-30 14:33:08.9222 [debug] result [RESULT#9] already in array
2014-07-30 14:33:08.9222 [debug] result [RESULT#10] already in array
2014-07-30 14:33:08.9222 [debug] result [RESULT#11] already in array
2014-07-30 14:33:08.9222 [debug] result [RESULT#12] already in array
2014-07-30 14:33:08.9227 [debug] Added 0 results to array
2014-07-30 14:33:08.9227 [debug] 12 results already in array


Does that mean the results are already calculated by the clients? What does it mean to say “results are already in array”?

3) You mentioned I should try to set a higher debug level. OK, I added:

<debug_send/>
<debug_send_scan/>
<debug_send_job/>
<debug_user_messages/>


to my config.xml. Do I need to stop and restart something? If so, what? (Maybe not, as if the scheduler is a CGI app… won’t it necessarily ready the “config.xml” every time it runs?)

4) What log am I supposed to be looking in? There doesn’t seem to be a log called “scheduler.log” or “dispatcher.log”.
ID: 55166 · Report as offensive

Message boards : Server programs : jobs are not getting dispatched

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.