Grass Valley Aurora Browse v.6.0b Installation - Manual (Page 118)

118 Aurora Browse Installation and Configuration Guide September 22, 2006
Chapter 5 Troubleshooting the system
Proxy troubleshooting tips
Use the following table to identify and resolve problems related to the creation and
storage of low-res proxy assets.
Symptom Solution
An operational Browse scavenge
system (on an Open SAN)
suddenly stops working or there is
a drop in scavenge performance for
more than an hour. Debug as follows:
1. Copy and paste a short test clip into the scavenge folder, note the name and time.
2. Profile MDI stage: Use the Browse event viewer on the machine running the Profile
MDI, verify that the Profile MDI service reports the creation of the new clip. Look
for a CREATE_CLOSE message.
- If the message doesn’t show up, or there are errors in the MDI’s log, restart the
Profile MDI service.
3. Rules Wizard Stage: Look at the events on the NB server. You’re looking for a
message from the rules wizard that it received a CREATE_CLOSE message from
the Profile MDI. You should then see follow-up messages as a new job is being
created and sent to the Sequential encoder.
- If the message does not arrive, or the Rules Wizard does not send the job, restart
the Rules Wizard service.
4. Sequential Encoder: Look at the events on the Sequential encoder. You’ll see a
new job showing up and the sequential encoder starting.
- If the job does not arrive, restart the Proxy Transfer Service.
5. Server: If the job arrives, but the sequential encoder can’t start, check the connection
to the target Profile:
a. Ping the Profile host name, make sure the ProLink server is running, make sure
no other application (i.e. VdrPanel or ConfigManager) is trying to use the playout
channel.
b. If the connection the Profile appears okay, restart the ProxyTransfer service and
run the test again with a new test clip.
c. If scavenge still fails, there are a couple of possibilities:
- Profile is too busy to respond to request. This can happen if several
MediaManager sessions are running in full refresh mode. If so, shut down these
sessions.
- ProNet is wedged. Restart the Profile.
In general, don’t reboot the system components such as the encoder or the NB server
until you’ve tried the above
The Aurora Browse client browse
comes up with results but
thumbnails are missing (broken
link indicators where thumbnails
should be). Video is also
inaccessible. Check Ethernet connections from NAS to the client network.
Check that the client account exists on the NAS. This is the account used to log into
the client browse machine.
The Aurora Browse client play
back video but scrubbing is poor. There is too much traffic on the network. Try to isolate Aurora Browse from other
network activity.
Use a switch rather than a hub for connectivity.
Recording does not start as
scheduled for ingest. Check that encoder, server and client workstation PC clocks are synchronized to house
timecode feed (reference NetTime setup instructions).
Check that all Thomson services are running on server and encoders (use windows
services panel from administrative tools).