Daemon error after first deployment with Ansible

[catalinad]

Good day,

I am deploying OTRS version 6.0.23 with Ansible on Ubuntu 18.04.
The deployment also integrates Apache and MariaDB. After it finishes I get this error when I try to start the Daemon:

OTRS-otrs.Daemon.pl - Daemon Kernel::System::Daemon::DaemonModules::SystemConfigurationSyncManager-10 No deployments found in Database!

I checked many times to see if there is a problem with permissions or with the database, but everything looks fine. I use the perl script to set the permisions and for the database configuration I use mariadb user "otrs" and run the sql scritps into the "otrs" database:
- "otrs-schema.mysql.sql"
- "otrs-initial_insert.mysql.sql"
- "otrs-schema-post.mysql.sql"

$HOME = /opt/otrs

If I ran from Ansible just ./otrs.Daemon.pl start and ./Cron.sh start from Ansible I would get the below error and in the UI I would see the error message the Daemon is not running. To fix this I would need to relogin to the VM and restart the Daemon pearl script, but it is not how I wanted because I want this to be done in an automated way.

Currently a workaround for this is to run with Ansible ./otrs.Daemon.pl start --debug SchedulerCronTaskManager SchedulerFutureTaskManager SchedulerGenericAgentTaskManager SchedulerTaskWorker SystemConfigurationSyncManager, ./Cron.sh start . I still get the below error, but at least I no longer get the error message in the portal that the Daemon is not running.

What should I do in this case, should I just ignore the error or what am I missing?

Thank you!
Catalina

[root]

Hi,

You have to run

Code: Select all

bin/otrs.Console.pl Maint::Config::Rebuild

after the initial installation.

- Roy

P.S.: Do you like to publish your playbook in the howto section?

[catalinad]

Hi Roy,

Thank you for the fast respone.
I ran what you suggested and I no longer get the error.

Unfortunately, I cannot share the Ansible code because it if for a client.

Cheers,
Catalina