Most likely you are using JCR storage (also called JSRP) for UGC. When you have multiple publishers, it is recommended to use MSRP wherein the UGC is stored in a Mongo instance.For more details you can refer to  Recommended Topologies for Communities​ and SRP - Community Content Storage Thanks,Neera...

If this is still not resolved, please contact Adobe Support with logs and all configuration changes you did.

The URI um/login?um_no_redirect=true is only for testing and since you go a message that client successfully authenticated, the test has passed. Also, if you are logged in via sso using /lc/ws, the sso is working fine. I think your system is setup fine for sso.

When a process is marked for termination or suspension, the process would terminate or suspend after the the step which is being currently being executed. This is designed as such so as not to cause any inconsistent state in the system and better handling in a cluster setup.

Can you share a bit more details? It would help if you can share the code you are using for deployment and a sample LCA demonstrating the issue.Also see Managing LiveCycle Applications with ant | Adobe LiveCycle Blog

This would require a deeper investigation. Can you please open a support case with Adobe enterprise support if you haven't done already?

Looks like there is a mix-up. MySQL is not supported for cluster installs. We'd get the install documentation corrected.

You may refer to following documents:https://helpx.adobe.com/pdf/aem-forms/6-2/install-single-server-weblogic.pdf https://helpx.adobe.com/pdf/aem-forms/6-2/install-single-server-websphere.pdf These documents have section for CLI installation

Okay, its not just the URL you'd like to change but the context path too. I can not comment unless I see the configuration or try replicating the issue myself. Can you please work with Adobe Support and open a Support ticket?

Can you check if the Externalizer service [1] is configured properly? [1] Externalizing URLs