The Vidispine self test will generate a brief report about the system infrastructure for simple troubleshooting.
The tests are:
api- The API test. Verifies both
solr- Verifies the Solr configuration.
database- Verifies that the database can be reached.
transcoder- Verifies that the transcoder can be reached.
jms- Verifies that the JMS queues are well configured.
tools- Verify the existence of various external tools.
simplejob- Verifies that the transcoder can execute a simple transcode job.
thumbnail- Verifies the thumbnail configuration.
dbstats- Returns some statistics from the database schema.
ldap- Verifies the LDAP configuration.
fileaccesstest- Verifies write access of application server files.
cluster- Verifies the status of cluster instances and lists its members.
There are four possible outcomes of a test:
- Vidispine is well configured and running properly.
- Some configuration is not valid.
- There are tools missing, which could lead to failures of some functions.
- Important configuration or tools are missing or invalid, Vidispine will not run properly.
Running the tests can take a while, depending on the size of the system. The
dbstats is typically the slowest as it examines the number of rows in the
database among other things. Hence, it sometimes can be beneficial to only
run certain specific tests.
Use the self test resource to execute the tests. For example:
<SelfTestDocument xmlns="http://xml.vidispine.com/schema/vidispine" status="failed" took="38170ms"> <test name="api" status="warning" took="408ms"> <test name="adminApi" status="warning"> <message>API is 4.2</message> <message>Transcoder VX-1 is ERROR: Could not connect</message> <message>Transcoder VX-2 is 4.1.4-gea8cc32-12511</message> </test> <test name="apiNoAuth" status="ok"> <message>Base uri: http://localhost:8089/</message> </test> </test> ... </SelfTestDocument>