FS#63446 - [gnunet] starting systemd service fails

Attached to Project: Community Packages
Opened by Louis Holbrook (lash) - Monday, 12 August 2019, 20:02 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 16 June 2021, 12:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Attempting to systemctl start gnunet out of the box fails, as it is set to run as nobody user but nobody's home dir is / by system default.

Additional info:

* Linux sostenuto 5.2.5-arch1-1-ARCH #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019 x86_64 GNU/Linux
* gnunet 0.11.6-1

Steps to reproduce:

systemctl start gnunet then journalctl -u gnunet reported a corresponding error (not permitted).

I created an override with a new user gnunet (home dir, bash as shell). When starting now the log says success, but service still doesn't run - no process and systemctl status gnunet says dead. If I then login as user gnunet and run same command (gnunet-arm -s -c /etc/gnunetd.conf) then it runs fine.

---

log (with user nobody):

# systemctl start gnunet
# journalctl -eu gnunet
Aug 12 21:24:40 amoroso gnunet-arm[2969]: Aug 12 21:24:40-842064 util-2969 WARNING Failed to expand `USERPROFILE' in `${USERPROFILE}/.cache' as it is neither found in [PATHS] nor defined as a>
Aug 12 21:24:40 amoroso systemd[1]: Started A framework for secure peer-to-peer networking.
Aug 12 21:24:40 amoroso gnunet-arm[2969]: Aug 12 21:24:40-852591 util-disk-2972 ERROR `mkdir' failed on file `/${USERPROFILE}' at disk.c:809 with error: Permission denied
Aug 12 21:24:40 amoroso gnunet-arm[2969]: Failed to create directory for `/${USERPROFILE}/.cache/gnunet//gnunet-2019-08-12.log': Permission denied
Aug 12 21:24:40 amoroso gnunet-arm[2969]: Aug 12 21:24:40-853122 arm-2972 ERROR Assertion failed at service.c:2328.
Aug 12 21:24:41 amoroso systemd[1]: gnunet.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 12 21:24:41 amoroso systemd[1]: gnunet.service: Failed with result 'exit-code'.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 16 June 2021, 12:39 GMT
Reason for closing:  Won't fix
Additional comments about closing:  gnunet has been dropped to AUR
Comment by Louis Holbrook (lash) - Monday, 12 August 2019, 20:04 GMT
> and run same command

I realize this is unclear formulation. I mean if I login as gnunet and run the gnunet-arm command directly on the command line, it runs fine.
Comment by andy morris (fruitywelsh) - Tuesday, 24 September 2019, 14:50 GMT
I am running it as a user service. (keeping it in ${HOME}/.config/systemd/user/gnunet.service) and I get no errors. systemctl status works and shows it's "running", that said the basic test of gnunet-arm -I returns nothing. I too can start it with the basic gnunet-arm -s cmd, so I probally just add it to my autostart, but would prefer it a managed service.

Loading...