Using OmniSci Services
OmniSci features two system services:
omnisci_web_server. You can start these services individually using
For permanent installations of OmniSciDB, OmniSci recommends that you use
systemdto manage OmniSciDB services.
systemdautomatically handles tasks such as log management, starting the services on restart, and restarting the services if there is a problem.
systemdmanages the open-file limit in Linux. Some cloud providers and distributions set this limit too low, which can result in errors as your OmniSci environment and usage grow. For more information about adjusting the limits on open files, see Why am I seeing the error "Too many open files...erno24"? in Frequently Asked Questions.
You use the
install_omnisci_systemd.shscript to prepare
systemdto run OmniSci services. The script asks questions about your environment, then installs the
systemdservice files in the correct location. You must run the script as the root user so that the script can perform tasks such as creating directories and changing ownership.
install_omnisci_systemd.shscript asks for the information described in the following table.
To manually start OmniSciDB using
sudo systemctl start omnisci_server
sudo systemctl start omnisci_web_server
You can use
systemdto restart OmniSciDB — for example, after making configuration changes:
sudo systemctl restart omnisci_server
sudo systemctl restart omnisci_web_server
To manually stop OmniSciDB using
sudo systemctl stop omnisci_server
sudo systemctl stop omnisci_web_server
To enable the OmniSciDB services to start on restart, run:
sudo systemctl enable omnisci_server
sudo systemctl enable omnisci_web_server