Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Mauro Souza A good way to know is running a showmount -e on the laptop. If it returns the contents of your /etc/exports, we have to think about what else could possibly be wrong. If don't, look on dmesg or /var/log/messages to see any informative error messages. [root@localhost ~]# showmount -e Export list for localhost.localdomain: /tmp/iso * [root@localhost ~]# cat /etc/exports /tmp/iso *(ro,no_root_squash) [root@localhost ~]# Then: [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# If I omit 'localhost:' from the mount command, the mount works; in that no hate mail is returned and I can then cd to /tmp/iso and ls the contents of the DVD. But then the SLES install program running on z/VM can't find the repository. According to my notes, except for trying 'localhost:' in the mount command, this is the exact procedure we used to install RHEL about three weeks ago. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Just for grins, after you do the mount, run 'exportfs -a' to force the exports list to be updated. [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
[root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# Just for clarity, this part is on he laptop, yes? So the localhost: implies that the laptop is mounting *from* NFS (ie: client). It's not. It wants the CD. The vers=3 also implies NFS (client). Then you get mount.nfs: access denied, so yeah, the laptop things it is importing an NFS filesystem. It's not. If I omit 'localhost:' from the mount command, the mount works; in that no hate mail is returned and I can then cd to /tmp/iso and ls the contents of the DVD. But then the SLES install program running on z/VM can't find the repository. Perfect. So do that. NOTE: You may also need an 'exportfs -a' after mounting the CD. Your laptop, being the NFS server, needs to serve out the contents of the CD, not the empty directory over which it got mounted. VERY LIKELY, there was an exportfs operation before you mounted the CD, so your NFS server code still sees that empty directory. NOW ... to the installation end. You should be able to (from a shell) ... mkdir /tmp/testit mount thelaptop:/tmp/iso /tmp/testit What happens from that? -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of David Boyes Just for grins, after you do the mount, run 'exportfs -a' to force the exports list to be updated. [root@localhost ~]# exportfs -a exportfs: /tmp/iso requires fsid= for NFS export [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# Perhaps the access denied message (below) has something to do with this? [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
[root@localhost ~]# exportfs -a exportfs: /tmp/iso requires fsid= for NFS export [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# Perhaps the access denied message (below) has something to do with this? It does indeed, but it's not the problem you're looking for. First step is to get the CD/DVD mounted on the right mountpoint on the NFS server (that's a physical device mount on the machine in question, so the localhost: syntax isn't usable -- you're not using the network for this step, it's a local device on a local mountpoint). Once the DVD is mounted, then you tell the NFS server to reparse /etc/exports using 'exportfs -a'. It doesn't automatically do this if something changes (in order to make NFS server configuration processing atomic; you might want to make a bunch of changes and then commit the export after you're all done messing around), and most NFS servers won't export an empty mountpoint, even if it is configured in /etc/exports) Is there any reason why you're not putting all the mount options in /etc/exports (that's what's in the parens)? You *will* forget one, and be very confused why it doesn't work -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# Just for clarity, this part is on he laptop, yes? Yes. So the localhost: implies that the laptop is mounting *from* NFS (ie: client). It's not. It wants the CD. The vers=3 also implies NFS (client). Then you get mount.nfs: access denied, so yeah, the laptop things it is importing an NFS filesystem. It's not. If I omit 'localhost:' from the mount command, the mount works; in that no hate mail is returned and I can then cd to /tmp/iso and ls the contents of the DVD. But then the SLES install program running on z/VM can't find the repository. Perfect. So do that. Done. NOTE: You may also need an 'exportfs -a' after mounting the CD. Done. Your laptop, being the NFS server, needs to serve out the contents of the CD, not the empty directory over which it got mounted. VERY LIKELY, there was an exportfs operation before you mounted the CD, so your NFS server code still sees that empty directory. NOW ... to the installation end. You should be able to (from a shell) ... mkdir /tmp/testit mount thelaptop:/tmp/iso /tmp/testit What happens from that? [root@localhost ~]# mount -o ro,vers=3,nolock /dev/sr0 /tmp/iso [root@localhost ~]# exportfs -a [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# mkdir /tmp/testit [root@localhost ~]# mount localhost:/tmp/iso /tmp/testit wait about two minutes ^C [root@localhost ~]# -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Try the -v flag on your mount. Perhaps verbose will give a clue of why it is hanging. The information contained in this e-mail message is intended only for the personal and confidential use of the designated recipient(s) named above. This message may be an attorney-client or work product communication which is privileged and confidential. It may also contain protected health information that is protected by federal law. If you have received this communication in error, please notify us immediately by telephone and destroy (shred) the original message and all attachments. Any review, dissemination, distribution or copying of this message by any person other than the intended recipient(s) or their authorized agents is strictly prohibited. Thank you. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Looks like part of the problem is that both ends call themselves localhost. DO NOT use localhost for the NFS mount (unless you really want to NFS mount something served back to the same box, clearly not this case). ... [root@localhost ~]# mount -o ro,vers=3,nolock /dev/sr0 /tmp/iso [root@localhost ~]# exportfs -a [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# mkdir /tmp/testit [root@localhost ~]# mount localhost:/tmp/iso /tmp/testit wait about two minutes ^C [root@localhost ~]# Maybe try mounting by IP address. mount 192.168.55.44:/tmp/iso /tmp/testit ... replacing 192.168.55.44 with the address of the laptop. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Veencamp, Jonathon D. Try the -v flag on your mount. Perhaps verbose will give a clue of why it is hanging. [root@localhost ~]# mount -v localhost:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:26:19 2013 mount.nfs: trying text-based options 'vers=4,addr=127.0.0.1,clientaddr=127.0.0.1' three minutes after timeout expired ^C [root@localhost ~]# -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth Looks like part of the problem is that both ends call themselves localhost. DO NOT use localhost for the NFS mount (unless you really want to NFS mount something served back to the same box, clearly not this case). ... Maybe try mounting by IP address. mount 192.168.55.44:/tmp/iso /tmp/testit ... replacing 192.168.55.44 with the address of the laptop. [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# In case you're assuming I have two machines, I have only the one Linux laptop, on which I've tried all suggestions so far. Should I be trying these mount commands from another machine, e.g. the SLES install program on z/VM? I could also use one of the RHEL identities on z/VM. -jc- -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Replying to myself -Original Message- -Original Message- From: Linux on 390 Port On Behalf Of Rick Troth Looks like part of the problem is that both ends call themselves localhost. DO NOT use localhost for the NFS mount (unless you really want to NFS mount something served back to the same box, clearly not this case). ... Maybe try mounting by IP address. mount 192.168.55.44:/tmp/iso /tmp/testit ... replacing 192.168.55.44 with the address of the laptop. [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# In case you're assuming I have two machines, I have only the one Linux laptop, on which I've tried all suggestions so far. Should I be trying these mount commands from another machine, e.g. the SLES install program on z/VM? I could also use one of the RHEL identities on z/VM. Here's what I get on the SLES install program on z/VM: / # mount 10.250.24.67:/tmp/iso /tmp/testit / # ls -l /tmp/testit drwxr-xr-x2 00 40 Mar 7 16:45 . drwxrwxrwt3 00 60 Mar 7 16:45 .. / # ls -l 10.250.24.67:/tmp/iso 10.250.24.67:/tmp/iso: No such file or directory / # -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
... replacing 192.168.55.44 with the address of the laptop. [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# I often get timeout (or never-completing mount) when some magical part of the RPC suite hasn't been started. The server will need at least 'rpc.mountd'. I think the client will need 'rpc.statd'. (I confess to not retaining these details.) Both are likely to need 'rpcbind'. In case you're assuming I have two machines, I have only the one Linux laptop, on which I've tried all suggestions so far. Yes, I was assuming that. Sorry to have missed that part. NFS mounting this content back on the laptop (from which it is served out) DOES answer the question if the NFS server software is working. Otherwise, it's not all that useful. Should I be trying these mount commands from another machine, e.g. the SLES install program on z/VM? I could also use one of the RHEL identities on z/VM. Yes. As I recall, you're using this media hosted on the laptop to effect an install hosted on VM. So you'll eventually want an NFS client mount on the SLES installation target end. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Hang in there, John. This will eventually work. Here's what I get on the SLES install program on z/VM: / # mount 10.250.24.67:/tmp/iso /tmp/testit / # ls -l /tmp/testit drwxr-xr-x2 00 40 Mar 7 16:45 . drwxrwxrwt3 00 60 Mar 7 16:45 .. The mount command on the SLES inst side appears to succeed. That's a good sign. But the content of that directory is still empty. Not so good. Did you do the 'exportfs' on the laptop after mounting the CD there? / # ls -l 10.250.24.67:/tmp/iso 10.250.24.67:/tmp/iso: No such file or directory / # The 10.250.24.67:/tmp/iso syntax is only useful as the object of an NFS (client) mount. 'ls' doesn't know what to do with it, so treats it like a local file which turns out to not exist. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth [ snip ] I often get timeout (or never-completing mount) when some magical part of the RPC suite hasn't been started. The server will need at least 'rpc.mountd'. I think the client will need 'rpc.statd'. (I confess to not retaining these details.) Both are likely to need 'rpcbind'. The systemctl command shows that rpcbind.service is running, but the others are not. It also shows nfs-mountd.service as failed (did not notice that before). There does not appear to be an rpc.mountd or rpc.statd in Fedora 18. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
