BUG REPORT: 100%CPU usage ofboinc.exe when --no_gui_rpc switch specified

Message boards : Questions and problems : BUG REPORT: 100%CPU usage ofboinc.exe when --no_gui_rpc switch specified
Message board moderation

To post messages, you must log in.

AuthorMessage
Raistmer

Send message
Joined: 9 Apr 06
Posts: 302
Message 81611 - Posted: 28 Sep 2017, 8:32:15 UTC

Details described here: https://setiathome.berkeley.edu/forum_thread.php?id=81632&postid=1892079
Bug is repeatable, I see it on ~8 hosts too.
ID: 81611 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 81672 - Posted: 1 Oct 2017, 21:07:30 UTC - in response to Message 81611.  

With the --no_gui_rpc switch you're telling the BOINC client not to send out any remote procedure calls, aka it's not communicating with anything out there (BOINC Manager, boinccmd, the screen saver, remotely controlled BOINC, any of the projects that support communications by RPC, etc.)
It's essentially deaf, mute and stupid.

I've tried finding when the option was added and what it was for, but apparently it happened before I switched to gmail, and I didn't retain the emails from the previous ISP. So that makes searching a little more troublesome. I've now asked David about it. Let's see what he comes up with.
ID: 81672 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5078
United Kingdom
Message 81673 - Posted: 1 Oct 2017, 22:23:01 UTC - in response to Message 81672.  
Last modified: 1 Oct 2017, 22:27:29 UTC

0d2a0ad9a3124776c45458f83fddfe75b0924117

davidpanderson committed on Jul 23, 2005

 +	- Core client: add "-no_gui_rpc" cmdline option.
 +		If present, don't create listening socket for GUI RPC.
 +		(Useful if bind() doesn't work).
See how that compares with what David remembers.
ID: 81673 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 81674 - Posted: 1 Oct 2017, 23:19:57 UTC - in response to Message 81673.  
Last modified: 1 Oct 2017, 23:20:09 UTC

He pointed me to the checkin notes 2005, same date, same message. Plus said that a client doesn't need GUI RPCs to do computing.. There. If it's broken, I don't think there's going to be a fix made for it. Easier to remove the option, because anyone can run the client on its own these days - which they couldn't when this option was added for BOINC 4.71 -- Oh my, anyone remember that version? :)
ID: 81674 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 81685 - Posted: 2 Oct 2017, 14:39:11 UTC - in response to Message 81674.  

And
It was added when manager and client were separate, otherwise there would have been no GUI RPC.

It's necessary for security-conscious users. GUI RPC is a potential security vulnerability.

I've put it in Github: Issue #2150
ID: 81685 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 81698 - Posted: 2 Oct 2017, 21:51:27 UTC

David found what ailed this and is putting a fix into a PR.
ID: 81698 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5078
United Kingdom
Message 81700 - Posted: 2 Oct 2017, 22:06:03 UTC - in response to Message 81698.  

David found what ailed this and is putting a fix into a PR.
Good. But that's one I would leave until v7.10.x, and let the real programmers have a good look at it.
ID: 81700 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15478
Netherlands
Message 81705 - Posted: 3 Oct 2017, 8:01:41 UTC

ID: 81705 · Report as offensive

Message boards : Questions and problems : BUG REPORT: 100%CPU usage ofboinc.exe when --no_gui_rpc switch specified

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.