Markos wrote: > Bob Proulx escreveu: > > 1. Look in /var/log/syslog for any relevant messages. > > After a normal boot I can't see any information related to nfs > on /var/log/syslog > > On Server the command cat /var/log/syslog returns: I didn't see anything relevant in that list. But it was a very short snippet of the full file. I assume that was just the parts you didn't know about. Because the original would be quite long. > Then I created on client (192.168.0.2) a directory /home/home_server > > And after the command on client > > mount -t nfs 192.168.0.1:/home /home/home_servidor You don't need the "-t nfs" part. It seems odd to me to see it there. Shouldn't hurt though. But I think this is the first time I have seen that coupled together. > the /home directory is mounted on client and I can see the messages > on /var/log/syslog > > On Server > > Feb 10 14:52:29 servidor ypserv[1042]: refused connect from 192.168.0.2:50898 to procedure ypproc_match (pimentel.edu,shadow.byname;-1) > Feb 10 14:52:32 servidor ypserv[1042]: refused connect from 192.168.0.2:33712 to procedure ypproc_match (pimentel.edu,shadow.byname;-1) > Feb 10 14:52:32 servidor ypserv[1042]: refused connect from 192.168.0.2:36811 to procedure ypproc_match (pimentel.edu,shadow.byname;-1) Shose are nis/yp errors. For the shadow map. Is nis/yp working okay for you? You said that it was. > Feb 10 14:54:39 servidor mountd[1052]: authenticated mount request from > 192.168.0.2:920 for /home (/home) I think that is a successful notification. > On client > > Feb 10 12:48:11 pc17 kernel: [ 726.729294] RPC: Registered udp transport module. > Feb 10 12:48:11 pc17 kernel: [ 726.729298] RPC: Registered tcp transport module. > Feb 10 12:48:11 pc17 kernel: [ 726.729300] RPC: Registered tcp NFSv4.1 backchannel transport module. > Feb 10 12:48:11 pc17 kernel: [ 726.763223] Slow work thread pool: Starting up > Feb 10 12:48:11 pc17 kernel: [ 726.763278] Slow work thread pool: Ready > Feb 10 12:48:11 pc17 kernel: [ 726.763341] FS-Cache: Loaded > Feb 10 12:48:11 pc17 kernel: [ 726.809331] FS-Cache: Netfs 'nfs' registered for caching > Feb 10 12:48:11 pc17 kernel: [ 726.935870] svc: failed to register lockdv1 RPC service (errno 97). Other than that last message those all look like normal startup notifications. I don't know anything about that last message. > > 2. Change /etc/network/interfaces 'allow-hotplug eth0' to 'auto eth0'. > > The file /etc/network/interfaces on server is: > ... > auto eth0 > iface eth0 inet static > address 192.168.0.1 > netmask 255.255.255.0 No upstream gateway? An isolated machine? Otherwise looks okay. > The file /etc/network/interfaces on client is: > ... > auto eth0 > iface eth0 inet static > address 192.168.0.2 > netmask 255.255.255.0 > gateway 192.168.0.1 Looks okay. > > 3. Remove "bg" from the /etc/fstab options list. Any status on that part of the experiment? > > Additionally since then I wonder if you are booting with legacy boot > > order or if you are using the new parallel boot order. Do you have > > this file: > > > > ls -ldog /etc/init.d/.legacy-bootordering > > There is no such file neither on the client nor the server. Okay. Means you are using the current parallel boot process. > > dpkg -l | grep ^rc > > No return of this command. Good! For people upgrading from previous versions there is often lint left behind there and sometimes that lint causes problems. > This is a new installation (CD 1 and 2) both the client and the server. Should be good. > I'm thinking don't insist too much about it and include the file /etc/ > rc.local of the client the command: > > mount -t nfs 192.168.0.1:/home /home/home_servidor > > It is not an elegant solution, but it solves the problem for now. If that works then okay. I always hate leaving things in a broken state elsewhere. Because the things you are reporting should be working okay. They work okay for me and many others using the standard bits. But if you are happy at that point then it is your judgement call of when to stop and leave it in a state you can use it. > Is there any difference in operation between the mounting of a partition > using the /etc/fstab and /etc/rc.local? Not in operation. It only changes how it is started up. It will be identical in operation after that point. Bob
Attachment:
signature.asc
Description: Digital signature