cfy_manager rabbitmq install problem

[ghost]

Hi:

Trying to install cloudify under an openstack centOS instance. All the time error with cloudify-rabbitmq appear and drive me crazy:

2018-10-24 12:14:32,876 - [MAIN] - ERROR - NetworkError: Failed to connect to localhost:5671...

I think is the timeout that cfy_manager has for restart the service. In my case rabbitmq take a lot of time to restart and cloudify-rabbitmq does never start in the specified timeout of cfy_manager.

Cloudify manager version: 18.10.4
Rabbitmq server start properly and is working fine before cloudify are installed:

[root@testcl centos]# rabbitmqctl status
Status of node rabbit@testcl ...
[{pid,18393},
 {running_applications,
     [{rabbit,"RabbitMQ","3.7.7"},
      {mnesia,"MNESIA  CXC 138 12","4.15.4"},
      {rabbit_common,
          "Modules shared by rabbitmq-server and rabbitmq-erlang-client",
          "3.7.7"},
      {ranch_proxy_protocol,"Ranch Proxy Protocol Transport","1.5.0"},
      {ranch,"Socket acceptor pool for TCP protocols.","1.5.0"},
      {ssl,"Erlang/OTP SSL application","9.0"},
      {public_key,"Public key infrastructure","1.6.1"},
      {asn1,"The Erlang ASN1 compiler version 5.0.6","5.0.6"},
      {os_mon,"CPO  CXC 138 46","2.4.5"},
      {jsx,"a streaming, evented json parsing toolkit","2.8.2"},
      {xmerl,"XML parser","1.3.17"},
      {recon,"Diagnostic tools for production use","2.3.2"},
      {crypto,"CRYPTO","4.3"},
      {inets,"INETS  CXC 138 49","7.0"},
      {lager,"Erlang logging framework","3.6.3"},
      {goldrush,"Erlang event stream processor","0.1.9"},
      {compiler,"ERTS  CXC 138 10","7.2.2"},
      {syntax_tools,"Syntax tools","2.1.5"},
      {syslog,"An RFC 3164 and RFC 5424 compliant logging framework.","3.4.2"},
      {sasl,"SASL  CXC 138 11","3.2"},
      {stdlib,"ERTS  CXC 138 10","3.5.1"},
      {kernel,"ERTS  CXC 138 10","6.0"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang/OTP 21 [erts-10.0.2] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:64] [hipe]\n"},
 {memory,
     [{connection_readers,0},
      {connection_writers,0},
      {connection_channels,0},
      {connection_other,0},
      {queue_procs,0},
      {queue_slave_procs,0},
      {plugins,5892},
      {other_proc,23711656},
      {metrics,184484},
      {mgmt_db,0},
      {mnesia,72912},
      {other_ets,2421216},
      {binary,77616},
      {msg_index,28656},
      {code,20418905},
      {atom,1082561},
      {other_system,10119414},
      {allocated_unused,2210768},
      {reserved_unallocated,2273280},
      {strategy,rss},
      {total,[{erlang,58123312},{rss,62607360},{allocated,60334080}]}]},
 {alarms,[]},
 {listeners,[{clustering,25672,"::"},{amqp,5672,"::"}]},
 {vm_memory_calculation_strategy,rss},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,2926336409},
 {disk_free_limit,50000000},
 {disk_free,8127483904},
 {file_descriptors,
     [{total_limit,924},{total_used,2},{sockets_limit,829},{sockets_used,0}]},
 {processes,[{limit,1048576},{used,212}]},
 {run_queue,1},
 {uptime,505},
 {kernel,{net_ticktime,60}}]

Please, How I can solve this?

Thanks in advance!

Felix

[mcouthon]

When you say that RabbitMQ is installed and started before the Cloudify manager is installed, what do you mean?

Is there any specific reason that your RMQ is taking so long to start?

[ghost]

Thanks for your reply @mcouthon

First, I run cfy_manager, when it fail, I test if rabbitmq is the problem itself running rabbitmqctl, and run without problem as you can see in the logs before.
No, I dont have specific reason in why rabbitmq is taking so long to start, rabbitmq by default take a bit more to start than other service.

Please, How I can change the timeout if is this the problem?

Regards

Felix

[mcouthon]

There is currently no way to do this without altering the python code inside the cfy_manager package. This is the place where we wait for the port to be open: https://github.com/cloudify-cosmo/cloudify-manager-install/blob/master/cfy_manager/utils/network.py#L51
If you are comfortable with changing python code, you could increase this number as high as you'd like.

As you can see, though, it does 24 retries with a 2 second sleep each time. So it should be plenty.

[ghost]

Thanks so much.