I have setup 3 new servers. I am installing this from scratch.
Playbook Configuration:
My vars.yml file looks like this:
---
# Below is an example which installs a few services on the host, in different configuration.
# You should tweak this example as you see fit and enable the services that you need.
########################################################################
# #
# Playbook #
# #
########################################################################
# Put a strong secret below, generated with `pwgen -s 64 1` or in another way
# Various other secrets will be derived from this secret automatically.
mash_playbook_generic_secret_key: 'xxx'
########################################################################
# #
# /Playbook #
# #
########################################################################
########################################################################
# #
# Docker #
# #
########################################################################
# To disable Docker installation (in case you'd be installing Docker in another way),
# remove the line below.
mash_playbook_docker_installation_enabled: false
# To disable Docker SDK for Python installation (in case you'd be installing the SDK in another way),
# remove the line below.
devture_docker_sdk_for_python_installation_enabled: true
########################################################################
# #
# /Docker #
# #
########################################################################
########################################################################
# #
# com.devture.ansible.role.timesync #
# #
########################################################################
# To ensure the server's clock is synchronized (using systemd-timesyncd/ntpd),
# we enable the timesync service.
devture_timesync_installation_enabled: true
########################################################################
# #
# /com.devture.ansible.role.timesync #
# #
########################################################################
########################################################################
# #
# devture-traefik #
# #
########################################################################
# Most services require a reverse-proxy, so we enable Traefik here.
#
# Learn more about the Traefik service in docs/services/traefik.md
#
# If your server already runs Traefik, you will run into port conflicts by installing it twice.
# See docs/interoperability.md for solutions.
mash_playbook_reverse_proxy_type: playbook-managed-traefik
# The email address that Traefik will pass to Let's Encrypt when obtaining SSL certificates
devture_traefik_config_certificatesResolvers_acme_email: email@mydomain.com
# This will enable a Traefik Dashboard UI
devture_traefik_dashboard_enabled: true
devture_traefik_dashboard_hostname: traefik.cloud.mydomain.com
devture_traefik_dashboard_basicauth_enabled: true
devture_traefik_dashboard_basicauth_user: traefik-admin
devture_traefik_dashboard_basicauth_password: xxx
########################################################################
# #
# /devture-traefik #
# #
########################################################################
########################################################################
# #
# devture-postgres #
# #
########################################################################
# Most services require a Postgres database, so we enable Postgres here.
#
# Learn more about the Postgres service in docs/services/postgres.md
devture_postgres_enabled: true
# Put a strong password below, generated with `pwgen -s 64 1` or in another way
devture_postgres_connection_password: 'xxx'
########################################################################
# #
# /devture-postgres #
# #
########################################################################
########################################################################
# #
# exim_relay #
# #
########################################################################
# Various services need to send out email.
#
# Enabling this Exim relay SMTP mailer service automatically wires
# all other services to send email through it.
#
# exim-relay then gives you a centralized place for configuring email-sending.
exim_relay_enabled: true
exim_relay_hostname: cloud.mydomain.com
exim_relay_sender_address: "someone@{{ exim_relay_hostname }}"
# By default, exim-relay attempts to deliver emails directly.
# To make it relay via an external SMTP server, see docs/services/exim-relay.md
########################################################################
# #
# /exim_relay #
# #
########################################################################
########################################################################
# #
# uptime-kuma #
# #
########################################################################
# Learn more about the Uptime-kuma service in docs/services/uptime-kuma.md
#
# This service is only here as an example. If you don't wish to use the
# Uptime-kuma service, remove the whole section.
uptime_kuma_enabled: true
uptime_kuma_hostname: uptime-kuma.mydomain.com
# For now, hosting uptime-kuma under a path is not supported.
# See: https://github.com/louislam/uptime-kuma/issues/147
# uptime_kuma_path_prefix: /uptime-kuma
########################################################################
# #
# /uptime-kuma #
# #
########################################################################
# You can add additional services here, as you see fit.
# To discover new services and configuration, see docs/supported-services.md
Matrix Server:
OS: Ubuntu 22.04
Architecture amd64
Ansible:
TASK [galaxy/systemd_service_manager : Fail if service isn't detected to be running] ************************************************************************************************************************
skipping: [mydomain.com] => (item=mash-container-socket-proxy.service)
failed: [mydomain.com] (item=mash-traefik.service) => changed=false
ansible_loop_var: item
item: mash-traefik.service
msg: mash-traefik.service was not detected to be running. It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.). Try running `systemctl status mash-traefik.service` and `journalctl -fu mash-traefik.service` on the server to investigate. If you're on a slow or overloaded server, it may be that services take a longer time to start and that this error is a false-positive. You can consider raising the value of the `devture_systemd_service_manager_up_verification_delay_seconds` variable. See `/home/user/hetzner-cloud-environment/mash-playbook/roles/galaxy/systemd_service_manager/defaults/main.yml` for more details about that.
skipping: [mydomain.com] => (item=mash-postgres.service)
skipping: [mydomain.com] => (item=mash-exim-relay.service)
skipping: [mydomain.com] => (item=mash-uptime-kuma.service)
Problem description:
I am running just install-all on my workstation. There are no errors apart from the last above. Checking the servers, there are no Docker containers at all.
Additional context
Add any other context about the problem here.
I have setup 3 new servers. I am installing this from scratch.
Playbook Configuration:
My
vars.yml
file looks like this:Matrix Server:
Ansible:
Problem description:
I am running just install-all on my workstation. There are no errors apart from the last above. Checking the servers, there are no Docker containers at all.
Additional context Add any other context about the problem here.