...

If proxying is required for HTTP(S) connectivity in your environment, please see this article for help.

Unimus doesn't properly display special characters

In some cases, you might see that Unimus doesn't properly show special / national characters (they are shown as a question mark).

This can be solved by properly setting the DB charset / collation:

1. Shut down Unimus
2. Set DB collation to UTF8mb4 and charset to UTF8mb4_unicode_cs
3. Start Unimus

After setting tables in the DB to this, any new special characters written to the DB should be displayed properly.
(this will not change data already existing in the DB)

MySQL DB initialization fails with "Specified key was too long" errors

When finishing the Deployment Wizard, you might see an error saying "Unable to upgrade database" when using a MySQL DB.

On some older versions of MySQL using the "utf8mb4" charset, the DB only support VARCHARs of max size 191.
Unimus requires multiple DB columns to be VARCHAR(255).

You can solve this by creating your database using the "utf8" charset:

CREATE DATABASE `dbname` DEFAULT CHARACTER SET utf8;
 or
CREATE DATABASE dbname CHARACTER SET utf8;

Device jobs show results in a wrong timezone

This issue is most usually caused by the scheduler itself running in the wrong timezone, but to the user, all jobs results / logs, etc. are shown as if in wrong timezone.

This is usually caused by a wrong timezone configuration in Linux.

cat /etc/timezone
timedatectl

Both outputs should show correct timezone.

If one (or both) are not correct, here is how to fix this:
(please substitute your actual TZ in the echo command)

systemctl stop unimus
echo "Europe/Rome" | sudo tee /etc/timezone
sudo dpkg-reconfigure --frontend noninteractive tzdata
systemctl start unimus

The above commands are for Ubuntu / Debian - please check for proper commands if using a different Linux distribution.

TODO

•  TODO Tomas Kirnak - Port 8085 not free - how to find out and how to change port
•  TODO Tomas Kirnak - Unimus running as a service refuses to start - run Unimus manually to get a more detailed error report