Versions Compared

Old Version 1

changes.mady.by.user Copy Page Tree

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: link corrected

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

Table of contents

Table of Contents
excludeTable of contents
stylesquare

Description

Use this option to change alert management settings as shown below:

Settings

Mail mode (TEXT/HTML)

Alerts are by default sent in HTML format. With some mail clients, HTML mails are not correctly displayed or even rejected. This option is used to switch between HTML format and pure TEXT format.

Div
classpagebreak

 


HTML mail example:

 


TEXT mail example:

Mail recipients list

All alerts coming from monitoring scripts and checks scripts are sent using a common alert script that sends emails (via "sendmail") to the recipients list that can be defined using this option.

...

(warning) Do not add blank lines and set one recipient per line

Div
classpagebreak

 


Create/update alert mail footer

Used to add comments at the end of the mail.

(lightbulb) HTML tags like new line, font and bold can be added within the file. In case the format is switched to TEXT, these tags will be automatically removed from the text mail.

Example:

Enable/disable wall alert messages

This option enables or disables (default) the "wall" messages sent via the alert script.

 
Div
classpagebreak


Update/reinstall common alert script

All alerts coming from monitoring scripts and checks scripts are sent using a common alert script.

...

The table below lists all available values for parameter 1 in case you plan to customize the scripts and send alerts by your own (monitoring software lines of commands, snmptrap, etc...)

 
Div
classpagebreak


Parameter 1 can have the following values:

Parameter 1

Severity

Description

ABORTEDCRITICALGuest has stopped without user or service request

AKSUSBFAIL

CRITICAL

If the dongle is detected as removed whereas it is disconnected, the askusb daemons are restarted. If the restart fails after 15 tries, this message is sent

BOOTDUPL

WARNING

Tried to start a guest that is already running or a guest is found more than once in the guests list

BOOTNOTFND

CRITICAL

The file containing the guests to start is empty or not found

EMULSTART

INFORMATIONAL

Emulator has been started

EXPCHK

CRITICAL, MAJOR, MINOR, INFORMATION

The license is about to expire

FOUND

INFORMATIONAL

License dongle found at startup

HASPWARN

CRITICAL

Warning messages found in the license, guests cannot start

IFCFGADDRCRITICALThe network interface defined in the configuration has already an assigned IP address, cannot be used for guest
IFCFGCRITCRITICALOne parameter in the ifcfg-ethN file is not configured correctly (mandatory value)
IFCFGUNKNCRITICALThe interface name defined in the configuration file is not valid (not found with 'ifconfig <eth>' command)
IFCFGWARNWARNINGOne parameter in the ifcfg-ethN file is not configured correctly (recommended value)

INVALID

CRITICAL

Invalid configuration on dongle to start the guest

NOTFOUND

CRITICAL

The guests have not been able to start at boot due to dongle disconnected

REMOVED

CRITICAL

Dongle has been removed: the guest sees the dongle as disconnected and will stop after the defined interval if the dongle is not replaced

REMOVRESET

ERROR

Dongle seen as removed whereas not disconnected (aksusb driver failure). In this case the USB is reset and drivers are restarted ((warning) Not valid if the dongle is a network dongle and then located on another server)

STOPPED

CRITICAL

Guest has been stopped, reasons explained in parameters 4, 5 and 6

STOPPEDREQINFORMATIONALGuest has been stopped, requested by user or shutdown
TESTMAILINFORMATIONALUsed to test email mode when setting HTML or pure TEXT

TOEXIT

CRITICAL

The guest is about to exit, reasons explained in parameters 4 and 5

USBDISCONNECT

MAJOR

Dongle has been removed (immediate detection)

Div
classpagebreak

 


Select guests log alert level

Select the alert level to send alerts when events are found in the guest log file:

LevelInformationWarningError
0(error)(error)(error)
1(tick)(tick)(tick)
2(error)(tick)(tick)
3(error)(error)(tick)

(blue star) Requires the "charon_logevent" entry activated in the "crontab" file => menu option "Manage recursive jobs: license expiration check, log events (cron)"

(info) This does not affect guest startup alerts. You will receive alerts when a guest starts or stop whatever the level is.

Div
classpagebreak

 


View alerts history

This option will allow you to view the alerts history sent via the alert script. Alerts can be viewed in a continuous way or using a text editor.

...

  1. A message telling the emulator is started
  2. A message telling the license (main one) is found and that also displays its expiration date
  3. The main license dongle has been unplugged and the aksusbd monitor reported the alert (immediate). We can see one license (backup one) is still connected
  4. The license dongle was plugged in again.
    (info) We do not see here any dongle removal alert reported by the emulator itself, this is because by default the emulator checks for dongle presence every 1 hour (deferred)

 


(lightbulb) Press CTRL-C to get back to the previous menu

 
Div
classpagebreak


License expiration alerts from guests

This option will toggle on/off the WARNING alerts sent from the guest log file. By default these alerts are sent once per hour 120 hours before expiration whatever the license interval check is set to.

...