Page 1 of 1

osx 10.15.5 - FAHControl will not connect to localhost

Posted: Thu Jul 09, 2020 6:30 pm
by nleco
I installed the software yesterday and it ran and monitored correctly. I restarted my computer today (mac) and FAHControl cannot connect to localhost. If i go to client.foldingathome.org, It shows that it is running. I tried stopping and starting via the web ui. still not connecting. I have 2 other linux computers, which have not been rebooted since install, and those do connect.

I don't recall adding a password to my localhost client. I only added them to the linux hosts, I believe. I am trying to find the osx config xml file to verify.

Re: osx 10.15.5 - FAHControl will not connect to loalhost

Posted: Thu Jul 09, 2020 6:39 pm
by Joe_H
Under a default install, all data files including config.xml are located in /Library/Application Support/FAHClient.

Do you have the builtin firewall from the OS activated?

Re: osx 10.15.5 - FAHControl will not connect to loalhost

Posted: Thu Jul 09, 2020 6:43 pm
by nleco
my firewall is turned off.
I did also try to kill the process via the pid for 'FAHClient'.

the config file seems to have default values aside from my username/passkey.

Re: osx 10.15.5 - FAHControl will not connect to loalhost

Posted: Thu Jul 09, 2020 11:07 pm
by bruce
FAHClient is designed to run as a daemon (with permissions from Apple). If it's like the Linux daemon or the Windows service, it is supposed to restart itself... but I'm not an OS-X expert, so correct me if I'm wrong.

Re: osx 10.15.5 - FAHControl will not connect to loalhost

Posted: Fri Jul 10, 2020 1:51 am
by nleco
bruce wrote:FAHClient is designed to run as a daemon (with permissions from Apple). If it's like the Linux daemon or the Windows service, it is supposed to restart itself... but I'm not an OS-X expert, so correct me if I'm wrong.
I'm a bit unclear about this. I mentioned that the client does appear to be running. I can control it via the Web interface (client.foldingathome.org), which has an iframe pointing to the localhost ui. I can update it there, and via 'htop' I can see the cores begin to work based on the intensity.

The issue I am having is with FAHControl not connecting to the localhost instance. Curious if there is something that can help me diagnose why.

I do see this in the logs:

Code: Select all

default	18:53:48.269076-0700	FAHControl	Connection Error: 32: Broken pipe
default	18:53:48.771380-0700	FAHControl	Connection lost
default	18:53:48.771485-0700	FAHControl	ERROR on connection to 127.0.0.1:36330: Lost connection

Re: osx 10.15.5 - FAHControl will not connect to localhost

Posted: Fri Jul 10, 2020 2:05 am
by nleco
Bruce,
I found this while searching. saw you recommended use of telnet to test:
viewtopic.php?f=108&t=35365&p=335385&hilit=can%27t+connect+port+36330#p335385

i did do that. and what's interesting is I get this.

Code: Select all

Welcome to the FAHClient command server.
>
when I type 'help' it loses connection.

i see this when I ping what ports are in use:

Code: Select all

19:08:06 $ sudo lsof -i -n -P | grep TCP | grep FAHC
FAHContro 1322        ssanchez    9u  IPv4 0x1b443986d2fb0bf7      0t0    TCP 127.0.0.1:32455 (LISTEN)
FAHContro 1322        ssanchez   20u  IPv4 0x1b443986d3c59837      0t0    TCP 192.168.86.45:50521->192.168.86.44:36330 (ESTABLISHED)
FAHClient 2066          nobody    5u  IPv4 0x1b443986cb75b837      0t0    TCP *:7396 (LISTEN)
FAHClient 2066          nobody    6u  IPv4 0x1b443986d029f477      0t0    TCP *:36330 (LISTEN)

Re: osx 10.15.5 - FAHControl will not connect to localhost

Posted: Fri Jul 10, 2020 3:00 am
by Joe_H
Apple pulled out the native telnet from the command line environment, you can use the 'nc' command instead in Terminal:

nc 127.0.0.1 36330

That should give you the command server prompt. Does it still close after entering the 'help' command?

The output of the lsof command on my Mac looks like the following for comparison:

Code: Select all

$ sudo lsof -i -n -P | grep TCP | grep FAHC
FAHClient    71         nobody    5u  IPv4 0xd3d925bc30dae605      0t0  TCP *:7396 (LISTEN)
FAHClient    71         nobody    7u  IPv4 0xd3d925bc30dad335      0t0  TCP *:36330 (LISTEN)
FAHClient    71         nobody    8u  IPv4 0xd3d925bc481f4335      0t0  TCP 127.0.0.1:36330->127.0.0.1:49339 (ESTABLISHED)
FAHContro 22459       --------    9u  IPv4 0xd3d925bc481f4c9d      0t0  TCP 127.0.0.1:32455 (LISTEN)
FAHContro 22459       --------   20u  IPv4 0xd3d925bc48b8a8d5      0t0  TCP 127.0.0.1:49339->127.0.0.1:36330 (ESTABLISHED)
I am running 10.13.6 on this particular Mac, don't currently have a system running a later version.

Re: osx 10.15.5 - FAHControl will not connect to localhost

Posted: Fri Jul 10, 2020 3:03 am
by nleco
I installed telnet via homebrew. People ported it over.
https://formulae.brew.sh/formula/telnet

the 'nc' command you gave didn't seem to do anything. no prompt. What's interesting is that it actually did work right after I installed it.

Re: osx 10.15.5 - FAHControl will not connect to localhost

Posted: Fri Jul 10, 2020 4:06 am
by bruce
We probably should try to contact calxalot.

Re: osx 10.15.5 - FAHControl will not connect to localhost

Posted: Sat Jul 11, 2020 3:25 am
by calxalot
I would guess that you altered the allow/deny IP address settings. You should make sure that 127.0.0.1 is in all allow lists. You need to stop the client service before editing config.xml, which you should not do unless you absolutely have to. Make sure that config.xml is owned by user nobody after editing it, and before restarting the service.

Re: osx 10.15.5 - FAHControl will not connect to localhost

Posted: Sat Jul 11, 2020 5:44 am
by nleco
calxalot wrote:I would guess that you altered the allow/deny IP address settings. You should make sure that 127.0.0.1 is in all allow lists. You need to stop the client service before editing config.xml, which you should not do unless you absolutely have to. Make sure that config.xml is owned by user nobody after editing it, and before restarting the service.
That was exactly what happened and it slipped my mind. It was set to my LAN's address vs 127.0.0.1. This resolved it.

thank you so much.