![Harmonic MediaGrid Installation And Configuration Manual Download Page 283](http://html1.mh-extra.com/html/harmonic/mediagrid/mediagrid_installation-and-configuration-manual_3962095283.webp)
Chapter 9 Troubleshooting
© 2017 Harmonic Inc. All rights reserved.
283
Harmonic MediaGrid Release 4.1
Checking Log Files for Errors
dhcpd status example 2:
[root@CDL1 dhcp]# pgrep dhcpd
3027
As mentioned before, the DHCP servers in the Harmonic MediaGrid are configured in a peer
relationship. Both servers have to be up or one must timeout and wait for the other to come
online. In the output of /var/log/messages below, the communication between ContentDirector1
(shown as CLD1) and ContentDirector2 (shown as CLD2) has been interrupted. In the following
example, DHCP has been stopped on ContentDirector1, and the output messages are from
ContentDirector2. Note the “communications-interrupted” message:
Feb 9 13:30:57 CDL2 dhcpd: failover peer Public B: I move from normal
to communications-interrupted
Feb 9 13:30:57 CDL2 dhcpd: peer Public A: disconnected
Feb 9 13:30:57 CDL2 dhcpd: failover peer Public A: I move from normal
to communications-interrupted
Also shown in the output below is the services being restarted on ContentDirector1. Shortly after
restarting services on ContentDirector1, ContentDirector2 logs a message to /var/log/message
that communications have moved from interrupted to normal:
Feb 9 13:31:38 CDL2 dhcpd: failover peer Public B: I move from
communications-interrupted to normal
Feb 9 13:31:38 CDL2 dhcpd: Sending updates to Public B.
Feb 9 13:31:38 CDL2 dhcpd: pool 5555557d5ba0 10.35.135/24 total 150
free 63 backup 71 lts -4
Feb 9 13:31:38 CDL2 dhcpd: failover peer Public A: peer moves from
normal to normal
Feb 9 13:31:38 CDL2 dhcpd: failover peer Public A: I move from
communications-interrupted to normal
Feb 9 13:31:38 CDL2 dhcpd: Sending updates to Public A.
Feb 9 13:31:38 CDL2 dhcpd: pool 55555578f400 10.35.134/24 total 150
free 59 backup 66 lts -3
Checking Log Files for Errors
Looking for Startup Errors in the mdscore Log File
The number one cause of services not starting on ContentDirectors is that the times are not
synchronized across ContentDirectors. Times must be synchronized so that journaling and sync
files across the ContentDirectors have the same timestamps. The times must be within about 4/
10ths (0.4sec) of a second or less for the services to run. Below is a portion of the mdscore log
file that shows the error message for a ContentDirector, which does not have its time
synchronized with another running ContentDirector.
omcld status error:
[root@CDL1 ~]# service omcld status
mdsstartup (pid 27118) is running...
oujfh (pid 27144) is running...
ousd (pid 27134) is running...
ssmd (pid 27153) is running...
mdscore dead but pid file exists ****