Oracle VM Manager error messages are displayed in the user interface, in the Jobs tab, in the object's Events list and are also available in log files. Log files are stored in the following directory on the Oracle VM Manager host computer:
/u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/AdminServer/logs
There a few files of interest here:
access.log: Used to track HTTP access to the Web interface of the Oracle VM Manager and to the underlying Oracle WebLogic Server HTTP interface. This log can be used to track access and HTTP operations within Oracle VM Manager to help debug access issues and to audit access to the Oracle VM Manager.AdminServer.log: Used to track events within the underlying Oracle WebLogic Server framework, including events triggered by Oracle VM Manager. This log can be used to track a variety of issues within Oracle VM Manager including TLS/SSL certificate issues, server availability issues, and any actions performed within Oracle VM Manager which are usually identifiable by searching for items containing the stringcom.oracle.ovm.mgr. Log in failures resulting from locked accounts (as opposed to incorrect credentials) are also in this file.AdminServer-diagnostic.log: Used to track exceptions within the underlying Oracle WebLogic Server framework, including particular events triggered by Oracle VM Manager such as log in failures due to incorrect credentials. This log can be used to track Oracle VM Manager behavior that results in an exception or for log in failure, which can be tracked by searching for the stringAn incorrect username or password was specified.
Since log file format is determined by Oracle WebLogic Server, many of
these files may be difficult to read. A log parsing tool is
included with Oracle VM Manager to help extract useful information from
the actual log files. The log parsing tool is named
OvmLogTool.py and is located at:
/u01/app/oracle/ovm-manager-3/ovm_tools/bin
OvmLogTool.py can do three useful things:
Convert and combine all the AdminServer log files into one easier-to-read file.
Create a filtered summary log file that only lists errors.
Tail the AdminServer log, applying the filtering on the fly.
Usually analysis of the logs starts by generating an error summary log. The summary file can act as an index into the filtered file to investigate and analyze errors, providing you with time stamps an a shortened summary of each error that may need further investigation. To generate a summary log file, do the following:
# python OvmLogTool.py -s -o summary
processing input file: /u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/
AdminServer/logs/AdminServer.log00001
processing input file: /u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/
AdminServer/logs/AdminServer.log
This generates a file named summary in the
local directory. You can use this to look for
errors that occurred within Oracle VM Manager.
To get a full log of all events and errors within Oracle VM Manager you can do the following:
# python OvmLogTool.py -o filteredlog
processing input file: /u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/
AdminServer/logs/AdminServer.log00001
processing input file: /u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/
AdminServer/logs/AdminServer.log
This generates a file named filteredlog in
the local directory. You can use this to look for all events
that occurred within Oracle VM Manager.
Finally, you can use OvmLogTool.py to
filter results on the fly while tailing the log:
# python OvmLogTool.py -t
tailing log file: /u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/
AdminServer/logs/AdminServer.logUse Ctrl+C to exit the program when you have finished tailing the log file.