-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rabbitmq IP sent to the EMS is taken from the nfvo properties #43
Comments
You are referring to the parameter brokerIp, right? Yes that is still the case. I had the broker set to localhost in the nfvo file, and the EMS on the virtual machines would fail because of that. Once I changed it to a non-loopback IP it started working. It would be best to have it as a parameter in the generic properties file for that reason. |
@lorenzotomasini I assume this is done, right? |
why would you assume that? |
Hi @gc4rella I am using NFVO 5.2.0 and generic VNFM 5.2.0 Below is the log on VNFM and on VNF. Log on VNFM java.util.concurrent.TimeoutException: After 1000 seconds the ems did not answer. You can change this value by editing the application.properties propery "vnfm.rabbitmq.sar.timeout" Log from VNF SIPp ubuntu@sipp-client-6509088:/var/log/openbaton$ tail -f ems-receiver.log ubuntu@sipp-client-6509088:/var/log/openbaton$ ping 10.250.192.249 excerpt form booting log on VNF
|
I am having the exact same problem as @anhtrung87vn . Has anybody found a solution for this? Any help would be very much appriciated! |
Using release 4.0.0 it seems that the generic VNFM uses the rabbitmqIP which is set in the nfvo properties file, not the one set in the generic vnfm properties. Should be checked for upcoming release whether this is still the case.
The text was updated successfully, but these errors were encountered: