Log Files

Unwired Platform log files provide a source of troubleshooting information. Log file information is aggregated and displayed in the Sybase Control Center administrative console.

Accessing server logs

The server log records all system events as per the log level configuration for individual sub-components. For detailed diagnostics, you can configure individual sub-system's log level to DEBUG or TRACE level, and the messages recorded in the server log can help identify the problem. It is not recommended to leave sub-system log levels to those considering the performance impact and growth of the log file when large number of users may be accessing the system. Server log is separate for each server.

Server log settings are controlled from Sybase Control Center. Server log configuration settings changes on the primary server are propagated to other nodes within one minute, and do not require a cluster changing action.

In Sybase Control Center, navigate to Servers > <ServerName> Log node > General tab.

You can also view the server log from the command line using a text editor or any other third-party log viewing tool. (Sybase Control Center helps to view the server log remotely without needing access to the server's file system).

The main server log file is <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs\<hostname>-server.log.
The incoming HTTP requests log (for Data Change Notification, and others) is in the <hostname>-http.log file. You may also see some additional folders which contain log files produced by the internal modules of the Messaging Server. The key folders are JMSBridge and SUPBridge. The messages recorded in those files are controlled by the log level setting of the MSG sub-component of the Unwired Server logging system.

These key sub-systems can help troubleshoot issues:

Data Services – consider modifying this sub-system log level if you are trying to diagnose issues with backend EIS interaction, caching, and Data Change Notification.
MMS – considering modifying this sub-system log level if you are tying to diagnose issues with client interaction, message-based synchronization application activities such as subscription command processing, data import messages, etc., and replication-based synchronization application activities such as those during upload and download phases of the synchronization, data change notification processing, background tasks such as cache refresh, etc. among others.
MSG – consider modifying this sub-system if you are need to look at the individual messages being exchanged between one or more messaging-based synchronization application clients and server.

Accessing domain logs

The domain log shows data only if domain logging is enabled for that domain, and one of the packages in the domain has package-level logging enabled. Domain log data is automatically purged based on the domain log setting for the domain. Domain log is a cluster-wide logical view of the activities and errors.

Navigate to Domains > <DomainName> > Log node > General tab.

Accessing client logs

If client logging is enabled through the client object API, the client logs provide critical information about the application running on the device and its operational state. The client application information is uploaded from the device to Unwired Server, where it is visible using Sybase Control Center.

In the left navigation pane, expand the Packages folder and select the package you want to investigate, then in the right pane, select the Client Log tab.

Server Logs
Server logs provide a view of Unwired Server activity. Status and error messages are collected. You can set the level of granularity for messages captured, and the log file size through Sybase Control Center. In a troubleshooting situation, you may want to increase the granularity of messages captured.
Windows Event Log
Sybase Unwired Platform system messages are logged in the Microsoft Windows application event log.
Domain Logs
The domain log enables an administrator to monitor application activities throughout the system. Detailed views of application activities are available by subsystem. The administrator can review activities in a specific subsystem log view, view correlated data in multiple subsystems, or view a unified log across all subsystems. The administrator must enable logging, and then use log filters to view data of interest.
Client Logs
Client logs capture data about client application operations for all devices subscribed to a package. You can use the data to track errors and identify performance issues.
Unwired WorkSpace Log
You can view the Unwired WorkSpace log in the Error Log view, to see error messages from Unwired WorkSpace, exceptions, and stack traces. When gathering information to diagnose a problem, first collect the Unwired WorkSpace log, and review that information in combination with necessary server log entries (if needed) to diagnose the root cause.
Log File Locations
Use a text editor to review log files from the command line using a text editor if Sybase Control Center is not available, or to concentrate your review to a particular log.

Parent topic: Collecting Information

Related reference

Viewing Messages in Sybase Control Center

Created November 3, 2011. To comment on this topic, go to: DocCommentXchange.