Hello all, especially Jorge
I followed the thread and want to add something. My experience includes working
with CloudStack and XenServer from 2010-2018, and VMware since version 2, so
approximately 20 years.
First, there is no mature virtualization stack. They are all full of bugs, and
some require a huge technical team to manage, like openstack.
Even VMware, the flagship of virtualization, is full of bugs. Before
Broadcomgetton, there were so many incompetent developers, mostly from Egypt.
A good example is that VMware removed the option to choose suitable RAM and CPU
for master and worker nodes from VMware Tanzu Kubernetes, replacing it with
four predefined policies (e.g., four t-shirts).
We redesigned the wizard to allow choosing custom values, creating a one-time
policy.
A similar situation occurred in 2015 with CloudStack. There was no option to
use custom instances with suitable amounts of RAM and CPU, and the data disks
were nonsensical in my opinion.
Again, we created a wizard option to choose the proper amount of RAM, CPU, and
the appropriate size for the root disk.
We believe each customer's needs and workload are unique. There is no place for
predefined policies or flavors.
Now we are back with CloudStack due to the need for a more affordable cloud
option. However, we also face issues. For example, Kubernetes doesn't work with
XenServer; it is designed mostly for KVM.
KVM, however, doesn't have a normal fiber channel shared storage option. I
don't trust software-defined storages like CEPH or vSAN, as they introduce
fatal bugs almost every month that can result in data loss.
It seems now we need to create CloudStack Kubernetes support for XenServer. We
are doing all this with four very capable architects and developers.
I remember learning CloudStack approx year, around 2010, before we managed to
get the cloud up and running.
So don't whine, download the quick start guide from ShapeBlue, test, follow,
and debug errors.
Lugupidamisega / Best regards,
Kristian Liivak
Tegevjuht / CEO
[ mailto:[email protected] | [email protected] ] | +372 5685 0001
WaveCom AS | ISO 9001, 27001 & 27017 Certified DC and Cloud services
Endla 16, Tallinn 10142 | [ http://www.wavecom.ee/ | www.wavecom.ee ] | [
http://www.facebook.com/wavecom.ee | www.facebook.com/wavecom.ee ]
----- Original Message -----
From: "Jorge Ventura" <[email protected]>
To: [email protected]
Sent: Tuesday, 2 July, 2024 19:01:45
Subject: Re: Install cloudstack 4.19 , TOTAL WASTE OF TIME
On Tue, Jul 2, 2024 at 12:07 PM Rohit Yadav <[email protected]>
wrote:
Jorge,
It appears you’ve some configuration issue that’s specific to your env and
you're missing some package or configuration. Is your nfs/storage behind
some firewall?
I don't have any firewalls running on any host.
I wouldn't recommend using openvswitch with ACs unless you've prior
CloudStack experience. Also, as this is an opensource community driven
project throwing tantrums without sharing the problem isn't useful for
anyone.
I was not throwing tantrums. I am going to stop with this and just say
thanks to everyone that spent their time trying to help me, including you.
Sincerely,
Ventura
I suggest you to try a Ubuntu 22.04 based adv zone env with KVM and bridge
based networking, and read through the project documentation (and help
improve them or report issues). Here are my setup notes if you may find
them useful: https://rohityadav.cloud/blog/cloudstack-kvm/
Regards.
Regards.
________________________________
From: Jorge Ventura <[email protected]>
Sent: Tuesday, July 2, 2024 8:04:41 PM
To: [email protected] <[email protected]>
Subject: Re: Install cloudstack 4.19 , TOTAL WASTE OF TIME
It worth to mention the error below because it's happening before the timer
issue:
*Jul 02 14:31:28 host1-kvm java[2444]: ERROR
[kvm.resource.LibvirtConnection] (Agent-Handler-1:) (logid:) Connection
with libvirtd is broken: invalid connection pointer in
virConnectGetVersion*
On Tue, Jul 2, 2024 at 10:28 AM Jorge Ventura <
[email protected]> wrote:
Hi Guto,
Thank you for your email, I appreciate your attention to this matter.
I am creating an environment for testing and it's all based on Ubuntu
22.04 / Jammy. I am following the instructions from Installation Guide
<https://docs.cloudstack.apache.org/en/4.19.0.0/installguide/index.html
.
The cloudstack management controller is working fine but the problem is
with the kvm host. The log I presented is from the host trying to connect
to the controller at the port 8250.
I just installed chrony because I didn't before and rebooted the host.
Bellow is the two errors I am having but the second is the one that is
causing the exception.
Jul 02 13:06:23 host1-kvm java[1195]:* libvirt: Domain Config error :
invalid connection pointer in **virConnectGetVersion*
Jul 02 13:06:23 host1-kvm java[1195]: ERROR
[kvm.resource.LibvirtConnection] (Agent-Handler-1:) (logid:) Connection
with libvirtd is broken: invalid connection pointer in
virConnectGetVersion
Jul 02 13:06:23 host1-kvm java[1195]: INFO
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:)
Attempting
to create storage pool 598765d0-efc5-46b8-af72-6e6126c5d26d
(Filesystem) in
libvirt
Jul 02 13:06:23 host1-kvm java[1195]: libvirt: Storage Driver error :
Storage pool not found: no storage pool with matching uuid
'598765d0-efc5-46b8-af72-6e6126c5d26d'
Jul 02 13:06:23 host1-kvm java[1195]: WARN
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:) Storage
pool 598765d0-efc5-46b8-af72-6e6126c5d26d was not found running in
libvirt.
Need to create it.
Jul 02 13:06:23 host1-kvm java[1195]: INFO
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:) Didn't
find an existing storage pool 598765d0-efc5-46b8-af72-6e6126c5d26d by
UUID,
checking for pools with duplicate paths
Jul 02 13:06:23 host1-kvm java[1195]: INFO
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:) Trying
to
fetch storage pool 598765d0-efc5-46b8-af72-6e6126c5d26d from libvirt
Jul 02 13:06:23 host1-kvm java[1195]: *libvirt: error : internal error:
could not initialize domain event timer*
Jul 02 13:06:23 host1-kvm java[1195]: ERROR
[kvm.resource.LibvirtComputingResource] (Agent-Handler-1:) (logid:)
Failed
to get libvirt connection for domain event lifecycle
Jul 02 13:06:23 host1-kvm java[1195]: org.libvirt.LibvirtException:
internal error: could not initialize domain event timer
Jul 02 13:06:23 host1-kvm java[1195]: at
org.libvirt.ErrorHandler.processError(Unknown Source)
Jul 02 13:06:23 host1-kvm java[1195]: at
org.libvirt.ErrorHandler.processError(Unknown Source)
Jul 02 13:06:23 host1-kvm java[1195]: at
org.libvirt.Connect.domainEventRegister(Unknown Source)
Jul 02 13:06:23 host1-kvm java[1195]: at
org.libvirt.Connect.domainEventRegister(Unknown Source)
Jul 02 13:06:23 host1-kvm java[1195]: at
org.libvirt.Connect.addLifecycleListener(Unknown Source)
This is a test for proof of concept to present in my company and I am
using all machines in KVM nested. Most of the time I see people
suggesting
in this case to use VirtualBox but I am using KVM in Proxmox. I am
beginning to suspect that more twicks are necessary to overcome this
"domain event timer" issue.
I am also using Virtual Openswitch and had to create two networks in
advance:
<network>
<name>default</name>
<uuid>b966134d-74ec-4d4b-bc00-751899655f27</uuid>
<forward mode='bridge'/>
<bridge name='cloudbr0'/>
<virtualport type='openvswitch'/>
</network>
And
<network>
<name>ovs1</name>
<uuid>ddfe58a5-dc9e-4a7b-9301-7b4c86ad8cc1</uuid>
<forward mode='bridge'/>
<bridge name='cloudbr1'/>
<virtualport type='openvswitch'/>
</network>
And at agent.properties I configured:
network.bridge.type=openvswitch
I think at this point, the problem is the hardware clock that probably
does not allow the event timer configuration.
What do you think ?
Again, thank you.
On Mon, Jul 1, 2024 at 5:43 PM Guto Veronezi <[email protected]>
wrote:
Hello Jorge,
We are sorry that you are not having a good experience deploying the
platform. As Jayanth said, we will try to be as supportive as possible.
Based on the data and log you provided us, it seems to me that there is
some misconfiguration between the OS/hypervisor and CloudStack. Could
you provide us some details about the steps you followed to configure
your environment, like how you installed and configured the OS and the
hypervisor, how you introduced the host in CloudStack (if you manually
configured the agent.properties or let the ACS configure it), and so on.
As more detail you can provide, the more we can help you to track down
and solve the situation.
Best regards,
Daniel Salvador (gutoveronezi)
On 01/07/2024 12:31, Jorge Ventura wrote:
Hi Jayanth,
Thank you for reply.
The certificate problem I overcame setting the global
ca.plugin.root.auth.strictness=false.
After several changes and fixes, cloudstack agent doesn't start. Here
is my
agent.properties in the host:
#Storage
#Mon Jul 01 15:25:54 UTC 2024
cluster=default
pod=default
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
domr.scripts.dir=scripts/network/domr/kvm
host.cpu.manual.speed.mhz=1
hypervisor.type=kvm
port=8250
zone=default
local.storage.uuid=
host=10.0.1.1
guid="6553e7e1-1184-450f-8f04-551aced6820d"
host.manual.speed.mhz=3000
LibvirtComputingResource.id=0
network.bridge.type=openvswitch
workers=5
iscsi.session.cleanup.enabled=false
When I start cloudstack-agent.service, the service fails. Here is the
log:
Jul 01 15:28:11 host1-kvm systemd[1]: cloudstack-agent.service:
Scheduled
restart job, restart counter is at 349.
Jul 01 15:28:11 host1-kvm systemd[1]: Stopped CloudStack Agent.
Jul 01 15:28:11 host1-kvm systemd[1]: cloudstack-agent.service:
Consumed
3.743s CPU time.
Jul 01 15:28:11 host1-kvm systemd[1]: Started CloudStack Agent.
Jul 01 15:28:11 host1-kvm java[55609]: log4j:WARN No appenders could
be
found for logger (com.cloud.agent.AgentShell).
Jul 01 15:28:11 host1-kvm java[55609]: log4j:WARN Please initialize
the
log4j system properly.
Jul 01 15:28:11 host1-kvm java[55609]: log4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.AgentShell]
(main:) (logid:) Agent started
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.AgentShell]
(main:) (logid:) Implementation Version is 4.19.0.1
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.AgentShell]
(main:) (logid:) agent.properties found at
/etc/cloudstack/agent/agent.properties
Jul 01 15:28:11 host1-kvm java[55609]: SLF4J: Failed to load class
"org.slf4j.impl.StaticLoggerBinder".
Jul 01 15:28:11 host1-kvm java[55609]: SLF4J: Defaulting to
no-operation
(NOP) logger implementation
Jul 01 15:28:11 host1-kvm java[55609]: SLF4J: See
http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.AgentShell]
(main:) (logid:) Defaulting to using properties file for storage
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.AgentShell]
(main:) (logid:) Defaulting to the constant time backoff algorithm
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.utils.LogUtils]
(main:)
(logid:) log4j configuration found at
/etc/cloudstack/agent/log4j-cloud.xml
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.AgentShell]
(main:) (logid:) Using default Java settings for IPv6 preference for
agent
connection
Jul 01 15:28:11 host1-kvm java[55609]: INFO [cloud.agent.Agent]
(main:)
(logid:) id is 0
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[cloud.resource.ServerResourceBase] (main:) (logid:) Trying to
autodiscover this resource's private network interface.
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[cloud.resource.ServerResourceBase] (main:) (logid:) Using NIC
[name:cloudbr0 (cloudbr0)] as private NIC.
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:)
uefi.properties
file found at /etc/cloudstack/agent/uefi.properties
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:)
guest.nvram.template.legacy = "/usr/share/OVMF/OVMF_VARS.fd"
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:)
guest.loader.legacy = "/usr/share/OVMF/OVMF_CODE.secboot.fd"
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:)
guest.nvram.template.secure = "/usr/share/OVMF/OVMF_VARS.ms.fd"
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:)
guest.loader.secure ="/usr/share/OVMF/OVMF_VARS.ms.fd"
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:)
guest.nvram.path
= "/var/lib/libvirt/qemu/nvram"
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:) Failed to
find
keystore file: cloud.jks
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtConnection] (main:) (logid:) No existing
libvirtd
connection found. Opening a new one
Jul 01 15:28:11 host1-kvm java[55609]: libvirt: Network Driver error :
Network not found: no network with matching name 'default'
Jul 01 15:28:11 host1-kvm java[55609]: WARN
[kvm.resource.LibvirtComputingResource] (main:) (logid:) Ignoring
libvirt
error.
Jul 01 15:28:11 host1-kvm java[55609]: org.libvirt.LibvirtException:
Network not found: no network with matching name 'default'
Jul 01 15:28:11 host1-kvm java[55609]: at
org.libvirt.ErrorHandler.processError(Unknown Source)
Jul 01 15:28:11 host1-kvm java[55609]: at
org.libvirt.ErrorHandler.processError(Unknown Source)
Jul 01 15:28:11 host1-kvm java[55609]: at
org.libvirt.Connect.networkLookupByName(Unknown Source)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:1136)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.agent.Agent.<init>(Agent.java:193)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.agent.AgentShell.launchNewAgent(AgentShell.java:452)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:431)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.agent.AgentShell.launchAgent(AgentShell.java:415)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.agent.AgentShell.start(AgentShell.java:511)
Jul 01 15:28:11 host1-kvm java[55609]: at
com.cloud.agent.AgentShell.main(AgentShell.java:541)
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:) IO uring
driver
for Qemu: enabled
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.storage.KVMStoragePoolManager] (main:) (logid:) adding storage
adaptor for com.cloud.hypervisor.kvm.storage.LinstorStorageAdaptor
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.storage.KVMStoragePoolManager] (main:) (logid:) adding storage
adaptor for com.cloud.hypervisor.kvm.storage.StorPoolStorageAdaptor
Jul 01 15:28:11 host1-kvm java[55609]: WARN
[kvm.storage.KVMStoragePoolManager] (main:) (logid:) Duplicate
StorageAdaptor type PowerFlex, not loading
com.cloud.hypervisor.kvm.storage.ScaleIOStorageAdaptor
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.storage.KVMStoragePoolManager] (main:) (logid:) adding storage
adaptor for com.cloud.hypervisor.kvm.storage.IscsiAdmStorageAdaptor
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.storage.KVMStoragePoolManager] (main:) (logid:) adding storage
adaptor for com.cloud.hypervisor.kvm.storage.FiberChannelAdapter
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.storage.MultipathSCSIAdapterBase] (main:) (logid:) Loaded
FiberChannelAdapter for StorageLayer
Jul 01 15:28:11 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:) No
libvirt.vif.driver specified. Defaults to OvsVifDriver.
Jul 01 15:28:11 host1-kvm java[55609]: WARN [utils.script.Script]
(main:)
(logid:) Execution of process [55709] for command [/bin/bash -c ip
route |
grep 169.254.0.0/16 ] failed.
Jul 01 15:28:11 host1-kvm java[55609]: WARN [utils.script.Script]
(main:)
(logid:) Process [55709] for command [/bin/bash -c ip route | grep
169.254.0.0/16 ] encountered the error: [].
Jul 01 15:28:11 host1-kvm java[55609]: WARN [utils.script.Script]
(main:)
(logid:) Execution of process [55713] for command [/bin/bash -c ip
address
add 169.254.0.1/255.255.0.0 dev cloud0;ip route add 169.254.0.0/16
dev
cloud0 src 169.254.0.1 ] failed.
Jul 01 15:28:11 host1-kvm java[55609]: WARN [utils.script.Script]
(main:)
(logid:) Process [55713] for command [/bin/bash -c ip address add
169.254.0.1/255.255.0.0 dev cloud0;ip route add 169.254.0.0/16 dev
cloud0
src 169.254.0.1 ] encountered the error: [RTNETLINK answers: File
existsError: Device for nexthop is not up.].
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[cloud.serializer.GsonHelper]
(main:) (logid:) Default Builder inited.
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:) iscsi
session
clean up is disabled
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:) Skipping
the
memory balloon stats period setting, since there are no VMs (active
Libvirt
domains) on this host.
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (main:) (logid:) The
[vm.memballoon.stats.period] property is set to '0', this prevents
memory
statistics from being displayed correctly. Adjust (increase) the
value
of
this parameter to correct this.
Jul 01 15:28:12 host1-kvm java[55609]: INFO [cloud.agent.Agent]
(main:)
(logid:) Agent [id = 0 : type = LibvirtComputingResource : zone =
default :
pod = default : workers = 5 : host = 10.0.1.1 : port = 8250
Jul 01 15:28:12 host1-kvm java[55609]: INFO [utils.nio.NioClient]
(main:)
(logid:) Connecting to 10.0.1.1:8250
Jul 01 15:28:12 host1-kvm java[55609]: INFO [utils.nio.Link] (main:)
(logid:) Conf file found: /etc/cloudstack/agent/agent.properties
Jul 01 15:28:12 host1-kvm java[55609]: WARN [utils.nio.Link] (main:)
(logid:) Failed to load keystore, using trust all manager
Jul 01 15:28:12 host1-kvm java[55609]: INFO [utils.nio.NioClient]
(main:)
(logid:) SSL: Handshake done
Jul 01 15:28:12 host1-kvm java[55609]: INFO [utils.nio.NioClient]
(main:)
(logid:) Connected to 10.0.1.1:8250
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (Agent-Handler-1:) (logid:)
Host
uses control group [cgroup2fs].
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (Agent-Handler-1:) (logid:)
Calculating the max shares of the host.
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.resource.LibvirtComputingResource] (Agent-Handler-1:) (logid:)
The
max shares of the host is [16].
Jul 01 15:28:12 host1-kvm sudo[55750]: root : PWD=/ ; USER=root ;
COMMAND=/usr/bin/grep InitiatorName= /etc/iscsi/initiatorname.iscsi
Jul 01 15:28:12 host1-kvm sudo[55750]: pam_unix(sudo:session): session
opened for user root(uid=0) by (uid=0)
Jul 01 15:28:12 host1-kvm sudo[55750]: pam_unix(sudo:session): session
closed for user root
Jul 01 15:28:12 host1-kvm java[55609]: libvirt: Domain Config error :
invalid connection pointer in virConnectGetVersion
Jul 01 15:28:12 host1-kvm java[55609]:
* ERROR [kvm.resource.LibvirtConnection] (Agent-Handler-1:) (logid:)
Connection with libvirtd is broken: invalid connection pointer in
virConnectGetVersion*
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:)
Attempting
to create storage pool acf61505-38f5-425d-b1c6-071faa28b1fd
(Filesystem) in
libvirt
Jul 01 15:28:12 host1-kvm java[55609]: libvirt: Storage Driver error :
Storage pool not found: no storage pool with matching uuid
'acf61505-38f5-425d-b1c6-071faa28b1fd'
Jul 01 15:28:12 host1-kvm java[55609]: WARN
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:)
Storage
pool acf61505-38f5-425d-b1c6-071faa28b1fd was not found running in
libvirt.
Need to create it.
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:)
Didn't
find an existing storage pool acf61505-38f5-425d-b1c6-071faa28b1fd by
UUID,
checking for pools with duplicate paths
Jul 01 15:28:12 host1-kvm java[55609]: INFO
[kvm.storage.LibvirtStorageAdaptor] (Agent-Handler-1:) (logid:)
Trying to
fetch storage pool acf61505-38f5-425d-b1c6-071faa28b1fd from libvirt
Jul 01 15:28:12 host1-kvm java[55609]: libvirt: error : internal
error:
could not initialize domain event timer
Jul 01 15:28:12 host1-kvm java[55609]:
*ERROR [kvm.resource.LibvirtComputingResource] (Agent-Handler-1:)
(logid:)
Failed to get libvirt connection for domain event lifecycle*
Jul 01 15:28:12 host1-kvm java[55609]: org.libvirt.LibvirtException:
internal error: could not initialize domain event timer
Jul 01 15:28:12 host1-kvm java[55609]: at
org.libvirt.ErrorHandler.processError(Unknown Source)
Jul 01 15:28:12 host1-kvm java[55609]: at
org.libvirt.ErrorHandler.processError(Unknown Source)
Jul 01 15:28:12 host1-kvm java[55609]: at
org.libvirt.Connect.domainEventRegister(Unknown Source)
Jul 01 15:28:12 host1-kvm java[55609]: at
org.libvirt.Connect.domainEventRegister(Unknown Source)
Jul 01 15:28:12 host1-kvm java[55609]: at
org.libvirt.Connect.addLifecycleListener(Unknown Source)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.setupLibvirtEventListener(LibvirtComputingResource.java:3712)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createLocalStoragePool(LibvirtComputingResource.java:3692)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.initialize(LibvirtComputingResource.java:3636)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.agent.Agent.sendStartup(Agent.java:460)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:1125)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.utils.nio.Task.call(Task.java:83)
Jul 01 15:28:12 host1-kvm java[55609]: at
com.cloud.utils.nio.Task.call(Task.java:29)
Jul 01 15:28:12 host1-kvm java[55609]: at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
Jul 01 15:28:12 host1-kvm java[55609]: at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
Jul 01 15:28:12 host1-kvm java[55609]: at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
Jul 01 15:28:12 host1-kvm java[55609]: at
java.base/java.lang.Thread.run(Thread.java:829)
Jul 01 15:28:12 host1-kvm java[55609]: INFO [cloud.agent.Agent]
(Agent-Handler-2:) (logid:) Process agent startup answer, agent id =
0
Jul 01 15:28:12 host1-kvm java[55609]: INFO [cloud.agent.Agent]
(Agent-Handler-2:) (logid:) Set agent id 0
Jul 01 15:28:12 host1-kvm java[55609]: INFO [cloud.agent.Agent]
(Agent-Handler-2:) (logid:) Startup Response Received: agent id = 0
Jul 01 15:28:12 host1-kvm java[55609]: INFO [cloud.agent.Agent]
(AgentShutdownThread:) (logid:) Stopping the agent: Reason = sig.kill
Jul 01 15:28:13 host1-kvm systemd[1]: cloudstack-agent.service: Main
process exited, code=exited, status=1/FAILURE
Jul 01 15:28:13 host1-kvm systemd[1]: cloudstack-agent.service: Failed
with
result 'exit-code'.
Jul 01 15:28:13 host1-kvm systemd[1]: cloudstack-agent.service:
Consumed
3.833s CPU time.
On Mon, Jul 1, 2024 at 11:40 AM Jayanth Babu A
<[email protected]> wrote:
Hi Jorge,
The community likes to be supportive as much as possible. Please let
us
know where you’re stuck.
Is that the subject with “Certificate Problem using Ubuntu
22.04/Jammy:
===> unsupported certificate purpose”?
Regards,
Jayanth Reddy
From: Jorge Ventura <[email protected]>
Date: Monday, 1 July 2024 at 8:03 PM
To: [email protected] <[email protected]>
Subject: Install cloudstack 4.19 , TOTAL WASTE OF TIME
I expected a very mature product but it's not.
Absolute waste of time.
Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL
INFORMATION intended solely for the use of the addressee(s). If you
are not
the intended recipient, please notify the sender by e-mail and delete
the
original message. Further, you are not authorised to copy, disclose,
or
distribute this e-mail or its contents to any other person and any
such
actions are unlawful and strictly prohibited. This e-mail may contain
viruses. NxtGen Datacenter & Cloud Technologies Private Ltd
(“NxtGen”)
has
taken every reasonable precaution to minimize this risk but is not
liable
for any damage you may sustain as a result of any virus in this
e-mail. You
should carry out your own virus checks before opening the e-mail or
attachment. NxtGen reserves the right to monitor and review the
content of
all messages sent to or from this e-mail address. Messages sent to or
from
this e-mail address may be stored on the NxtGen e-mail system. ***
End
of
Disclaimer ***NXTGEN***
