Unable to add host - cannot find the server resources at http:// x.x.x.x

[mjstark]

Have tried to add host. Im able to ping the host, so I know its up. I've tried adding a host via key and password and I get the same issue regarding "cannot find the server resources at . This is a snipplet of my log file where you see the log entry when I tried adding my host server.

help on this matter would be greatly appreciated.

Thanks

[boring-cyborg[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[DaanHoogland]

@mjstark , is there a firewall in between (check not only port 22 but also 8250 for instance.

[mjstark]

Will check and get back to u

[mjstark]

Port 8250 wasn't open, because the agent is restarting every few seconds I found, with code exited, with status=67.

However, "libvirtd" is running fine....

agent.properties (copied from another KVM host and replaced the "guid" and the LibvirtComputingResource.name, including "LibvirtComputingResource.name"

I used uuidgen to generate a new guid and uuid

cluster=1
LibvirtComputingResource.name=cloudstack-kvm03.gigabitguy.com
pod=1
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
private.network.device=cloudbr0
domr.scripts.dir=scripts/network/domr/kvm
guest.network.device=cloudbr0
keystore.passphrase=gdkGRUvUhb58BzTt
hypervisor.type=kvm
port=8250
zone=1
public.network.device=cloudbr0
local.storage.uuid=d912e269-dd88-4709-afae-83071a808a5a
LibvirtComputingResource.uuid=5e9bcbe0-d3b8-463d-a27f-147fa9c24f94
host=172.16.5.1
guid=d912e269-dd88-4709-afae-83071a808a5a
LibvirtComputingResource.id=2
workers=5
iscsi.session.cleanup.enabled=false
vm.migrate.wait=3600

[mjstark]

just to add...

the other KVM host are up and running fine, same h/w, software versions and network interfaces and bridge's

[rajujith]

@mjstark can you enable DEBUG level log verbosity and restart the agent.

sed -i 's/INFO/DEBUG/g' /etc/cloudstack/agent/log4j-cloud.xml

Review /var/log/cloudstack/agent/agent.log for the issues in connecting to the management server or starting the agent.

Make sure the '172.16.5.1' is the management server IP.

[DaanHoogland]

also make sure the right ports are open.