dehydrated runs with "-e", which exits on error, so when the invalid_challenge hook exited with a non-zero status (ie. error), that'd cause dehydrated to exit as well, and we'd never get to cleaning up these challenges, they'd just accumulate in storage indefinately.
By removing the non-zero exit code, dehydrated continues running, thus cleaning up the challenges.
dehydrated runs with "-e", which exits on error, so when the invalid_challenge hook exited with a non-zero status (ie. error), that'd cause dehydrated to exit as well, and we'd never get to cleaning up these challenges, they'd just accumulate in storage indefinately.
By removing the non-zero exit code, dehydrated continues running, thus cleaning up the challenges.
As of https://github.com/dehydrated-io/dehydrated/commit/4b7a1e4c, there's some logging around non-zero exit codes.