Dear Bob, Em Sáb, 2013-02-09 às 12:52 -0700, Bob Proulx escreveu: > Markos wrote: > > I just checked the configuration file /etc/fstab on the client machine > > and the server IP address is correct. 192.168.0.1 > > > > When writing the message I copied and pasted the IP address of the site > > that I used as a reference and I forgot to check. > > > > Sorry for the mistake. > > No problem. We have all made those. > > > Do you have any other suggestions? > > What did you find when you tried the others suggestions? Specifically: > > 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: Feb 10 14:31:12 servidor rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="985" x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type 'lightweight'. Feb 10 14:31:12 servidor rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="985" x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type 'lightweight'. Feb 10 14:31:18 servidor anacron[1067]: Job `cron.daily' terminated Feb 10 14:31:18 servidor anacron[1067]: Normal exit (1 job run) Feb 10 14:32:13 servidor kernel: [ 378.758482] ip_tables: (C) 2000-2006 Netfilter Core Team Feb 10 14:32:13 servidor kernel: [ 378.797306] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) Feb 10 14:32:13 servidor kernel: [ 378.798066] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use Feb 10 14:32:13 servidor kernel: [ 378.798073] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or Feb 10 14:32:13 servidor kernel: [ 378.798078] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. 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 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) Feb 10 14:54:39 servidor mountd[1052]: authenticated mount request from 192.168.0.2:920 for /home (/home) 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). > 2. Change /etc/network/interfaces 'allow-hotplug eth0' to 'auto eth0'. > The file /etc/network/interfaces on server is: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 The file /etc/network/interfaces on client is: # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 > 3. Remove "bg" from the /etc/fstab options list. > > 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. > And that made me wonder if there are additional files left behind as > lint from previous upgrades in /etc/init.d that may be causing > problems keeping it using legacy boot ordering. > > dpkg -l | grep ^rc > No return of this command. This is a new installation (CD 1 and 2) both the client and the server. > Are there packages installed, removed, but not purged that would > contain /etc/init.d files? If you do then it is probably time to do > housecleaning. > > Bob 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. Is there any difference in operation between the mounting of a partition using the /etc/fstab and /etc/rc.local? Thank you very much for your attention. Markos www.c2o.pro.br -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1360517500.3578.24.ca...@malgas.petrobras.biz
