How do I know if the platform is running, and how much memory it is using?
As all of the parts of the platform are hosted as services, you can use
systemctl to see their status, i.e.
systemctl status omnia omnia-*.
Alternatively, you can use
ps aux | grep Omnia,
htop (requires install) to see more information, such as memory usage or service uptime.
In order to know the memory of the VM, you can use
How do I extract the platform?
The easiest way is to install
unzip, and just do
unzip OmniaPlatform.Full.VersionNumber.zip. You can also install
p7zip-full and do
7z x OmniaPlatform.Full.VersionNumber.zip.
How do I read logs?
The logs produced by the platform all go to
/var/log/omnia/. You can consult them with whatever solution you prefer: downloading and reading locally, using
On top of those, the services themselves will log to the system’s log, which you can access with
Finally, NGINX also has its own logs. They are configured to go to
How do I monitor disk space?
The recommended tool to see what is using disk space in your vm is
ncdu, which must be installed. Running it as
sudo ncdu / will give you the most details.
How do I update the platform?
OmniaPlatform.Binaries.VersionNumber.zip. Delete the contents of
/home/omnia/bin/, then extract it to that folder. Restart the site with
systemctl restart omnia.
How to increase the file size limit?
By default, NGINX sets a max size to the body of each request, using the directive client_max_body_size, whose default value is 1MB.
Sets the maximum allowed size of the client request body, specified in the “Content-Length” request header field. If the size in a request exceeds the configured value, the 413 (Request Entity Too Large) error is returned to the client. (from NGINX documentation)
In order to allow file uploads higher than 1MB, it’s neccessary to replace the value of the directive:
Edit the NGINX configuration file (
nanoor a similar tool;
Search the directive client_max_body_size (if it doesn’t exist, then add it inside and at the end of http);
Set the directive’s value to the new max size (like the following example):
Save the changes.
After updating the configuration, you need to reload NGINX.