I think I've followed the example as far as I can BUT I don't seem to be able to connect to the 2nd BOINC client using the BOINCMgr. I have attempted to connect to the 2nd client using the advanced/select computer/host name/password mechanism using computer name "localhost:9999" and the password created vis notepad in gui_rpc_auth.cfg but keep getting attached back to the orig BOINC client. This is true even if I put the " <allow_multiple_clients>1</allow_multiple_clients>" line in cc_config.xml ... any ideas on how to do the connect??

BTW: do I need admin priv for any of the steps??

Ed F

Since i've still got my 2nd Boinc Installation backed up on a USB Stick (The Hardrive failed a bit later taking out that host's Win 7 installation), i've been looking through it,

The one thing i haven't seen mentioned is the setting up of remote_hosts.cfg with the host details, the host i was using the 2nd Boinc Installation was known as P5N-E-SLI, so that was what went in there.

I'm thinking of fitting a third GPU (only a PCI GT430) in my i7-2600K/GTX460/HD5770 host this weekend, and this time just attach it to Seti Beta, since at the moment i have no Seti Beta tasks, so i can't loose any.

Claggy

The one thing i haven't seen mentioned is the setting up of remote_hosts.cfg with the host details, the host i was using the 2nd Boinc Installation was known as P5N-E-SLI, so that was what went in there.

I don't understand the reference ... where do I get more info??

Ed F

http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely

---

O.K., almost everything is working but would like info on what to do to the BOINCMGR to "see" both BOINC's

Here is my startup now ...

rem
rem cd C:\BOINC_test_data_1
start C:\BOINC_test_programs\boinc.exe --gui_rpc_port 31416 --dir C:\BOINC_test_data_1 --detach
rem
rem cd C:\BOINC_test_data_2
start C:\BOINC_test_programs\boinc.exe --gui_rpc_port 31417 --dir C:\BOINC_test_data_2 --allow_multiple_clients --detach
rem
cd C:\BOINC_test_data_1
start C:\BOINC_test_programs\boincmgr.exe /s
rem

The 31417 instance of BOINC doesn't even show up on netstat ...

I am able to run the 2 boinc's running independent WU's just fine ... I just can't admin them both.

(what I have been doing is shutting both boincs down and reversing the starting order) then I can "see" the other boinc.

Ideas??

Ed F

What you should be able to do is start up a 2nd Boinc Manager, it'll connect to the 1st client, then use 'select computer' put in localhost:31417 and the gui_rpc password to connect it to the 2nd client,

Claggy

well, not quite ...

(I'm using SETI@HOME with the lunatic opt apps)

If I attempt to start a new BOINCMGR, the currently running one flashes but stays on the origional "localhost:31416" and I can't get to 31417

If I "switch user", so I have 2 accounts active, and fire up BOINCMGR using "localhost:31417" I can see/manage it just fine

BUT

on both 31416 AND 31417 I get

2/8/2012 11:49:57 AM | | GPUs have become unusable; disabling tasks
.
.
.
2/8/2012 11:58:35 AM | | GPUs have become usable; enabling tasks

as long as I'm in BOINCNGR on the second account the GPU's don't run!!

SO I'm still confused as what to do.

Any help??

Ed F

1) Normally, only one copy of BOINCMGR is allowed to run at once. But there is a command (Advanced view, Advanced menu, next to last item): "Launch another BOINC Manager". That bypasses the 'only one copy' restriction, and allows you to fill in the 'localhost:31417' that Claggy was suggesting.

2) 'GPUs have become unusable' isn't a function of the Manager: the Manager is merely reporting the status of the underlying client. With Windows 7 (or Vista), the core client can only access the GPU drivers if it is running under the same user account as the currently logged-in active user: so if you switch users, the core client loses contact with the drivers and hence with the GPU. You can get round that by shutting down the core client and restarting it in the new user context.

If you would prefer to use just one program to monitor both instances of the client, you could try BoincTasks. I tried a multiple client setup as a test and used BT to monitor both instances with no problems. If you decide to try BoincTasks, click on the download tab on BT's site and use the 1.30 version.

1) Normally, only one copy of BOINCMGR is allowed to run at once. But there is a command (Advanced view, Advanced menu, next to last item): "Launch another BOINC Manager". That bypasses the 'only one copy' restriction, and allows you to fill in the 'localhost:31417' that Claggy was suggesting.

seems NOt to work ... i get something like:

"Authorization failed connecting to running client. Make sure you start this program in the same directory as the client"

I get this attempting to attach to 31416 or 31417.

2) 'GPUs have become unusable' isn't a function of the Manager: the Manager is merely reporting the status of the underlying client. With Windows 7 (or Vista), the core client can only access the GPU drivers if it is running under the same user account as the currently logged-in active user: so if you switch users, the core client loses contact with the drivers and hence with the GPU. You can get round that by shutting down the core client and restarting it in the new user context.

yes, I knew this but I thought it MAY help as a diagnostic point ... sorry.

Any other ideas on how to get 2 boincmgr's running??

Ed F

seems NOt to work ... i get something like:

"Authorization failed connecting to running client. Make sure you start this program in the same directory as the client"

Is your remote_hosts.cfg file up to date?

Gruß,
Gundolf

Is your remote_hosts.cfg file up to date?

I'm not sure how this relates to running 2 boincs on 1 computer ... It LOOKS like this is used for cross computer control ... ???

so the answer is NO remote_hosts.cfg is not up to date ... it doesn't exist :)

Advice??

Ed F

I'm not sure either, but it won't hurt to try. ;-)

There's also an <allow_remote_gui_rpc> cc_config.xml option or the --allow_remote_gui_rpc command-line option respectively, for a brief check if it would be needed.

Gruß,
Gundolf

I've been thinking... while I wrote an answer to someone else.
Since 6.12 it's no longer possible to run multiple BOINC Manager instances without pointing all of them to their own client. Only one BM can show the contents of one client, any other BM running on the system needs to be pointed at another Boinc.exe, installed in a different directory than the one the present one is installed in.

So you can't point both at C:\BOINC_test_programs\boinc.exe, since one of the Boinc instances needs to be running from its own directory. Or, at least, as far as I know...

---