+

Search Tips   |   Advanced Search

(dist)(iseries)

Command-line tool problems

Troubleshoot a variety of problems relating to using command-line tools.

What kind of problem are you having?


The addNode.sh script or BBOWADDN job fails during node federation.

This error occurs only if the BBODCFGW job is run on the deployment manager during customization. The BBODCFGW adds an unmanaged node with a Web server to the deployment manager, causing the node federation from a base server to fail.

To fix this problem, do not configure the BBODCFGW job on the deployment manager until all nodes are federated into the cell. Also, do not add any unmanaged nodes into the cell until all node are federated. A web server can be configured on a managed node without any problems.


Just-in-time (JIT) compiler is disabled when you start the application server with DEBUG enabled on a Red Hat Linux machine

The just-in-time (JIT) compiler is disabled when you start the application server with Software Developer Kit (SDK) DEBUG enabled on a Red Hat Linux machine, even though JIT is set to enabled. To verify this setting, check the SystemOut.log or the startServer.log file.

Use the console to remove the following DEBUG options of the Java process definition. -Xdebug -Xnoagent

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.


The startServer.sh or stopServer.sh commands fail to start or stop the server when the server definition is part of the configuration repository

This problem occurs when the startServer.sh or stopServer.sh commands are trying to start or stop non Java process. To solve this problem, use the -nowait option to start or stop the server, for example:

(iseries)


No indication that a server is already started on Windows

When attempting to start an already-started server from the command line, there is no indication that the server is already started and running. When running startManager.bat on Windows the following output is displayed before the command returns:

ADMU7701I: Because dmgr is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.

When running startServer.bat, the following output is displayed before the command returns:

ADMU7701I: Because server1 is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.

When running WASService.exe, the following output is displayed before the command returns:

Start Service: service name

To check if the server is started or if the service is running, use the serverStatus server_name command or the WASService -status service_name command.


Use one or more % characters as part of the value for a parameter

The % character is a special character used by the Microsoft Windows operating systems. If we are running on a Microsoft Windows operating system, and you are:

We must use two % characters (%%) for each % character contained in the parameter value to prevent the % characters that are part of the parameter value from being consumed by the operating system.

For example, to use was%admin as the value of the -password parameter, specify the following command:

wsadmin.bat -username wsadmin -password was%%admin

instead of:

wsadmin.bat -username wsadmin -password was%admin


ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager

The workaround for this problem is to adjust the time on the node to be within the recommended amount of the deployment manager. Verify that the time zones are correct and that the times within the time zones are correct. For AIX systems, if the time on the node system is within five minutes of the deployment manager, review the timezone setting in the /etc/environment file. Verify that the TZ= property is set correctly. For example, in the Central Time Zone, it should read TZ=CST6CDT. For more information, see the environment file section of the Files Reference website.


stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname

If the stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname, we can stop the server using one of following methods:


Entering passwords on the command line

There are operating system differences when specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. For the bash shell on a Windows system, we can use the UNIX conventions.

On Unix type operating systems, it is usually better to always encapsulate string values associated with all tags in double quotes (""). You will also need to escape, using a '\' character, the following characters if they appear in the string values: '!', '\', '"', '`'. This will prevent some command line shells from interpreting specific characters within these values.

Some examples of usage follow:

When prompted by gsk7capicmd for a value (for example a password) quoting the string and adding the escape characters should not be done because the shell is no longer influencing this input.


Avoid trouble: In general, for ws_ant.sh scripts, use single quote for strings containing special characters:

gotcha

If none of these steps fixes the problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes). If we don't find the problem listed there contact IBM support.


Related concepts

  • Troubleshooting help from IBM


    Related tasks

  • Use command-line tools
  • Use High Performance Extensible Logging to troubleshoot applications

  • Diagnose and fix problems: Resources for learning