You are not logged in.
Where on the filesystem does sm-notify cache the list of clients it queries and how can one clear that list? I ask due to a delay in starting nfs-server.service which coincides with a number of entries in journalctl detailing hostnames of VMs that no longer exist. My thought is that if I clear the cache file, I can avoid the delay and multiple entries in journalctl.
I found links to others with this observation and question but no answer. I tried grepping for these hostnames in /var/lib/nfs but got nothing.
...
Nov 17 09:06:14 ease sm-notify[48033]: DNS resolution of vm-audio failed; retrying later
Nov 17 09:06:15 ease sm-notify[48033]: DNS resolution of vm-stockcar failed; retrying later
Nov 17 09:06:16 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:06:16 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:06:40 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:06:48 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:06:48 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:11 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:18 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:18 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:25 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:38 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:49 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:07:49 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:08:09 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:08:15 ease sm-notify[48033]: DNS resolution of vm-audio failed; retrying later
Nov 17 09:08:15 ease sm-notify[48033]: DNS resolution of vm-stockcar failed; retrying later
Nov 17 09:08:19 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:08:19 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:08:40 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:08:51 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:08:51 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
Nov 17 09:09:11 ease systemd-networkd[422]: veth9TTRO4: Failed to save link data to /run/systemd/netif/links/7: Permission denied
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Files
/var/lib/nfs/statd/sm
directory containing monitor list
/var/lib/nfs/statd/sm.bakdirectory containing notify list
/var/lib/nfs/statd/state
NSM state number for this host
/proc/sys/fs/nfs/nsm_local_statekernel's copy of the NSM state number
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
@lone_wolf - I read that but I do not have a statd directory under /var/lib/nfs at all. If I grep each file under /var/lib/nfs for one of those hostnames, I do not find a match. Interestingly, if I delete that entire dirtree, and reinstall nfs-utils, the problem went away. I think that is direct evidence that the offending list is under that dirtree (sqlite perhaps) but the method I used to clear the cache is very blunt-force.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline