Support Centre

Find articles, help and advice.

Welcome, Guest Login

Support Center

BES - Debugging the AlertServer

Last Updated: Aug 14, 2014 09:12AM UTC
The AlertServer can be placed into debug in two ways:

1. Direct telnet <bes_server> 40000
    - Option 't' to toggle debug.
2. AlertServer GUI from BES Console

Note: Both methods access the AlertServer maintenance port 40000, and have the same functionality. However, do not leave a session to port 40000 open as this will stop further connections to the port. It should only be open for as long as is required.

AlertServer GUI

To enable debugging, navigate to Tools > Command and select Toggle Debug. This enables debugging (see Figure 1) and the debug messages are written to the POWERPack_Log [$PPLOG/POWERPack_Log]. When debug is enabled, three files are created, populated and stored in $PPLOG:

- SendMessage_Log
- MessageQueue_Log
- AllAlertServerQueue_Log

Note: These files can grow quite large, therefore do not leave AlertServer in debug for too long.

Memory Usage Issues

The Alertserver Java Process can be setup to dump memory usage statistics to a file, to help determine how/why AlertServer is using memory. In order to do this, perform the following tasks:
  • Edit the $PPHOME/bin/AlertServer script from:
          Old: exec ./java -Xmx"$MEMALLOC"m....
          New: exec ./java -Xmx"$MEMALLOC"m -Xrunhprof:file=/tmp/stats.txt....
  • Recycle AlertServer (ppCycle AlertServer)

The Java runtime environment will now collect statistics on memory usage, and AlertServer will run slower as a result but will still be usable. Let the AlertServer run in this state for as long as required, or asked for by Interlink Software support.
  • Dump the statistics to the file: kill -3 <pid of A/S>
  • Remove update from the AlertServer script and recycle AlertServer.
  • Send statistics file to Interlink Software Support.

Message Channel Flooding

A flood occurs when a message channel receives a large volume of messages. During flood conditions, the POWERPackTrans starts to buffer events to control the flow to AlertServer. When a message channel buffer exceeds the 200, 2000, and 5000 message threshold, an alert is sent by the System message channel indicating a buffer threshold has been exceeded for a specific message channel. When the buffer for the message channel reduces in size, and is no longer exceeding a threshold, a clear alert is sent that closes out the previous threshold alert for the message channel. You can interact with the buffered events (e.g. to remove them) by placing the message channel into pause mode with the ppPause command: ppPause -n <MC>.

If you wish to change the thresholds for the incoming event stream, edit the BufferAlert parameter in POWERPackTrans.cfg located in $PPHOME/cfg.
- Global POWERPackTrans transformer options.
  • >> BufferAlert <nnn> <mmm> <ccc>
    • Where: <nnn> = minor
      • <mmm> = major
        <ccc> = critical

Example: BufferAlert 200 2000 5000

The BufferAlert parameter controls the creation of the alert produced by the System message channel. For example, if a message channel suddenly receives 3000 messages, an alert will be displayed in AlertServer:

BufferSize of internal alert stream 3000 exceeds defined threshold 2000.

Contact Us
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found