Unable to install 7.5.1 on MacOS 10.15.4

[BadWolf]

Hi, I have an issue installing the latest client on my iMac:

- Installer runs without an error message and finishes with the message that the installation was successful
- Local Web Control page loads but eventually times out while trying to connecting to the client
- I can't access (although admin rights) /usr/local/bin to see whether FAHClient really doesn't exist
- In /Applications/Folding@Home folder there's only FAHControl and FAHViewer
- /Library/Application Support/FAHClient is empty

Only thing I can find are the following error messages in /var/logs/system.log during installation and after installation, every 10 second the "no such file of directory" error:

Code: Select all

Apr  1 14:49:00 BadWolf AGMService[591]: ProcessPath : /System/Library/CoreServices/Installer.app/Contents/MacOS/Installer
Apr  1 14:49:00 BadWolf Installer[2600]: assertion failed: 19E266: libxpc.dylib + 92807 [32B0E31E-9DA3-328B-A962-BC9591B93537]: 0x89
Apr  1 14:49:01 BadWolf com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.77455B3B-363E-42EF-A37F-6C3D9E0D0B3B[2601]): Caller wanted oneshot behavior for pre-existing instance: caller = Installer
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient): This service is defined to be constantly running and is inherently inefficient.
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient[2623]): Could not find and/or execute program specified by service: 2: No such file or directory: /usr/local/bin/FAHClient
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient[2623]): Service setup event to handle failure and will not launch until it fires.
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient[2623]): Service exited with abnormal code: 78
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient[2625]): Could not find and/or execute program specified by service: 2: No such file or directory: /usr/local/bin/FAHClient
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient[2625]): Service setup event to handle failure and will not launch until it fires.
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient[2625]): Service exited with abnormal code: 78
Apr  1 14:49:18 BadWolf com.apple.xpc.launchd[1] (org.foldingathome.fahclient): Service only ran for 0 seconds. Pushing respawn out by 10 se

