There are several tasks you should do after you install the SFU software.
Before you start using SFU and before you actually install N1GE. please
check that user mapping is working correctly by following these steps.
Open a Interix shell.
Use the su command to switch to a known user.
Verify the access permissions of NFS shares which should be accessible
by that user.
Try to access these network resources. If a user cannot access a Network
drive, most likely the User Name Mapping is not working correctly.
Check users home directories. To enable the automounting of the users
home directories use this series of menus:
Control Panel -> Administrative Tools -> Computer Management -> Users -> Properties -> Profile
click on connect to, select a drive letter,
and enter the path of the users home directory in UNC notation:\\<server>\<share>\<user
home>
Within the Interix subsystem, you might access all NFS
shares through the special directory:/net/<server>/<share>
You might also create links to these directories to access the shares directly
(for example, ln -s /net/myserver/export/share00/home /home).
Enable Administrator names on your machines.
Make sure
that the Administrator accounts on all machines which should be enabled as executions
hosts for N1GE use the same account name (e.g. Administrator).
Also make
sure that this user has manager privileges in your N1GE cluster. If this is not the
case then before the installation of the execution daemon, please add the privileges
using this command:qconf -am <Administrator>
Set the CLI commands which start an editor. Make sure to set the EDITOR
environment variable to vi or your preferred UNIX editor within
the Interix subsystem before you start using UNIX commands.
The following section describes some common problems that users may encounter
when installing and using N1GE in a Services for UNIX environment on a Windows system.
Impossible connect to the Interix subsystem via telnet or rsh
Make sure that the correct services are started. The corresponding
Windows services have to be disabled. The Interix versions of telnetd and rshd have to be started. You can do this task by removing the pound sign
(#) from the following lines part of /etc/inetd.conf
#telnet stream tcp nowait NULL /usr/sbin/in.telnetd in.telnetd -i
#shell stream tcp nowait NULL /usr/sbin/in.rshd in.rshd -a
|
If it is still not possible to connect to the machine, please check your firewall
configuration. Donot block connections to corresponding ports:
Service | Ports
---------+-----------
ftp | 20, 21
ssh | 22
telnet | 23
rsh | 514
|
The wrong default login shell is started. Why?
.rhost and host.equiv authentications fails if new
users accounts are created and if passwords of existing users are changed. The command regpwd has to be called. After that, use the steps to register passwords
correctly.
Why is the access to NFS mounted home directories to slow?
User Name Mapping might be the cause for this problem. If you have a large
number of user maps, installing User Name Mapping on a Domain Controller improves
performance by reducing network traffic. It is possible to create a User Name Mapping
server pool. This method means you can use DNS round-robin to create a pool of computers
running User Name Mapping. This will provide improved performance on wide area networks
as well as provide fail over when one of the servers is no longer available
How can I map user root if it does not exist
in the NIS maps?
First create a passwd file which
contains an entry for the user root. Then, explicitly map the root account (no basic mapping) using the created passwd file.
Finally, change the mapping to use the NIS maps. Note that the previous root mapping will persist.
NIS Server cannot be contacted during the SFU installation
Interrupt the SFU installation and make sure that there is no other service
or application running which already configures or uses the NIS server. If this is
the case, then disable this service for the time of the SFU installation.
The Interix Subsystem of SFU and/or the User Mapping is not enabled
after reboot
Make sure that following services are automatically started
after machine reboot: Interix Subsystem Startup, User
Name Mapping
Also if you use NFS mounted directories that also enable the service
per default: Client for NFS
Queues stick in u-statefor a very long time
After the installation/restart of an execution host the corresponding queues
have attached the unknown (u) state for a very long. This is normal behavior for Windows
machines. After a full load report interval the u-state should be gone. If this is
not the case, then check that the sge_execd has really been started
on the corresponding machine.