Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Moved GF login steps

Table of Contents

Log Files Generated by the Controller

...

To change the default location or names of the Controller logs

...

  1. In a web browser, log in to the Controller's Glassfish administration console, as described in

...

  1. Access the

...

  1. Administration Console.

...

  1. From the left-side navigation tree, expand Configurations -> server-config and click Logger Settings.

...

  1. Set the new location for server.log by modifying the Log File value.
    The default value points to the logs directory located at the root of the Controller home directory.

    No Format

...

  1. ${com.sun.aas.instanceRoot}/../../../../logs/server.log

...

  1.  If you specify a directory that does not exist, it is created when you restart the application server.

...

  1. Change the database.log location by opening the <Controller_Installation_Directory>/db/db.cnf file.

...

  1. Set the value of the log-error property to the new location of the database.log file. This directory location must exist before you restart the Controller or you will get start-up errors.

...

  1. Change the startAS.log location by opening the <Controller_Installation_Directory>/bin/controller.sh file.

...

  1. Edit the log location specified in the following line to reflect the new location:

    No Format

...

  1. nohup ./asadmin start-domain domain1 > $INSTALL_DIR/logs/startAS.log

...

...

  1.  

  2. Open the <Controller_Installation_Directory>/appserver/glassfish/domains/domain1/config/domain.xml file, and change the log location specified in the following:

    • log-root attribute of the domain element.

    • file attribute of the log-service element.

    • tx-log-dir attribute of the transaction-service element.

...

  1. Copy if desired any existing logs from the default directory (<Controller_Installation_Directory>/logs) to the new location.

...

  1. Restart the Controller. See Start or Stop the Controller.

...

  1. Verify that the database.log, server.log, and startAS.log files are being written to the new location and remove the old log files.

Configuring Debug Logging for the Controller

...

By default, the Controller generates logs at the INFO level. You can change the level for one or all of the components. This may be needed, for example, when you are debugging your system, and want the Controller to generate more information in the form of logs. On the other hand, you may wish to reduce logging verbosity to minimize the reduce the rate of growth of log files. The following steps describe how to change the default log levels.1.

  1. In a web browser, log in to the Controller's Glassfish administration console, as described in

...

  1. Access the

...

  1. Administration Console.

...

  1. From the left-side navigation tree, expand Configurations -> server-config and click Logger Settings.

...

  1. Click the Log Levels tab.

...

  1. Modify those components that start with "com.appdynamics". By sorting the list by name, you can quickly access the com.appdynamics components. For each component, modify the log level by choosing a new level from the Log Level menu. For example, to debug the system, we suggest setting the log level to FINE.

...

  1. Click Save.

...

Accessing the Glassfish Admin Console

You can view and modify general Controller logging behavior from the application server's administration console. The log-related settings include log levels, the log file location, and log rotation thresholds.

To access log-related settings in the administration console

1. In a web browser, open the following URL:

No Format

http://<Controller-Host>:4848

Note that port 4848 is the default port number for the administration console. This value is determined by the port set for the network-listener named admin-listener in the domain.xml file.

Also note that for security reasons the server does not accept remote connections by default. If you attempt to access the console remotely, you will see the following error: "Secure Admin must be enabled to access the DAS remotely."

2. Log in using "admin" as the username and, for the password, enter the value contained in the <controller_install_directory>/.passwordfile file.

3. From the left-side navigation tree, expand Configurations -> server-config and click Logger Settings.

Learn More