Sponsored Content
Full Discussion: Unable to create a SPOT
Operating Systems AIX Unable to create a SPOT Post 302927659 by bakunin on Thursday 4th of December 2014 10:56:41 AM
Old 12-04-2014
Quote:
Originally Posted by trivium012
So I'm guessing I really do have an NFS problem, but I have no idea how to troubleshoot this problem...
Again, you shouldn't (and need not) export anything by hand when you use NIM. Your exports file shows that a lot of directories are exported already. Some of them are probably exported by allocating NIM resources to machines, but some may be exported by hand.

If you use the NIM server alone or get some downtime for it: deallocate all resources at the NIM-server, then remove everything "/nim/..." (which i presume to be the root for your NIM resources) from the exports file. Always deallocate with the "force" option (otherwise that fails most of the times).

You might want to use something like:

Code:
lsnim -t standalone | while read system junk ; do
     nim -o reset -a force=yes $system
     nim -Fo deallocate -a subclass=all $system
done

Only then allocate resources again. These (and ONLY these) should appear in the exports file.

Next thing is to check the client you test with if the NIM connection is working. Quite often this is the problem. If you use "nimsh" check if the nimsh service is running on the client, otherwise you need a running rsh:

Code:
root@client # lssrc -g nimclient
 nimsh            nimclient        5505154      active

Now test this by placing a simple script (just put a "date" command into it, is enough) in "/nimres/scripts" (or somewhere, this is how i call the directory), add a nim resource of the type "script" and let it point to the script. Then test the client by

Code:
nim -o cust -a script=<scriptname> <client>

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

Unable to create a group

Hi, I'm trying to create a new group on an AIX 5.2.0.0. server but am getting the following error: root:/root $ mkgroup debt 3004-698 Error committing changes to "debt" : Value is invalid. I've change the group name to no affect. Does anyone have any ideas what could be causing this? ... (0 Replies)
Discussion started by: m223464
0 Replies

2. Solaris

unable to create flar

Hello friend, Now i'm doing JDS3.1 in v440 servers.while checking the lustatus command getiing out like this lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- --------... (0 Replies)
Discussion started by: rjay.com
0 Replies

3. UNIX for Dummies Questions & Answers

Unable to create alias

I am using Solaris 9 machine. I am unable to create any aliases. I gave the following command: alias ls='ls -ltr' It did nt give any errors. But next time, I use ls, it is working simply as ls but not like ls -ltr. I am not having admin permissions. Is it the reason. (3 Replies)
Discussion started by: mumashankar
3 Replies

4. UNIX for Dummies Questions & Answers

Unable to create a bootable tape

Good morning, I have no unix training. My daily backup failed with the following error. ' Cannot create /tmp/tape.bootimage because it already exists. I am using smit to run a rootvg and SAPvg backup. What should I do? (1 Reply)
Discussion started by: ubyankees
1 Replies

5. HP-UX

Need help. Unable to create threads after a certain number

Hi, I have a process which creates pthreads to generate some reports. After creating the reports these threads return null. But after 1024 threads, the process is not able to create any threads further.,and at max 5 threads are existing simultaneously and are returning the control back after... (2 Replies)
Discussion started by: Krsh
2 Replies

6. Solaris

Unable to create folder as a user

Hi All, I am trying to create a folder in /export/home/user1 directory as a user1 but I am getting the error message as -bash-3.00$ mkdir abc mkdir: Failed to make directory "abc"; Permission denied Also I tried creating the folder but it fails too -bash-3.00$ touch abc touch: cannot... (2 Replies)
Discussion started by: Manjunath K V
2 Replies

7. Red Hat

unable to open / create any file in vi

Hi, I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5, example vi test it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies

8. AIX

Unable to Create spot from mksysb

Hello All, Kindly need help in my problem i.e. I get this error when i create spot from mksysb. #0042-001 nim: processing error encountered on "master": 0042-001 m_mkspot: processing error encountered on "master": 0042-175 c_mkspot: An unexpected result was returned by the... (2 Replies)
Discussion started by: emerann
2 Replies

9. Forum Support Area for Unregistered Users & Account Problems

Unable to create new thread

Hi. I registered, but when trying to post, I get ... "Sorry, you do not have enough Bits to post a new thread" Google & Forum search showed some hits, but no solution. Please advide. Thanks! (1 Reply)
Discussion started by: gehe
1 Replies

10. Solaris

Unable to create a ftp user only

Hi all I am facing difficulties when using the useraddcommand. when running useradd -u 60006 -g 100 -d /opt/xxx/yyy/z -m -s /bin/false ftpuser It does create the user, but with a wrong home directory. It creates its home directory at /home/ftpuser Please can you help? (2 Replies)
Discussion started by: fretagi
2 Replies
exports(4)						     Kernel Interfaces Manual							exports(4)

