web/control does not show any activity on system-d-less OS
Moderators: Site Moderators, FAHC Science Team
web/control does not show any activity on system-d-less OS
Hello ,
i have several computer running OS Linux without system-d.
when on those go to
https://v8-4.foldingathome.org/machines
there is shown the correct count of "machines"
however GPU and CPU is showing 0 and no folding activity, although it is folding as shown on other pc.
why is that so?
https://ibb.co/LDqbqVQz
i have several computer running OS Linux without system-d.
when on those go to
https://v8-4.foldingathome.org/machines
there is shown the correct count of "machines"
however GPU and CPU is showing 0 and no folding activity, although it is folding as shown on other pc.
why is that so?
https://ibb.co/LDqbqVQz
-
- Site Moderator
- Posts: 1554
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: web/control does not show any activity on system-d-less OS
You will need to build 8.4.9 yourself on a machine without systemd.
https://github.com/FoldingAtHome/fah-cl ... /README.md
The installer package won’t work either because it assumes systemd.
https://github.com/FoldingAtHome/fah-cl ... /README.md
The installer package won’t work either because it assumes systemd.
Re: web/control does not show any activity on system-d-less OS
thanks, issue is that i don't have the package installed ,
but am logged into the browser with correct credentials and just want to consult the progress.
do you say i need to install the fahclient in order to be able to correctly retrieve the webdata?
on another computer (with kubuntu, reliant on system-d) , which also has the fahclient not installed, i am correctly able to retrieve the progress-data via webbrowser.
but am logged into the browser with correct credentials and just want to consult the progress.
do you say i need to install the fahclient in order to be able to correctly retrieve the webdata?
on another computer (with kubuntu, reliant on system-d) , which also has the fahclient not installed, i am correctly able to retrieve the progress-data via webbrowser.
-
- Site Moderator
- Posts: 1554
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: web/control does not show any activity on system-d-less OS
You don’t need to install. You just need to have the client running with your account-token in the config.xml in the current working directory of the client.
-
- Site Moderator
- Posts: 1554
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: web/control does not show any activity on system-d-less OS
I don’t think the downloaded client will run without the linked systemd libs.
-
- Posts: 144
- Joined: Wed Aug 08, 2012 3:08 am
Re: web/control does not show any activity on system-d-less OS
You don't need systemd with the tarball
And it will run from the terminal, without being installed as a service... If I remember correctly you don't even need to be a sudoer with the tarball install.
Code: Select all
wget https://download.foldingathome.org/releases/public/fah-client/debian-10-64bit/release/fah-client_8.4.9-64bit-release.tar.bz2
tar xf fah-client_8.4.9-64bit-release.tar.bz2
cd fah-client_8.4.9-64bit-release
./fah-client --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/ --account-token=YOURACCOUNTTOKEN --machine-name="YOURRIGNAME" --user=YOURUSERNAME --team=YOURTEAMNUMBER --passkey=YOURPASSKEY
MSI Z77A-GD55 - Core i5-3550 - Inno3D RTX 5080 - Ubuntu 25.04 - 6.14 kernel - 570.133
MSI MPG B550 - Ryzen 5 5600X - PNY RTX 4080 Super - Ubuntu 25.04 - 6.14 kernel - 570.169
MSI MPG B550 - Ryzen 5 5600X - PNY RTX 4080 Super - Ubuntu 25.04 - 6.14 kernel - 570.169
-
- Site Moderator
- Posts: 1554
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: web/control does not show any activity on system-d-less OS
Have you tested the tarball without systemd?
My understanding is that the client is hard linked to one or two libs, such as libsystemd-login
My understanding is that the client is hard linked to one or two libs, such as libsystemd-login
-
- Posts: 144
- Joined: Wed Aug 08, 2012 3:08 am
Re: web/control does not show any activity on system-d-less OS
It works on vast.ai that has no systemd available (to my knowledge). Let's see if it works for nada391...
Re: web/control does not show any activity on system-d-less OS
hello ,Nicolas_orleans wrote: ↑Mon Jul 28, 2025 8:05 pm You don't need systemd with the tarballAnd it will run from the terminal, without being installed as a service... If I remember correctly you don't even need to be a sudoer with the tarball install.Code: Select all
wget https://download.foldingathome.org/releases/public/fah-client/debian-10-64bit/release/fah-client_8.4.9-64bit-release.tar.bz2 tar xf fah-client_8.4.9-64bit-release.tar.bz2 cd fah-client_8.4.9-64bit-release ./fah-client --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/ --account-token=YOURACCOUNTTOKEN --machine-name="YOURRIGNAME" --user=YOURUSERNAME --team=YOURTEAMNUMBER --passkey=YOURPASSKEY
tried this, bit cumbersome, since am already aloggid in with the webbrowser, via email/password.
now it simply showed up another machine (the current laptop), but the other ones that are folding are not being shown with the current activity.
https://ibb.co/LXWt2frh
Code: Select all
05:12:56:I1:****************************** CBang ******************************
05:12:56:I1: Version: 1.7.2
05:12:56:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
05:12:56:I1: Org: Cauldron Development
05:12:56:I1: Copyright: Cauldron Development, 2003-2024
05:12:56:I1: Homepage: https://cauldrondevelopment.com/
05:12:56:I1: License: LGPL-2.1-or-later
05:12:56:I1: Date: Nov 19 2024
05:12:56:I1: Time: 21:54:38
05:12:56:I1: Revision: 443c54e909eb8d8994405a18fb328b5b05a623a5
05:12:56:I1: Branch: master
05:12:56:I1: Compiler: GNU 8.3.0
05:12:56:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char
05:12:56:I1: -ffunction-sections -fdata-sections -O3 -funroll-loops -fno-pie
05:12:56:I1: -fPIC
05:12:56:I1: Platform: linux 4.19.0-27-cloud-amd64
05:12:56:I1: Bits: 64
05:12:56:I1: Mode: Release
05:12:56:I1:***************************** System ******************************
05:12:56:I1: CPU: AMD PRO A12-8830B R7, 10 COMPUTE CORES 4C+6G
05:12:56:I1: CPU ID: AuthenticAMD Family 21 Model 101 Stepping 1
05:12:56:I1: CPUs: 4
05:12:56:I1: Memory: 14.55GiB
05:12:56:I1:Free Memory: 7.56GiB
05:12:56:I1: OS Version: 6.1
05:12:56:I1:Has Battery: true
05:12:56:I1: On Battery: false
05:12:56:I1: Hostname: devuan
05:12:56:I1: UTC Offset: 2
05:12:56:I1: PID: 28345
05:12:56:I1: CWD: /home/rich/fah-client_8.4.9-64bit-release
05:12:56:I1: Exec: /home/rich/fah-client_8.4.9-64bit-release/fah-client
05:12:56:I1:*******************************************************************
05:12:56:I2:<config/>
05:12:56:I1:Opening Database
05:12:56:E :Exception: Machine ID not available
05:12:56:I1:Generating RSA key.............................++++-..........++++-
05:12:57:I1:F@H ID = iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ
05:12:57:I3:Loading default resource group
05:12:57:I1:Listening for HTTP on 127.0.0.1:7396
05:12:57:I3:Loaded 0 wus.
05:12:57:I1:OUT1:> PUT https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:12:57:I1:OUT2:> GET https://api.foldingathome.org/gpus HTTP/1.1
05:12:58:I1:OUT1:< HTTP/1.1 200 HTTP_OK
05:12:58:I1:Account linked
05:12:58:I1:OUT3:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:12:59:I1:OUT3:< HTTP/1.1 200 HTTP_OK
05:12:59:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:00:I1:OUT2:< HTTP/1.1 200 HTTP_OK
05:13:00:I3:gpus = {
05:13:00:I3: "gpu:00:01:00": {"vendor": 4098, "device": 39028, "type": "amd", "supported": false, "description": "Carrizo [Radeon R5/R6/R7 Series]"}
05:13:00:I3:}
05:13:00:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:00:I1:Logging into node account
05:13:01:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:01:I1:OUT6:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:02:I1:OUT6:< HTTP/1.1 200 HTTP_OK
05:13:02:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:03:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:03:I1:Logging into node account
05:13:03:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:03:I1:OUT7:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:05:I1:OUT7:< HTTP/1.1 200 HTTP_OK
05:13:05:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:06:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:06:I1:Logging into node account
05:13:06:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:06:I1:OUT8:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:07:I1:OUT8:< HTTP/1.1 200 HTTP_OK
05:13:07:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:08:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:08:I1:Logging into node account
05:13:09:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:09:I1:OUT9:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:10:I1:OUT9:< HTTP/1.1 200 HTTP_OK
05:13:10:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:11:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:11:I1:Logging into node account
05:13:11:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:11:I1:OUT10:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:13:I1:OUT10:< HTTP/1.1 200 HTTP_OK
05:13:13:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:13:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:13:I1:Logging into node account
05:13:14:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:14:I1:OUT11:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:15:I1:OUT11:< HTTP/1.1 200 HTTP_OK
05:13:15:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:16:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:16:I1:Logging into node account
05:13:16:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:17:I1:OUT12:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:18:I1:OUT12:< HTTP/1.1 200 HTTP_OK
05:13:18:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:19:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:19:I1:Logging into node account
05:13:19:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:19:I1:OUT13:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:20:I1:OUT13:< HTTP/1.1 200 HTTP_OK
05:13:20:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:21:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:21:I1:Logging into node account
05:13:22:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:22:I1:OUT14:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:23:I1:OUT14:< HTTP/1.1 200 HTTP_OK
05:13:23:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:24:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:24:I1:Logging into node account
05:13:24:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:24:I1:OUT15:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:25:I1:OUT15:< HTTP/1.1 200 HTTP_OK
05:13:25:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:26:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:26:I1:Logging into node account
05:13:27:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:27:I1:OUT16:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:28:I1:OUT16:< HTTP/1.1 200 HTTP_OK
05:13:28:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:29:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:29:I1:Logging into node account
05:13:29:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:29:I1:OUT17:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:31:I1:OUT17:< HTTP/1.1 200 HTTP_OK
05:13:31:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:31:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:31:I1:Logging into node account
05:13:32:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:32:I1:OUT18:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:33:I1:OUT18:< HTTP/1.1 200 HTTP_OK
05:13:33:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:34:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:34:I1:Logging into node account
05:13:34:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:34:I1:OUT19:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:36:I1:OUT19:< HTTP/1.1 200 HTTP_OK
05:13:36:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:36:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:36:I1:Logging into node account
05:13:37:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:37:I1:OUT20:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:38:I1:OUT20:< HTTP/1.1 200 HTTP_OK
05:13:38:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:39:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:39:I1:Logging into node account
05:13:39:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:40:I1:OUT21:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:41:I1:OUT21:< HTTP/1.1 200 HTTP_OK
05:13:41:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:42:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:42:I1:Logging into node account
05:13:42:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:42:I1:OUT22:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:43:I1:OUT22:< HTTP/1.1 200 HTTP_OK
05:13:44:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:44:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:44:I1:Logging into node account
05:13:45:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:45:I1:OUT23:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:46:I1:OUT23:< HTTP/1.1 200 HTTP_OK
05:13:46:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:47:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:47:I1:Logging into node account
05:13:47:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:47:I1:OUT24:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:49:I1:OUT24:< HTTP/1.1 200 HTTP_OK
05:13:49:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:49:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:49:I1:Logging into node account
05:13:50:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:50:I1:OUT25:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:51:I1:OUT25:< HTTP/1.1 200 HTTP_OK
05:13:51:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:52:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:52:I1:Logging into node account
05:13:53:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:53:I1:OUT26:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:54:I1:OUT26:< HTTP/1.1 200 HTTP_OK
05:13:54:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:55:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:55:I1:Logging into node account
05:13:55:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:55:I1:OUT27:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:57:I1:OUT27:< HTTP/1.1 200 HTTP_OK
05:13:57:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:13:58:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:13:58:I1:Logging into node account
05:13:58:I1:Account websocket closed: UNACCEPTABLE msg=
05:13:58:I1:OUT28:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:13:59:I1:OUT28:< HTTP/1.1 200 HTTP_OK
05:13:59:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:00:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:00:I1:Logging into node account
05:14:01:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:01:I1:OUT29:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:02:I1:OUT29:< HTTP/1.1 200 HTTP_OK
05:14:02:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:03:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:03:I1:Logging into node account
05:14:03:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:04:I1:OUT30:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:05:I1:OUT30:< HTTP/1.1 200 HTTP_OK
05:14:05:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:06:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:06:I1:Logging into node account
05:14:06:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:06:I1:OUT31:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:07:I1:OUT31:< HTTP/1.1 200 HTTP_OK
05:14:08:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:08:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:08:I1:Logging into node account
05:14:09:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:09:I1:OUT32:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:10:I1:OUT32:< HTTP/1.1 200 HTTP_OK
05:14:10:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:11:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:11:I1:Logging into node account
05:14:11:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:12:I1:OUT33:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:13:I1:OUT33:< HTTP/1.1 200 HTTP_OK
05:14:13:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:14:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:14:I1:Logging into node account
05:14:14:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:14:I1:OUT34:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:16:I1:OUT34:< HTTP/1.1 200 HTTP_OK
05:14:16:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:16:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:16:I1:Logging into node account
05:14:17:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:17:I1:OUT35:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:18:I1:OUT35:< HTTP/1.1 200 HTTP_OK
05:14:18:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:19:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:19:I1:Logging into node account
05:14:20:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:20:I1:OUT36:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:21:I1:OUT36:< HTTP/1.1 200 HTTP_OK
05:14:21:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:22:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:22:I1:Logging into node account
05:14:22:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:22:I1:OUT37:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:24:I1:OUT37:< HTTP/1.1 200 HTTP_OK
05:14:24:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:25:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:25:I1:Logging into node account
05:14:25:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:25:I1:OUT38:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:26:I1:OUT38:< HTTP/1.1 200 HTTP_OK
05:14:26:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:27:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:27:I1:Logging into node account
05:14:28:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:28:I1:OUT39:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:29:I1:OUT39:< HTTP/1.1 200 HTTP_OK
05:14:29:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:30:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:30:I1:Logging into node account
05:14:30:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:30:I1:OUT40:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:32:I1:OUT40:< HTTP/1.1 200 HTTP_OK
05:14:32:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:32:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:32:I1:Logging into node account
05:14:33:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:33:I1:OUT41:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:34:I1:OUT41:< HTTP/1.1 200 HTTP_OK
05:14:34:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:35:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:35:I1:Logging into node account
05:14:36:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:36:I1:OUT42:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:37:I1:OUT42:< HTTP/1.1 200 HTTP_OK
05:14:37:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:38:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:38:I1:Logging into node account
05:14:38:I1:Account websocket closed: UNACCEPTABLE msg=
05:14:38:I1:OUT43:> GET https://api.foldingathome.org/machine/iYLptPY36ZPoonwxjkWA03TBgvyPjA3ypXpyB5FassQ HTTP/1.1
05:14:40:I1:OUT43:< HTTP/1.1 200 HTTP_OK
05:14:40:I1:OUT5:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
05:14:40:I1:OUT5:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
05:14:40:I1:Logging into node account
05:14:41:I1:Account websocket closed: UNACCEPTABLE msg=
^C05:14:41:I1:Clean exit
Last edited by nada391 on Tue Jul 29, 2025 7:52 am, edited 2 times in total.
Re: web/control does not show any activity on system-d-less OS
the webview could not read the data from the other computer that are folding although i am logged in with correct credentials, which consider bit strange, but maybe we can solve this riddl.e
-
- Posts: 144
- Joined: Wed Aug 08, 2012 3:08 am
Re: web/control does not show any activity on system-d-less OS
The log shows that the client is using the tarball folder, as intended, and the screenshot shows that you have a machine ready to fold. Please press fold so we know if it is working without systemd (your initial question)
Then, if you cannot see your other rigs, it could mean something is wrong with your credentials or token, but it's another issue
Then, if you cannot see your other rigs, it could mean something is wrong with your credentials or token, but it's another issue
MSI Z77A-GD55 - Core i5-3550 - Inno3D RTX 5080 - Ubuntu 25.04 - 6.14 kernel - 570.133
MSI MPG B550 - Ryzen 5 5600X - PNY RTX 4080 Super - Ubuntu 25.04 - 6.14 kernel - 570.169
MSI MPG B550 - Ryzen 5 5600X - PNY RTX 4080 Super - Ubuntu 25.04 - 6.14 kernel - 570.169
Re: web/control does not show any activity on system-d-less OS
yeh, the whole point of the exercise , is that i'd like to check on progress of the fah-folding
without the need to install fahclient on every computer in order to so;
since i am logged in correctly, don't see how i could easily mess up the credentials;
but as far i know, have not changed the passkey or token even inadvertently lately.
Either the non-system-d is mssing some features that prevents the retrieval of the data, or there is some flaw;
to my knowledge, on System-D Linux am able to retrieve the data correctly without needing to install the client;
without the need to install fahclient on every computer in order to so;
since i am logged in correctly, don't see how i could easily mess up the credentials;
but as far i know, have not changed the passkey or token even inadvertently lately.
Either the non-system-d is mssing some features that prevents the retrieval of the data, or there is some flaw;
to my knowledge, on System-D Linux am able to retrieve the data correctly without needing to install the client;