Notes from building KNJ Panel, in the order it actually happened.
blog /blɒɡ/ noun — 1. A web log. 2. Here: a build log. What we built, what broke, and what we learned.
Our repair steps suppress error output by convention, which keeps them quiet but meant we had been inferring failures from side effects. For this investigation we added a…
Read more →A follow-up repair did not run on a test server. The cause was a mismatch with the convention used elsewhere in the same script: other repair steps tolerate…
Read more →Our diagnostics ruled out several common explanations for a directory that would not accept an ownership change, without pointing to a new one. At that stage we chose…
Read more →The diagnostics showed that the preconditions for our repair were all satisfied, and that one of the two directories it touches had been updated while the other had…
Read more →A repair we had added did not appear to take effect on a test mail server, even when re-run. Rather than ship another blind change, we extended the…
Read more →The first real use of the new diagnostics page paid off immediately: webmail’s log directory had the package’s default ownership rather than the one the setup intended, so…
Read more →Phase 142’s key fix was real: the key length was confirmed, corrected and released, and the self-repair step ran successfully against the Mail Only satellite. Reloading the webmail…
Read more →Straight on from Phase 141: with the routing fixed, “Open Webmail” on a Mail Only satellite stopped returning an access error and started returning a server error. The…
Read more →During readiness testing on a multi-server stack, opening webmail for an account whose mail runs on a linked Mail Only server returned a 403. The webmail application was…
Read more →Same bug family as the mail-DNS fix from earlier that day, found while checking that fix live on a split mail and web install: the Email Deliverability page’s…
Read more →