Summary: Isode components write to logging streams when events occur.
Facility ALERTD
Messages relating to the Alert Daemon
Name | Severity | ID | Description | Action |
---|---|---|---|---|
BadSomData | error | 211 | A data item read from a SOM result does not have the expected format. | Correct configuration error |
ChannelMissing | error | 204 | The Alert Daemon's XML file is misconfigured. | Correct configuration error |
CheckThreadFail | error | 218 | Failed to create a thread to check for configuration changes | Contact Isode support |
DuplicateIntKey | error | 215 | The list of SOM attribute types has a duplicate key | Correct configuration error |
DuplicateStringKey | error | 216 | The list of SOM attribute types has a duplicate key | Correct configuration error |
FindNextChangeNotificationFail | error | 221 | A call to FindNextChangeNotification failed | Contact Isode support |
InvalidFilter | error | 203 | The Alert Daemon's XML file is misconfigured. | Correct configuration error |
ItemMissing | fatal | 201 | The Alert Daemon's XML file is missing a mandatory item. | Correct configuration error |
Level1Alert | warning | 254 | A Level 1 Alert has been generated. The message identifies the monitor which gave rise to the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level1AlertChannel | notice | 259 | A Level 1 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level1AlertMta | notice | 264 | A Level 1 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level2Alert | warning | 253 | A Level 2 Alert has been generated. The message identifies the monitor which gave rise to the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level2AlertChannel | warning | 258 | A Level 2 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level2AlertMta | warning | 263 | A Level 2 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level3Alert | error | 252 | A Level 3 Alert has been generated. The message identifies the monitor which gave rise to the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level3AlertChannel | error | 257 | A Level 3 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level3AlertMta | error | 262 | A Level 3 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level4Alert | fatal | 251 | A Level 4 Alert has been generated. The message identifies the monitor which gave rise to the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level4AlertChannel | fatal | 256 | A Level 4 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level4AlertMta | fatal | 261 | A Level 4 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level5Alert | critical | 250 | A Level 5 Alert has been generated. The message identifies the monitor which gave rise to the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level5AlertChannel | critical | 255 | A Level 5 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
Level5AlertMta | critical | 260 | A Level 5 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert. | Investigation will depend upon the specific monitor which has triggered the alert. |
ServerShutdown | notice | 213 | The alertd process is stopping. | No Operator Action |
ServerStartup | notice | 212 | The alertd process is starting up. | No Operator Action |
ShutdownHandleCreateFail | error | 219 | Failed to create handle for shutdown | Contact Isode support |
SomDataItemNotFound | error | 208 | The specified SOM data item could not be located. | Correct configuration error |
SomInitFail | fatal | 217 | Failed to initialize SOM interface | Contact Isode support |
SomInvalid | fatal | 202 | The Alert Daemon's XML file is misconfigured. | Correct configuration error |
SomOperation | error | 207 | A call to the specified SOM operation failed. Channel and MTA names may have been included in the operation's Selector | Correct configuration error |
SomSessionCallback | error | 209 | Failed to set up a callback routine | Correct configuration error |
SomSessionClose | error | 214 | A call to SOMSessionClose failed. | Correct configuration error |
SomSessionCreate | error | 205 | A call to SOMSessionCreate failed. | Correct configuration error |
SomSessionOpen | error | 206 | A call to SOMSessionOpen failed. | Correct configuration error |
SomUnknownKey | error | 210 | A filter item specifies an unknown key | Correct configuration error |
WaitMultipleObjectsFail | error | 222 | A call to WaitMultipleObejcts failed | Contact Isode support |
WatcherHandleCreateFail | error | 220 | Failed to create handle for file watch | Contact Isode support |
XMLerror | fatal | 200 | The Alert Daemon's XML file contain a parse error. | Correct configuration error |
XMLerror
- Message Text
- XML error in config file: %1
- Parameters
- Detail of the error
- Description
- The Alert Daemon's XML file contain a parse error.
- Action
- Correct configuration error
ItemMissing
- Message Text
- XML item missing in config file: %1
- Parameters
- Detail of the error
- Description
- The Alert Daemon's XML file is missing a mandatory item.
- Action
- Correct configuration error
SomInvalid
- Message Text
- The Monitor specification named %1 has an invalid SOM connection id
- Parameters
- Detail of the error
- Description
- The Alert Daemon's XML file is misconfigured.
- Action
- Correct configuration error
InvalidFilter
- Message Text
- The Monitor %1 %2
- Parameters
- Monitor name
- Detail of the error
- Description
- The Alert Daemon's XML file is misconfigured.
- Action
- Correct configuration error
ChannelMissing
- Message Text
- The Monitor %1 specifies an MTA name but no channel name
- Parameters
- Monitor name
- Description
- The Alert Daemon's XML file is misconfigured.
- Action
- Correct configuration error
SomSessionCreate
- Message Text
- Failed to create a SOM session: %1
- Parameters
- Error string
- Description
- A call to SOMSessionCreate failed.
- Action
- Correct configuration error
SomSessionOpen
- Message Text
- Failed to open a SOM session (%1): %2
- Parameters
- Connection key
- Error string
- Description
- A call to SOMSessionOpen failed.
- Action
- Correct configuration error
SomOperation
- Message Text
- %1 operation failed (chan:%2, mta:%3): %4
- Parameters
- Operation name
- Channel name (if any)
- MTA name (if any)
- Error text
- Description
- A call to the specified SOM operation failed. Channel and MTA names may have been included in the operation's Selector
- Action
- Correct configuration error
SomDataItemNotFound
- Message Text
- SOM data item type %1 not found in result
- Parameters
- Data item type
- Description
- The specified SOM data item could not be located.
- Action
- Correct configuration error
SomSessionCallback
- Message Text
- Failed to setup SOM %1 callback: %2
- Parameters
- Callback type
- Error string
- Description
- Failed to set up a callback routine
- Action
- Correct configuration error
SomUnknownKey
- Message Text
- Unknown filter item key %1
- Parameters
- FilterItem key
- Description
- A filter item specifies an unknown key
- Action
- Correct configuration error
BadSomData
- Message Text
- Bad SOM data value, expected type %1, value %2
- Parameters
- Expected data type
- Actual value
- Description
- A data item read from a SOM result does not have the expected format.
- Action
- Correct configuration error
ServerStartup
- Message Text
- Starting %1 with service %2
- Parameters
- Program name
- Service name
- Description
- The alertd process is starting up.
- Action
- No Operator Action
ServerShutdown
- Message Text
- Stopping %1 (service %2)
- Parameters
- Program name
- Service name
- Description
- The alertd process is stopping.
- Action
- No Operator Action
SomSessionClose
- Message Text
- Failed to close a SOM session (%1): %2
- Parameters
- Connection key
- Error string
- Description
- A call to SOMSessionClose failed.
- Action
- Correct configuration error
DuplicateIntKey
- Message Text
- Duplicate SOM attribute type %1
- Parameters
- Attribute key
- Description
- The list of SOM attribute types has a duplicate key
- Action
- Correct configuration error
DuplicateStringKey
- Message Text
- Duplicate SOM attribute type %1
- Parameters
- Attribute key
- Description
- The list of SOM attribute types has a duplicate key
- Action
- Correct configuration error
SomInitFail
- Message Text
- SOMInit failed: %1
- Parameters
- Detail of the error
- Description
- Failed to initialize SOM interface
- Action
- Contact Isode support
CheckThreadFail
- Message Text
- Failed to create tailoring check thread
- Description
- Failed to create a thread to check for configuration changes
- Action
- Contact Isode support
ShutdownHandleCreateFail
- Message Text
- Failed to create handle for shutdown
- Description
- Failed to create handle for shutdown
- Action
- Contact Isode support
WatcherHandleCreateFail
- Message Text
- Failed to create handle for file watch
- Description
- Failed to create handle for file watch
- Action
- Contact Isode support
FindNextChangeNotificationFail
- Message Text
- FindNextChangeNotification failed: %1
- Parameters
- Detail of the error
- Description
- A call to FindNextChangeNotification failed
- Action
- Contact Isode support
WaitMultipleObjectsFail
- Message Text
- WaitMultipleObjects failed: %1
- Parameters
- Detail of the error
- Description
- A call to WaitMultipleObejcts failed
- Action
- Contact Isode support
Level5Alert
- Message Text
- Alert %1 (%2): %3
- Parameters
- Monitor name
- Monitor description
- Detail of the Critical event
- Description
- A Level 5 Alert has been generated. The message identifies the monitor which gave rise to the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level4Alert
- Message Text
- Alert %1 (%2): %3
- Parameters
- Monitor name
- Monitor description
- Detail of the Fatal event
- Description
- A Level 4 Alert has been generated. The message identifies the monitor which gave rise to the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level3Alert
- Message Text
- Alert %1 (%2): %3
- Parameters
- Monitor name
- Monitor description
- Detail of the Error event
- Description
- A Level 3 Alert has been generated. The message identifies the monitor which gave rise to the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level2Alert
- Message Text
- Alert %1 (%2): %3
- Parameters
- Monitor name
- Monitor description
- Detail of the Warning event
- Description
- A Level 2 Alert has been generated. The message identifies the monitor which gave rise to the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level1Alert
- Message Text
- Alert %1 (%2): %3
- Parameters
- Monitor name
- Monitor description
- Detail of the Notice event
- Description
- A Level 1 Alert has been generated. The message identifies the monitor which gave rise to the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level5AlertChannel
- Message Text
- Alert %1 (%2): %3 on channel %4
- Parameters
- Monitor name
- Monitor description
- Detail of the Critical event
- Channel name
- Description
- A Level 5 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level4AlertChannel
- Message Text
- Alert %1 (%2): %3 on channel %4
- Parameters
- Monitor name
- Monitor description
- Detail of the Fatal event
- Channel name
- Description
- A Level 4 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level3AlertChannel
- Message Text
- Alert %1 (%2): %3 on channel %4
- Parameters
- Monitor name
- Monitor description
- Detail of the Error event
- Channel name
- Description
- A Level 3 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level2AlertChannel
- Message Text
- Alert %1 (%2): %3 on channel %4
- Parameters
- Monitor name
- Monitor description
- Detail of the Warning event
- Channel name
- Description
- A Level 2 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level1AlertChannel
- Message Text
- Alert %1 (%2): %3 on channel %4
- Parameters
- Monitor name
- Monitor description
- Detail of the Notice event
- Channel name
- Description
- A Level 1 Alert has been generated for a channel. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level5AlertMta
- Message Text
- Alert %1 (%2): %3 on channel %4, mta %5
- Parameters
- Monitor name
- Monitor description
- Detail of the Critical event
- Channel name
- MTA name
- Description
- A Level 5 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level4AlertMta
- Message Text
- Alert %1 (%2): %3 on channel %4, mta %5
- Parameters
- Monitor name
- Monitor description
- Detail of the Fatal event
- Channel name
- MTA name
- Description
- A Level 4 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level3AlertMta
- Message Text
- Alert %1 (%2): %3 on channel %4, mta %5
- Parameters
- Monitor name
- Monitor description
- Detail of the Error event
- Channel name
- MTA name
- Description
- A Level 3 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level2AlertMta
- Message Text
- Alert %1 (%2): %3 on channel %4, mta %5
- Parameters
- Monitor name
- Monitor description
- Detail of the Warning event
- Channel name
- MTA name
- Description
- A Level 2 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.
Level1AlertMta
- Message Text
- Alert %1 (%2): %3 on channel %4, mta %5
- Parameters
- Monitor name
- Monitor description
- Detail of the Notice event
- Channel name
- MTA name
- Description
- A Level 1 Alert has been generated for a peer MTA. The message contains the name of the specific monitor triggering the alert.
- Action
- Investigation will depend upon the specific monitor which has triggered the alert.