fails to configure because statd.service is missing

Bug #1398508 reported by Norbert Kiesel
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
Expired
High
Unassigned
Vivid
Expired
High
Unassigned

Bug Description

I use systemd (all from Ubuntu packages), and nfs-common fails to configure. root cause is
# sh -x /var/lib/dpkg/info/nfs-common.postinst configure
+ set -e
+ ucf --three-way /usr/share/nfs-common/conffiles/idmapd.conf /etc/idmapd.conf
+ ucf --three-way /usr/share/nfs-common/conffiles/nfs-common.default /etc/default/nfs-common
+ getent passwd statd
+ dpkg --compare-versions ge 1:1.0.7-10
+ chown statd: /var/lib/nfs/sm /var/lib/nfs/sm.bak /var/lib/nfs
+ [ -f /var/lib/nfs/state ]
+ chown statd /var/lib/nfs/state
+ [ != ]
+ dpkg --compare-versions lt 1:1.1.0-14
+ dpkg-statoverride --list /sbin/mount.nfs
+ dpkg --compare-versions lt-nl 1:1.2.0-2ubuntu1
+ dpkg --compare-versions lt-nl 1:1.2.4-1ubuntu3
+ [ -f /lib/init/rw/sendsigs.omit.d/statd ]
+ [ -x /etc/init.d/statd ]
+ [ -x /etc/init.d/statd ]
+ [ -e /etc/init/statd.conf ]
+ [ -n ]
+ _dh_action=start
+ invoke-rc.d statd start
Failed to issue method call: Unit statd.service failed to load: No such file or directory.
invoke-rc.d: initscript statd, action "start" failed.
+ exit 6

I do not have /etc/init.d/statd, but i do have /etc/init/statd.conf (which came from nfs-common itself).

I "fixed" this by changing || to && in the following line of nfs-common.postinst:

if [ -x "/etc/init.d/statd" ] || [ -e "/etc/init/statd.conf" ]; then

Same fix twice more for gssd and idmapd

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: nfs-common 1:1.2.8-9ubuntu1.1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 2 11:07:43 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-02-04 (1032 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to utopic on 2014-09-27 (66 days ago)

Revision history for this message
Norbert Kiesel (nk-iname) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Yes. This is on the list of packages requiring porting this cycle for systemd, available here:
http://people.canonical.com/~jhunt/systemd/packages-to-convert/

Changed in nfs-utils (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Brian Murray (brian-murray) wrote :

It looks to me like this will have been fixed by one of these uploads. Can you confirm?

nfs-utils (1:1.2.8-9ubuntu6) vivid; urgency=medium

  * Revert previous upload; per upstream, rpc.idmapd is not used when the
    nfsidmap utility is available and configured for use in request-key
    upcalls. So rpc.idmapd does not need to be started on clients anymore.

 -- Steve Langasek <email address hidden> Fri, 06 Mar 2015 10:19:57 -0800

nfs-utils (1:1.2.8-9ubuntu5) vivid; urgency=medium

  * Add 27-systemd-start-nfs-idmapd-also-on-clients.patch: idmapd is needed
    for clients too, so start it from nfs-client.target and stop binding to it
    in nfs-server.service. (LP: #1428961)

 -- Martin Pitt <email address hidden> Fri, 06 Mar 2015 11:56:46 +0100

nfs-utils (1:1.2.8-9ubuntu4) vivid; urgency=medium

  * Add autopkgtest for installing server and client on localhost, setting up
    two exports, rebooting, and ensuring that the NFS mounts work.
  * Add 23-systemd-relax-dependencies.patch: Stop depending on basic.target in
    the daemons which still do; i. e. add DefaultDependencies=no. This makes
    it possible to run NFS during early boot, helps if you e. g. have /var
    on NFS, and avoids dependency cycles with rcS init.d scripts which depend
    on $remote_fs. (LP: #1428487)
  * Shift number prefixes of other systemd patches accordingly, and adjust
    them to the above patch.

 -- Martin Pitt <email address hidden> Thu, 05 Mar 2015 10:43:54 +0100

nfs-utils (1:1.2.8-9ubuntu3) vivid; urgency=medium

  * Add 00git-start-statd-systemd.patch: Latest start-statd script from
    1.3.2 to start rpc-statd.service under systemd.
  * Add 23-systemd-pipefs_in_run.patch: systemd: Mount rpc_pipefs in /run instead of
    /var/lib/nfs/, like in the upstart units.
  * Add 24-systemd-daemon-paths.patch: Adjust program paths in systemd units.
  * debian/nfs-kernel-server.links: Add nfs-kernel-server.service alias
    symlink, to match SysV init script.
  * Add 25-systemd-server-before-client.patch: Order NFS server before client,
    to make mounting NFS shares from localhost work reliably.
  * Add debian/nfs-utils_env.sh: Translate our /etc/default files into runtime
    configuration for nfs-config.service.
  * debian/nfs-{common,kernel-server}.install: Install systemd units.
  * debian/rules: Enable/start systemd units. (LP: #1312976)

 -- Martin Pitt <email address hidden> Thu, 05 Mar 2015 07:46:41 +0100

Changed in nfs-utils (Ubuntu Vivid):
status: Triaged → Incomplete
Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 1398508] Re: fails to configure because statd.service is missing

On Wed, Mar 25, 2015 at 10:17:26PM -0000, Brian Murray wrote:
> It looks to me like this will have been fixed by one of these uploads.
> Can you confirm?

Unfortunately not. I purged systemd and went back to upstart after encountering
a persistent segfaulting bug. Basically systemd would segfault, do some sort of
odd recovery to avoid a kernel panic, and not respond to anything until a
reboot.

--
Kind regards,
Loong Jin

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nfs-utils (Ubuntu) because there has been no activity for 60 days.]

Changed in nfs-utils (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nfs-utils (Ubuntu Vivid) because there has been no activity for 60 days.]

Changed in nfs-utils (Ubuntu Vivid):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.