NAME
exports - Defines remote mount points for NFS mount requests SYNOPSIS
/etc/exports DESCRIPTION
The exports file specifies remote mount points for the NFS mount protocol per the NFS server specification (see Network File System Proto- col Specification, RFC1094). Each entry in the /etc/exports file consists of a filesystem or directory name followed by an optional list of options or an optional list of identifiers or both. The identifiers define which remote hosts can mount that particular filesystem or directory. The identifiers listed beside the name of each filesystem or directory can be either host names, IP addresses, or NIS netgroups names. If no identifiers are listed, the entry is exported to all hosts. A backslash character () in the right-most position of a line indicates line continuation. A number sign (#) either at the beginning of a line or at the end of a syntax line marks a comment that extends to the end of that line. You cannot use a number sign at the end of a line containing a backslash character because the backslash nullifies the end of line character. Note that the mount command will touch the /etc/exports file when issued with the -t nfs option. If you create a new /etc/exports file, you should ensure that its ownership is equivalent to that of the default, which is; bin:bin (3:4). The format of the exports file is as follows: pathname [option ...] [identifier ...] #comments The pathname specifies the name of a mounted local filesystem or a directory of a mounted local filesystem. The pathname must begin in column 1. The following are valid export file options: Maps client superuser access to uid 0 for all hosts mounting this path. If you want to allow client superusers access to the filesystem or directory with the same permissions as a local superuser, use -root=0. Use -root=0 only if you trust the superuser on the client system. The default is for client superusers to be mapped to uid -2, which maps a client superuser to nobody. This limits access to world accessible files. If both the -root=0 option and the -anon=uid option are used, the root option overrides the uid specified in anon for client superusers. Maps the client superusers on the specified hosts only to uid 0. The format for the hostlist argument is as follows: client[:client]... The client specification can be a host name or IP address. By default, client superusers are mapped to -2. This option overrides the uid specified in -anon=uid for client superusers in hostlist. Maps anonymous users to the specified uid. Client superusers are considered anonymous by the NFS server, as are requests that come in without UNIX authentication. By default, anonymous users are mapped to uid -2. Setting anon to -1 disables anonymous access. The filesystem or directory is exported read-only (default is read-write). The -o option is a synonym for -ro for backward compatibility. limits read-write access to the hosts specified. All other hosts allowed to mount this path are granted read-only access. The format for the hostlist argument is as follows: client[:client]... The client specification can be a host name or IP address. If both the -ro and -rw=hostlist options are specified, -rw prevails. Exports a filesystem or directory for WebNFS public access. Note that only one exported filesystem can have this option set. Note When the -public option is set, the mount access list is ignored by the WebNFS server. This means that all hosts using the WebNFS protocol have access to this directory. After setting the -public option, be sure to send the mountd process a HUP signal. See kill(1) for further information. Used with -public option. Enables the server to look for an index.html file when given a directory name. Specifies the hosts to grant mount access to. The format for the hostlist argument is as follows: client[:client]... The client specification can be a host name, IP address, or NIS network group. This option is provided for readability and compatibility with certain export file formats. Alternatively, to identify the client systems who are allowed access to this export use the whitespace separated identifier list described below. The options can be applied to both file system and directory entries in /etc/exports. Alternatively, you can list options using only one leading dash and separating them with commas as in -option[,option].... You use the identifier field to specify host names, network groups, or both, separated by white space that specify the access list for this export. Host names can optionally contain the local BIND domain name. A whitespace character in the left-most position of a line indi- cates line continuation. Note If no hosts or netgroups are specified, the mount daemon exports this file system or directory to anyone requesting it. See the mountd(8) reference page for information on how to limit this scope to known hosts or to hosts in the same BIND domain. For example, suppose you enter: /usr -root=0 milan kuan_yin.cis.berkeley.edu /usr/local 555.555.55.55 /u2 -ro /u3/dir1 -rw=milan:venice:florence /u3/dir2 -root=milan,access=venice:florence /u3/dir3 -root=0,access=milan:venice:florence /u3/dir4 -root=0 milan venice florence /u3/dir5 -root=milan -anon=-1 /u3/dir6 -ro -public milan venice florence If /usr, /u2 and /u3 are local file system mount points, this specifies the following: /usr is exported read-write to hosts milan and kuan_yin.cis.berkeley.edu with root mapped to uid=0. /usr/local is exported read-write to host 555.555.55.55 with root mapped to -2. (For security reasons, this example uses the fictitious IP address 555.555.55.55.) /u2 is exported to all hosts read-only with root mapped to -2. /u3/dir1 is exported read-write to hosts milan, venice, and florence and read-only to all other hosts. For all hosts, root is mapped to -2. /u3/dir2 is exported with root mapped to 0 to host milan. Hosts milan, venice, and florence are allowed to mount this directory read-write. Root on hosts venice and florence is mapped to -2. /u3/dir3 is exported read-write and with root mapped to 0 to hosts milan, venice, and florence. /u3/dir4 is exported in the same manner as the previous example. /u3/dir5 is exported read-write to all hosts. Anonymous users are not allowed to mount this directory, with the exception of the client superuser on host milan. Root is mapped to 0 on host milan and to -2 on all other hosts. /u3/dir6 Hosts milan, venice, and florence are allowed to mount this directory read-only. All other hosts have read-only WebNFS access, but cannot mount this directory. Each file system that you want to allow clients to mount must be explicitly defined. Exporting only the root (/) will not allow clients to mount /usr. Exporting only /usr will not allow clients to mount /usr/local, if it is a file system. Duplicate directory entries are not allowed. The first entry is valid and following duplicates are ignored. Desired export options must be explicitly specified for each exported resource: file system or directory. If a file system and subdirecto- ries within it are exported, the options associated with the file system are not ``inherited.'' You do not need to export an entire file system to allow clients to mount subdirectories within it. The access list associated with each exported resource identifies which clients can mount that resource with the specified options. For example, you can export an entire file system read-only, with a subdirectory within it exported read-write to a subset of clients. If a client that is not identified in the export access list of a directory attempts to mount it, then access is checked against the closest exported ancestor. If mount access is allowed at a higher level in the directory tree of the file system, the export options associated with the successful match will be in effect. To make a change to the exports file and have it take effect immediately, send the mountd process a HUP signal. Otherwise, the mountd process will reread the exports file the next time it receives a mount request from an NFS client or a showmount -e request. RELATED INFORMATION
Daemons: mountd(8), nfsd(8) Commands: showmount(8) Files: hosts(4), netgroup(4) Network Administration delim off exports(4)
All times are GMT -4. The time now is 06:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy