Community

Right now I'm evaluating Nimbula Director. I have installed nimbula to 3 servers according to Evaluator's guide, but I can't upload evaluator machine images - when I'm uploading images it tries to contact api on port number 444, but it seems that nothging is listening on this port (I have checked this with netcat and ethereal - no TCP connection to this port).

How can I fix this?

Hi Alexander,

Can you logon to one of the nodes and execute the following command:

nimbula-test-services

That command will check/test all the services that need to be running in order for Director to work correctly. The output of that command will give us a clue as to what might be wrong.

Are there firewall rules that might be blocking access?

Regards,
Lee Engel
Nimbula Support

lee@nimbula.com
Hi Alexander,

nimbula-test-services

[nimbulaadmin@8c-89-a5-a2-1c-7a ~]$ sudo nimbula-test-services
2013-03-01 09:04:16,880 INFO: Discovering nodes...
Please enter /root/root password for node lookup:
2013-03-01 09:04:19,778 INFO: Checking for the API...
2013-03-01 09:04:19,784 INFO: Authenticating...
2013-03-01 09:04:20,451 INFO: Discovered 5 nodes in 10.0.220.192/26
2013-03-01 09:04:20,451 INFO: Discovered 5 nodes
2013-03-01 09:04:20,452 INFO: Checking for SSH on all nodes...
2013-03-01 09:04:20,454 INFO: Checking for bIC on all nodes...
2013-03-01 09:04:20,455 INFO: Checking for bIC master in DNS...
2013-03-01 09:04:20,503 INFO: Checking Control Plane DNS...
2013-03-01 09:04:20,505 INFO: Checking PXE stack...
2013-03-01 09:04:20,508 INFO: Checking Gluster servers...
2013-03-01 09:04:20,514 INFO: Checking Hadoop NameNode...
2013-03-01 09:04:20,517 INFO: Checking Hadoop Secondary NameNode...
2013-03-01 09:04:20,519 INFO: Checking Hadoop DataNodes...
2013-03-01 09:04:20,521 INFO: Checking ZooKeepers...
2013-03-01 09:04:20,527 INFO: Checking MongoDB replica sets ...
2013-03-01 09:04:20,529 INFO: Checking API DNS...
2013-03-01 09:04:20,530 INFO: Checking memcache server...
2013-03-01 09:04:20,533 INFO: Checking bAuth...
2013-03-01 09:04:20,535 INFO: Checking bAuthFront...
2013-03-01 09:04:20,538 INFO: Checking bUser...
2013-03-01 09:04:20,540 INFO: Checking bUserFront...
2013-03-01 09:04:20,543 INFO: Checking bImage...
2013-03-01 09:04:20,545 INFO: Checking bFederated...
2013-03-01 09:04:20,548 INFO: Checking bNet...
2013-03-01 09:04:20,550 INFO: Checking bOrchestrationSite...
2013-03-01 09:04:20,552 INFO: Checking bSecSite...
2013-03-01 09:04:20,554 INFO: Checking bServiceSite...
2013-03-01 09:04:20,557 INFO: Checking bStorageSite...
2013-03-01 09:04:20,559 INFO: Checking bEvent...
2013-03-01 09:04:20,561 INFO: Checking bAWS...
2013-03-01 09:04:20,564 INFO: Checking bMeteringSite...
2013-03-01 09:04:20,566 INFO: Checking cluster controllers...
2013-03-01 09:04:20,623 INFO: Checking sanity of cluster controller 10.0.220.207
2013-03-01 09:04:20,623 INFO: Checking site controller...
2013-03-01 09:04:20,660 INFO: Checking for bNode on all nodes...
2013-03-01 09:04:20,704 INFO: Checking sanity of node 10.0.220.210
2013-03-01 09:04:20,749 INFO: Checking sanity of node 10.0.220.209
2013-03-01 09:04:20,814 INFO: Checking sanity of node 10.0.220.205
2013-03-01 09:04:20,857 INFO: Checking sanity of node 10.0.220.207
2013-03-01 09:04:20,895 INFO: Checking sanity of node 10.0.220.211
2013-03-01 09:04:20,895 INFO: Checking for bSecNode on all nodes...
2013-03-01 09:04:20,896 INFO: Checking for bNatNode on all nodes...
2013-03-01 09:04:20,898 INFO: Checking for flow-engine on all nodes...
2013-03-01 09:04:20,900 INFO: Checking DHCP services...
2013-03-01 09:04:20,900 INFO: Checking vService managers...
2013-03-01 09:04:20,900 INFO: Checking bOrchestration managers...
2013-03-01 09:04:20,900 INFO: Checking storage nodes...
2013-03-01 09:04:20,900 INFO: Checking site monitoring...
2013-03-01 09:04:20,903 INFO: Checking cluster monitoring...
2013-03-01 09:04:20,911 INFO: Checking every node has a collecter gmond (gmond-node)
2013-03-01 09:04:20,911 INFO: Checking node monitoring masters are running (gmond)...
2013-03-01 09:04:20,912 INFO: Checking site SNMP trap daemon...
2013-03-01 09:04:20,914 INFO: Checking cluster SNMP trap daemons...
2013-03-01 09:04:20,916 INFO: Checking Nimbula trap handler daemons...
2013-03-01 09:04:20,919 INFO: Checking for SNMP agent on all nodes...
2013-03-01 09:04:20,919 INFO: Checking NTP servers...
2013-03-01 09:04:20,924 INFO: Checking for site logging servers...
2013-03-01 09:04:20,929 INFO: Checking for cluster logging servers...
2013-03-01 09:04:20,934 INFO: Checking for local logging servers...
2013-03-01 09:04:20,936 INFO: Checking for image data endpoint...
2013-03-01 09:04:20,939 INFO: Checking backend webserver...
2013-03-01 09:04:20,941 INFO: Authenticating...
2013-03-01 09:04:21,093 INFO: Listing a collection in each service...
2013-03-01 09:04:25,841 INFO: Checking frontend webserver...
2013-03-01 09:04:25,843 INFO: Authenticating...
2013-03-01 09:04:26,018 INFO: Listing a collection in each service...

lee@nimbula.com

Are there firewall rules that might be blocking access?

No firewall. Tried from the same node:

[nimbulaadmin@8c-89-a5-a2-1c-7a ~]$ nc -vvv 10.0.220.219 444
nc: connect to 10.0.220.219 port 444 (tcp) failed: Connection refused
[nimbulaadmin@8c-89-a5-a2-1c-7a ~]$

From the output of nimbula-test-services, it seems that the cluster is healthy.

Can you paste the command(s) you are using to upload the machine image? (please also include the output of these commands).

Lee

lee@nimbula.com
From the output of nimbula-test-services, it seems that the cluster is healthy.

Can you paste the command(s) you are using to upload the machine image? (please also include the output of these commands).

Lee

Lee, As you can see - netcat gives us 'Connection Refused' on port 444 of api - so this is not depending on commands I'm using to upload an image.

Screenshots attached.

Attachments:

Hi,

It seems that you may have encountered a known issue but I'll need a copy of your site.conf file. Could you attach it?

Regards,
Lee

Edited lee@nimbula.com (March 1, 2013 02:40:57)

Just to clarify - it's not really a "known issue". It's a situation where the default configuration can cause this problem.

A workaround would be to add the machine image using the CLI tool.

Please do send your site.conf in the mean time.

Lee

lee@nimbula.com

Please do send your site.conf in the mean time.

Attached site.conf

Attachments:

Does anybody have ideas how to fix this?

Hi Alexander,

I've requested our development team to get involved with this case. I should have something for you in a few hours.

Regards,
Lee Engel