I try to upgrade my datastax setup to DSE 5.01 + opscenter6.0 but I ran into an issue.
I have two interfaces per node : rpc_ip (for clients and management) and listen_ip (inter-node traffic). when I added nodes to opsc I gave the rpc_ip and it works.
opsc itself in connected to rpc_ip only.
but now opsc try to connect to listen_ip to connect agent which is not working (agent are connected to rpc_ip).
I tried both to install agent from package or let opsc install them with the same result.
Regards,
Fred
ok, I found it :-)
in /var/lib/datastax-agent/conf/address.yaml the variable stomp_interface was not set on the correct IP. once fixed (with IP address of opsc in "rpc" network), the agent connected opsc and gave it the right IP (I presume).
in opsc node change to state 'agent detected but is unreachable via http' for a few seconds and then switch to 'agent are healty' state.
Best regards,
Fred
Related
Has anybody tried out virtual machines in the UK area of bluemix?
I am able to start a vm but get an timeout when i try so connect to the vm via ssh.
I used the std Debian image that can be choosen on setup time and injected an ssh key for connecting. The security group I used was allow_all.
When trying to ping or to connect via ssh directly or the openstack cli the connection times out.
regards
Johannes
There was a bug in the setup of the vm, so I actually had no chance to access it.
In Azure, I created a virtual network and then associated an Ubuntu Server virtual machine, created with Azure Resource Manager Deployment method, with the network. I then updated the associated Network Security Group and added an inbound security rule for port 80 (Source:Any, Destination:Any, Service:TCP/80). After installing Apache on the VM, I tried to access the server from my browser, but have run into a wall. I can SSH into the VM just fine, but web is a no-go, and I cannot figure out why. Any help would be appreciated.
It sometimes happen to me too because I forgot to RESTART the VM, yes just restart it. At least this works for me. and also dont forget to add outbound rule too
It worked for me with this inbound rule.
Note that when a VM is created from the portal (in ARM model), it gets automatically associated to a virtual network (vnet), a specific subnet within the vnet and a network security group.
When creating the inbound security rule, make sure to:
identify the correct network security group associated to the VM
use a priority number lower than 65500
set the source port range as *
You also need open port 80 on the VM to allow web access.
I dont think that creating your Network Security Group opens the desired port on the VM automatically.
By default in Azure Resource Manager (ARM), all ports are open; there is no need to make Network Security Groups (NSGs) to open ports, only to close them. Here is an example of an ARM template that deploys an ubuntu VM with apache:
https://github.com/Azure/azure-quickstart-templates/tree/master/apache2-on-ubuntu-vm
Alternatively, if you want an auto-scaling LAP stack using VM Scale Sets (in public preview), you can find the ARM template for that here:
https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-lapstack-autoscale
Hope this helps! :)
I am new in using rabbitMQ and I am trying to sent an 'hello' message over internet,
I am implementing the example available in the rabbitMQ website Java RabbitMQ Hello world example, but in the example they use localhost, I try to change it to the IP address for the sender and receiver computer as explained at the website and put the sender code at a machine and receiver code on another, but it doesn't work.
My questions:
1) is rabbitMQ works over internet or it works just over local network?
2) in both cases, how to configure each computer and what each one should have?
3) Do I need to install rabbitMQ on both machines? or on one of them to run it a server?
Please if anyone can help me in configure them step-by-step, get me an answer with details.
It is a grant problem.
The user guest guest ( default for rabbitmq ) works only in localhost.
Please read this post:
Can't access RabbitMQ web management interface after fresh install
and also this:
RabbitMQ 3.3.1 can not login with guest/guest
To enable guest guest and/or create a new user.
The best practice is to create another user.
Let me answer your questions one by one
1) Yes. RabbitMQ should work over internet, you should be able to connect by giving the public ip of the RabbitMQ server. If you connecting to a server with username/password enabled then it should be provided while creating the connection.
ConnectionFactory factory = new ConnectionFactory();
factory.setUsername("username");
factory.setPassword("pwd");
2) One of the machines should have the RabbitMQ server(broker) installed and running. You can produce or consume messages from any of the machines using Java RabbitMQ client. If you had 3 machines then all three, the RabbitMQ server, message producer and message consumer could be on 3 machines.
3) You don't need to install RabbitMQ on both the machines. Install only on the machine which is running as server.
I have a cluster of computers and I am using one of them as a kickstart server.
I configured DHCP/TFTP/FTP on it and it worked fine. When you boot any box in the cluster and choose to boot from network, it will reach out to that kickstart server, lease an IP, install OS..etc. However, using one box dedicated for kickstart is such a waste of resource and I am wondering is it possible to use some level of virtualization to achieve that, so you end up with a image that is a fully functional ks server and can be running on any box with the virtuallization tool set up?
I have used VirtualBox, Vagrant and Docker before but I am not sure will these tools be powerful enought to do it? Can anyone give some directional guidance or resource to help me get started.
Just virtualize the kickstart server;
Use the virtual environment DHCP Server facility and set the Kickstart Server DHCP module as "proxyDHCP"
When a PXE client boots up will get its IP from the virtual environment DHCP Server and the PXE booting information from the instance of the kickstart proxyDHCP server.
Next the PXE client will know where the TFTP and the rest of the kickstart facilities are located and will continue the boot/install.
Yep I always run kickstart on a VM, A good way to do things is have a bunch of VM's and share them across hosts. Pretty much every site I build out I have the following VM's
Build: running Kickstart/Cobbler, DHCP, TFTP
Provision: running Puppet or Chef
Monitoring: Zenoss or Nagios
The VM's disks all live on iscsi and create the VM's with libvirt KVM. Everything can easily live on one server. I usually have a second server that is prepared for the VM's and if there is ever an outage I just bring them up on the second server.
I am trying to install Eucalyptus in a virtual machine. I am using vmware version 9 and Eucalyptus FastStart version 3.1 And the network adapter which I have choose is NAT..
I am having problem with front end installation. This are some details about the problem
Details about my node controller
Host name:neel.localdomain
Wired connection:
Ip address:192.168.211.11
NetMask:24
Gateway:192.168.211.2
DNS Server:8.8.8.8,8.8.4.4
Wireless conection:
Ip address:192.168.211.12
NetMask:24
Gateway:192.168.211.3
DNS Server:8.8.8.8,8.8.4.4
Details about my front end
HostName:localhost.localdomain
wired connection:
Ip address:192.168.211.13
NetMask:24
Gateway:192.168.211.4
DNS Server:8.8.8.8,8.8.4.4
Wireless connection:
Ip address:192.168.211.14
NetMask:24
Gateway:192.168.211.5
DNS Server:8.8.8.8,8.8.4.4
Public Ip range list:
192.168.211.50-192.168.211.74
During node registration process i enter the following ip address 192.168.211.11 to get registered but i get the following error
ssh:connect to host 192.168.211.11 port 22:no route to host
rsync: connection unexpectedly closed(0 bytes received so far)[sender]
rsync error:unexplained error (code 255) at io.c(600)[sender=3.0.6]
One more doubt of mine is while installing front end do node controller have to be in on state and also logged in and I am installing both the front end and also cloud controller in different virtual machine but in same laptop is that ok?
FastStart is intended for use on hardware, if you want to use Eucalyptus in a VM you might want to try eucadev although the intended usage is development and testing of Eucalyptus.
please refer to faststart guide:
https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html#faststart-guide/index.html
And yes, I also have installed successfully Eucalyptus from Faststart using VMware workstation.
Basic idea is to Install Node Controller First & after that starts the Front end
installation keeping node controller active on the same laptop using VMware.
Hope this will help to solve your NC registration problem.