This chapter lists an assortment of common problems and their solutions.
The problems solved include:
The default values for the controls are NTSC-specific. If you are using a 625/50 system, set the following system control in /usr/vtr/config/system-defaults/main:
vtr.main.timing_standard 625 |
This control sets the timing of the system, including the DIVO cards, to 625/50.
In /usr/vtr/config/device-defaults/DIVO, make sure the control vtr.media.video.output.timing is set to its default value, system.
If you find that the DIVO board has been left in a bad state, for example, you cannot reset it, use the divo_reset command, included in the divo.sw.diag images, to correct the problem. For example, the DIVO reset command is in the directory, /usr/dmedia/DIVO/bin.
If you are using a 625/50 system, see “625/50 Clips Do Not Play”.
If vvtr crashes, you might have exceeded the number of configured pollable semaphores. The log would appear as follows:
C 06-14:29:23.348170 1386 Failed opening semaphore file descriptor (sems open=147): No space left on device A 06-14:29:23.348985 1386 FATAL SYSTEM ERROR: SYSTEM CONFIGURATION ERROR |
To fix the problem, follow these steps:
Edit /var/sysgen/master.d/usema and increase USMAXDEVS, for example, to 1050.
Rebuild the kernel (autoconfig) and reboot the system to activate the change.
VST crashes after a few seconds if you do not have an audio source. If you are having audio sync problems when there is no audio, do the following:
Turn the audio off: in the /usr/vtr/config/device-defaults directory, edit the DIVO file and add:
vtr.media.audio.input.channels.clip “0” |
If you do not have an audio source, disable input audio by setting the unit control:
vtr.media.audio.input.port ““ |
VST crashes after a few seconds if you do not have an audio source. To fix this problem, disable input audio by setting the unit control:
vtr.media.audio.input.port ““ |
The system normally boots from the primary root plex, that is, root.data.0.0. If the primary plex becomes unavailable, you can either label the disks and swap master and slave, or you can use the following procedure to set up the system so that it can boot from the secondary root plex, for example, system.data.1.0.
From the System Maintenance Menu, choose Enter Command Monitor (5).
Display the PROM environment variables:
>> printenv SystemPartition=dksc(0,1,8) OSLoadPartition=dksc(0,1,0) root=dks0d1s0 ... |
The swap PROM environment variable (which is set below) is not displayed because it is not saved in NVRAM.
Reset the SystemPartition, OSLoadPartition, and root environment variables to the values of the disk partition that contains the alternate plex and the swap environment variable to have the value of the alternate swap partition. For example:
>> setenv SystemPartition dksc(0,2,8) >> setenv OSLoadPartition dksc(0,2,0) >> setenv root dks0d2s0 >> setenv swap /dev/dsk/dks0d2s1 |
Exit the Command Monitor and restart the system:
>> exit ... Option? 1 Starting up the system... ... |
Inside the /usr/vtr/adm/crash directory is a subdirectory for each program that crashes. If a program crashes, a directory is dynamically created with that program name. Inside that directory a core file is created containing the crash information.
When VST detects a program crash, it renames the core file to core.number, where number is the next incremental number. This scheme prevents core files from overwriting each other.
VST crash files are saved to aid SGI support personnel in diagnosing VST software errors.