NFS directory cannot be used

Last post 07-22-2019, 10:37 AM by pasko@mkb.ru. 6 replies.
Sort Posts: Previous Next
  • NFS directory cannot be used
    Posted: 07-18-2019, 10:00 AM

    Hello

    Trying to install Сlient software on Linux. All the time the error is that the installation directory "/opt/simpana" NFS directory cannot be used.

    Although this is the usual lvm disk. What could be the installation error?

    # lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 30G 0 disk
    ├─sda1 8:1 0 1G 0 part /boot
    └─sda2 8:2 0 29G 0 part
    ├─rhel_rhel8--temp--basic-root 253:0 0 6G 0 lvm /
    ├─rhel_rhel8--temp--basic-swap 253:1 0 3G 0 lvm [SWAP]
    ├─rhel_rhel8--temp--basic-var 253:2 0 3G 0 lvm /var
    ├─rhel_rhel8--temp--basic-opt 253:3 0 256M 0 lvm /opt
    ├─rhel_rhel8--temp--basic-home 253:4 0 512M 0 lvm /home
    └─rhel_rhel8--temp--basic-simpana 253:5 0 10G 0 lvm /opt/simpana
    sdb 8:16 0 200G 0 disk /pgdata
    sr0 11:0 1 1024M 0 rom

    Regards, Aleksandr 

  • Re: NFS directory cannot be used
    Posted: 07-18-2019, 10:11 AM

    Hi there,

    We are getting the same error as above on red hat 8.  Using latest version of commvault installer. My colleague has narrowed it down to a script acced is_nfs failing as per below


    8146 140165806728576 07/18 15:14:28 ###  Client Name: template-redhat8
    8146 140165806728576 07/18 15:14:28 ###  Installation directory:/opt/commvault
    8146 140165806728576 07/18 15:14:28 ###  is_nfs script failed, error code [127] error string [./is_nfs: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
    ]
    None
    8146 140165806728576 07/18 15:14:28 ###  /opt/commvault is NFS directory and cannot be used
    8146 140165806728576 07/18 15:14:28 ###  NFS directory cannot be used
    None
    8146 140165806728576 07/18 15:14:49 ###  Exception in runInstallTUI:I/O operation on closed file
    Traceback (most recent call last):
      File "source/install.py", line 24, in launchInstallUI
      File "source/gxlibrary/upgrade/utils.py", line 52, in wrapper
      File "source/gxlibrary/ui/wizard.py", line 48, in run
      File "source/gxlibrary/upgrade/utils.py", line 52, in wrapper
      File "source/gxlibrary/ui/wizard.py", line 392, in start
      File "source/gxlibrary/ui/tui.py", line 462, in run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 278, in run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/raw_display.py", line 272, in run_wrapper
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 343, in _run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 673, in run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 694, in _loop
      File "source/gxlibrary/upgrade/utils.py", line 52, in wrapper
      File "source/gxlibrary/ui/wizard.py", line 239, in quit
      File "source/gxlibrary/xmlhandler.py", line 211, in updateXml
    ValueError: I/O operation on closed file
    8146 140165806728576 07/18 15:14:49 ###  Instance failed before creating registry. Cleaning up
    Traceback (most recent call last):
      File "source/install.py", line 24, in launchInstallUI
      File "source/gxlibrary/upgrade/utils.py", line 52, in wrapper
      File "source/gxlibrary/ui/wizard.py", line 48, in run
      File "source/gxlibrary/upgrade/utils.py", line 52, in wrapper
      File "source/gxlibrary/ui/wizard.py", line 392, in start
      File "source/gxlibrary/ui/tui.py", line 462, in run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 278, in run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/raw_display.py", line 272, in run_wrapper
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 343, in _run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 673, in run
      File "/updatebuild/11.0/Build80_SP8/cxunix/libraries/python/linux-glibc2.3-x86_64/lib/python2.7/site-packages/urwid/main_loop.py", line 694, in _loop
      File "source/gxlibrary/upgrade/utils.py", line 52, in wrapper
      File "source/gxlibrary/ui/wizard.py", line 239, in quit
      File "source/gxlibrary/xmlhandler.py", line 211, in updateXml
    ValueError: I/O operation on closed file

    Any ideas on how to fix?

     

     

    Maurice

  • Re: NFS directory cannot be used
    Posted: 07-18-2019, 3:12 PM

    Hi

    Can you try applying execute permissions on the entire media? Probably is_nfs file doesnt have execute permission. This can happen when media is copied using tools like winscp.

     

    chmod -R 755 <medialocation>

    Thanks,

    Narender 

  • Re: NFS directory cannot be used
    Posted: 07-19-2019, 2:40 AM

    Hi

    applied the command, but all the error remained

     

  • Re: NFS directory cannot be used
    Posted: 07-19-2019, 12:51 PM

    For the following issue on RHEL8,

     

    8146 140165806728576 07/18 15:14:28 ###  is_nfs script failed, error code [127] error string [./is_nfs: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
    ]

    you need to install few RPM's as these are removed by distro.

    http://documentation.commvault.com/commvault/v11_sp16/article?p=3146.htm

    Red Hat Enterprise Linux/CentOS 8.x with glibc 2.28.x

    *Before you install the Commvault software, you must manually install the libxcrypt.x86_64 and libnsl.x86_64 packages on the computer.

     

    If error still exists on RHEL7, please provide the output of following command.

     

    ls -l <medialocation>/linux-x8664/linux-glibc2.3-x86_64/BinaryPayLoad/is_nfs

     

    Thanks,

    Narender

  • Re: NFS directory cannot be used
    Posted: 07-22-2019, 10:18 AM

    Hi Aleksandr,

    Was this helpful in resolving the issue?

    Thanks,

    Narender

  • Re: NFS directory cannot be used
    Posted: 07-22-2019, 10:37 AM

    Hi Narender,

    Thanks for the help. Workaround did not use.

    Created an incident in the support and I will wait for them to answer the deadlines, when to wait for support RHEL8.

    Regards, Aleksandr

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy