Checking Log Files

Log files contain detailed information about the operation of the PowerMedia WMS. This information may be useful in troubleshooting issues that may arise during application development and deployment. Tracing a call through the log files also can help one to become familiar with the operation of the PowerMedia WMS.

Log files are stored in the directory /var/snowshore/logs. The log files and their description (including PowerMedia WMS component if applicable) are provided below. See also Log Naming Convention for information on the naming convention for log files.

File

Contents

PowerMedia WMS Component

accounting.log

Clear text log created from Generate Accounting Logs option in Configure Logs page of Web User Interface (Web UI).

 

audit.log

All SNMP sets and user configuration changes made through the Web UI. (PowerMedia WMS persisted settings.)

Web UI

cache.log

Squid cache processes.

HTTP

cache_access.log

Squid cache accesses.

Cache

fido.log

Messages associated with fetching Internet domain objects

FIDO

lighttpdaccess.log

Used by RESTful web server.

web_service.fcgi

lighttpderror.log

Used by RESTful web server.

web_service.fcgi

messages.log

Messages written when the Syslog option is enabled.

Syslog

msaccounting.log

Encrypted log created from Generate Accounting Logs option in Configure Logs page of Web UI.

 

mserv.log

Details of creating and managing RTP streams on the PowerMedia WMS. 

MServ

msinit.log

Log entries of the PowerMedia WMS initialization.

MSInit

msprovider.log

License information. 

MSProvider

restfulwslog.txt

Used by RESTful web server.

web_service.fcgi

rtspc.log

RTSP information.

RTSPC

<hostname>_system_
info.log

System information log file created from Gather System Information option in Configure Logs page of Web UI.

 

snowshore_additional_install.log

Used to verify installation or upgrade.

 

To troubleshoot, you can generate the system information log file at the time an issue occurs. To generate this log file:

  1. Log in to the PowerMedia WMS Web UI.

  2. Select Logs>Configure to display the Configure Logs page.

  3. Click the Create button next to System Configuration Log.

  4. Click OK. The Log Files page is displayed and the log file called <hostname>_system_info.log is created.

Note: Be aware that logging affects system performance. Increasing the number of logs enabled and the level of detail requested may adversely affect system performance.

For more information about logging, see Logs Menu.

Checking Network Connectivity

If a call cannot be successfully placed, check that there is connectivity to the required networks.

  1. Ping the devices used in the call. Using Network>Utilities>Ping from the Web UI, try pinging the application server IP address and the IP address of the RTP device.

  2. If either ping command fails, select Network>Configure>Interfaces. Check to ensure that the interfaces are active and that one of the interfaces is designated as supporting RTP.

  3. Check the routing table for routes, network masks, and default gateways using Network>Configure>Interfaces.

Recovering after a Power Failure

When a system reboots, it does a file system check. Under most circumstances, the system recovers automatically and reboots. In rare circumstances, the system can have issues and be unable to recover the file system. In this case, use the following procedure.

  1. Connect to the serial port of the PowerMedia WMS.

  2. Power up the system and watch the terminal page. As the file check happens, it can find bad files that need to be repaired.

  3. When asked to repair a file, type y.

At the end of this process, the system should reboot and recover.

Note: It is recommended that a UPS be used to power the system to avoid issues from power fluctuations.