Solaris AdminSuite 3.0 Troubleshooting

• Home Directory Not Created
• Mailbox Not Created
• Server/Domain Mismatch
• Server Cannot Authenticate Your Identity
• Administrator Cannot Be Authenticated
• Serial Port Problems
• Configuring the Microsoft Windows Environment
• Problem Adding Multiple Users
• Stopping and Restarting the AdminSuite Server
• Out-of-Memory Error
• AdminSuite Server Failure

When you add a new user, you must specify the name of the server on which the user's home directory is located. If AdminSuite cannot contact that server, you will be notified that the user was added but the home directory could not be created.

There are a few possible reasons why the home directory was not created: you may have mistyped the server name in the wizard, the server might be temporarily out of service, or AdminSuite might not be running on the server.

To create the user's home directory after you have added the user, be sure AdminSuite is running on the server, then:

1. In User Accounts, double-click the user's name.
2. In User Properties, click the Home Directory tab.
3. In the Home Directory Server field, type the server name.

   Note: This field is writable only until the directory is created. Once the directory is created, the server name cannot be changed.

When you add a new user while managing a NIS or NIS+ domain, you must specify the name of the server on which the user's mailbox is located. (The mailbox is the file that contains the user's newly received email.) If AdminSuite cannot contact that server, you will be notified that the user was added but the mailbox could not be created.

There are a few possible reasons why the mailbox was not created: you may have mistyped the server name in the wizard, the server might be temporarily out of service, or AdminSuite might not be running on the server.

To create the user's mailbox after you have added the user, be sure AdminSuite is running on the server, then:

1. In User Accounts, double-click the user's name.
2. In User Properties, click the Mail tab.
3. In the Mail Server field, type the server name.

   Note: This field is writable only until the mailbox is created. Once the mailbox is created, the server name cannot be changed.

An error message appears when you attempt to manage a domain, but the domain name and the name of the machine originally selected to manage that domain are not correctly matched.

Click Domain->Add/Delete Domain. Find the domain you attempted to log on to in the List of Domains. Is the domain name spelled correctly? Is the server name spelled correctly? Is the server the appropriate one for the domain being managed?

If the domain name or server name is incorrect (or the two are incompatible), delete the incorrect domain and add the one you want to log on to.

There are a few reasons why the management server might be unable to authenticate the identity of a user (verify the user's identity by checking the user's name against the password):

• Problem: The password entered by the user is incorrect.
• Solution: Check the password and re-enter it.

• Problem: The user account is locked, preventing the user from logging on.
• Solution: In User Accounts, open the user's Properties dialog box. On the General tab, unlock the account by selecting Account is Always Available or Account is Available Until (and enter a date).

• Problem: The user account does not have a password assigned to it.
• Solution: In User Accounts, open the user's Properties dialog box. On the Password tab, select User Must Set Password At Next Logon, or User Must Use This Password At Next Logon (and inform the user of the password).

• Problem: The user account does not exist in the passwd table used by the server for user logons.
• Solution: Make sure the user is added to the passwd table. Delete the user, through User Accounts, and re-create the account on the appropriate server.

• Problem: AdminSuite is searching in the wrong passwd file or table for this user's information because of incorrect settings in the /etc/nsswitch.conf file.
• Solution: Make sure settings in the /etc/nsswitch.conf file are configured for the way you want authentication information to be found.

An administrator is unable to create the home directory or mailbox for a user because the home directory or mailbox server is unable to authenticate the administrator.

• Problem: The administrator's user account does not exist in the passwd table used by the home directory or mailbox server.
• Solution: Make sure the administrator is added to the passwd table on the server. Delete the administrator's account, through User Accounts, and re-create the account (with the rights to administer users) on the appropriate server.

• Problem: AdminSuite is searching the wrong passwd file or table for authentication information.
• Solution: Make sure settings in the /etc/nsswitch.conf file are configured for the way you want authentication information to be found.

When a serial port message refers you to troubleshooting, see if there is additional information in Log Viewer, and then step through each of the following problems and solutions in succession:

• Problem: The file for storing serial port information is unavailable.
• Solution: This could be temporary. Try again.

• Problem: The service access facility daemon is no longer running.
• Solution: Start the service access facility daemon:
  1. As root, run:

        usr/lib/saf/sac -t 300
        /usr/lib/saf/ttymon

  2. Search in two log files generated by the service access daemon for clues: /var/saf/_log and /var/saf/zsmon/log.
