I think you need to add
StandardOutput=null
To the service file; otherwise the client logs to both /var/log/foldingathome/log.txt and the journal.
Git Clone URL: | https://aur.archlinux.org/foldingathome.git (read-only, click to copy) |
---|---|
Package Base: | foldingathome |
Description: | A distributed computing project for simulating protein dynamics |
Upstream URL: | https://foldingathome.org/ |
Keywords: | fah science |
Licenses: | GPL-3.0-or-later |
Submitter: | dtw |
Maintainer: | PlasticSoup |
Last Packager: | PlasticSoup |
Votes: | 179 |
Popularity: | 0.26 |
First Submitted: | 2007-06-28 14:55 (UTC) |
Last Updated: | 2024-12-09 00:07 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 23 Next › Last »
I think you need to add
StandardOutput=null
To the service file; otherwise the client logs to both /var/log/foldingathome/log.txt and the journal.
@geripgeri Thought that directory existed even with no graphics card, made it optional.
Hey @jpkotta!
/dev/dri
doesn't exist in my your system, /usr/bin/chown
and /etc/foldingathome
both exist.
After I added ReadWritePaths=-/dev/dri
to foldingathome.service
the service starts without any issue!
Thank you for your help!
@geripgeri: Does /dev/dri
exist on your system? If not, try editing foldingathome.service
to have ReadWritePaths=-/dev/dri
(this should probably be changed in the package, you shouldn't need /dev/dri
if you're doing CPU folding).
As for the chown
, that doesn't make sense. Do /usr/bin/chown
and /etc/foldingathome
both exist?
Hey! I'm getting this error message: The system is up to date. I don't have GPU in this pc, FAH worked for me before.
systemd[1]: Starting Folding@home distributed computing client...
systemd[2846840]: foldingathome.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/dri: No such file or directory
systemd[2846840]: foldingathome.service: Failed at step NAMESPACE spawning /usr/bin/chown: No such file or directory
systemd[1]: foldingathome.service: Control process exited, code=exited, status=226/NAMESPACE
systemd[1]: foldingathome.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Folding@home distributed computing client
What could cause this issue?
@alucryd: I realise I should've tried this before, either way it does not help. Moved back sleep to the main service and re-activated the nvidia one and I ended up having to run startx manually. (as graphical.target wasn't active)
EDIT: It's now happening with only foldingathome.service, so I guess it's the sleep command then, but it used to work before? Computers yo...
@katt: Can you try putting the sleep command back to the foldingathome.service unit?
I've just discovered that with the foldingathome-nvidia service activated, graphical.target stays "inactive (dead)" until I've logged out and back in. This causes problems such as xorg not autostarting (https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login).
This didn't happen a while back so possibly has something to do with the moved sleep command?
Yes, fully updated. After a sudo useradd fah
, the service starts fine.
Correction: I found an /etc/nsswitch.conf.pacnew. My existing /etc/nsswitch.conf didn't allow systemd to control users and groups. I fixed that, removed the manually-created user, and the service started normally.
Pinned Comments
SovietReimu1228 commented on 2024-08-22 14:48 (UTC)
I'll leave a note for those who are having trouble starting FAH after updating. You should do
pacman -Rs foldingathome
and install again. This will create thefah-client
user.