Installing OPDK 4.16.09 with All-In-One (AIO) option failing with timeout

Google Cloud Apigee
1

While installing opdk v4.16.09 (it might happen with other versions as well) the below setup command

/opt/apigee/apigee-setup/bin/setup.sh -p aio -f configFile

fails with the following error

Checking for qpid-server on 127.0.0.1 port 8083  .............................................................
qpid-server failed to answer on 127.0.0.1 port 8083.
[2017-02-28 01:51:33 PM] Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1
[2017-02-28 01:52:30 PM] Using defaults from /tmp/config-aio.txt

How to avoid this problem?

2 Likes
2

In this case, qpid-server process is started successfully but it has not yet opened the port 8083 for listening. That is, even though the qpid-server process has started successfully, due to some reasons, there is a delay in opening the HTTP port 8083 and start listening. This delay could be more than 60 seconds which is the default maximum time period for the installation process to wait for the qpid process to be available at the port 8083. If this does not happen then the installation process fails with the above error.

To avoid this problem, we can increase the maximum wait time period value from 60 seconds to say 300 seconds (5 minutes) and rerun the setup.

To increase the delay, perform the following actions

1. vi /opt/apigee/edge-qpid-server-4.16.09-0.0.1040/lib/actions/wait_for_ready

2. change the value of PORT_TIMEOUT=${PORT_TIMEOUT:-60} to PORT_TIMEOUT=${PORT_TIMEOUT:-300} and save the file.

3.rerun the setup.

Similar errors might occur during the installation of the postgres-server server as below.

Checking for postgres-server on 127.0.0.1 port 8084  .............................................................
postgres-server failed to answer on 127.0.0.1 port 8084.
[2017-02-28 05:49:39 PM] Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1
[2017-02-28 06:12:27 PM] Using defaults from /tmp/config-aio.txt

To increase the delay, perform the following actions

1. vi /opt/apigee/edge-postgres-server-4.16.09-0.0.1040/lib/actions/wait_for_ready

2. change the value of PORT_TIMEOUT=${PORT_TIMEOUT:-60} to PORT_TIMEOUT=${PORT_TIMEOUT:-300} and save the file.

3.rerun the setup.

Similar errors might occur during the installation of the edge-management-server server as below.

apigee-service: edge-management-server: edge-management-server is running
Checking for management-server on 127.0.0.1 port 8080  .............................................................
management-server failed to answer on 127.0.0.1 port 8080.
[2017-02-28 06:23:23 PM] Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1
[2017-02-28 06:25:12 PM] Using defaults from /tmp/config-aio.txt

To increase the delay, perform the following actions

1. vi /opt/apigee/edge-management-server-4.16.09-0.0.1040/lib/actions/wait_for_ready

2. change the value of PORT_TIMEOUT=${PORT_TIMEOUT:-60} to PORT_TIMEOUT=${PORT_TIMEOUT:-300} and save the file.

3.rerun the setup.

Similar errors might occur during the installation of the edge-router server as below.

apigee-service: edge-router: edge-router is running
Checking for router on 127.0.0.1 port 8081  .............................................................
router failed to answer on 127.0.0.1 port 8081.
[2017-02-28 06:46:42 PM] Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1
[2017-02-28 06:49:14 PM] Using defaults from /tmp/config-aio.txt

To increase the delay, perform the following actions

1. vi /opt/apigee/edge-router-4.16.09-0.0.1040/lib/actions/wait_for_ready

2. change the value of PORT_TIMEOUT=${PORT_TIMEOUT:-60} to PORT_TIMEOUT=${PORT_TIMEOUT:-300} and save the file.

3.rerun the setup.

Similar errors might occur during the installation of the message-processor server as below.

Checking for message-processor on 127.0.0.1 port 8082  .............................................................
message-processor failed to answer on 127.0.0.1 port 8082.
[2017-03-01 02:25:03 AM] Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 1
[2017-03-01 02:26:52 AM] Using defaults from /tmp/config-aio.txt

To increase the delay, perform the following actions

1. vi /opt/apigee/edge-message-processor-4.16.09-0.0.1040/lib/actions/wait_for_ready

2. change the value of PORT_TIMEOUT=${PORT_TIMEOUT:-60} to PORT_TIMEOUT=${PORT_TIMEOUT:-300} and save the file.

3.rerun the setup.
2 Likes
3

Hi @phani b madgula,

Which VMs/Provider you are using for an install?

I am having same experience randomly on GCE. It baffles me, as there should not be a delay at this point usually, and yet sometimes it takes between 3 and 50 minutes to pass this line:

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #bfbfbf; background-color: #0000b3} span.s1 {font-variant-ligatures: no-common-ligatures}

2017-02-24 18:22:53,896 main INFO KERNEL.DEPLOYMENT - ServiceDeployer.init() : ServiceDeployer.init() : Initializing service : ZooKeeperService that implements InitializeAwareService

2017-02-24 18:27:01,719 main INFO o.a.c.f.i.CuratorFrameworkImpl - CuratorFrameworkImpl.start() : Starting

A cleaner way to change the PORT_TIMEOUT setting is:

PORT_TIMEOUT=120

line needs to be added to /opt/apigee/customer/default.sh

This way you don’t need to change it per component.

Every component will consult this file.

4

Hi @ylesyuk1,

Thanks for comments. I was not aware of setting PORT_TIMEOUT in /opt/apigee/customer/default.sh so that all components would use it.

Yes, I experienced this problem in GCE. Also it was random behavior. Sometimes, for some components, the PORT would come up within 60 seconds.

5

@phani b madgula @yuriyl

I have the sam eissue with ‘qpid’. As said by Phani I changed the timeout to 300 secs, it waits for 300 secs and I get the same error again. In this case what should be done?

6

See my suggestion on this other post:

https://community.apigee.com/questions/42511/ver-41705-aio-failing-on-qpid-timeout.html
7

Can you please check /etc/hosts and see any ipV6 entries. If you find entries starting with ::1 , please comment that one and run setup again

8

@phani b madgula the slow behavior of the system during startup could be related to the lack of entropy on the system.

Install rng-tools and configure it as mentioned on this post. That will solve the problem:

[https://community.apigee.com/questions/39287/error-installing-management-server-management-serv.html](https://community.apigee.com/questions/39287/error-installing-management-server-management-serv.html)
9

I have the same issue.. i did all the advices but still face the issue. did u manage to overcome this ?

1 Like
10

i have the same error , did you fix it ? @shawkyfoda