Multiserver APS Installer Issue: Revisited
Since #4787 we've upgraded our servers and now have a dedicated DB server for our mirrored multiserver steup, so the previous issue no longer applies (though it should still be looked into for the sake of others, of course).
But now we're facing much the same problem, but in reverse.
When you install an APS package on a mirrored multiserver setup, with a dedicated DB server, it creates the database on the DB server (and correctly marks it as a "remote server") but then fills out the "Remote Access IPs" with the IP address of only the master web server, but not of the web server mirrors.
So when my other web servers attempt to access the database, they're denied.
If I manually edit the "Remote Access IPs" to include the mirrored web servers (or leave the field blank for "any", which is okay for my particular setup, as all the servers are on their own private network behind a firewall - but, more generally, the fix ought to be to list the IPs of all the web servers, or use a /netmask when the web servers all have consecutive IPs, in case publicly accessible IP addresses are involved to lock it down to the needed IPs only), then it works fine.
Between this and the previous issue, the general problem seems to be that the APS installer really isn't taking account of mirrored multiserver setups and is presuming access by only one server, when somewhat the point of a mirrored multiserver setup is to have many web servers (and, in our case, to use shared storage on the backend and load-balancing on the frontend so that it can be scaled up).