Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator best practices

Command-line tool problems

This topic provides troubleshooting support for 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.
• Just-in-time (JIT) compiler is disabled when you start application server with DEBUG enabled on a Red Hat Linux machine
• The startServer.sh or stopServer.sh commands fail to start or stop the server when the server definition is part of the configuration repository.
• (Windows) With Windows service, there is no indication when a server is already started.
• "ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the dmgr" error message occurs during federation
• The stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname.
• (Windows) (AIX) Entering passwords on the command line

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

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

To fix this problem, do not configure the BBODCFGW job on the dmgr 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 admin console to remove the following DEBUG options of the Java process definition. -Xdebug -Xnoagent

New feature: Beginning in WAS v8.0 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:

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:

startServer.sh webserver1 -nowait

stopServer.sh webserver1 -nowait

With Windows service, there is no indication when a server is already started. (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.

"ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the dmgr" error message occurs during federation

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 dmgr, 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. See the environment file section of the Files Reference website.

The 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, you can stop the server using one of following methods:

• Stop the server process on the operating system (for example, on AIX, HP-UX, Linux, or Solaris computers, issue the kill command).

  Or

• Open a wsadmin tool connection directly to the connector port of the server and call the stop method for the MBean of the server. This method is recommended because it allows ongoing work to shut down gracefully.
  1. Issue the following command to connect to the server:

     wsadmin -host host_name  -port connector_port  -conntype [SOAP | RMI ]
     -user user_ID -password password 

  2. Invoke the stop method on the MBean of the server. For example, in Jython you can use:

     serverMBean = AdminControl.completeObjectName("*,type=Server")
        AdminControl.invoke(serverMBean, "stop")
     

Entering passwords on the command line (Windows) (AIX)

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. If you are using the bash shell on a Windows system, you 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:

gsk7capicmd -keydb -create -db "/tmp/key.kdb" -pw "j\!jj"

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. (Windows)

stopserver server1 -username fn_wasadmin -password $mypass35%% -trace

(AIX)

stopserver server1 -username fn_wasadmin -password '$mypass35%' -trace

Use single quotation marks to specify that what is inside the single quotation marks is to be used. Using single quotation marks can be helpful for any characters that might otherwise have special meaning (like the dollar sign ("$") or the backslash ("\")). Single quotation marks treat these characters literally. In this case, the password being supplied is $mypass35% .

If none of these steps fixes your 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 you don't find your problem listed there contact IBM support.
Troubleshoot help from IBM
Use command-line tools
Use HPEL to troubleshoot applications

Related

Diagnosing and fixing problems: Resources for learning

+

Search Tips   |   Advanced Search