gestern habe ich eine sehr umfangreiche Softwareaktualisierung durchgeführt (fast 2.000 Pakete). Seitdem habe ich keinen Zugriff mehr auf meine NFS Verbindungen. Ich kann auch keine NFS Dienste starten. Ich habe erst mal ein Rollback durchgeführt. Habt Ihr eine Idee, woran es liegen kann?
# journalctl -b 0 --output=short-monotonic --no-hostname | grep -iE 'nfs|autof'
10.798770] systemd[1]: Mounting NFSD configuration filesystem...
10.983823] systemd[1]: nfs-server.service: Found ordering cycle on NAS\x2dHomes.mount/start
10.983931] systemd[1]: nfs-server.service: Found dependency on nfs-server.service/start
10.984014] systemd[1]: nfs-server.service: Job NAS\x2dHomes.mount/start deleted to break ordering cycle starting with nfs-server.service/start
11.148765] kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
11.375475] systemd[1]: Mounted NFSD configuration filesystem.
11.373527] kernel: Installing knfsd (copyright (C) 1996 [email]okir@monad.swb.de[/email]).
24.238065] systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
24.461175] systemd[1]: Starting NFSv4 Client Tracking Daemon...
24.461301] systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
24.578509] systemd[1]: Started NFSv4 Client Tracking Daemon.
42.128994] systemd[1]: Starting Notify NFS peers of a restart...
42.129922] systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
42.175104] mount[1719]: mount.nfs: Failed to resolve server NASvokapod.fritz.box: Name or service not known
42.175504] mount[1717]: mount.nfs: Failed to resolve server NASvokapod.fritz.box: Name or service not known
42.192398] systemd[1]: Started Notify NFS peers of a restart.
42.256706] systemd[1]: Started NFS status monitor for NFSv2/3 locking..
1344.161388] kernel: FS-Cache: Netfs 'nfs' registered for caching
1344.341176] kernel: NFS: Registering the id_resolver key type
# systemctl list-unit-files | grep -iE 'nfs|autof'
proc-fs-nfsd.mount static -
var-lib-nfs-rpc_pipefs.mount static -
autofs.service enabled disabled
nfs-blkmap.service disabled disabled
nfs-idmapd.service static -
nfs-mountd.service static -
nfs-server.service enabled disabled
nfs-utils.service static -
nfsdcld.service static -
nfs-client.target disabled disabled
localhost:~ # systemctl status nfs.service nfs-server.service autofs.service
Unit nfs.service could not be found.
○ nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/nfs-server.service.d
└─options.conf
/run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: inactive (dead)
Mar 06 10:30:58 localhost systemd[1]: nfs-server.service: Found ordering cycle on NAS\x2dHomes.mount/start
Mar 06 10:30:58 localhost systemd[1]: nfs-server.service: Found dependency on nfs-server.service/start
Mar 06 10:30:58 localhost systemd[1]: nfs-server.service: Job NAS\x2dHomes.mount/start deleted to break ordering cycle start>
Mar 06 11:17:19 localhost.localdomain systemd[1]: nfs-server.service: Found ordering cycle on NAS\x2dHomes.mount/start
Mar 06 11:17:19 localhost.localdomain systemd[1]: nfs-server.service: Found dependency on nfs-server.service/start
Mar 06 11:17:19 localhost.localdomain systemd[1]: nfs-server.service: Unable to break cycle starting with nfs-server.service>
Mar 06 11:17:59 localhost.localdomain systemd[1]: nfs-server.service: Found ordering cycle on NAS\x2dHomes.mount/start
Mar 06 11:17:59 localhost.localdomain systemd[1]: nfs-server.service: Found dependency on nfs-server.service/start
Mar 06 11:17:59 localhost.localdomain systemd[1]: nfs-server.service: Unable to break cycle starting with nfs-server.service>
● autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-03-06 10:31:30 CET; 53min ago
Process: 2654 ExecReload=/usr/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Main PID: 1723 (automount)
Tasks: 3 (limit: 4915)
CPU: 31ms
CGroup: /system.slice/autofs.service
└─1723 /usr/sbin/automount --systemd-service --dont-check-daemon
Mar 06 10:31:30 localhost.localdomain systemd[1]: Starting Automounts filesystems on demand...
Mar 06 10:31:30 localhost.localdomain systemd[1]: Started Automounts filesystems on demand.
Mar 06 10:33:38 localhost.localdomain systemd[1]: Reloading Automounts filesystems on demand...
Mar 06 10:33:38 localhost.localdomain systemd[1]: Reloaded Automounts filesystems on demand.
lines 1-33/33 (END)
Normalerweise, NFS verlangt nicht, dass alle Systemuhren synchronisiert sind –
Aber, ich möchte nicht wissen, welche Nebeneffekte auftauchen wenn, die Systemzeiten nicht synchronisiert sind.
Ja, ja, normalerweise „nur” die Zeitstempeln bezüglich Dateien, aber …
boo#1197349, aber ein bisschen voreilig, oder? Ihr habt ja noch nicht einmal an der Oberfläche gekratzt, z.B. das Paket auf die üblichen Verdächtigen eingegrenzt. Da könnt ihr Euch schon ein wenig anstrengen statt Foren-Themen nach Bugzilla kopieren zu lassen.