Observing logouts or hang in UI when we have two UI and Management servers

We have 2 management servers and 2 Edge UI in our Edge PCF setup. This is the default configuration of Edge for PCF. Basically it installs 2 management server jobs. Each job has open ldap, management server, and edge UI running on them.

As per the doc http://docs.apigee.com/private-cloud/v4.17.05/installing-edge-using-ops-manager we tried to setup stickiness with a 60 second expiration for the AWS ELB. However, we notice that while working in Edge-UI the browser will hang for 30 to 60 seconds and also we get logged out. Need some insight on this setting and/or how we should be configuring it for AWS ELB.

Solved Solved
0 4 356
1 ACCEPTED SOLUTION

After some investigation we found the following solution for this issue:

  1. Please check the values for the following properties on both the UI servers
    • application.secret in /opt/apigee/edge-ui/conf/application.conf
    • mail.smtp.credential and apigee.mgmt.credential in /opt/apigee/edge-ui/conf/apigee.conf
  2. This behavior is usually seen if the values of these properties are different in both the machines.
  3. If you do see the values for different for one or more properties, then get the value(s) from one machine and update the same value(s) on the other machine.That is ensure that these properties have the same values on both the UI servers.Use the following steps to do this:
    • Note down the values of the above mentioned properties on let’s say UI server #1
    • Create a file /opt/apigee/customer/application/ui.properties on UI server #2
    • Add the following lines to the file:
      conf_application_application.secret=<value>
      conf_apigee_mail.smtp.credential=<value>
      conf_apigee_apigee.mgmt.credential=<value>

      Note: Use the corresponding values for each of the properties from the other machine.

    • Ensure this file is owned by apigee:
      chown apigee:apigee /opt/apigee/customer/application/ui.properties
    • Restart the UI server #2:
      /opt/apigee/apigee-service/bin/apigee-service edge-ui restart
  4. Remove/Disable the sticky session from the AWS ELBs.

With these steps, we no longer observed the hangs or the logouts in UI.

View solution in original post

4 REPLIES 4

After some investigation we found the following solution for this issue:

  1. Please check the values for the following properties on both the UI servers
    • application.secret in /opt/apigee/edge-ui/conf/application.conf
    • mail.smtp.credential and apigee.mgmt.credential in /opt/apigee/edge-ui/conf/apigee.conf
  2. This behavior is usually seen if the values of these properties are different in both the machines.
  3. If you do see the values for different for one or more properties, then get the value(s) from one machine and update the same value(s) on the other machine.That is ensure that these properties have the same values on both the UI servers.Use the following steps to do this:
    • Note down the values of the above mentioned properties on let’s say UI server #1
    • Create a file /opt/apigee/customer/application/ui.properties on UI server #2
    • Add the following lines to the file:
      conf_application_application.secret=<value>
      conf_apigee_mail.smtp.credential=<value>
      conf_apigee_apigee.mgmt.credential=<value>

      Note: Use the corresponding values for each of the properties from the other machine.

    • Ensure this file is owned by apigee:
      chown apigee:apigee /opt/apigee/customer/application/ui.properties
    • Restart the UI server #2:
      /opt/apigee/apigee-service/bin/apigee-service edge-ui restart
  4. Remove/Disable the sticky session from the AWS ELBs.

With these steps, we no longer observed the hangs or the logouts in UI.

Hi @AMAR DEVEGOWDA,

We are also facing the same issue. Do you also have expireSessionCookiesInternally and trackSessionCookies set to true? Do we need to disable this as well if we are not using session stickiness?

As per the documentation, Apigee suggests using these properties for storing session in memory which also adds a security feature.

Thanks.

@Mohammed Zuber,

If you don't have the sticky sessions, then you should set expireSessionCookiesInternally and trackSessionCookies back to false (default values).

If you have trackSessionCookies set to true, then you need to have the sticky sessions enabled.

@AMAR DEVEGOWDA, Thanks a lot. This solved the problem of intermittent logouts.