Troubleshooting user access to the Administrative command-line interface

Use the information in this topic to troubleshoot problems that you are having with a user attempting to access the Administrative command-line interface.

Problem

A user was unable to access the Administrative command-line interface.

Investigation

If the user received access denied errors
Perform the following steps until the problem is resolved:
  1. Using SSH, access the engine that is having failures.
  2. View the tank.passwd file to verify that the user name and password are correct.
    # cat ~/.tank.passwd
  3. Recreate the password file.
    cd ~; /usr/tank/admin/bin/tankpasswd -u ldap_username -p ldap_passwd
    where the ldap_username and ldap_password are for the user that is having problems.
  4. Run the lsserver command to verify that you have access to the metadata server.
    sfscli>lsserver
  5. Verify that the LDAP server is running and that there is no configuration problem between the LDAP server and the administrative agent. Check the administrative log to determine whether you are receiving errors about the SAN File System not being able to connect to the LDAP server.
If the user received administrative agent or CIM agent not found errors.
Perform the following steps until the problem is resolved:
  1. Run the ps shell command to verify that the administrative agent is running.
    ps -efw | grep -i cimom.cimom
    You should see results similar to this:
    root      4070  3822  0 07:26 ?        S      0:08 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4087  4070  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4088  4087  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4089  4087  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4090  4087  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4098  4087  0 07:27 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    ldap      4099   758  0 07:27 ?        S      0:00 
    /usr/sbin/slapd -u ldap
    root      4101  4087  0 07:27 ?        S      2:11 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4102  4087  0 07:27 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
  2. If the administrative agent is not running, use the startCimom command to start the administrative agent. If you run into problems starting the administrative agent, view the administrative log or /usr/tank/admin/log/stderr.log and attempt to resolve any problems that you find.
  3. Verify that the console has been started.
    /opt/was/bin/serverStatus.sh metadata_server
    where metadata_server is the host name of the server that you are trying to access.
    Note: Run the script with no parameters to obtain additional help on using the script.
  4. If the console is not running, run /usr/tank/admin/bin/startConsole to start the console. If you run into problems starting the console, view the log indicated by the error message and attempt to resolve any problems that you find.
  5. If both the administrative agent and console are running, suspect an IP networking problem.

Parent topic: Troubleshooting an administrative server

Related tasks
Accessing an engine through SSH

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.