Not sure the client's running

If you're new to FAH and need help getting started or you have very basic questions, start here.

Moderators: Site Moderators, FAHC Science Team

Paul_M
Posts: 8
Joined: Tue May 27, 2025 6:15 pm

Re: Not sure the client's running

Post by Paul_M »

There is something in the console app showing fah errors...
2025-11-23 13:52:09.196235 (system/org.foldingathome.fahclient) <Notice>: service state: spawning
2025-11-23 13:52:09.196281 (system/org.foldingathome.fahclient) <Notice>: launching: semaphore
2025-11-23 13:52:09.198753 (system/org.foldingathome.fahclient [27967]) <Notice>: xpcproxy spawned with pid 27967
2025-11-23 13:52:09.198775 (system/org.foldingathome.fahclient [27967]) <Notice>: internal event: SPAWNED, code = 0
2025-11-23 13:52:09.198779 (system/org.foldingathome.fahclient [27967]) <Notice>: service state: xpcproxy
2025-11-23 13:52:09.198783 (system/org.foldingathome.fahclient [27967]) <Notice>: deferred event: domain spawn response: 0
2025-11-23 13:52:09.198788 (system/org.foldingathome.fahclient [27967]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2025-11-23 13:52:09.211862 (system/org.foldingathome.fahclient [27967]) <Notice>: service state: running
2025-11-23 13:52:09.211877 (system/org.foldingathome.fahclient [27967]) <Notice>: internal event: INIT, code = 0
2025-11-23 13:52:09.211886 (system/org.foldingathome.fahclient [27967]) <Notice>: Successfully spawned fah-client[27967] because semaphore
2025-11-23 13:52:09.223877 (pid/27967 [fah-client]) <Notice>: uncorking exec source upfront
2025-11-23 13:52:09.223910 (pid/27967 [fah-client]) <Notice>: created
2025-11-23 13:52:09.388381 (system/org.foldingathome.fahclient [27967]) <Notice>: exited due to exit(1), ran for 191ms
2025-11-23 13:52:09.388405 (system/org.foldingathome.fahclient [27967]) <Notice>: service state: exited
2025-11-23 13:52:09.388414 (system/org.foldingathome.fahclient [27967]) <Notice>: internal event: EXITED, code = 0
2025-11-23 13:52:09.388419 (system) <Notice>: service inactive: org.foldingathome.fahclient
2025-11-23 13:52:09.388448 (system/org.foldingathome.fahclient [27967]) <Notice>: service state: not running
2025-11-23 13:52:09.388455 (system/org.foldingathome.fahclient) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
2025-11-23 13:52:09.388542 (system/org.foldingathome.fahclient) <Notice>: internal event: WILL_SPAWN, code = 0
2025-11-23 13:52:09.388548 (system/org.foldingathome.fahclient) <Notice>: service state: spawn scheduled
2025-11-23 13:52:09.388552 (system/org.foldingathome.fahclient) <Notice>: service spawn deferred by 10 seconds due to throttle
2025-11-23 13:52:09.388563 (pid/27967 [fah-client]) <Notice>: shutting down
2025-11-23 13:52:09.388570 (pid/27967 [fah-client]) <Notice>: cleaning up

That's just a small excerpt - no idea what it means...
calxalot
Site Moderator
Posts: 1709
Joined: Sat Dec 08, 2007 1:33 am
Location: San Francisco, CA
Contact:

Re: Not sure the client's running

Post by calxalot »

Are you using http/https proxies?
Paul_M
Posts: 8
Joined: Tue May 27, 2025 6:15 pm

Re: Not sure the client's running

Post by Paul_M »

I'm not sure what that means.
The browser is pointing at https...
That console dump appears to suggest that the service is starting and running for a fraction of a second and then stopping...
calxalot
Site Moderator
Posts: 1709
Joined: Sat Dec 08, 2007 1:33 am
Location: San Francisco, CA
Contact:

Re: Not sure the client's running

Post by calxalot »

Is the client log.txt empty?
calxalot
Site Moderator
Posts: 1709
Joined: Sat Dec 08, 2007 1:33 am
Location: San Francisco, CA
Contact:

Re: Not sure the client's running

Post by calxalot »

After a little searching, it seems xpcproxy is possibly both a part of macOS security and a bit of adware installed in multiple browsers.
jonault
Posts: 224
Joined: Fri Dec 14, 2007 9:53 pm

Re: Not sure the client's running

Post by jonault »

I see that same notice about xpcproxy in launchd.log when fahclient starts. It's definitely part of MacOS, in /usr/libexec.
Image
jonault
Posts: 224
Joined: Fri Dec 14, 2007 9:53 pm

Re: Not sure the client's running

Post by jonault »

One thing that's different - I don't see that message about "deferred event: domain spawn response"; instead a couple lines down I see "job state = running". I did have a work unit already in progress that I stopped & restarted, though, so maybe that would explain the difference.

2025-11-24 20:13:06.736510 (system/org.foldingathome.fahclient [10535]) <Notice>: xpcproxy spawned with pid 10535
2025-11-24 20:13:06.736550 (system/org.foldingathome.fahclient [10535]) <Notice>: internal event: SPAWNED, code = 0
2025-11-24 20:13:06.736553 (system/org.foldingathome.fahclient [10535]) <Notice>: service state: xpcproxy
2025-11-24 20:13:06.736621 (system/org.foldingathome.fahclient [10535]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2025-11-24 20:13:06.749954 (system/org.foldingathome.fahclient [10535]) <Notice>: service state: running
2025-11-24 20:13:06.749971 (system/org.foldingathome.fahclient [10535]) <Notice>: internal event: INIT, code = 0
2025-11-24 20:13:06.749975 (system/org.foldingathome.fahclient [10535]) <Notice>: job state = running
2025-11-24 20:13:06.749989 (system/org.foldingathome.fahclient [10535]) <Notice>: Successfully spawned fah-client[10535] because one-shot
2025-11-24 20:13:06.759326 (pid/10535 [fah-client]) <Notice>: uncorking exec source upfront
2025-11-24 20:13:06.759353 (pid/10535 [fah-client]) <Notice>: created
Image
Post Reply