[edit]
While waiting for approval for this new topic, I found the following topic (with a cryptic title, therefor I didn't find it with previous searches) on the forum:
viewtopic.php?f=106&t=32209

Looks the same, only that there it's mentioned the error also occurs on 10.15.3, while a lot of my colleagues don't have this issue on their 10.15.3 laptops.
Only differences are that hey installed it on quite recent Macbooks and I'm trying to install on a iMac 2012.

In the meantime I've tried several uninstall/re-installs, but that didn't help either.

[Joe_H]

In the Terminal app, can you try the following:

sudo ls -l /usr/local/bin

to see if there is a FAHClient executable there? You should be prompted for your admin password. If it does show up there, could you post what the output was for that line? There should also be a FAHCoreWrapper file there.

I am assuming FAHClient is not showing up as running in Activity Monitor.

I can be of limited assistance as I don't have anything higher than High Sierra to test the installer on, but will bring this to the attention of developer who assisted in the port to OS X/macOS.

[BadWolf]

In the Terminal app, can you try the following:

sudo ls -l /usr/local/bin

to see if there is a FAHClient executable there? You should be prompted for your admin password. If it does show up there, could you post what the output was for that line? There should also be a FAHCoreWrapper file there.

These are the relevant lines of the output. The rest are a lot of symbolic links unrelated to FAH.

Code: Select all

-rwxr-xr-x  1 root     wheel  8405280 May 23  2018 FAHClient
-rwxr-xr-x  1 root     wheel  1350352 May 23  2018 FAHCoreWrapper

I am assuming FAHClient is not showing up as running in Activity Monitor.

Correct

I can be of limited assistance as I don't have anything higher than High Sierra to test the installer on, but will bring this to the attention of developer who assisted in the port to OS X/macOS.

Thanks.

[calxalot]

I uninstalled fah, upgraded from macOS 10.15.3 to 10,15,4, and reinstalled fah. All seems to working ok for me.

Only thing I can think of is that you recently upgraded from pre 10.15, and the file system conversion and split hasn’t finished. Launched might be confused about where /usr/local/bin is.

Please indulge me and try a reboot.

[BadWolf]

I've been running 10.15.x for quite some time now. Upgrades to .4 last week I think.

I tried to following:
- Ran the uninstaller, rebooted, re-installed
- Rebooted while installed

Neither helped.

[dnandan]

I also have it (7.5.1) working on 10.15.4 without issues.

I also don't have much experience trouble shooting these types of things, but...


I'm assuming you have /Applications/Folding@home with a few files: FAHControl.app / FAHViewer.app

What errors are thrown if you try opening from a command line: Folding@home % open FAHControl.app ?

Or if you: $open /usr/local/bin/FAHClient - What errors are seen?

Is this a 'Control app' issue - Or is this a 'Client' issue?

- if you had this running previously to .4 upgrade, perhaps you have some associated legacy files that didn't get cleaned up properly.

dan

[dnandan]

I'm running 7.5.1 on 10.15.4 without any issues either.

Is this a Control or Client issue? From a command line, can you (use the open command):
$open /Applications/Folding@Home/FAHControl.app
$open /usr/local/bin/FAHClient

And see what your results are -

can you look in the directory /Applications/Folding@Home and check your files, I have 4 ( FAHControl.app, FAHViewer.app, Uninstall- pkg , and Web Control.

dan

[BadWolf]

Yesterday was my first time installing F@H, so never had it running on any other OS level or during an upgrade.

$open /Applications/Folding@Home/FAHControl.app

The Control panel opens, but just above the "Status/System Info/Log" tabs it says "Client: local Connecting Inactive" instead of "Client: local Online Running" which it says on my Windows laptop

$open /usr/local/bin/FAHClient

The following error: "The file /usr/local/bin/FAHClient does not exist."
When I "sudo" that command I don't get that error, but nothing happens/changes either.

can you look in the directory /Applications/Folding@Home and check your files, I have 4 ( FAHControl.app, FAHViewer.app, Uninstall- pkg , and Web Control.

Code: Select all

drwxr-xr-x  3 root  wheel     96 Apr  2 18:49 FAHControl.app
drwxr-xr-x  3 root  wheel     96 Apr  2 18:49 FAHViewer.app
-rw-r--r--  1 root  wheel  63405 May 23  2018 Uninstall Folding@home.pkg
-rw-r--r--  1 root  wheel     57 Apr 25  2018 Web Control.url

No other messages in my system.log besides the "No such file or directory" error from my initial post.

[dnandan]

I looked pithing the forums for '"Client: local Connecting Inactive" and matched a lot of other folks.

Somehow, you gotta figure out why you can execute into that /usr/local/bin directory.

In your first post, you wrote ' I can't access (although admin rights) /usr/local/bin to see whether FAHClient really doesn't exist' - you'll need to ( literally) go down this PATH ( echo $PATH ) - to see why you can see anything.
Also ' Installer runs without an error message and finishes with the message that the installation was successful'

So.. Where did the installer install it? If you look ( and i'm an old unix guy, so i generally do everything from a command prompt ) -

What do you see at: $ ls -l /usr/local - anything? I think you generally create the directory - I see my '/usr/local/bin' directory as I own the directory and I'm in admin group. ( basic 755 on the directory ).
Is the directory there? Do you own it? Any weird symbolic links along the way? Lets start back at the beginning -

dan

[TomJohnson]

Recommend putting the FAHControl app down in the Dock and running F@H from there. Setup and running the app is more straight forward and is easier to trouble shoot.

[dnandan]

My question remains as if you have a /usr/local/bin/ directory. sometimes, things had been place on other disks under '/opt/local/bin/' - I don't think this has happened, As fro Tom's suggestion that you put Control in the dock if you can, them I"m all for it as thats where they should be.

Its the client that needs ti be @ /usr/local/bin/ -- so, if you found that the directory doesn't exist - create it - mkdir /usr/local/bin, then try your install. sure sounds like the directory isn't there or some symbolic link may be broken..

let us all know.

dna & tom

[BadWolf]

I/we solved it!

I already found out with the help from Joe earlier this topic that FAHClient was placed in /usr/local/bin, but investigating further on your suggestions:

What do you see at: $ ls -l /usr/local - anything? I think you generally create the directory - I see my '/usr/local/bin' directory as I own the directory and I'm in admin group. ( basic 755 on the directory ).
Is the directory there? Do you own it? Any weird symbolic links along the way? Lets start back at the beginning -

This is where you pointed me to the real issue:

Code: Select all

$ ls -l /usr/local
total 0
drwx------  26 504   wheel  832 Apr  2 18:49 bin
drwxr-xr-x   5 root  wheel  160 Oct 19  2018 include
drwxr-xr-x  16 root  wheel  512 Oct 19  2018 lib
<snip>

So there was a 700 permission set on the bin directory, but it's owned by someone called 504 ... so that might explain why I (although an admin user) don't have normal access to the directory, but also why the OS couldn't execute the client executable?
I had a friend of mine check his permissions on the bin directory and with the help of sudo I chown'ed (root:wheel) and chmod'ed (755) the permission to copy his and now Control connects to Client. Web Control still doesn't connect, but no worries ... I can do everything from Control.

Thanks for the support!

[dnandan]

good to hear!

[TomJohnson]

Wheel User is used when no User Account name is found and causes user permission problems for the app. Easiest way to fix this problem. Go to Applications Folder then to Folding@home Folder. Do a Command I(nformation) on FAHControl.app. Unlock window, click on Wheel then click on minus sign to delete. Click on + sign then add your User Account name. Change Read only permissions to Read Write permissions. Lock window. Run F@H Control app from the Dock. PS For those running older OS go to Disk Utility app then Repair Permissions to do the same thing as just mentioned.