Cloud UI Login Failures

Symptoms: When you attempt to log into the Cloud UI, the login process appears to hang and then fails.

Resolution: The administration console that supports the Cloud UI might be running out of Java heap space, causing login failures. This issue is expected to be fixed in a future release. As a workaround, you can manually increase the heap size.

In the current release, there is no direct way to change the Java heap size in the UI, so you need to increase the heap size as follows:

  1. For convenience, you can store the IP address of the host machine where the Cloud UI is running in the ADMIN_IP environment variable. Alternatively, replace $ADMIN_IP in the commands shown with the IP address.
  2. Create a file with your current configuration, here containerdata.json (requires that you have jq installed):

    curl -u root http://$ADMIN_IP:12400/api/v0/regions/ece-region/container-sets/admin-consoles | jq '.containers | ."admin-console" | .data' > containerdata.json

    When prompted, enter the password you use to log into the Cloud UI.

  3. Open the containerdata.json file in your favorite editor and locate this line:

    "ADMINCONSOLE_JAVA_OPTIONS=-Djute.maxbuffer=33554432 -Xmx256M -Xms256M",
  4. Increase the Java heap size by changing the values for Xmx and Xms to 1024 or 4096, depending on the size of your host machine. For example: Change the values to -Xmx1024M -Xms1024M.
  5. Save the configuration and exit the editor.
  6. Apply the new configuration:

    curl -XPOST -u root 'http://$ADMIN_IP:12400/api/v0/regions/ece-region/container-sets/admin-consoles/containers/admin-console' -d @containerdata.json
  7. On the host machine where the Cloud UI administration console is running, recreate the Cloud UI:

    docker stop frc-admin-consoles-admin-console && docker rm -f frc-admin-consoles-admin-console

    If you prefer, you can use the HTTPS protocol on port 12443, but it currently supports only a self-signed certificate. Alternatively, you can perform the step from localhost.

  8. Log into the Cloud UI administration console to confirm that the issue is resolved.