Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #67746 > unrolled thread

Bug#968251: nfs-kernel-server fails to start at boot

Back to article view | Back to linux.debian.kernel

Contents

  Bug#968251: nfs-kernel-server fails to start at boot fireba11 <debian@enlightning.de> - 2020-08-11 21:10 +0200
    Bug#968251: nfs-kernel-server fails to start at boot Salvatore Bonaccorso <carnil@debian.org> - 2020-08-12 08:50 +0200
    Processed (with 1 error): Re: Bug#968251: nfs-kernel-server fails  to start at boot "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-08-12 08:50 +0200
    Bug#968251: nfs-kernel-server fails to start at boot fl4co <fl4co@protonmail.com> - 2020-08-26 16:00 +0200

#67746 — Bug#968251: nfs-kernel-server fails to start at boot

Package: nfs-kernel-server
Version: 1:1.3.4-2.5+deb10u1
Severity: important

Dear Maintainer,

after the last update(s) nfs-kernel-server fails to start since the path to export isn't available yet.
adding a sleep 30 to the unit file works as a workaround ...
naturally starting the service manually after boot works too

it's probably an edge case since i got a large raid 5 with luks on a rather slow CPU so onlocking it takes quite a bit, my guess is the dependencies in the unit file don't work for that case


-- 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
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/srv/path1	 1.2.3.4(rw,async,no_subtree_check) 2.3.4.5(rw,async,no_subtree_check) 3.4.5.6(rw,async,no_subtree_check)
/srv/path2	 1.2.3.4(rw,async,no_subtree_check) 2.3.4.5(rw,async,no_subtree_check) 3.4.5.6(rw,async,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs

-- System Information:
Debian Release: 10.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-10-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-kernel-server depends on:
ii  keyutils      1.6-6
ii  libblkid1     2.33.1-0.1
ii  libc6         2.28-10
ii  libcap2       1:2.25-2
ii  libsqlite3-0  3.27.2-3
ii  libtirpc3     1.1.4-0.4
ii  libwrap0      7.6.q-28
ii  lsb-base      10.2019051400
ii  netbase       5.6
ii  nfs-common    1:1.3.4-2.5+deb10u1
ii  ucf           3.0038+nmu1

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#67751

Control: tags -1 + moreinfo
Control: severity normal

Hi

On Tue, Aug 11, 2020 at 09:01:14PM +0200, fireba11 wrote:
> Package: nfs-kernel-server
> Version: 1:1.3.4-2.5+deb10u1
> Severity: important
> 
> Dear Maintainer,
> 
> after the last update(s) nfs-kernel-server fails to start since the
> path to export isn't available yet.
> adding a sleep 30 to the unit file works as a workaround ...
> naturally starting the service manually after boot works too
> 
> it's probably an edge case since i got a large raid 5 with luks on a
> rather slow CPU so onlocking it takes quite a bit, my guess is the
> dependencies in the unit file don't work for that case

It is unlikely that this is caused by the last update as this was to
fix an issue with the /var/lib/nfs permissions. But could you provide
th bootlog/journal so we might get some information on the respective
timings of the units?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#67752 — Processed (with 1 error): Re: Bug#968251: nfs-kernel-server fails to start at boot

Processing control commands:

> tags -1 + moreinfo
Bug #968251 [nfs-kernel-server] nfs-kernel-server fails to start at boot
Added tag(s) moreinfo.
> severity normal
Unknown command or malformed arguments to command.


-- 
968251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968251
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#67878

[Multipart message — attachments visible in raw view] — view raw

I have the same problem on Raspberry Pi OS 64-bit, which is just the arm64 Debian port with an external repo for the custom kernel and not much more.

The NFS server fails on boot, but can be manually started, if a directory from an external drive is exported. I tried exporting a directory from my home (which is on the SD card) and it exports correctly on boot. Might be the NFS server trying to export a directory before the drive is mounted.

Relevant journal output:

$ journalctl -u nfs-server.service

-- Logs begin at Wed 2020-08-26 15:32:48 CEST, end at Wed 2020-08-26 15:43:50 CEST. --

ago 26 15:32:49 raspi systemd[1]: Starting NFS server and services...

ago 26 15:32:49 raspi exportfs[741]: exportfs: Failed to stat /media/hdd/nfs: No such file or directory

ago 26 15:32:49 raspi systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE

ago 26 15:32:49 raspi systemd[1]: nfs-server.service: Failed with result 'exit-code'.

ago 26 15:32:49 raspi systemd[1]: Stopped NFS server and services.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web