Consultor Eletrônico

Status: Unverified

GOAL:

What are the different log files available for Progress 9.x and WebSpeed 3.x

GOAL:

An explanation of the different log files contents.

GOAL:

Using Log files to troubleshoot problems.

GOAL:

adc0.exp, ads0.exp, admserv.log, AdminServerSystemOut.log, NS1.ns.log, asbroker1.broker.log, wsbroker1.broker.log, asbroker1.server.log, wsbroker1.server.log, admclnt.log

FACT(s) (Environment):

Progress 9.x
WebSpeed 3.x
OpenEdge 10.x

FIX:

Progress 9.x, WebSpeed 3.x and OpenEdge have more log files than earlier versions due to the Unified Broker strategy and the new components of that strategy.

The following explains what you might find in each log file.

AdminServerSystemOut.log

This log is mostly for AdminServer errors, however it is also used as a default log if there is no other log to write errors and messages to. In most cases, this log has little or no information in it but if the log grows in size there is probably useful information being written to it.

admserv.log

This log is for listing the startup of the AdminServer and all Name Servers and brokers afterward. It reports all transactions generated by the AdminServer managing and/or querying the Name Servers and brokers. It might list errors the occur during startup of any component. Any Java exceptions are reported here and point to the file (ads0.exp). The complete JAVA exception is listed.

NS1.ns.log (or Name Server Name.ns.log)

This log lists the startup of the Name Server and any errors related to the functions of the Name Server. The log shows the brokers (WebSpeed and AppServer) registering with the Name Server, and whether the Name Server has "Load Balancing Enabled" (no message, no load balancing). The NS1.ns.log also reports the inability of the Name Server to find a specific broker that is requested by a client. The standard loggingLevel=2 is recommended for systems in production mode, however it can be increased in order to gather more information (3 should give you all the detail you need).

asbroker1.broker.log (or AppServer Broker Name.broker.log)

This log lists the startup of the AppServer broker and all its AppServers. The server startup parameters are also listed here as well as connects and disconnects from the broker to the servers and all management of the servers. This log might show the errors when a broker fails to start. The standard brkrLoggingLevel=2 shows most errors, however it can be increased to gather more information (3 should give you all the detail you need).

asbroker1.server.log (or AppServer Broker Name.server.log)

This is the log for AppServer servers. Any errors the servers encounter should be listed here. You can expect to see errors (such as 4GL errors) that would usually go to the user in a non-AppServer configuration. The standard srvrLoggingLevel=2 should show most errors, however it can be increased to gather more information (3 should give you all the detail you need).

wsbroker1.broker.log (or WebSpeed Broker Name.broker.log)

This is the log for the WebSpeed broker. The start of the broker and agents, agent startup parameters, and any management to the agents (manual or autoTrim of agents, etc.). The log is defined by its thread information. Each each thread has a different prefix:

- L-3055> is the listener thread of broker, listening on port 3055.

- S-0001> is the server thread to the first agent.

- C-0001> is the client thread, from the HTML client to the broker.

The standard brkrLoggingLevel=2 should show most errors, however it can be increased to gather more information (3 should give you all the detail you need).

wsbroker1.server.log (or WebSpeed Broker Name.server.log)

This is the log for WebSpeed Agents. All errors the servers encounter should be listed here, including startup problems. You can expect to see errors (such as 4GL errors) that usually go to the user in a non-WebSpeed configuration. The standard srvrLoggingLevel=2 should show most errors, however it can be increased to gather more information (3 should give you all the detail you need).

ads0.exp

This file holds all Java exceptions that are reported by the AdminServer. It is an "appended .to" file, so over time, it can become quite large (it can be deleted with no ill effect).

adc0.exp (Windows only)

This file holds all errors encountered when the Progress Explorer communicating with the AdminServer. The file is an "appended to" file, so it can become quite large over time (it can be deleted with no ill effect).
ads0.exp and asc0.exp can be both on Windows 's' stands for server side, 'c' stands for client side for the Progress Explorer.
admclnt.log (Windows only)
This is the AdminServer 'Client' log file. It resides on the machine where Progress Explorer is running.
.