https://bugs.contribs.org/show_bug.cgi?id=10300
--- Comment #21 from Dan Brown <[email protected]> ---
Thought I'd added this last night, but I don't see it.
Obviously the issue has something to do with the curl commands added to config.
So, rolled the VM back to where the certs hadn't been successfully issued yet.
Ran dehydrated -c, and it behaved as I reported--gave a message that it was
using the default config file, then returned to the shell prompt. Changed the
curl commands to remove the redirect (the "2>&1 > /dev/null" at the end of each
line) so I could see what was happening. Ran "dehydrated -c" again, and
(unsurprisingly) the curl commands generated some ugly output, but issuing the
certs succeeded without any further issues.
Rolled back to a pre-issuance state again. Ran dehydrated -c, and it again
behaved as reported. Edited config to only remove the 2>&1 part of the
redirect--this should send stdout to /dev/null, but stderr still to the
console. Ran "dehydrated -c" again, and once again a cert was issued without
errors.
This isn't helping--no error output is being generated.
Rolled back again. Ran dehydrated -c. It behaved as reported. Changed
nothing, and ran dehydrated -c again. It completed without issues. This
didn't work last night--repeated invocations of dehydrated -c had the same
results as the first invocation.
Rolled back again. Edited config (without running dehydrated -c first) to
remove the 2>&1 from each of the curl commands. Ran dehydrated -c, and it
behaved as reported, with no further errors from curl. Ran dehydrated -c
again, and it completed without issues.
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
