...
Code Block | ||
---|---|---|
| ||
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.
The correct timezone needs to be set in 2 places. You can check using:
Code Block | ||
---|---|---|
| ||
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)
(please substitute your actual TZ in the echo command)
Code Block | ||
---|---|---|
| ||
systemctl stop unimus
echo "Europe/Rome" | sudo tee /etc/timezone
sudo dpkg-reconfigure --frontend noninteractive tzdata
systemctl start unimus |
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