Can you switch to "LogLevel md:debug" for a while and send me the details? Did this start on the v1.1.0 or before that?
> Am 11.12.2017 um 16:09 schrieb Steffen <i...@apachelounge.com>: > > > Running 1.1.0 with the new naming. > > When mod_md encounters an error it looks like it is going in a endless loop: > > > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 1. time, next run in 0:00:05 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 2. time, next run in 0:00:10 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 3. time, next run in 0:00:20 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 4. time, next run in 0:00:40 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 5. time, next run in 0:01:20 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 6. time, next run in 0:02:40 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 7. time, next run in 0:05:20 hours > [md:info] [pid 10372:tid 1964] AH10057: apachelounge.nl: encountered error > for the 8. time, next run in 0:10:40 hours > ... > ... > ... > > Above is during renew and using port 444.. > > Apache is running fine because the certificate is still valid. > > Does it stop ? > > When does it happen, on what errors ? Above happens when: (20014)Internal > error (specific information not available): AH10056: processing > apachelounge.nl. > > What to do. Stopping on above retries can be tricky because when the ACME CA > service is temp down or not reachable we do want maybe a retry. A reachable > error/down error is different then a configuration error causing it like in > above case.. > > > > > > > > >
