Specifications

A-37
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Appendix A Troubleshooting
Database Issues
Many Log Files
If one of the following conditions exists, it indicates that there were database replication errors:
• There are many log files with a filename similar to log.00000XXXX in the
/home/isa/Berkeley/DATADIR directory.
• Database could not be started. See the “Services Monitor” section on page 5-40 for more
information.
• Bidirectional connections are lost between servers. See the “Required Services Not Starting or
Running Correctly” section on page A-24.
• The following error message is listed in the /arroyo/log/avsdb-err.log.yyyyMMdd file:
tavsdb: unable to allocate memory for mutex; resize mutex region
# tail -f avsdb-err.log.20081111
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
tavsdb: unable to allocate memory for mutex; resize mutex region
• The /home/isa/Berkeley/DATADIR/REPLAY.db file increases to several GB.
$ ls -ltr
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002824
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002825
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002826
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002837
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002838
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002839
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002841
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002840
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002843
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002842
-rw-r--r-- 1 isa isa 5726769152 Nov 12 15:23 REPLAY.db
For resolution, see the “Corruption Recovery” section on page A-37.
Corruption Recovery
Caution Escalate to tier-three support before making any intrusive database changes.
If the CDSM database is corrupted and the Vault database is not corrupted, do the following:
Step 1 As user root, stop the CDSM database.
# /usr/bin/db_shutdown
Step 2 Confirm that the database is shut down.
# ps -ef | grep avsdb