On 01/04/2012 10:45:47 PM, Ed Greshko wrote:
> On 01/05/2012 02:22 PM, Geoffrey Leach wrote:
> > AFAIK you have the correct info -- sorry. Somehow I've done
> something
> > to confuse the server as to who's who. Any thoughts there?
>
> Well.... I'd first start off by not using hostnames for testing.
>
> I'd go to 192.168.10.2 and verify that the IP address is set as I
> think
> it is set by typing "ifconfig" and verifying it. I'd do the same
> with
> 192.168.10.4. I may even go so far as putting post-it notes on the
> displays of each system I'm working with to make sure of not getting
> confused as to what system is being typed on.
Well, my client system is in another room and has a 40" TV as its
monitor, so not much chance of confusion there :-)
I will do as you ask and not use hostnames in future. I did run
ifconfig as you suggested, and it revealed an inconsistency. That's
corrected now.
root@mtranch[1]->ifconfig
em1 Link encap:Ethernet HWaddr 00:18:F3:98:CD:0B
inet addr:192.168.10.2 Bcast:192.168.10.255
Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe98:cd0b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1860 errors:0 dropped:0 overruns:0 frame:0
TX packets:1740 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1774926 (1.6 MiB) TX bytes:204104 (199.3 KiB)
Interrupt:19 Base address:0xc400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3288 (3.2 KiB) TX bytes:3288 (3.2 KiB)
wlan0 Link encap:Ethernet HWaddr 00:19:D2:2D:F2:76
inet addr:192.168.10.3 Bcast:192.168.10.255
Mask:255.255.255.0
inet6 addr: fe80::219:d2ff:fe2d:f276/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5375 (5.2 KiB) TX bytes:5662 (5.5 KiB)
root@pvr[1]->ifconfig
em1 Link encap:Ethernet HWaddr 00:23:54:5D:3C:AE
inet addr:192.168.20.5 Bcast:192.168.20.255
Mask:255.255.255.0
inet6 addr: fe80::223:54ff:fe5d:3cae/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9884 (9.6 KiB) TX bytes:6524 (6.3 KiB)
Interrupt:20 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:285 errors:0 dropped:0 overruns:0 frame:0
TX packets:285 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24332 (23.7 KiB) TX bytes:24332 (23.7 KiB)
wlan0 Link encap:Ethernet HWaddr 00:1A:EF:03:03:E3
inet addr:192.168.10.4 Bcast:192.168.10.255
Mask:255.255.255.0
inet6 addr: fe80::21a:efff:fe03:3e3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:316 errors:0 dropped:0 overruns:0 frame:0
TX packets:317 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:38828 (37.9 KiB) TX bytes:37617 (36.7 KiB)
On pvr (client, em1 is connected (hard wire) to a Silicon Dust HD
tuner. The network setup is this: pvr wireless to a Netgear router to
an ethernet connection to mtranch (server) So I'm assuming that the
different IP addresses for wlan0 are not important.
> Then, I guess, I'd do what Craig has suggested.
Now, I' repeating Craig's instructions.
root@mtranch[8]->systemctl restart nfs-lock.service
root@mtranch[9]->systemctl restart nfs-idmap.service
root@mtranch[10]->systemctl restart nfs-server.service
root@mtranch[11]->tail -n 15 /var/log/messages
Jan 5 12:50:13 mtranch kernel: [ 6656.331338] NFSD: starting 90-second
grace period
Jan 5 12:50:13 mtranch rpc.mountd[4202]: Version 1.2.5 starting
Jan 5 12:51:26 mtranch rpc.statd[1041]: Caught signal 15, un-
registering and exiting
Jan 5 12:51:26 mtranch systemd[1]: nfs-lock.service: main process
exited, code=exited, status=1
Jan 5 12:51:26 mtranch sysctl[4213]: fs.nfs.nlm_tcpport = 0
Jan 5 12:51:26 mtranch sysctl[4213]: fs.nfs.nlm_udpport = 0
Jan 5 12:51:26 mtranch systemd[1]: Unit nfs-lock.service entered
failed state.
Jan 5 12:51:26 mtranch rpc.statd[4219]: Version 1.2.5 starting
Jan 5 12:51:26 mtranch sm-notify[4220]: Version 1.2.5 starting
Jan 5 12:51:26 mtranch sm-notify[4220]: Already notifying clients;
Exiting!
Jan 5 12:51:26 mtranch rpc.mountd[4202]: Caught signal 15, un-
registering and exiting.
Jan 5 12:51:26 mtranch kernel: [ 6729.295100] nfsd: last server has
exited, flushing export cache
Jan 5 12:51:26 mtranch kernel: [ 6729.402844] NFSD: Using /var/lib/
nfs/v4recovery as the NFSv4 state recovery directory
Jan 5 12:51:26 mtranch kernel: [ 6729.402868] NFSD: starting 90-second
grace period
Jan 5 12:51:26 mtranch rpc.mountd[4250]: Version 1.2.5 starting
root@pvr[3]->telnet 192.168.10.2 2049
Trying 192.168.10.2...
Connected to 192.168.10.2.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
> Also, when you include in your email message what you are seeing are
> you
> using copy/paste or just typing what you've seen? I ask that since
> on
> my default F16 installs $PS1 is defined as [\u@\h \W]\$ which gives
> the
> hostname of the system you are on so as to limit confusion.
>
OK, I confess. Sometimes I opted for copying down the results rather
than putting them on disk. The ssh connection failed. Its OK now, but
in the event it fails again, I promise, no scribbling! :-)
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
