Configure server log properties to specify the amount of detail that is written to the log, as well as the duration of the server log life cycle. Server log properties are only set on the primary node; property settings on secondary nodes are read-only.
How changes are applied in a cluster depends on whether you are configuring a primary or secondary server. Sybase recommends you only configure log settings on the primary server. If you change the setting on a secondary server, the configuration is updated only for that server and is temporary (eventually the primary settings are propagated to all servers in the cluster).
Additionally, you should always use Sybase Control Center to configure server logs. If you manually edit the configuration file, especially on secondary servers in a cluster, the servers may not restart correctly once shut down.
- In the left navigation pane, expand the Servers folder and select the server to configure.
- Select Log.
- In the right administration pane, click the Settings tab.
- The option "Rollover server log on server restart" is set by default. When selected, this option means a new version of the log file is created after server restart, and the old one is archived.
- Set the server log size and backup behavior that jointly determine the server log life cycle.
- Set the Maximum file size, in kilobytes, megabytes, or gigabytes, to specify the maximum size that a file can reach before a new one is created. The default is 10MB.
Alternatively, select No limit to log all events in the same file, with no maximum size.
- Set the Maximum backup index to determine how many log files are backed up before the oldest file is deleted. The index number you choose must be a positive integer between 1 and 65535. The default is 10 files.
Alternatively, select No limit to retain all log files.
- For each components, choose a log level:
| Component |
Default Log Level |
|---|
| MMS |
Info |
| PROXY |
Info |
| MSG |
Info |
| Security |
Info |
| Mobilink |
Info |
| DataServices |
Info |
| Other |
Warn |
| DOEC |
Info |
Note: DOEC only appears if you run the DOEC installer after installing SUP cluster.
| Log level |
Messages logged |
|---|
| All |
Complete system information |
| Trace |
Finer-grained informational events than debug |
| Debug |
Very fine-grained system information, warnings, and all errors |
| Info |
General system information, warnings, and all errors |
| Warn |
Warnings and all errors |
| Error |
Errors only |
| Console |
Messages that appear in the administration console only (when Unwired Server is running in non-service mode) |
| Off |
Do not record any messages |
- Click Save.
Log messages are recorded as specified by the settings you choose. The log file is located in:
<UnwiredPlatform_InstallDir>\<UnwiredPlatform>\Servers\UnwiredServer\logs\<hostname>-server.log.
Log life cycle default example
If you keep the default maximum file size and default index, an Unwired Server writes to the log file until 10MB of data has been recorded. As soon as the file exceeds this value, a new version of the log file is created (for example, the first one is <hostname>-server.log.1). The contents of the original log are backed up into this new file. When the <hostname>-server.log file again reaches its limit:
- The contents of <hostname>-server.log.1 are copied to <hostname>-server.log.2.
- The contents of <hostname>-server.log are copied to <hostname>-server.log.1.
- A new copy of <hostname>-server.log is created.
This rollover pattern continues until the backup index value is reached, with the oldest log being deleted. If the backup index is 10, then <hostname>-server.log.10 is the file removed, and all other logs roll up to create room for the new file.