Accessing the PBX logs
PBX uses unified logging. PBX logs are written to the following:
/opt/VRTSpbx/log (UNIX)
install_path\VxPBX\log (Windows)
The unified logging originator number for PBX is 103. See the NetBackup Logging Reference Guide for more information on unified logging.
Error messages regarding PBX may appear in the PBX log or in the unified logging logs for nbemm, nbpem, nbrb, or nbjm. The following is an example of an error that is related to PBX:
05/11/10 10:36:37.368 [Critical] V-137-6 failed to initialize ORB: check to see if PBX is running or if service has permissions to connect to PBX. Check PBX logs for details
To access the PBX logs
- Use the vxlogview command to view PBX and other unified logs. The originator ID for PBX is 103. For more information, see the vxlogview man page.
See also the NetBackup Logging Reference Guide for topics on unified logging.
- To change the logging level for PBX, enter the following:
pbxcfg -s -l debug_level
where debug_level is a number from 0 to 10, where 10 is the most verbose (the default).
To check the current verbosity, enter the following:
pbxcfg -p
PBX may log messages by default to the UNIX system logs (
/var/adm/messagesor/var/adm/syslog) or to the Windows Event Log. As a result, the system logs may fill up with unnecessary PBX log messages, since the messages are also written to the PBX logs:UNIX:
/opt/VRTSpbx/logWindows:
<install_path>\VxPBX\log - To disable PBX logging to the system logs or event logs, enter the following command:
# vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false
You do not have to restart PBX for this setting to take effect.