aboutsummaryrefslogtreecommitdiff
path: root/scripts/testing/debug-vm.sh
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-17 14:32:38 -0500
committerCraig Jennings <c@cjennings.net>2026-05-17 14:32:38 -0500
commit494769e3698fb02f5bdd1ec8f09fbdec4218e63e (patch)
tree78586ae799f4d906a414ae4f934466093c2e76dc /scripts/testing/debug-vm.sh
parent9ccfcfde2ec79b1a8b7ca7df985313ac3db7f51a (diff)
downloadarchsetup-494769e3698fb02f5bdd1ec8f09fbdec4218e63e.tar.gz
archsetup-494769e3698fb02f5bdd1ec8f09fbdec4218e63e.zip
fix(cmail-setup-finish): verify both Bridge ports and dump status on failure
The "verifying Bridge is listening" check used a regex `127\.0\.0\.1:(1143|1025)` against `ss -ltn` output. That matches if *either* port is listening, but the success message claims both are. So a half-broken Bridge (IMAP up, SMTP down or vice versa) would pass the check. I split the check into two greps and report which port is missing. When the check fails, the script now also prints the last 10 lines of `systemctl --user status protonmail-bridge` to stderr so the operator sees the service state immediately instead of being told to go run the command themselves.
Diffstat (limited to 'scripts/testing/debug-vm.sh')
0 files changed, 0 insertions, 0 deletions