I'm seeing some "write: cert: Broken pipe" from my acme-client cron jobs, it looks like there's a race somewhere:
acme-client: /etc/ssl/private/symphytum.spacehopper.org.key: loaded RSA domain key acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key acme-client: /etc/ssl/symphytum.spacehopper.org.crt: certificate valid: 50 days left acme-client: write: cert: Broken pipe acme-client: bad exit: keyproc(43738): 1 Running it in a tight loop I'm seeing it on 15/1000 calls, but seem to be hitting it much more often than this in cronjobs. May be connected, even without the bad exit, the output of a normal run isn't in a consistent order: run1:acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key run1:acme-client: /etc/ssl/symphytum.spacehopper.org.crt: certificate valid: 50 days left run1:acme-client: /etc/ssl/private/symphytum.spacehopper.org.key: loaded RSA domain key run10:acme-client: /etc/ssl/private/symphytum.spacehopper.org.key: loaded RSA domain key run10:acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key run10:acme-client: /etc/ssl/symphytum.spacehopper.org.crt: certificate valid: 50 days left run225:acme-client: acme-client: /etc/ssl/private/symphytum.spacehopper.org.key: loaded RSA domain key/etc/acme/letsencrypt-privkey.pem: loaded RSA account key run225:acme-client: /etc/ssl/symphytum.spacehopper.org.crt: certificate valid: 50 days left run344:acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key run344:acme-client: /etc/ssl/symphytum.spacehopper.org.crt: certificate valid: 50 days left run344:acme-client: /etc/ssl/private/symphytum.spacehopper.org.key: loaded RSA domain key run344:acme-client: write: cert: Broken pipe run344:acme-client: bad exit: keyproc(8172): 1
