Multiple Managers getting confused with WU progress for multiple clients

Message boards : Questions and problems : Multiple Managers getting confused with WU progress for multiple clients
Message board moderation

To post messages, you must log in.

AuthorMessage
Duff_Moss

Send message
Joined: 16 Jun 11
Posts: 7
Australia
Message 38492 - Posted: 16 Jun 2011, 13:53:47 UTC

Hi,

This problem has been bugging me for a while, and I can't seem to solve it.

I have two boinc clients running and two managers - one for each boinc client. That works well enough. The problem I have is that the elapsed time, progress and time to complete gets confused on the managers.

What seems to happen, is that both managers report the progress of the first active unit of the first client that is launched on the system. Besides that, all other details are correct (workunit name, project etc). I know the WU is processing properly as the progress is correct in the stderr.txt file. The WU completes ok - just the manager doesn't track it's progress correctly.


I am running BOINC 6.10.60


I am running two clients because I have one that is run as a service. Problem with run as a service is that it wont recognise my ATI GPU, so I run a second on demand client that only does GPU work.

Any ideas
ID: 38492 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15116
Netherlands
Message 38494 - Posted: 16 Jun 2011, 14:51:42 UTC - in response to Message 38492.  

You can set up both clients to run with their own RPC port and then have both Managers start with that port as well. Then they should always show the correct client they're on.

You would have to start them (from your batch file, or script) in this fashion:
c:\program files\boinc\boinc.exe --allow_multiple_clients --gui_rpc_port 31416 --detach
c:\program files\boinc\boincmgr.exe -m -g 31416 -n localhost
c:\program files\boinc\boinc.exe --allow_multiple_clients --gui_rpc_port 31418 --detach
c:\program files\boinc\boincmgr.exe -m -g 31418 -n localhost

You can use different port numbers, of course. The ones I used, 31416 (default) and 31418 are only examples.
ID: 38494 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4872
United Kingdom
Message 38497 - Posted: 16 Jun 2011, 15:35:03 UTC - in response to Message 38494.  

Just check that the --detach command (as shown in the documentation) works properly for you. I recently hit a problem with it, and found that the actual source code uses --detach_phase_two, which worked better for my purposes.

Also, note that the new format --detach_console (shown in the revised documentation) will only start working from v6.12.34 at the earliest, and possibly not until v6.14
ID: 38497 · Report as offensive
Duff_Moss

Send message
Joined: 16 Jun 11
Posts: 7
Australia
Message 38510 - Posted: 17 Jun 2011, 4:26:47 UTC - in response to Message 38494.  

I do have both clients using a different port, but I wasn't launching the manager directly as you suggest. I would open the manager, which would of course connect the the 'default' client. I would open a second instance of the manager, which would also connect to the default client. I would then in the second manager connect to a new computer, and then specify the localhost with the second client's port.

So maybe it has something to do with that method. I will try as you suggest and see how it goes.

Thanks
ID: 38510 · Report as offensive
Duff_Moss

Send message
Joined: 16 Jun 11
Posts: 7
Australia
Message 38511 - Posted: 17 Jun 2011, 4:27:35 UTC - in response to Message 38497.  

Just check that the --detach command (as shown in the documentation) works properly for you. I recently hit a problem with it, and found that the actual source code uses --detach_phase_two, which worked better for my purposes.

Also, note that the new format --detach_console (shown in the revised documentation) will only start working from v6.12.34 at the earliest, and possibly not until v6.14



I definitely didn't use the detach command - so indeed it keeps the console open. I will give that a try too. Thanks also.

ID: 38511 · Report as offensive
Duff_Moss

Send message
Joined: 16 Jun 11
Posts: 7
Australia
Message 38733 - Posted: 30 Jun 2011, 13:45:56 UTC - in response to Message 38494.  

Not sure what I am doing wrong, but I can't get the boinc manager to launch as you have described:

c:\program files\boinc\boincmgr.exe -m -g 31418 -n localhost

It doesn't understand those switches. If I do a /h I dont see any of those switches listed?


ID: 38733 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15116
Netherlands
Message 38734 - Posted: 30 Jun 2011, 15:26:07 UTC - in response to Message 38733.  
Last modified: 30 Jun 2011, 15:26:38 UTC

If not -x, then /x as attributes. Although "-n namestring" is on 6.12 only, if I recall correctly.

So instead of c:\program files\boinc\boincmgr.exe -m -g 31418 -n localhost
try
c:\program files\boinc\boincmgr.exe /m /g 31418 /n localhost
ID: 38734 · Report as offensive

Message boards : Questions and problems : Multiple Managers getting confused with WU progress for multiple clients

Copyright © 2022 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.