Filter
Top Products
Appendix A Logging
ERROR log messages 45
Could not update signatures from network (authorization denied).
The license is not authorized to download micro-updates.
Could not update signatures from network (license verification failed
tid:38977 (No sessions available)). The number of sessions authorized for
this license has been reached.
Could not update signatures from network (microupdate file XXXX
failed the integrity check). The computed checksum is incorrect.
Failed to load checksum file from cache (<filename>) The Cartridge
failed to load a checksum file from disk.
Unable to load symbol <sym> This message is logged when there is a
problem loading the cartridge adapter. It is likely that there will be problems with
subsequent message classification.
Could not create message score. Expect errors related to reading
message scores This message is logged when the cartridge cannot initialize a
new message score. If this message is logged the cartridge will return a score of
zero for this message. This problem should be identified and fixed immediately to
achieve high accuracy.
Could not free per-thread storage for message scores This message is
logged at shutdown when the cartridge cannot free per-thread storage used for
message scores. This will not affect accuracy but implies a resource leak.
Could not update <mu_source> from [network or] disk
(<disk_error|net_error|decode_error>) This message is logged when the
cartridge attempts to update a source from the network or disk but both methods
fail. Cartridge accuracy will be significantly reduced without current micro-
update files, so the problem should be identified and solved as quickly as
possible.
Invalid micro-update interval <interval>, using default interval of 3
hours. This message is logged at startup when the value for “micro-update
interval” in cartridge.cfg is not “auto” or a positive integer.
Invalid cache path <path>, using default value “.”. This message is
logged at startup when the value for “micro-update cache path” in cartridge.cfg is
empty. If the path is specified but is not a directory or cannot be created, a
different message will be logged.