| 2024-01-24 11:56:33 |
Piotr Parczewski |
description |
Only the first execution of cron job in letsencrypt-lego container is successful on active host. Subsequent end up with:
/usr/bin/letsencrypt-certificates: line 174: ip: command not found
2024/01/19 20:00:01 [INFO] [myhostname.mydomain - cron] This Letsencrypt-lego host is passive, nothing to do...
2024/01/19 21:21:23 [INFO] [myhostname.mydomain - cron] This Letsencrypt-lego host is passive, nothing to do...
/usr/bin/letsencrypt-certificates: line 174: ip: command not found
2024/01/20 00:00:01 [INFO] [myhostname.mydomain - cron] This Letsencrypt-lego host is passive, nothing to do...
/usr/bin/letsencrypt-certificates: line 174: ip: command not found |
Only the first execution of cron job in letsencrypt-lego container is successful on active host. Subsequent ends up with:
/usr/bin/letsencrypt-certificates: line 174: ip: command not found
2024/01/19 20:00:01 [INFO] [myhostname.mydomain - cron] This Letsencrypt-lego host is passive, nothing to do...
2024/01/19 21:21:23 [INFO] [myhostname.mydomain - cron] This Letsencrypt-lego host is passive, nothing to do...
/usr/bin/letsencrypt-certificates: line 174: ip: command not found
2024/01/20 00:00:01 [INFO] [myhostname.mydomain - cron] This Letsencrypt-lego host is passive, nothing to do...
/usr/bin/letsencrypt-certificates: line 174: ip: command not found |
|
