Checking designate/2. ~/Downloads/f1badd08-a9a6-405a-b0be-d7f49ece023c/designate_2 $ tail var/log/designate/designate-mdns.log -n 2 2021-04-19 16:04:24.389 64928 ERROR designate oslo_db.exception.CantStartEngineError: No sql_connection parameter is established 2021-04-19 16:04:24.389 64928 ERROR designate
The last line logged by designate-mdns was at 16:04. While the configuration files were rendered at 16:05:12 $ grep -C 2 base-config.rendered var/log/juju/unit-designate-2.log | head -n 5 2021-04-19 16:05:12 DEBUG jujuc server.go:211 running hook tool "juju- log" for designate/2-identity-service-relation-changed- 330171960584494981 2021-04-19 16:05:12 DEBUG juju-log identity-service:105: tracer> tracer: set flag base-config.rendered tracer: ++ queue handler reactive/designate_handlers.py:144:run_db_migration tracer: ++ queue handler reactive/designate_handlers.py:155:sync_pool_manager_cache designate-mdns failed to start because the systemd service hit start- limit-hit Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Failed with result 'exit-code'. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Service hold-off time over, scheduling restart. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Scheduled restart job, restart counter is at 481. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Failed to reset devices.list: Operation not permitted Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Start request repeated too quickly. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Failed with result 'start-limit-hit'. I think this is something that should be fixed in the package, since we may need to do adjustments to designate-mdns.service https://www.freedesktop.org/software/systemd/man/systemd.unit.html#StartLimitIntervalSec=interval ** Also affects: designate (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [bionic-ussuri] next charm fails to start mdns service + [bionic-ussuri] designate-mdns.service Failed with result 'start-limit-hit' ** Summary changed: - [bionic-ussuri] designate-mdns.service Failed with result 'start-limit-hit' + [bionic-ussuri] designate-mdns.service: Failed with result 'start-limit-hit' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925233 Title: [bionic-ussuri] designate-mdns.service: Failed with result 'start- limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-designate/+bug/1925233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs