For anyone finding this thread, please check the issue[1] for the current status.
Quick summary:
- we are doing 32-bit tests (and have been)
- this problem only occurs if the app
suspicious_loginis enabled (it is not by default) - fix is easy if you find yourself in this situation: disable the
suspicious_loginapp from the command-line (see the issue for command examples to do this) or before upgrading Server - breakage occurs due to a mixture of a third-party tool (Composer) enforcing a config parameter we already had in place that should have prevented this app from functioning on 32-bit environments already (apparently this wasn’t the case due to a bug in that tool that was recently fixed which is where the error message reported here is coming from) + we could have had another layer of prevention in-place in that app to prevent it outright from even being activated in 32-bit environments
- if you’re using IPv6 at all, the
suspicious_loginapp probably would have already been broken in odd ways in 32-bit environments, though it may or may not have been noticeable - we’ll likely add that second layer of prevention which will more cleanly prevent this app from even being enabled in 32-bit environments going forward