Posts by Hans Tobeason

1) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 57067)
Posted 25 Oct 2014 by Hans Tobeason
Post:
I will try your suggestions soon - but, in the meantime, I did want to report that, in the 4-5 days since I have NOT been running BOINC Manager on the MacMini (just the daemon), I have never lost screen sharing to it. I would consider it pretty much definitive that BOINC Manager was the culprit.
2) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56968)
Posted 22 Oct 2014 by Hans Tobeason
Post:
Success! I honestly do not know what I did wrong, but it's all good now. I'm going to hope that my screen sharing issue will no longer manifest.

I do have one question --

I noted at <http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely> that there's a command line option to allow access to the daemon from anywhere: --allow_remote_gui_rpc. Would it be possible to modify the shell script to incorporate that option? My MacBookPro will not always be at the address I set up in remote_hosts.cfg.

Again, thank you for all your help.
3) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56965)
Posted 22 Oct 2014 by Hans Tobeason
Post:
Charlie -

This is a mystery - but I have good news...

I went back to square one. Uninstalled BOINC. Rebooted. Followed your instructions above (same as I did before, but whatever...). The daemon seems to be launching now! I must have done something wrong before (several times).

Next step - trying to get access from my MacBookPro. I will report.

Thanks, and sorry for the confusion.

Hans
4) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56955)
Posted 22 Oct 2014 by Hans Tobeason
Post:
I've triple-confirmed that BOINCManager.app (v7.4.23) is in /Applications.

Here's the plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>GroupName</key>
	<string>boinc_master</string>
	<key>Label</key>
	<string>edu.berkeley.boinc</string>
	<key>Program</key>
	<string>/Applications/BOINCManager.app/Contents/Resources/boinc</string>
	<key>ProgramArguments</key>
	<array>
		<string>/Applications/BOINCManager.app/Contents/Resources/boinc</string>
		<string>-redirectio</string>
		<string>-daemon</string>
	</array>
	<key>RunAtLoad</key>
	<true/>
	<key>UserName</key>
	<string>boinc_master</string>
	<key>WorkingDirectory</key>
	<string>/Library/Application Support/BOINC Data/</string>
</dict>
</plist>
5) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56878)
Posted 21 Oct 2014 by Hans Tobeason
Post:
BOINC Manager is NOT in Login Items.
edu.berkeley.boinc.plist is in LaunchDaemons.

sudo launchctl load /Library/LaunchDaemons/edu.berkeley.boinc.plist
returns:
launchctl: no plist was returned for: /Library/LaunchDaemons/edu.berkeley.boinc.plist
launchctl: no plist was returned for: /Library/LaunchDaemons/edu.berkeley.boinc.plist
nothing found to load

sudo launchctl start edu.berkeley.boinc
returns:
launchctl start error: No such process

After a restart, neither stderrdae.txt nor stdoutdae.txt were recreated.
6) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56864)
Posted 21 Oct 2014 by Hans Tobeason
Post:
Thank you for your reply.

Yes, I used Activity Monitor to check. Normally, when I launch BOINC Manager, I see both the boinc daemon and the Manager application in AM. After running the shell script and restarting, I do not see the daemon.

Just now, when I launched BOINC Manager to verify that I was able to see the daemon, I got this error: BOINC Manager - Daemon Start Failed.

Attempting to launch the daemon using "sudo launchctl start edu.berkeley.boinc" results in:

launchctl start error: No such process

If I re-install BOINC, launching Manager works, and I see both the daemon and Manager in AM. It seems that running the shell script is somehow doing some damage...

Note also that I do see edu.berkeley.boinc.plist in LaunchDaemons after running the shell script.

I have uninstalled BOINC (using the uninstaller script) and reinstalled it. I've also manually removed edu.berkeley.boinc.plist. I can now run Manager without error, and I'm seeing the boinc process in AM. I will await further instructions.

Thank you.
7) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56859)
Posted 20 Oct 2014 by Hans Tobeason
Post:
I've attempted to follow the instructions above, but the BOINC daemon is not launching on the MacMini (the host computer).

I successfully ran the shell script. I confirmed that the edu.berkeley.boinc.plist file was created in LaunchDaemons. I restarted the MacMini. The daemon does not seem to have launched.

Please advise. Thank you.
8) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56844)
Posted 20 Oct 2014 by Hans Tobeason
Post:
Spoke too soon... Can't see the MacMini this morning. I will now try the daemon setup.
9) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56748)
Posted 17 Oct 2014 by Hans Tobeason
Post:
Again, thank you for your replies...

I can confirm that running BOINC Manager in "Advanced View" solves this issue. I've now been running for almost two days without a problem, so I'm not going to go through the process for running BOINC as a daemon.
10) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56731)
Posted 16 Oct 2014 by Hans Tobeason
Post:
BOINC Manager 7.4.23/wxWidgets 3.0.0 exhibits the same problem - running it appears to kill my ability to "share" (either screen sharing or file sharing) through the Finder interface. Curiously, I can sometimes get vnc access to the Mini (vnc://macmini.local). I am going to test the "Advanced View" hypothesis again - letting BOINC Manager run in that mode for 24 hours.
11) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56720)
Posted 15 Oct 2014 by Hans Tobeason
Post:
Thank you for your reply.

[1] I'm not sure I understand what you're asking here - if I DON'T run BOINC Manager on the Mini, screen sharing DOES work - that's the issue - running BOINC Manager (eventually) causes screen sharing to fail - if BOINC Manager is NOT running, screen sharing is fine.

[1a] An interesting update - last night, I kept BOINC Manager running on the Mini, but I changed its mode to "Advanced View". This morning, when I would have expected screen sharing fail, it was fine! I know this is only one night's worth of testing, but still...

[1b] I will try the test version - in Simple View - and see how that works.

[2] I will hold off on this approach while I continue to test the above scenarios.

Thank you!
12) Message boards : BOINC Manager : BOINC Manager Killing Screen Sharing (Message 56714)
Posted 14 Oct 2014 by Hans Tobeason
Post:
I've tested this repeatedly, and it is reproducible...

I run BOINC Manager 7.2.42 on a MacMini under OS X 10.9.5. The Mini is headless, and I access it through screen sharing from a MacBookPro on the same local network. After BOINC Manager has been running for a while - overnight, say - I can no longer "see" the Mini. It will appear in the "Shared" list in a Finder window of the MacBookPro, but it will not "connect", nor can I screen share into it. Curiously, when this happens I can sometimes use "Connect to Server" on the MacBookPro and vnc: into the Mini, but not always. And, when I do so, I find that I cannot reboot the Mini - it's almost as if the Mini's Finder is locked up. The only way to reestablish connectivity to the Mini is to force reboot it.

Any thoughts/advise most appreciated. Thank you.



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.