Accessing log files not available via console
Contrary to the log files listed before, the following log files cannot be displayed in the console via a node or tab. These log files can be viewed only via the Direct Access node:
- Select the device under a device group or the Device Topology node in the left window pane.
- Select its Direct Access node.
If the Request System Credentials system variable is activated and you have not identified yourself yet to this device in the current session yet, an Identification window appears. - Enter your credentials and click OK .
- Select the File System node and browse the directory structure down to the respective directory under
Installation Directory/master}} or {{client/log
. - Select the log file to display in the right window pane.
- Select the Edit> Edit File
An Edit Text File window opens on the screen with the contents of the file. . - Select the OK button at the bottom to close the window.
Console logs
Two optional log files console.log
and console.xmlrpc
. These can only be found on the master in the default log directory Installation Directory/master/log/HttpProtocolHandler
. They are not generated by default. You can configure the agent to generate these logs via the console.ini
configuration file which is located in the master's Installation Directory/master/config
directory. In this case you need to set the parameters EnableAccessLog
and EnableXmlRpcLog
to true
. If you make changes to these settings the master must be rebooted for them to take effect.
- The
EnableAccessLog
parameter activates the generation of theconsole.log
which logs all http access calls to the CM console. - The
EnableXmlRpcLog
parameter activates the generation of theconsole.xmlrpc
log file which contains the xml content of these calls. Be careful when activating this log, it can become very large very quickly.
Diagnostic logs
The diagnostics tool also generates its own log files, one per scan and device. These files are also located centrally on the master in the Installation Directory/master/log/Diagnostics/<device_deviceID>
directory. Their naming scheme is <device name>_<execution time>
. This file logs all queries that are sent to the database by the master which take longer than a specific time. By default this log file is not generated.
You can configure the settings of this log file and activate it via the Vision64Database.ini
configuration file under the Debug
section which is located in the master's Installation Directory/master/config
directory. If you make changes to these settings the master must be rebooted for them to take effect.
HTTP protocol handler logs
The HTTP Protocol Handler provides two optional log files HttpProtocolHandler.log
and HttpProtocolHandler.xmlrpc
. These can only be found on the master in the default log directory Installation Directory/master/log/HttpProtocolHandler
. They are not generated by default. You can configure the agent to generate these logs via the HttpProtocolHandler.ini
configuration file which is located in the master's Installation Directory/master/config
directory. In this case you need to set the parameters EnableAccessLog
and EnableXmlRpcLog
to true
. If you make changes to these settings the master must be rebooted for them to take effect.
- The
EnableAccessLog
parameter activates the generation of theHttpProtocolHandler.log
which logs all http access calls. - The
EnableXmlRpcLog
parameter activates the generation of theHttpProtocolHandler.xmlrpc
log file which contains the xml content of these calls. Be careful when activating this log, it can become very large very quickly.
Comments
Log in or register to comment.