I uninstalled cloudstack-agent and reinstalled and then set libvirt
parameters again. Libvirt is now running and host is added but it is in
alert state. While adding the UI it raised error ; Unable to find server
resources. However in UO when I click on the host, it shows CPU info
properly.

What to do now?

On Thu, 18 Jul 2024, 19:59 Fariborz Navidan, <mdvlinqu...@gmail.com> wrote:

> Any idea? Please help.
>
> On Thu, 18 Jul 2024, 18:50 Fariborz Navidan, <mdvlinqu...@gmail.com>
> wrote:
>
>> Hi
>>
>> Masking libvirtd service caused cloustack agent not to be able to start
>> or restart. I unmasked libvirtd service and  now in dead status restarting
>> it does not bring it up.
>>
>> On Thu, 18 Jul 2024, 09:34 Wei ZHOU, <ustcweiz...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Can you try the following command ?
>>>
>>> systemctl mask virtqemud.socket virtqemud-ro.socket
>>> virtqemud-admin.socket virtqemud virtnetworkd virtstoraged
>>>
>>>
>>> -Wei
>>>
>>> On Wed, Jul 17, 2024 at 10:23 PM Fariborz Navidan <mdvlinqu...@gmail.com>
>>> wrote:
>>> >
>>> > Thank you. cloudstack-setup-agent exists but it requires me to put
>>> network
>>> > configuration in /etc/sysconfig/network-scripts directory which seems
>>> that
>>> > no longer supported in AlmaLinux 9. I already have bridges created
>>> using
>>> > NetworkManager via nmcli command.
>>> >
>>> > What do you advise?
>>> >
>>> > On Wed, 17 Jul 2024, 21:56 Wei ZHOU, <ustcweiz...@gmail.com> wrote:
>>> >
>>> > > The command should exist on kvm hosts
>>> > >
>>> > > I meant is the systemctl mask command in the pull request
>>> > >
>>> > >
>>> > > On Wednesday, July 17, 2024, Fariborz Navidan <mdvlinqu...@gmail.com
>>> >
>>> > > wrote:
>>> > >
>>> > > > Thank you Wei,
>>> > > >
>>> > > > Unfortunately your given commands cannot be found.
>>> > > >
>>> > > > bash: cloudstack-setup-agent:: command not found
>>> > > >
>>> > > > Any idea?
>>> > > >
>>> > > > Thanks.
>>> > > >
>>> > > > On Wed, 17 Jul 2024, 20:33 Wei ZHOU, <ustcweiz...@gmail.com>
>>> wrote:
>>> > > >
>>> > > > > Maybe the following commands help
>>> > > > >
>>> > > > > https://github.com/apache/cloudstack/pull/7114/files
>>> > > > >
>>> > > > >
>>> > > > > -Wei
>>> > > > >
>>> > > > > On Wed, Jul 17, 2024 at 6:30 PM Fariborz Navidan <
>>> > > mdvlinqu...@gmail.com>
>>> > > > > wrote:
>>> > > > > >
>>> > > > > > To add on this, my host OS is AlmaLinux 9. Any idea on this
>>> issue?
>>> > > > > >
>>> > > > > > Please help me.
>>> > > > > >
>>> > > > > > On Wed, 17 Jul 2024, 18:28 Muhammad Hanis Irfan Mohd Zaid, <
>>> > > > > > hanisirfan.w...@gmail.com> wrote:
>>> > > > > >
>>> > > > > > > To add on this, I've also experienced the same error when
>>> adding a
>>> > > > > host. I
>>> > > > > > > can also confirm that the status of libvirtd from systemctl
>>> that
>>> > > it's
>>> > > > > > > running fine. I can add the host only after doing a couple of
>>> > > reboots
>>> > > > > to
>>> > > > > > > the while the add host process is running in the UI.
>>> > > > > > >
>>> > > > > > > On Wed, 17 Jul 2024, 22:03 Fariborz Navidan, <
>>> > > mdvlinqu...@gmail.com>
>>> > > > > > > wrote:
>>> > > > > > >
>>> > > > > > > > Yes. Output of command systemctl status libvirtd shows
>>> service is
>>> > > > > active
>>> > > > > > > > and running.
>>> > > > > > > >
>>> > > > > > > > Please advise.
>>> > > > > > > >
>>> > > > > > > > Thanks
>>> > > > > > > >
>>> > > > > > > > On Wed, 17 Jul 2024, 16:48 Wei ZHOU, <
>>> ustcweiz...@gmail.com>
>>> > > > wrote:
>>> > > > > > > >
>>> > > > > > > > > is libvirtd running well ?
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > On Wed, Jul 17, 2024 at 3:07 PM Fariborz Navidan <
>>> > > > > > > mdvlinqu...@gmail.com>
>>> > > > > > > > > wrote:
>>> > > > > > > > > >
>>> > > > > > > > > > Hello everyone,
>>> > > > > > > > > >
>>> > > > > > > > > > I'm in a situation where I need to migrate my
>>> infrastructure
>>> > > to
>>> > > > > new
>>> > > > > > > > > servers
>>> > > > > > > > > > as soon as possible. I have installed CS 4.18
>>> management and
>>> > > > > agent on
>>> > > > > > > > the
>>> > > > > > > > > > same node. I have gone through the installation guide
>>> and
>>> > > > > configured
>>> > > > > > > > > > libvirtd based on documentation.  However, I am unable
>>> to
>>> > > add a
>>> > > > > KVM
>>> > > > > > > > host.
>>> > > > > > > > > > Below is the error I am getting in the agent.log file.
>>> Please
>>> > > > > note
>>> > > > > > > > that I
>>> > > > > > > > > > have set all required parameters in libvirt config
>>> file.
>>> > > > > > > > > >
>>> > > > > > > > > > 2024-07-17 14:54:59,872 ERROR [cloud.agent.AgentShell]
>>> > > > > (main:null)
>>> > > > > > > > > (logid:)
>>> > > > > > > > > > Unable to start agent:
>>> > > > > > > > > > com.cloud.utils.exception.CloudRuntimeException:
>>> Failed to
>>> > > > > connect
>>> > > > > > > > socket
>>> > > > > > > > > > to '/var/run/libvirt/virtqemud-sock': Connection
>>> refused
>>> > > > > > > > > >         at
>>> > > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > >
>>> > > > > > >
>>> > > > >
>>> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(
>>> > > > LibvirtComputingResource.java:1097)
>>> > > > > > > > > >         at com.cloud.agent.Agent.<init>(Agent.java:191)
>>> > > > > > > > > >         at
>>> > > > > > > >
>>> com.cloud.agent.AgentShell.launchNewAgent(AgentShell.java:452)
>>> > > > > > > > > >         at
>>> > > > > > > > > >
>>> > > > > > > >
>>> > > > >
>>> > >
>>> com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:431)
>>> > > > > > > > > >         at
>>> > > > > > > com.cloud.agent.AgentShell.launchAgent(AgentShell.java:415)
>>> > > > > > > > > >         at com.cloud.agent.AgentShell.
>>> > > > start(AgentShell.java:511)
>>> > > > > > > > > >         at com.cloud.agent.AgentShell.
>>> > > > main(AgentShell.java:541)
>>> > > > > > > > > >
>>> > > > > > > > > > It says that agent is unable to connect libvirt.
>>> > > > > > > > > >
>>> > > > > > > > > > Please advise.
>>> > > > > > > > > >
>>> > > > > > > > > > Thanks.
>>> > > > > > > > >
>>> > > > > > > >
>>> > > > > > >
>>> > > > >
>>> > > >
>>> > >
>>>
>>

Reply via email to