This is all I managed to retrieve from the logs (/var/log/daemons, /var/log/messages):
Mar 12 09:27:20 server mountd[50607]: Socket disconnected Mar 29 18:05:30 server mountd[52162]: Socket disconnected Apr 16 12:04:07 server mountd[66430]: Socket disconnected Apr 17 17:55:26 server mountd[14081]: Socket disconnected No messages from nfsd and portmap. If the logs are true, then mountd is the daemon that is causing problems. The manual says > -d Enable debugging mode. mountd will not detach from the > controlling terminal and will print debugging messages to stderr. The above option does not work, because it detaches from the terminal: > > doas /sbin/mountd -d > Here we go. I tried "mountd_flags=-d" in rc.conf.local, and rebooted the whole OS, because mountd refuses soft restart. As a result, the OS refuses to boot. System crashed. On 18 April 2018 2:47 AM, IL Ka <kazakevichi...@gmail.com> wrote: > You could use ktrace(1) to trace all calls and then use kdump(1) to read > them, and may help you to find what cause it to die, but it may be tricky for > anyone except nfsd developer.. > You can also try to find person who supports it by looking at last commits to: > https://github.com/openbsd/src/blame/master/sbin/nfsd/nfsd.c > and email this person, but I do not know if it will help, or talk to people > on bugs@ list. > > Or you can move to samba/smbd: SMB must have good support in Windows. > > On Wed, Apr 18, 2018 at 2:53 AM, Rupert Gallagher <r...@protonmail.com> wrote: > >>> Do you mean nfsd server dies? >> >> I mean the NFS service as delivered by nfsd, portmap and mountd. >> >>> Does it provide core dump? >> >> No! >> >>> You do not need to restart it >> manually: just create script that checks for server existence (like >> ``/etc/rc.d/nfsd check``) and run it if it is dead. >> I usually prepare my servers from source with custom patches and settings. >> When a server dies on me, it makes a lot of noise in the logs, and it >> happens rarely. In 30+ years of activity, I have never restarted a >> production server because of clients using it! >> >> NFS is an exception. I am using the obsd default, and it dies on me under >> load and without logs. It is unreliable.