It looks like we failed to fix this behaviour that we've already seen in the past
Nov 20 16:48:24 certcentral1001 systemd[1]: Stopping Central Certificates Service... Nov 20 16:48:24 certcentral1001 systemd[1]: Stopped Central Certificates Service. Nov 20 16:48:24 certcentral1001 systemd[1]: Started Central Certificates Service. Nov 20 16:48:26 certcentral1001 certcentral-backend[3712]: SIGHUP received Nov 20 16:48:26 certcentral1001 certcentral-backend[3712]: Missing/invalid DNS zone updater CMD timeout, using the default one: 60.00 Nov 20 16:48:26 certcentral1001 certcentral-backend[3712]: Number of certificates per status: Counter({'VALID': 4, 'INITIAL': 2}) Nov 20 16:48:26 certcentral1001 certcentral-backend[3712]: Creating initial self-signed certificate for netbox / ec-prime256v1 Nov 20 16:48:26 certcentral1001 certcentral-backend[3712]: Creating initial self-signed certificate for netbox / rsa-2048 Nov 20 16:48:27 certcentral1001 certcentral-backend[3712]: Starting main loop... Nov 20 16:48:27 certcentral1001 certcentral-backend[3712]: Handling new certificate event for netbox / ec-prime256v1 [... log continues as expected .... ]