• Problem: No data is available for a port, or a port appears to be missing.
• Solution: Look in the /dev/term directory. If no files are in the directory, the ports do not exist. If the ports exist, then the files /etc/saf/_sactab and /etc/saf/zsmon/_pmtab are corrupted. Contact your senior administrator to restore the corrupted file.

The following three environment variables are needed for the AdminSuite client to successfully run in a Microsoft Windows environment (Windows NT, 95, or 98):

WS JAVA_HOME CLASSPATH

When the AdminSuite client is installed, two files are updated with the settings for these three variables:

admapp.bat batchapp.bat

Each file is modified to include the following three lines at the top of each file:

set WS=base install dir set JAVA_HOME=java install dir - obtained from registry set CLASSPATH=current CLASSPATH;%WS%\admswt10.jar;%WS%\jcbwt360J.jar;%WS%\swingall.jar;%JAVA_HOME%;%WS%\classes;

For example, if you use AdminSuite default settings for the base directory and for JAVA_HOME, the settings for these three variables are:

set WS=C:\Progra~1\Sunw\Admins~1 set JAVA_HOME=C:\jdk117 set CLASSPATH=C:\Progra~1\Sunw\Admins~1\admswt10.jar;C:\Progra~1\Sunw\Admins~1\jcbwt360J.jar;C:\Progra~1\Sunw\Admins~1\swingall.jar;C:\jdk117;C:\Progra~1\Sunw\Admins~1\classes;

NOTE: The paths for the file names shown previously are converted into a short file name format. For example, C:\Program Files\Sunw\AdminSuite is converted to C:\Progra~1\Sunw\Admins~1.

If the two batch files above do not have these environment variables set, the AdminSuite client will NOT run.

NOTE: It is possible to set system variables instead of editing the batch files. It can be done either way, as long as the WS, JAVA_HOME, and CLASSPATH environment variables are set correctly when the batch files are run.

The inability to add multiple users through the Multiple Users Wizard may indicate that AdminSuite files have been removed.

Verify that the following files are in /opt/SUNWseam/3_0/etc:

AdminAuths.properties AdminClient.properties AdminServer.properties

If these files do not exist, reinstall AdminSuite.

To stop and restart the AdminSuite server:

1. As root, change to the /opt/SUNWseam/3_0/sbin directory.
2. Type the following commands:

      ./admsvr stop
      ./admsvr start

If you encounter an "OutofMemoryError" error, you will need to restart AdminSuite.

1. Exit AdminSuite.
2. Change to the bin directory (if you are not there already):

      cd /opt/SUNWseam/3_0/bin

3. Restart AdminSuite:

      ./admapp &

1. Exit AdminSuite.
2. Change to the sbin directory:

      cd /opt/SUNWseam/3_0/sbin

3. Become root and stop the AdminSuite server:

      ./admsvr stop

4. Restart the AdminSuite server:

      ./admsvr start

5. Exit the root user session.
6. Change to the bin directory:

      cd /opt/SUNWseam/3_0/bin

7. Restart AdminSuite:

      ./admapp &

Note: If you must increase the number of objects to view, you can increase the memory allocation pool. The maximum memory allocation pool for the Java Virtual Machine (VM) is 32MB by default. To increase the maximum size of the memory pool for the AdminSuite server or application, modify the memory allocation parameter for the Java VM command line in the admsvr and/or admapp startup scripts.

For example, to increase the maximum memory pool size for the AdminSuite server to 48MB:

1. Log in as root.
2. Edit the /opt/SUNWseam/3_0/sbin/admsvr file.
3. Change the line:

      JAVA_FLAGS=" -mx32m "

   to

      JAVA_FLAGS=" -mx48m "

1. Log in as root.
2. Edit the /opt/SUNWseam/3_0/bin/admapp file.
3. Change the line:

      JAVA_FLAGS=" -mx32m "

   to

      JAVA_FLAGS=" -mx48m "

If the AdminSuite server fails, multiple symptoms may appear:

• The AdminSuite application may seem to stall.
• Several error messages may appear. Some may indicate that the server is unable to determine which rights you have been granted, and that the connection to the host is refused.
• You will be unable to add or modify anything through the AdminSuite client.

1. Close the AdminSuite application.
2. Become root.
3. Change to the /opt/SUNWseam/3_0/sbin directory.
4. Restart the AdminSuite server:

      ./admsvr start

5. Exit the root user session.
6. Change to the /opt/SUNWseam/3_0/bin directory.
7. Restart the AdminSuite application:

      ./admapp &