wrong paths in systemd units

[Daniel Axtens]

When I try to shut down nfs-ganesha, I see:

Jan 15 06:07:27 a systemd[1]: Stopping NFS-Ganesha file server...
Jan 15 06:07:27 a systemd[15021]: nfs-ganesha.service: Failed at step EXEC spawning /bin/dbus-send: No such file or directory

This is because the unit file /lib/systemd/system/nfs-ganesha.service reads
ExecStop=/bin/dbus-send --system --dest=org.ganesha.nfsd --type=method_call /org/ganesha/nfsd/admin org.ganesha.nfsd.admin.shutdown

The correct path is /usr/bin/dbus-send.

Fixing that causes the issue to go away.

There seem to be other systemd unit issues, but I haven't looked at them yet.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nfs-ganesha 2.4.5-2 [modified: lib/systemd/system/nfs-ganesha.service]
ProcVersionSignature: User Name 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
Date: Mon Jan 15 06:09:55 2018
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: nfs-ganesha
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ganesha.ganesha.conf: [modified]
mtime.conffile..etc.ganesha.ganesha.conf: 2018-01-15T06:07:04.105671

[Daniel Axtens (daxtens)]

Also, in /lib/systemd/system/nfs-ganesha-config.service, nfs-ganesha-config.sh is in /usr/lib, not /usr/libexec.

[Daniel Axtens (daxtens)]

Also, in nfs-ganesha-lock.service:

.include /usr/lib/systemd/system/rpc-statd.service

needs to become

.include /lib/systemd/system/rpc-statd.service

Without this, the server starts but does not work at all.

[Daniel Axtens (daxtens)]

Small correction, even with these changes I cannot get the server to actually serve files.

[windowsguy (something-f)]

Not seeing this problem now, with FSAL VFS it does start (but then it stops due to issues binding to IPV6 interfaces for which there's a fix in upstream).

[windowsguy (something-f)]

Sorry about the spam - I just noticed you saw that on shutdown. Mine can't even start so I don't know whether the problem exists on my system.

[Daniel Axtens (daxtens)]

This all seems to work on Bionic, so closing this issue.