Your message dated Sat, 14 Sep 2024 09:51:51 +0200 (CEST)
with message-id <20240914075151.983eabe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #860264,
regarding nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to 
resolve ..."
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: normal

The NFS server starts before DNS is working, causing exportfs to fail:

wooledg:~$ sudo systemctl status nfs-kernel-server
[sudo] password for wooledg:
* nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor prese
  Drop-In: /etc/systemd/system/nfs-server.service.d
           `-waitlonger.conf
   Active: active (exited) since Wed 2017-04-12 16:39:29 EDT; 6min ago
 Main PID: 513 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/nfs-server.service

Apr 12 16:39:29 wooledg systemd[1]: Starting NFS server and services...
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase-fla
Apr 12 16:39:29 wooledg systemd[1]: Started NFS server and services.

I attempted to work around this by creating a drop-in unit thing:

wooledg:~$ cat /etc/systemd/system/nfs-server.service.d/waitlonger.conf
[Unit]
Wants= network-online.target
After= network-online.target

But this didn't help.  With or without the drop-in thing, the exportfs
command fails at boot time.  If I login and manually run "exportfs -a"
or restart nfs-kernel-server (or nfs-server), then it's fine.

For now, I'm willing to entertain any kludge workarounds.  This is just
a desktop workstation.  But anyone experiencing this on a server may
want a more robust fix.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp  40904  mountd
    100005    1   tcp  50855  mountd
    100005    2   udp  53578  mountd
    100005    2   tcp  40253  mountd
    100005    3   udp  33327  mountd
    100005    3   tcp  47879  mountd
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    3   udp   2049
    100021    1   udp  56937  nlockmgr
    100021    3   udp  56937  nlockmgr
    100021    4   udp  56937  nlockmgr
    100021    1   tcp  41093  nlockmgr
    100021    3   tcp  41093  nlockmgr
    100021    4   tcp  41093  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/home   ebase(ro,sync,no_subtree_check) ebase-fla(ro,sync,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs
/home   
ebase.eeg.ccf.org(ro,root_squash,sync,wdelay,no_subtree_check,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=1)
/home   
ebase-fla.eeg.ccf.org(ro,root_squash,sync,wdelay,no_subtree_check,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=1)
/       
ebase.eeg.ccf.org(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=390003:390004:390005:1)
/       
ebase-fla.eeg.ccf.org(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=390003:390004:390005:1)

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-kernel-server depends on:
ii  init-system-helpers  1.47
ii  keyutils             1.5.9-9
ii  libblkid1            2.29.2-1
ii  libc6                2.24-9
ii  libcap2              1:2.25-1
ii  libsqlite3-0         3.16.2-3
ii  libtirpc1            0.2.5-1.1
ii  libwrap0             7.6.q-26
ii  lsb-base             9.20161125
ii  netbase              5.4
ii  nfs-common           1:1.3.4-2.1
ii  ucf                  3.0036

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- debconf-show failed

--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore

--- End Message ---

Reply via email to