This topic lists additional troubleshooting information for VRC server operation.
The key processes that need to be running for VRC operation are:
VRCServer
mysql
tomcat (grep on security)
LDAP (grep on dcx)
rvrd
The VRC logging structure captures:
User activity
Problems with the dial plan
System activity
System errors
Debugging information
The following table shows where the logging information is captured:
Log file |
User Activity |
Dial Plan Problems |
System Activity |
System Errors |
Debug/Trace |
Internal (server) |
X |
X |
X |
X |
X |
System (server) |
X |
X |
X |
|
|
Audit (server) |
X |
|
|
|
|
User (client) |
per user |
per user |
per user |
|
|
The maximum size of the log file is fixed in the system properties file. As a result, the log file only grows up to the maximum file size. When the maximum size is reached, the log file is backed (into .old file) and a new file with the same name (for example, GdpmInternal.log) is created for logging.
The maximum disk space used for a given log file is twice the size specified in the GDPM properties file.
Debugging information:
Debug logs are located in the /opt/vnm/gdpm/data/log directory.
Can be set from the console for individual VRC subsystems.
Can be set from the gdpm.properties file. This method survives restarts and can be overridden from the console.
If debugging is set from the console, it does not persist through a server restart.