The IP that agents connect to is configured in CloudStack itself, specifically the "host" parameter in Global Settings. Try setting that to the IP that the management server is listening on 8250/tcp, and restart CloudStack.
Best regards, Kirk On 09/11/2014 06:31 PM, Piers wrote: > On 12/09/14 11:13, Rohit Yadav wrote: >> >> To start again, you don’t have to remove the package or conf again and >> again. Just shutdown all java services (management and agent, tomcat >> etc.) and deploy the database, and finally start the management server. > > Good to know - thank you > >>> # configure with IP thanks to Rohit >>> cloudstack-setup-databases cloud:xxxx@localhost >>> --deploy-as=root:xxxxxx -i 192.168.5.1 >> After you setup databases, just run cloudstack-agent (if KVM) and >> start the cloudstack-management. And you should be good. Make sure >> you’ve openjdk 1.7 installed and if you run “java -version” it should >> say 1.7 version etc. Else google on how to install/setup openjdk 1.7 >> as your default java version/tool. >> > > java version "1.7.0_65" > OpenJDK Runtime Environment (rhel-2.5.1.2.el6_5-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > > > >> Look in the logs for possible errors >> /var/log/cloudstack/management/management-server.log >> >> Looks like you’re playing with KVM, you may try to set up CloudStack >> cloud all in one box: http://bhaisaab.org/logs/cloudstack-kvm/ >> >> > > Getting closer: > > [root@ade1]# tail /var/log/cloudstack/agent/agent.log > > WARN [utils.nio.NioConnection] (Agent-Selector:null) Unable to connect > to remote: is there a server running on port 8250 > > > > > [root@ade1]# /etc/init.d/cloudstack-management start > Starting cloudstack-management: [ OK ] > [root@ade1]# netstat -nap | grep 8250 > [root@ade1]# > > I noticed that the IP the agent was looking on was different to the one > in db.properties > > I am going to wipe the database again and watch the a agent log as well > as management to see where it is going wrong. > > Thanks > > Piers >
