Status: Verified
GOAL:
Where are the various Progress log files located?
GOAL:
Can the logging level be changed for the various Progress log files?
GOAL:
What information do the various Progress log files contain?
GOAL:
What Progress log file is associated with each product?
GOAL:
Which Progress log file do I use to troubleshoot problems?
FIX:
Progress Log Files:
In Progress version 9.1 the Unified Broker Strategy was introduced which resulted in more log files being available than in earlier versions to make it easier to trace and prevent problems. Log files should not only be used to trace problems but also to avoid them as well as monitor the system and configuration. A database administrator should always check the log files for warnings, messages and errors, especially before and after a backup. The data in a database is, of course, the most important factor, however it is also important to understand that the status of this data, which the log files will give information about, is just as important. The behavior of the applications can also be traced in the log files. Even if everything seems to work perfectly there might be warnings or even errors which should be looked into. To improve the performance of the database and the application the log files offer valuable information.
Location:
Most Progress log files are by default located in the working directory. This can be changed in the ubroker.properties file or preferably with the Progress Explorer connected locally or remotely. In the ubroker.properties you may edit this in the 'brokerLogFile=' field in the definitions. If you use the Progress Explorer it can be done in the 'Logging Setting' in the properties for the broker or the server. The Database log files are placed in the directory where the Database resides, and the location cannot be changed.
Logging level:
For most log files there is an option for how much information you wish to be written to the log files, these are 'Error Level', 'Terse' and 'Verbose'. The default setting is 'Terse' and the following summarizes the differences:
Level 1, Errors and Information:
This includes all error messages and informational messages that are very infrequent. These include startup and shutdown messages that occur once during the life of the session.
Level 2, Terse (the Default):
This includes Level 1 plus information messages that occur very infrequently, but also indicate that the system is operating properly. These include AppServer registration events, client connection and disconnection events, and so on.
Level 3, Verbose:
This includes Level 2 plus informational messages that occur more frequently and might help the client to debug their application. These include messages such client requests to the Application Broker, keep-alive messages from the broker, and logging of each remote procedure execution event.
If you experience some problems with the performance it is advisable to put this to 'Verbose' level for a short time to better monitor and troubleshoot the problem. If you want to report the problem to Technical Support you should do this and supply the engineer handling your call with the appropriate log files. However in a standard situation the 'Error Level' or 'Terse' should be sufficient.
Differences between Broker and Server log files:
For WebSpeed brokers, AppServer brokers and SonicMQ adapters you have two types of log files: one broker and one server (extensions: .broker.log and .server.log). The <name>.broker.log contains information on the startup and shutdown of the broker and all servers. The server startup parameters are also listed here as well as connections and disconnections from the broker to the servers and management of the servers. This file will show the errors when a broker fails to start. The <name>.server.log contains any errors the servers encounter. You can expect to see errors (e.g. 4GL errors) that would usually go to the user.
Short description of the log files
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 Na.me Servers and brokers. It might list the errors that occur during startup of any component. Any Java exceptions are reported here and point to the file ads0.exp where the complete JAVA exception is listed.
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.
ads0.exp
This file holds all Java exceptions that are reported by the AdminServer. It is an "appended to" file, and it can become quite large, but can be deleted with no ill effect.
adc0.exp (Windows only)
This file holds all errors encountered when the Progress Explorer communicates with the AdminServer. The file is an "appended to" file, and can become quite large over time, but can be deleted with no ill effect.
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 of the agents (manual or autoTrim of agents, etc.). The log is defined by its thread information. Each thread has a different Prefix, L-xxx is the listener thread of the broker, listening to a predefined port number, S-xxx is the server thread to the agents, C-xxx is the client thread from the HTML client to the broker. The standard logging level of 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. (S-xxx, date, [PID] initializing WTA server). The standard logging level is 2 and should show most errors, however it can be increased to gather more information, again 3 should give you all the detail you need.
asbroker1.broker.log (or <AppServer Broker NAME>.broker.log)
This file lists the startup of the AppServer broker and all its AppServers. The server startup parameters are also listed here as well as connections and disconnections from the broker to the servers and all management of the servers. This file will show errors when a broker fails to start. Again 2 default logging level is 2 with 3 giving more detail.
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. Again 2 default logging level is 2 with 3 giving more detail.
orabroker1.broker.log
Oracle DataServer Broker generates a log file that contains a detailed record of its activity, including the date and time of significant events. Communication with the NameServer will be written to this log.
odbbroker1.broker.log
The Progress DataServer for ODBC allows the Progress Application Development Environment (ADE) and applications created with Progress in Windows to access certain ODBC-compliant databases, such as DB2, Informix On-line, Microsoft Access, Microsoft SQL Server and Sybase. Information and errors for this area are logged in this file.
sonicMQ.broker.log (or <SonicMQ Broker Name>.broker.log)
This file is related to the SonicMQ adapter. The broker is listening to the client and when the client requests a connection the broker will spawn a Server. If an error occurs at this time it will be written to this log.
sonicMQ.server.log (or <SonicMQ Broker Name>.server.log)
T.his file is related to the SonicMQ adapter. Again the broker is listening to the client and when the client requests a connection, the broker will spawn a Server. If an error occurs during the spawning process, for example, at execution's time or during the spawning process etc, errors are written in this log.
Aia1.aia.log (or <AppServerInternetAdapter-Name>.aia.log)
Each AppServer Internet Adapter (AIA) generates a log file that contains a detailed record of its activity, including the date and time of significant events.
NS1.ns.log (or <Name Server Name>.ns.log)
This file lists the startup of the Name Server and any errors related to the functions of the Name Server. It shows the brokers (WebSpeed and AppServer) registering with the Name Server, and whether the Name Server has load balancing enabled. This file also reports the inability of the Name Server to find a specific broker that is requested by a client. Again 2 default logging level is 2 with 3 giving more detail.
<Database Name>.lg
This log file contains a history of significant database events such as start-up, shutdown, parameter settings and system errors. This file always has a .lg. extension. Old entries can be removed if you want to reduce it's size (use a text editor or the Progress log maintenance command PROLOG). Do not remove any entries while the database is in use. The command PROLOG ('prolog <Database Name>') will remove all except the most resent entries from the file. It is recommended to check the file for grave errors before removing any entries.
Which Progress log file do I use to troubleshoot problems?
Related to
Log files
Name or How to get it:
PC
Dr Watson
Event Viewer
AdminServer
Drwtsn32.log from WINNT directory. Start-Programs-Admin Tools-Event Viewer.Admserv.log, jvmStart.log, Cmdplugin.log, admcInt.log
NameServer
<NameServer>.ns.log
WebSpeed
Broker Log File
Server LogFile
MessengerAdminServer and NameServer
<brokername>.broker.log
<brokername>.server.log
msngr.lo (Msngr cannot connect to Agent)Admserv.log,<NameServer>.ns.log
AppServer
Broker Log File
Server Log File
<broker name>.broker.log
<broker name>.server.log
ODBC DataServer
DataServer Log File
Dataserve.lg
SonicMQ
4GL Adapter:
Broker Log
Server Log
SonicMQ Broker:
<4GLAdapterName.broker>.log
<4GLAdapterName.server>.log
Specified by the properties BROKER_LOG
SQL92
DB Log File
SQLExplorer
ODBC Trace
<DB Name>.lg
sqlexp.log
ODBC Adm-Trace-Start Button
ESQL C / HLC
DB Log Files
<DB Name>.lg
ODBC Merant
ODBC TraceSQL89:
OID Log Files
ODBC Adm-Trace-Start
ButtonProoidrv.log
Apptivity
Log File Specified by property
Apptivity.lo.file
ActiveX
Dr Watson
Event Viewer
Drwtsn32.log
Start-Programs-Adm
Tools-Event Viewer.
Webclient
Client Side:
S.erver Side:
AIA Log FileWeb Server Log File
Jrun and AIA
Start - Programs - PSC WebClient 9.1B - Application Manager - Chose application to Troubleshoot.
<AppServer Internet Adapter-Name>.aia.logDepends on the Type of Web Server.Default-out.log, default-event.log and default-err.log etc.(See KB # 20773)
.