Re: [DNG] NFS rookie mistake?
On 6/1/22 21:04, Ken Dibble wrote: Here is the story: I needed to do some server maintenance so I issued $init 1. After the maintenance was done I issued $init 5. Everything was fine except no nfs-server-kernel running. No problem. Issue $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd Not starting: portmapper is not running ... (warning). Problem to be investigated LATER. Issue $ /etc/init.d/rpcbind restart System response: Stopping RPC port mapper daemon: rpcbind. Starting RPC port mapper daemon: rpcbind. No problem. Try nfs server again. $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd mountd. no problem. So, Now it is LATER. So obviously when I went to runlevel 1, rpcbind was stopped and didn't come back up when I went back to runlevel 5. Investigate: /etc$ sudo find . -name *nfs-kernel-server ./rc2.d/S04nfs-kernel-server ./rc0.d/K01nfs-kernel-server ./rc1.d/K01nfs-kernel-server ./default/nfs-kernel-server ./init.d/nfs-kernel-server ./rc3.d/S04nfs-kernel-server ./rc4.d/S04nfs-kernel-server ./rc6.d/K01nfs-kernel-server ./rc5.d/S04nfs-kernel-server Observation: nfs-kernel-server gets killed at 0,1,6 and gets started at runlevels 2-5 /etc$ sudo find . -name *rpcbind ./rc0.d/K06rpcbind ./rc1.d/K06rpcbind ./rcS.d/S17rpcbind ./default/rpcbind ./init.d/rpcbind ./rc6.d/K06rpcbind ./insserv.conf.d/rpcbind Observation: The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. Conclusion: So either rpcbind shouldn't be killed at runlevel 1 or it should be started prior to nfs-kernel-server on runlevels 2-5. OR . I have no clue about something here. Regards, Ken Reported to Devuan BTS, result follows: Re: bug#680: RPCBind incorrect or incomplete runlevels Control: tag -1 debian Ken, Thanks for this. On Fri, Jun 03, 2022 at 10:45:38AM -0400, Ken Dibble wrote: Package: rpcbind Version: 1.2.5-9 The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. I don't know why the LSB header specifies that either. The oldest version in Debian[1] also has the same header wrt runlevels. src:rpcbind is not a forked package and Devuan uses Debian's packages directly without recompilation. Please report this to Debian's BTS to be addressed. Thanks Mark [1]https://deb.debian.org/debian/pool/main/r/rpcbind/rpcbind_0.2.3-0.6.dsc Reported to Debian BTS on June 7. Thanks for the help. Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] NFS rookie mistake?
No nothing in the logs. That's why I decided to try and restart nfs manually, then discovered the reason it wouldn't start was rpcbind not running. Ken On 6/2/22 17:45, Rod Rodolico via Dng wrote: Is there anything in the logs? Rod On 6/2/22 09:03, Ken Dibble wrote: Thanks for the attempt, but I don't think the situations are related. I am on Chimaera, everything starts normally on reboot, just not on manual runlevel change. Thanks. Ken On 6/1/22 22:53, Rod Rodolico via Dng wrote: Sorry, I pushed the wrong button and did not reply to list. Apologize. Is this related to http://kb.unixservertech.com/start/debugging/linux? Summary: NFS would not start after upgrade to Devuan Beowulf. Appears to be an issue with Debian. Looking in the logs, I saw '/run/rpcbind not owned by root failed' Solution: echo 'PATH="$PATH:/usr/bin"' >> /etc/default/rpcbind Read the (short) article if you want links and a little more info (it is my notes). Rod On 6/1/22 20:04, Ken Dibble wrote: Here is the story: I needed to do some server maintenance so I issued $init 1. After the maintenance was done I issued $init 5. Everything was fine except no nfs-server-kernel running. No problem. Issue $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd Not starting: portmapper is not running ... (warning). Problem to be investigated LATER. Issue $ /etc/init.d/rpcbind restart System response: Stopping RPC port mapper daemon: rpcbind. Starting RPC port mapper daemon: rpcbind. No problem. Try nfs server again. $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd mountd. no problem. So, Now it is LATER. So obviously when I went to runlevel 1, rpcbind was stopped and didn't come back up when I went back to runlevel 5. Investigate: /etc$ sudo find . -name *nfs-kernel-server ./rc2.d/S04nfs-kernel-server ./rc0.d/K01nfs-kernel-server ./rc1.d/K01nfs-kernel-server ./default/nfs-kernel-server ./init.d/nfs-kernel-server ./rc3.d/S04nfs-kernel-server ./rc4.d/S04nfs-kernel-server ./rc6.d/K01nfs-kernel-server ./rc5.d/S04nfs-kernel-server Observation: nfs-kernel-server gets killed at 0,1,6 and gets started at runlevels 2-5 /etc$ sudo find . -name *rpcbind ./rc0.d/K06rpcbind ./rc1.d/K06rpcbind ./rcS.d/S17rpcbind ./default/rpcbind ./init.d/rpcbind ./rc6.d/K06rpcbind ./insserv.conf.d/rpcbind Observation: The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. Conclusion: So either rpcbind shouldn't be killed at runlevel 1 or it should be started prior to nfs-kernel-server on runlevels 2-5. OR . I have no clue about something here. Regards, Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] NFS rookie mistake?
Is there anything in the logs? Rod On 6/2/22 09:03, Ken Dibble wrote: Thanks for the attempt, but I don't think the situations are related. I am on Chimaera, everything starts normally on reboot, just not on manual runlevel change. Thanks. Ken On 6/1/22 22:53, Rod Rodolico via Dng wrote: Sorry, I pushed the wrong button and did not reply to list. Apologize. Is this related to http://kb.unixservertech.com/start/debugging/linux? Summary: NFS would not start after upgrade to Devuan Beowulf. Appears to be an issue with Debian. Looking in the logs, I saw '/run/rpcbind not owned by root failed' Solution: echo 'PATH="$PATH:/usr/bin"' >> /etc/default/rpcbind Read the (short) article if you want links and a little more info (it is my notes). Rod On 6/1/22 20:04, Ken Dibble wrote: Here is the story: I needed to do some server maintenance so I issued $init 1. After the maintenance was done I issued $init 5. Everything was fine except no nfs-server-kernel running. No problem. Issue $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd Not starting: portmapper is not running ... (warning). Problem to be investigated LATER. Issue $ /etc/init.d/rpcbind restart System response: Stopping RPC port mapper daemon: rpcbind. Starting RPC port mapper daemon: rpcbind. No problem. Try nfs server again. $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd mountd. no problem. So, Now it is LATER. So obviously when I went to runlevel 1, rpcbind was stopped and didn't come back up when I went back to runlevel 5. Investigate: /etc$ sudo find . -name *nfs-kernel-server ./rc2.d/S04nfs-kernel-server ./rc0.d/K01nfs-kernel-server ./rc1.d/K01nfs-kernel-server ./default/nfs-kernel-server ./init.d/nfs-kernel-server ./rc3.d/S04nfs-kernel-server ./rc4.d/S04nfs-kernel-server ./rc6.d/K01nfs-kernel-server ./rc5.d/S04nfs-kernel-server Observation: nfs-kernel-server gets killed at 0,1,6 and gets started at runlevels 2-5 /etc$ sudo find . -name *rpcbind ./rc0.d/K06rpcbind ./rc1.d/K06rpcbind ./rcS.d/S17rpcbind ./default/rpcbind ./init.d/rpcbind ./rc6.d/K06rpcbind ./insserv.conf.d/rpcbind Observation: The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. Conclusion: So either rpcbind shouldn't be killed at runlevel 1 or it should be started prior to nfs-kernel-server on runlevels 2-5. OR . I have no clue about something here. Regards, Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 US https://dailydata.net 214.827.2170 ext 100 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] NFS rookie mistake?
Thanks for the attempt, but I don't think the situations are related. I am on Chimaera, everything starts normally on reboot, just not on manual runlevel change. Thanks. Ken On 6/1/22 22:53, Rod Rodolico via Dng wrote: Sorry, I pushed the wrong button and did not reply to list. Apologize. Is this related to http://kb.unixservertech.com/start/debugging/linux? Summary: NFS would not start after upgrade to Devuan Beowulf. Appears to be an issue with Debian. Looking in the logs, I saw '/run/rpcbind not owned by root failed' Solution: echo 'PATH="$PATH:/usr/bin"' >> /etc/default/rpcbind Read the (short) article if you want links and a little more info (it is my notes). Rod On 6/1/22 20:04, Ken Dibble wrote: Here is the story: I needed to do some server maintenance so I issued $init 1. After the maintenance was done I issued $init 5. Everything was fine except no nfs-server-kernel running. No problem. Issue $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd Not starting: portmapper is not running ... (warning). Problem to be investigated LATER. Issue $ /etc/init.d/rpcbind restart System response: Stopping RPC port mapper daemon: rpcbind. Starting RPC port mapper daemon: rpcbind. No problem. Try nfs server again. $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd mountd. no problem. So, Now it is LATER. So obviously when I went to runlevel 1, rpcbind was stopped and didn't come back up when I went back to runlevel 5. Investigate: /etc$ sudo find . -name *nfs-kernel-server ./rc2.d/S04nfs-kernel-server ./rc0.d/K01nfs-kernel-server ./rc1.d/K01nfs-kernel-server ./default/nfs-kernel-server ./init.d/nfs-kernel-server ./rc3.d/S04nfs-kernel-server ./rc4.d/S04nfs-kernel-server ./rc6.d/K01nfs-kernel-server ./rc5.d/S04nfs-kernel-server Observation: nfs-kernel-server gets killed at 0,1,6 and gets started at runlevels 2-5 /etc$ sudo find . -name *rpcbind ./rc0.d/K06rpcbind ./rc1.d/K06rpcbind ./rcS.d/S17rpcbind ./default/rpcbind ./init.d/rpcbind ./rc6.d/K06rpcbind ./insserv.conf.d/rpcbind Observation: The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. Conclusion: So either rpcbind shouldn't be killed at runlevel 1 or it should be started prior to nfs-kernel-server on runlevels 2-5. OR . I have no clue about something here. Regards, Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] NFS rookie mistake?
Sorry, I pushed the wrong button and did not reply to list. Apologize. Is this related to http://kb.unixservertech.com/start/debugging/linux? Summary: NFS would not start after upgrade to Devuan Beowulf. Appears to be an issue with Debian. Looking in the logs, I saw '/run/rpcbind not owned by root failed' Solution: echo 'PATH="$PATH:/usr/bin"' >> /etc/default/rpcbind Read the (short) article if you want links and a little more info (it is my notes). Rod On 6/1/22 20:04, Ken Dibble wrote: Here is the story: I needed to do some server maintenance so I issued $init 1. After the maintenance was done I issued $init 5. Everything was fine except no nfs-server-kernel running. No problem. Issue $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd Not starting: portmapper is not running ... (warning). Problem to be investigated LATER. Issue $ /etc/init.d/rpcbind restart System response: Stopping RPC port mapper daemon: rpcbind. Starting RPC port mapper daemon: rpcbind. No problem. Try nfs server again. $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd mountd. no problem. So, Now it is LATER. So obviously when I went to runlevel 1, rpcbind was stopped and didn't come back up when I went back to runlevel 5. Investigate: /etc$ sudo find . -name *nfs-kernel-server ./rc2.d/S04nfs-kernel-server ./rc0.d/K01nfs-kernel-server ./rc1.d/K01nfs-kernel-server ./default/nfs-kernel-server ./init.d/nfs-kernel-server ./rc3.d/S04nfs-kernel-server ./rc4.d/S04nfs-kernel-server ./rc6.d/K01nfs-kernel-server ./rc5.d/S04nfs-kernel-server Observation: nfs-kernel-server gets killed at 0,1,6 and gets started at runlevels 2-5 /etc$ sudo find . -name *rpcbind ./rc0.d/K06rpcbind ./rc1.d/K06rpcbind ./rcS.d/S17rpcbind ./default/rpcbind ./init.d/rpcbind ./rc6.d/K06rpcbind ./insserv.conf.d/rpcbind Observation: The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. Conclusion: So either rpcbind shouldn't be killed at runlevel 1 or it should be started prior to nfs-kernel-server on runlevels 2-5. OR . I have no clue about something here. Regards, Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 US https://dailydata.net 214.827.2170 ext 100 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] NFS rookie mistake?
Here is the story: I needed to do some server maintenance so I issued $init 1. After the maintenance was done I issued $init 5. Everything was fine except no nfs-server-kernel running. No problem. Issue $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd Not starting: portmapper is not running ... (warning). Problem to be investigated LATER. Issue $ /etc/init.d/rpcbind restart System response: Stopping RPC port mapper daemon: rpcbind. Starting RPC port mapper daemon: rpcbind. No problem. Try nfs server again. $sudo /etc/init.d/nfs-kernel-server restart System response: Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon Starting NFS kernel daemon: nfsd mountd. no problem. So, Now it is LATER. So obviously when I went to runlevel 1, rpcbind was stopped and didn't come back up when I went back to runlevel 5. Investigate: /etc$ sudo find . -name *nfs-kernel-server ./rc2.d/S04nfs-kernel-server ./rc0.d/K01nfs-kernel-server ./rc1.d/K01nfs-kernel-server ./default/nfs-kernel-server ./init.d/nfs-kernel-server ./rc3.d/S04nfs-kernel-server ./rc4.d/S04nfs-kernel-server ./rc6.d/K01nfs-kernel-server ./rc5.d/S04nfs-kernel-server Observation: nfs-kernel-server gets killed at 0,1,6 and gets started at runlevels 2-5 /etc$ sudo find . -name *rpcbind ./rc0.d/K06rpcbind ./rc1.d/K06rpcbind ./rcS.d/S17rpcbind ./default/rpcbind ./init.d/rpcbind ./rc6.d/K06rpcbind ./insserv.conf.d/rpcbind Observation: The only time rpcbind is brought up is at system start. RUNLEVEL 1 kills it. Conclusion: So either rpcbind shouldn't be killed at runlevel 1 or it should be started prior to nfs-kernel-server on runlevels 2-5. OR . I have no clue about something here. Regards, Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
