Rss Categories

Common Linux Installation Problems

Reference Number: AA-01772 Views: 20283 0 Rating/ Voters

Required Permissions

If you are trying to install LumenVox on Linux, please be sure that you are logged in as root or a user with root-level permissions.

Dependency Issues

Like most Linux software, LumenVox is dependent on a number of open source, third-party software packages. These packages vary depending on which LumenVox packages are being installed.

With one exception, all of the packages LumenVox depends upon are available in the default Red Hat and Cent OS repositories, so as long as you are using yum (as detailed in the Linux installation instructions) the third-party packages should be installed for you along with the LumenVox packages.

The only non-standard package LumenVox requires is a specific version of the js JavaScript library. As of LumenVox version 11.1, this package is hosted along with the LumenVox packages on our webserver. If you use yum to fetch and install the LumenVox packages, it should be able to resolve that dependency.

If for some reason you are unable to use yum, you will need to resolve the dependency issues manually. The output from the rpm -i command should list any missing packages. Often times those packages may also have dependencies, so resolving these issues can take a while. LumenVox strongly recommends the use of yum to avoid this process, especially if you are relatively unfamiliar with Linux. If you install your software without yum, please be sure and get the appropriate js RPM from the download section for your distribution and architecture.

Note that if you do not have a valid Red Hat subscription and you are using Red Hat Enterprise Linux, yum may fail, so verify that this is not the case.

'cannot restore segment prot after reloc: Permission denied'

Any error that reads like the one above ("cannot restore segment prot after reloc") is related to selinux. Please disable selinux on your machine or add the appropriate policy.

Services Mysteriously Stopping

If you notice that LumenVox services stop running mysteriously, and there appears to be nothing in the LumenVox logs to indicate why the process was stopped, it is possible that you don't have sufficient memory installed on your system.

Speech Recognition is very CPU and memory intensive, so you need to ensure that your system has sufficient memory, otherwise the Operating System (kernel) may take measures for self-preservation. This is known as the OOM (Out Of Memory) Killer - this mechanism is known as Out of Memory Management, and is responsible for stopping processes when system memory reaches critical levels.


Please note that LumenVox has no control over which processes the OOM Killer decides to stop, however since many LumenVox services, including the ASR use large amounts of memory, they are particularly prominent targets. This does not mean that there is a problem in the LumenVox code, it means that you need to install more memory on your system.

You can detect when any process has been stopped by the OOM Killer by running the following command from the system console:

grep -i 'killed process' /var/log/messages

Also, depending on how your Linux system is configured, you may try one of these:

grep oom /var/log/*
grep total_vm /var/log/*

Check the output of any of these commands indicates some oom-killer activity, which would look something like this:

Jan 30 14:39:44 UOC-LV1 kernel: lv_sre_server invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
Jan 30 14:39:44 UOC-LV1 kernel: lv_sre_server cpuset=/ mems_allowed=0
Jan 30 14:39:44 UOC-LV1 kernel: CPU: 1 PID: 18605 Comm: lv_sre_server Not tainted 3.10.0-327.36.2.el7.x86_64 #1

If you encounter this type of error, please install more memory before calling LumenVox, since this is most likely the issue, which can only be resolved by installing more memory.

If you believe that you have sufficient memory for running your LumenVox services, and yet still see these types of issues, try to determine whether some other processes are using large amounts of memory, but calling the following command from the console to list applications using the most memory, in descending order:

ps -e -o pid,user,cpu,size,rss,cmd --sort -size,-rss | head