Host error (miniONE)

Community Support
1

Hi,
I’m fairly new to OpenNebula and I just installed it with miniONE on our server(Ubuntu 24.04).
Installation was successful and KVM is enabled and the services are confirmed running.

When I login to FireEdge I created the host but cannot enable it, it only shows “ERROR”.

Could you offer any guidance on how I can resolve this?

Thanks.

2

Hello @it_asigra,

Welcome to this forum. May I ask why you installed miniONE?, let me know if you need to test OpenNebula for other purposes too.

In any case, for your situation, I would suggest to follow these steps:

  1. Verify Host Status in FireEdge Sunstone
  2. Inspect Host Monitoring Information
  3. Examine OpenNebula Logs
  4. Confirm SSH Connectivity
  5. Validate KVM Hypervisor Configuration
  6. Check Network Configuration

If the issue persist, I will ask you to share the logs, and any extra configuration you’ve applied.

Cheers,

3

Hi Francisco,
We wanted something to test a KVM environment. Would miniONE work for our use case?

4

Yep, it will work for testing.
If you need it for a production environment, you will definitely need a full version of OpenNebula Platform.

Cheers,

5

Hi Francisco,
Please see below:

  1. Verify Host Status in FireEdge Sunstone
    STATE: ERROR
  2. Inspect Host Monitoring Information
    will need some guidance on this
  3. Examine OpenNebula Logs
    no errors in oned.log
  4. Confirm SSH Connectivity
    confirmed ok
  5. Validate KVM Hypervisor Configuration
    I believe I set this correctly
    KVM Node Installation — OpenNebula 6.10.3 documentation
  6. Check Network Configuration
    Virtual Network shows READY
6

Hello,

Thanks for the info, but it’s not enough to understand where’s the error, so could you please share what you have by using this command?: onehost show -j <host_id>

Also, logs could give a better picture of the situation, so please share /var/log/one/monitor.log if possible.

Cheers,

7

monitor.log attached
monitor.log (42.2 KB)

results for command `onehost show -j node01:
{
“HOST”: {
“ID”: “7”,
“NAME”: “node01”,
“STATE”: “3”,
“PREV_STATE”: “3”,
“IM_MAD”: “kvm”,
“VM_MAD”: “kvm”,
“CLUSTER_ID”: “0”,
“CLUSTER”: “default”,
“HOST_SHARE”: {
“MEM_USAGE”: “0”,
“CPU_USAGE”: “0”,
“TOTAL_MEM”: “0”,
“TOTAL_CPU”: “0”,
“MAX_MEM”: “16000000”,
“MAX_CPU”: “4”,
“RUNNING_VMS”: “0”,
“VMS_THREAD”: “1”,
“DATASTORES”: {
“DISK_USAGE”: “0”,
“FREE_DISK”: “0”,
“MAX_DISK”: “0”,
“USED_DISK”: “0”
},
“PCI_DEVICES”: {
},
“NUMA_NODES”: {
}
},
“VMS”: {
},
“TEMPLATE”: {
“ERROR”: "Wed Mar 26 09:15:21 2025 : Error monitoring Host node01 (7): ",
“IM_MAD”: “kvm”,
“RESERVED_CPU”: “-4”,
“RESERVED_MEM”: “-16000000”,
“VM_MAD”: “kvm”
},
“MONITORING”: {
}
}
}

8

Hey there,

It looks like this MiniOne has been slightly modified. First of all the HostID should be 0 and not 7 as you see it on the first Error message.

Please take a look to the Documentation: KVM Node Instalation
To understand how to add hosts :wink:

As it seems right now, it looks like you don’t have connection with the frontend, and that’s why the State returns Error.

Cheers,

9

Hi Francisco,

I did follow those steps yesterday actually and still shows error.

Also the HostID is 7 now because I tried adding hosts before & I deleted them(thats why the count it at 7 now) trying to troubleshoot this issue.

10

Looking at the monitoring log you provided there is

Wed Mar 26 09:15:21 2025 [Z0][MDP][W]: Start monitor failed for host 7: Could not update remotes
Wed Mar 26 09:15:21 2025 [Z0][HMM][E]: Unable to monitor host id: 7
Wed Mar 26 09:15:21 2025 [Z0][HMM][D]: Updated Host 7, state ERROR
Wed Mar 26 09:18:36 2025 [Z0][HMM][D]: Monitoring host node01(7)
Wed Mar 26 09:18:36 2025 [Z0][MDP][I]: Command execution failed (exit code: 255): exec 2>/dev/null; cd '/var/lib/one/remotes'/ && rsync -LRaz --delete . 'node01':'/var/tmp/one'/
Wed Mar 26 09:18:36 2025 [Z0][MDP][I]: Received UNDEFINED msg:

When a host is created on the frontend, the frontend will try to sync the driver code at /var/lib/one/remotes to /var/tmp/one/. For this to work, the oneadmin user in the frontend needs to have a passwordless SSH connection to the oneadmin user in the hypervisor host. This is all explain in the documentation linked previously.

This is likely the cause of this problem. Without this, the monitoring cannot start.

11

Thanks Daniel.

I’m trying the steps again. Can you clarify what I should be entering for ‘frontend>’ and ‘node1>’ values for this command?
ssh-keyscan ‘frontend>’ ‘node1>’ ‘node2>’ ‘node3>’ … >> /var/lib/one/.ssh/known_hosts

I’ve entered ‘frontend>’ as the OpenNebula server IP and ‘node1>’ as our Ubuntu server IP. Is this correct?