Browse
 
Tools
Rss Categories

Server Startup Procedure

Reference Number: AA-00656 Views: 3337 0 Rating/ Voters

The LumenVox Engine (both client and server) perform a series of checks when initialized. If these checks fail, it can cause the application to terminate. If your application is crashing at startup, it is likely related to be one of these items.

This procedure applies to the LumenVox Speech Engine Server, the process that actually performs the decodes (lv_sre_server on Linux and LV_Engine_SERVER.exe on Windows). The speech client (the SpeechPort interface library) has its own startup procedure.

  1. Determines the location of the asr_server_restart.txt log file where errors related to startup will be written. Critical errors that prevent the engine from starting up will also be written to lumenvox_critical.txt. On Linux, this will be located in the folder determined by the LVLOGS value from lumenvox_settings.conf; on Windows this will  be located in the folder specified by the path $LVBIN\Logs or to $LVLOGS if $LVLOGS is defined. Most startup logs and errors are also displayed to console when the engine is run in console mode.
  2. On Windows only, if the LumenVox_Product.dub file is located in the $LVBIN folder, then a warning is added to the asr_server_restart.txt log to indicate that any system variables are being overridden by this.
  3. Checks the sre_server.conf configuration file to make sure that atleast one of LOAD_LOW_RES_MODEL, LOAD_MED_RES_MODEL or LOAD_HIGH_RES_MODEL is enabled.
  4. Verifies that there is a valid LVLANG directory. On Windows, this is the path contained in the environment variable $LVLANG; on Linux it is the path specified by the value of LANGDIR in lumenvox_settings.conf. (On Windows, if there is an empty file called LumenVox_Product.dub, then LVLANG is set to <the application's runtime directory/Lang> .
  5. The application checks to ensure there is an LVLANG/Dict folder, and that this directory contains at least one .model data file. In version 10.2 and prior, this log did not show up in lumenvox_critical.txt but it did show up in asr_server_restart.txt and on the console.
  6. On Linux only, it checks to confirm that the /etc/lumenvox/lumenvox_settings.conf file exists, and that the CACHEDIR parameter has a value. In version 10.2 and prior, this log did not show up in lumenvox_critical.txt but it did show up in asr_server_restart.txt and on the console.