nfs-ganesha-config.service fails to start due to bad path

[Jason Alavaliant]

The nfs-ganesha package installs the systemd unit file
/lib/systemd/system/nfs-ganesha-config.service

which specifies
ExecStart=/usr/lib/ganesha/nfs-ganesha-config.sh

but no such file is provided by the package so the service fails to start.

The package does install a /usr/lib/nfs-ganesha-config.sh so I'd presume either the file is being installed to the wrong location when the package is being built or the nfs-ganesha-config.service needs it's ExecStart= value corrected.

I'm using bionic/18.04, I've not tested for if the bug is present in other package versions.

[Christian Ehrhardt  (paelzer)]

At least in 20.04 this is:
ExecStart=/bin/bash -c "${NUMACTL} ${NUMAOPTS} /usr/bin/ganesha.nfsd ${OPTIONS} ${EPOCH}"

So lets mark later versions as fixed - I haven't checked details whyn this was changed or if the Bionic report is true.

[Brett Milford (brettmilford)]

I'm seeing this:

May 13 08:51:21 juju-a9d6f4-26-lxd-11 systemd[1]: nfs-ganesha-config.service: Failed to reset devices.list: Operation not permitted
May 13 08:51:21 juju-a9d6f4-26-lxd-11 systemd[1725289]: nfs-ganesha-config.service: Failed to execute command: No such file or directory
May 13 08:51:21 juju-a9d6f4-26-lxd-11 systemd[1725289]: nfs-ganesha-config.service: Failed at step EXEC spawning /usr/lib/ganesha/nfs-ganesha-config.sh: No such file or directory
May 13 08:51:21 juju-a9d6f4-26-lxd-11 systemd[1]: nfs-ganesha-config.service: Main process exited, code=exited, status=203/EXEC
May 13 08:51:21 juju-a9d6f4-26-lxd-11 systemd[1]: nfs-ganesha-config.service: Failed with result 'exit-code'

Package:
nfs-ganesha:
  Installed: 3.0.3-0ubuntu3.1~cloud0
  Candidate: 3.0.3-0ubuntu3.1~cloud0
  Version table:
 *** 3.0.3-0ubuntu3.1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri/main amd64 Packages
        100 /var/lib/dpkg/status
     2.6.0-2 500
        500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages