CHAPTER G G - 42
Explanation: The scan engine is not responding to the keep-alive messages and it
has not reported scan nor initialization statuses for a limited time period (300 sec-
onds). The problem may be in a file which the scan engine is scanning. If the user
can recognize the source as a problematic file, the user should make a bug report
and send a file sample to F-Secure.
Resolution: fsavd shuts down the scan engine process and restarts the scan engine.
Could not open logfile <file path>: <OS error message>
Explanation: fsavd failed to open the logfile <file path> for logging.
Resolution: fsavd writes logs to default logfile (stderr). The user may reconfigure the
logfile location and restart fsavd.
Cannot change working directory to '<file path>'.
Explanation: fsavd failed change working directory database directory.
Resolution: fsavd tries to continue using the current directory as working directory.
ERRORS
Failed to open scan engine shared library.
Explanation: fsavd cannot find required scan engine shared library files which are
normally found from <install directory>/lib.
Resolution: fsavd exits with error status. Installation or engine directory in configura-
tion file maybe incorrect or --enginedirectory command-line option has incorrect
path.
Failed to load required symbol from scan engine library.
Explanation: fsavd finds required scan engine shared library files but fails to load cor-
To Next Page
Loading...