This blog provides a running list of troubleshooting hints and tips for IBM Systems director.
This entry in the Power Implementers blog provides a running list of troubleshooting hints and tips for IBM Systems Director. It will be updated on a regular basis as new troubleshooting information is added. To help you navigate through the troubleshooting hints and tips, please refer to the index following this introduction. I'll include the date the blog was last updated, as well as a date in each section to show when that particular section was added (or updated).
Date Last Updated: 10 June 2013
- Working with Expired User-IDs
- Database Size Exceeded
- Commands to Manage Systems Director Agent on VIOS
Working with Expired User IDs
I was working with a customer environment today that was experiencing problems starting IBM Systems Director. Running the smstatus –r command while ISD was trying to start would eventually return an error indication. The first step in troubleshooting this kind of issue is to look at the messages generated in the lwi error log (/opt/ibm/director/lwi/logs/error-log-0.html).
If the messages in the error log indicate items such as
Couldn't get connection from LWI
then it may be a simple case of resetting the password that Systems Director uses to connect to DB2. The password itself is stored in /opt/ibm/director/lwi/conf/overrides/database.properties and is encrypted, so a command needs to be run to reset the password as follows:
The following messages should be output:
Found properties file - database.properties
Reading file - /opt/ibm/director/bin../lwi/conf/overrides/database.properties
Encrypting passwords for LWI for file /opt/ibm/director/bin../lwi/conf/overrides/database.properties
LWI change password return code = 0
After the password has been changed, Systems Director can be restarted with the smstart command.
Correcting a DISABLED or RESTRICTED account
Another issue that can cause Systems Director to have problems connecting to the database is an expired or restricted user account. This error shows up in the log as follows:
com.ibm.db2.jcc.am.SqlNonTransientConnectionException: [jcc][4.13.80] T2LUW excpetion: SQL30082N Securing processing failed with reason code "19" ("USERID DISABLED or RESTRICTED"). SQLState=00001
You can correct this issue by resetting the user account that Systems Director uses to connect to the database. By default, the user account is dirinst1. The first step is to reset the unsuccessful login count for the user:
The next step is to change the password:
The final step is to clear the password flags for the user. This will reset the lock flag for the user:
After the above commands have been run, Systems Director can be started with the smstart command.
Database Size Exceeded
Systems Director issues can occur when the size of the database exceeds the amount of space available on the file system hosting the database. The documentation for Systems Director recommends a size of 2GB for the database; however, the reality is that the size is dependent on the number of resources being managed and the inventory collected. One of the symptoms of running out of space for the database is failure for discovery and inventory collection operations. In addition, errors with SQLCODE=-289 and SQLSTATE=57011 will be generated in the Systems Director error log (/opt/ibm/director/lwi/logs/error-log-0.html).
The solution to this issue is to ether allocate sufficient disk space to the file system up front or monitor the space being used in the file system and increase the space available as needed. The space available on the file system can be increased with the following command:
The above command will add 5GB of space to the /home file system. (This assumes that unallocated space is available in the logical volume hosting the file system.)
Commands to Manage Systems Director Agent on VIOS
When the Common Agent is installed on a managed end-point, in addition to the agent code itself, commands for stopping, starting, and checking the status of the common agent are also installed. The Information Center for IBM Systems Director documents these commands for the various end-point types, but it doesn't provide documentation for the VIOS server. All of the commands shown in this blog entry need to be run from the VIOS unrestricted shell, which can be entered through the following command:
The commands for managing the common agent on VIOS are listed below.
Stopping the Common Agent. From the unrestricted shell, entering the following command will stop the common agent:
The output from the above command should reflect:
Stopping dirsnmpd. . .
Stopping tier1slp. . .
Stopping cimlistener. . .
The stopagent_vios command stops the Common and Platform agents as well as the Service Location Protocol (SLP); however, it won't stop the cimserver. The cimserver can be stopped with the following command:
The output from the ‘cimserver –s’ command should be:
Starting the Common Agent. From the unrestricted shell, run the following command to start the agent:
The output from the above command should reflect:
Starting cimlistener. . .
Starting tier1slp. . .
Starting dirsnmpd. . .
Starting Director ommon Agent. . .
Waiting for agent process to start up
The command will start the Common and Platform agents as well as the SLP and cimserver services.
Checking the Agent Status. The following command, run from the unrestricted shell, will check the status of the agent:
If the agent is active/started, the command will return "Running." If the agent isn't running, then the command will return "Stopped."