Message boards : BOINC client : Does BOINC check the remote manager at startup?
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Jun 08 Posts: 641 |
I am using BAM! and boinc.exe is launched using --detach --allow_remote_gui_rpc Note: BM and BoincTray are not being used and were edited out of the registery. For local management I use BT (Boinctasks). Recently, due to a bug in the gpugrid CUDA handler, I went to BAM! and checked the box that should have caused the gpugrid project to become suspended. This worked fine on 2 out of 5 systems, but the 3 it didnt work on I had to attach a monitor and keyboard to and bring up safe mode and delete any gpugrid files down in in ProjectData. These systems ran the gpugrid project seemingly before checking to see if the project was suspended. This caused the system to freeze because of the CUDA bug. Anyway, I was wondering if boinc.exe checks the remote manager before launching the project. Maybe this feature is only in BM and I am not running BM. |
Send message Joined: 20 Dec 07 Posts: 1069 |
Maybe this feature is only in BM and I am not running BM. I can't say anything about your problem with BAM!, but I'm pretty sure that (a missing) BM is not the problem. It's just a GUI; all checking/scheduling etc. is done by the client not the manager. Gruß Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) |
Send message Joined: 5 Mar 08 Posts: 272 |
I get messages in the BOINC event log at start up complaining it can't find the host defined in my remote_hosts file (usually it's off). I don't worry about it but that indicates the core client is checking the remote hosts are accessible. Not sure if this relates to your issue with the account manager as I don't run one. I find BOINCtasks does what I need controlling the projects the various machines are attached to. MarkJ |
Send message Joined: 27 Jun 08 Posts: 641 |
Yea - pretty sure now that boinc just could not make the connection. At the gpugrid project there was a suggestion to put a 30 second delay somewhere into into cc_config to allow more time to "fix" the problem. Setting the "project suspend" flag at BAM! would have worked and did on my systems right on the router but failed on the ones I had on the A/C power line ethernet as that, I am guessing, had not recovered properly. |
Copyright © 2025 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.