Filter
Top Products
Appendix A Logging
WARN log messages 43
instances, but a large number of warnings indicate a problem with the in-
memory set of signatures.
Could not update signature <sig> from local set ([add/remove]
portion) Incremental micro-update files may contain updates to meta-data
associated with a signature, and this log message indicates a problem updating
signature meta-data.
Unable to parse mime parts of message, skipping This message is
logged when the cartridge is unable to parse the mime parts present in a message.
In this case the network classifier will not compute fingerprints for the message
and the message will be scored with a score of zero.
Statistics reporting is enabled, but “customer id” is set to "none".
Set it to an address of the form
"<companyname>@feedback.cloudmark.com" This message is logged
when statistics reporting is enabled but “customer id” is still set to its default
value of "none".
Invalid configuration directory This message is logged when the cartridge
is configured with an invalid directory containing whitelist.cfg. In this case no
local whitelist entries will be used.
Could not [find | open] config file <file> (<disk_error>), local whitelist
will be disabled This message is logged when the cartridge cannot open or
read the configured whitelist.cfg file. In this case no local whitelist entries will be
used.
Malformed line '<line>', <parse_error>, skipping This message is
logged when the whitelist module could not parse a line in whitelist.cfg. Such
lines will be ignored. Examples include “unknown type”, “missing command or
regex”, “malformed regex”, “missing address”, etc.
Could not save engine information '<string>' --> '<string>'. When
used with CMAE, the cartridge is initialized with engine information such as the
CMAE version string, application name, and so on. This information is saved
within the cartridge and included in statistics reports. This message is logged
when the cartridge could not properly save that information.