Error: Management Server not reachable - Where I can find details?

Not applicable

Hi,

I am installing the API Manager on a local machine.

I followed the steps at the page http://docs.apigee.com/private-cloud/latest/onboard-organization
but when I run the command "apigee-service apigee-provision setup-org -f configFile" I get the following error:

[root@ip-10-0-0-43 bin]# /opt/apigee/apigee-service/bin/apigee-service apigee-provision setup-org -f /home/apigee/configOrganizationCpaasdcpp.conf
Sourcing in /opt/apigee/customer/defaults.sh
Checking for required variables
Checking required variable ADMIN_EMAIL...OK
Checking required variable ENV_NAME...OK
Checking required variable MSIP...OK
Checking required variable ORG_NAME...OK
Checking required variable VHOST_ALIAS...OK
Checking required variable VHOST_NAME...OK
Checking required variable VHOST_PORT...OK
Checking for optional variables
Found optional variable APIGEE_ADMINPW...OK
Found optional variable APIGEE_PORT_HTTP_MS...OK
Found optional variable FIRST_NAME...OK
Found optional variable LAST_NAME...OK
Found optional variable NEW_USER...OK
Found optional variable ORG_ADMIN...OK
Found optional variable USER_NAME...OK
Found optional variable USER_PWD...OK
This script will create an organization with an organization admin,
enable role based access control and create enviroments.
Create User
-----------
Checking for required variables
Checking required variable ADMIN_EMAIL...OK
Checking required variable FIRST_NAME...OK
Checking required variable LAST_NAME...OK
Checking required variable MSIP...OK
Checking required variable USER_NAME...OK
Checking required variable USER_PWD...OK
Checking for optional variables
Found optional variable APIGEE_ADMINPW...OK
Found optional variable APIGEE_PORT_HTTP_MS...OK
Error: Management Server not reachable


Do you know if exists a more detailed log file?
where is it?

0 9 2,569
9 REPLIES 9

Not applicable
Error:ManagementServernot reachable.
Is your management server running?
apigee-service edge-management-server status or
ps -ef | grep edge-management-server should tell you that

Not applicable

Few things to check:

  • Make sure Management Server and OpenLDAP are running:
/opt/apigee/apigee-service/bin/apigee-all status
  • Make sure /home/apigee/configOrganizationCpaasdcpp.conf is owned by apigee user (apigee:apigee).
  • Make sure MSIP variable in configOrganizationCpaasdcpp.conf has the correct host/ip for the Management Server.
  • Make sure iptables or SElinux are preventing the connectivity.

hi @Maudrit, thank you for your answer. I report below the results:

  • Make sure Management Server and OpenLDAP are running:
    the result is positive.

/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-management-server status
apigee-service: edge-management-server: OK
+ apigee-service edge-message-processor status
apigee-service: edge-message-processor: OK
+ apigee-service edge-router status
apigee-service: edge-router: OK
+ apigee-service edge-ui status
apigee-service: edge-ui: OK
  • Make sure /home/apigee/configOrganizationCpaasdcpp.conf is owned by apigee user (apigee:apigee).
    it was owned by ROOT but, after changing the ownership, the result is the same.
  • Make sure MSIP variable in configOrganizationCpaasdcpp.conf has the correct host/ip for the Management Server.
    OK
  • Make sure iptables or SElinux are preventing the connectivity.
    how can I check this?

Hi @Maudrit ,

Where can I check that iptables or SElinux are preventing the connectivity?

Hello Fabio,

did you got any fix for above mentioned issue? If yes then please share the resolution for this.

Thanks

Can you try manually sending a request to the Management Server?

Actually I had issue with host and IP tables so after correcting them this issue is fixed.

Thanks.

Hi Hawagir,

Can you provide us more information about your issue and solution, thank you in advance ...

Most popular reasons of this issue to happen are related to connectivity problems.

An example: firewall settings between nodes set up after MS was installed but before apigee-provision
command was run.

Another example, when you need proxy settings for apigee-install/apigee-setup commands to be able to reach external RPM repo. Then you remove them or not configure them properly to ignore local servers.

It is an easy problem to troubleshoot. From a node where you run an install/provision command try to execute a curl request to Management Server. If you fail to do it, then setup command will have troubles to reach MS as well. Sort out connectivity before re-running install/setup command.