Before starting, Unimus performs a startup health-check - called internally as Boot or Starter.
The Starter checks if all conditions required for properly running Unimus are met.
If not, it presents an error message describing the problem.
This article offers suggestions on solving the most common first-run issues.
Logging path not accessible
Unimus logs to logging files located in these directories:
Linux - /var/log/unimus Windows - C:\ProgramData\Unimus\log
These directories must be accessible to the user running Unimus.
Please fix the permissions and restart Unimus.
Config file not accessible
Unimus uses a configuration file located in:
Linux - /etc/unimus/unimus.properties Windows - C:\ProgramData\Unimus\unimus.properties
The user running Unimus must have access to these directories, and must have a read-write access to the config file.
Please fix the permissions and restart Unimus.
Licensing server not reachable
Unimus must be able to communicate with the licensing server to successfully start.
Please ensure connectivity with https://licensing.unimus.net/.
You can check if licensing responds using:
curl https://licensing.unimus.net/status && echo
Or simply try to visit https://licensing.unimus.net/status in a web browser on your Unimus server.
If proxying is required for HTTP connectivity in your environment, please see this article for help.