© 2017 Harmonic Inc. All rights reserved.
281
Harmonic MediaGrid Release 4.1
Chapter 9
Troubleshooting
This section provides some troubleshooting information for the Harmonic MediaGrid, including
the following topics:
Verifying the DHCP Server Is Running on the ContentDirectors
Troubleshooting on the ContentBridge
Security with Microsoft Domain Controllers
Understanding Device, USM, and SNMP Errors in SystemManager
Troubleshooting the ContentStore 5840
Troubleshooting a Component, Cluster, or Client Failure
CAUTION:
If you do not understand the procedures or recommendations described in this chapter, please
consult with Technical Support before proceeding.
Harmonic MediaGrid Log Files
The Harmonic MediaGrid provides log files for all of the core services. Utilizing these logs will
assist in determining the root cause of problems or assist engineering in determining problems in
the code. The path to the log files is /var/log/omneon/remote.
Log files include:
ssmd
: SliceServer Manager
mdscore
: MetaData Server
startup
: Core Harmonic MediaGrid Services Startup and Shutdown
mdsckschedule
: Checkpoint Schedule
oujfh
: Provide at support/engineering request
ousd
: Social director
ssmgc
: SliceServer Manager Garbage Collector
The first three log files (ssmd, mdscore, and startup) are the most commonly utilized log files
when troubleshooting Harmonic MediaGrid problems. The logs will rotate and be archived when
they approach or reach 250MB depending upon the system check which is performed hourly.
The files are archived with the format of filename.1.gz, filename.2.gz, etc. The exception to this is
the remotelogs files. The archive depth is presently 13 files deep but can be configured to archive
more files.
Harmonic MediaGrid breaks the log files out by IP address for each of the devices in the cluster.
ContentServers have two log files so long as the IP interfaces are up and active.