Roll back from 4.19.06 to 4.18.05. Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1

Google Cloud Apigee
1

We have a custom edge private cloud installation based on the 12-node clustered installation (two regions). We have upgraded (mostly) to 4.19.06 on these boxes, but are attempting to do a rollback from 4.19.06 to 4.18.05 to ensure we’re able to in higher environments.

The docs here: https://docs.apigee.com/private-cloud/v4.19.06/rollback-41906 do not make it clear which order the components should be rolled back in, so we began the process on a edge management server. We successfully rolled back cassandra and zookeeper (profile “ds”), but when attempting to run:

sudo /opt/apigee/apigee-setup/bin/setup.sh -p ms -f /home/apigee/response-edge.txt

the tail end of the script outputs:

Checking for optional variables
Found optional variable LDAP_PORT...OK
Found optional variable LDAP_TYPE...OK
Found optional variable LDAP_SID...OK
Found optional variable LDAP_PEER...OK
Found optional variable APIGEE_BIND_DN...OK
Stopping openldap
apigee-service: apigee-openldap: pid=14384
apigee-service: apigee-openldap: Not running (DEAD)
apigee-service: apigee-openldap: OK
apigee-configutil: apigee-openldap: # OK
updated property lib_settings_ldap_port in file /opt/apigee/token/application/openldap.properties
updated property RUN_USER in file /opt/apigee/etc/apigee-openldap.d/apigee-openldap.sh
updated property lib_settings_ldap_sid in file /opt/apigee/token/application/openldap.properties
updated property lib_settings_ldap_peer in file /opt/apigee/token/application/openldap.properties
updated property lib_settings_apigee_bind_dn in file /opt/apigee/token/application/openldap.properties
apigee-configutil: apigee-openldap: # OK
apigee-configutil: apigee-openldap: # OK
apigee-service: apigee-openldap: Not running (NO_LOCKFILE)
apigee-service: apigee-openldap: status=2, continuing
apigee-service: apigee-openldap: OK
apigee-service: apigee-openldap: apigee-openldap is running
Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1

A status check tells that everything but edge-management-server is running. edge-management-server was there before, but now is gone.

sudo /opt/apigee/apigee-service/bin/apigee-all status
+ apigee-service apigee-cassandra status
apigee-service: apigee-cassandra: OK
+ apigee-service apigee-openldap status
apigee-service: apigee-openldap: OK
+ apigee-service apigee-zookeeper status
apigee-service: apigee-zookeeper: OK
+ apigee-service edge-ui status
apigee-service: edge-ui: OK

Our config is:

cat /home/apigee/response-edge.txt
HOSTIP="XX.XX.XX.XX"

MSIP="XX.XX.XX.XX"
ADMIN_EMAIL="XX@XX.com"
APIGEE_ADMINPW="XXXXXX"
LICENSE_FILE="/tmp/apigee/license.txt"

USE_LDAP_REMOTE_HOST="n"

LDAP_TYPE="2"
LDAP_SID="1"
LDAP_PEER="XX.XX.XX.XX"
APIGEE_LDAPPW="XXXXXX"

ENABLE_AX="y"

MP_POD="gateway"
REGION="dc-1"

USE_ZK_CLUSTER="y"
ZK_HOSTS="XX.XX.XX.XX XX.XX.XX.XX XX.XX.XX.XX XX.XX.XX.XX XX.XX.XX.XX XX.XX.XX.XX:observer"
ZK_CLIENT_HOSTS="XX.XX.XX.XX XX.XX.XX.XX XX.XX.XX.XX"

USE_CASS_CLUSTER="y"
CASS_HOSTS="XX.XX.XX.XX:XX.XX.XX.XX.XX.XX.XX.XX XX.XX.XX.XX:XX.XX.XX.XX.XX.XX.XX.XX XX.XX.XX.XX:XX.XX.XX.XX.XX.XX.XX.XX"

USE_CASS_CLUSTERNAME="Apigee"
CASS_AUTH="y"
CASS_USERNAME="cassandra"
CASS_PASSWORD="XXXXXX"

PG_PWD="XXXXXX"

SKIP_SMTP="n"
SMTPHOST="xxxxxx.xxxx.xxx"
SMTPPORT="25"
SMTPSSL="n"
SMTPMAILFROM="XX@XX.com"

BIND_ON_ALL_INTERFACES="y"

Any guidance would be most helpful!

2

The link you have specified is correct. You can follow the steps to stop and uninstall the components. Then you need to reinstall the bootstrap for 4.18.05, then apigee setup install and install the components in the nodes. I can say its more similar to reinstall of 4.18.05. So, not a worry.

3

Hi @Priyadarshi, tried that but still got the same error as Michael.

@Michael - did you get a resolution for this error?

4

is your configuration file correct? can you see the log file for the error?

5

Yes it is the same config file which was successfully used to upgrade to 19.06 prior to this rollback. The edge management server log file has not been updated with any errors, last entry was with information about the uninstall during the rollback

6

It looks issue with openldap. You can do installation of other components successfully and then do openldap installation from scratch.

7

Do you know if we can just rollback the edge only components and leave the other components at the upgraded version? for example can we leave cassandra, zookeeper, openldap at the upgraded versions and just roll back router, qpid, MP, etc?

8

Apigee doesn’t allow components in different versions. You have to maintain same version across all components