When starting my SA / ASA server, I am getting the error message “Unable to access log file”. What can I do?
A. It is possible that a virus-scanning NLM decided that the .log file was infected with a virus and either moved or deleted it. Make sure that any virus-scanning NLMs are set to ignore both .db and .log files. Q. A request caused a fatal error in the server, and now I can’t shut it down. Now when I try to reload it, I get “This module is ALREADY loaded and cannot be loaded more than once.” A. By definition, a fatal error is one from which we cannot recover. If you’re running SA 5.5 or ASA 6.x, fatal errors are not always handled gracefully. Sometimes the server refuses to shut down cleanly after a fatal error, and the machine must be rebooted. In the second case above, the server didn’t actually shut down at all, but the screen was closed, which made it look like it shut down. Fatal error handling has been cleaned up in ASA 7.0 and later – when a fatal error occurs, the server is immediately shut down. Note that a number of “Module did not release n resources” messages will be display
Related Questions
- How can I resolve this error message that is received when testing the authentication on the ASA: ERROR: Authentication Server not responding: No error?
- When starting my SA / ASA server, I am getting the error message "Cannot open transaction log file -- No such file or directory". What can I do?
- When starting my SA / ASA server, I am getting the error message "Unable to access log file". What can I do?
