Error Host Added

[Technology Rss]

Hello dear,

I have 2 server AlmaLinux8 and create Basic zone using all public ip 
address.


1. ACS MGMT+NFS
2. KVM

After create basic zone I see below error
https://prnt.sc/tFkMf4uUVL86



2023-12-06 05:09:00,781 ERROR [kvm.resource.LibvirtConnection] 
(Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: 
invalid connection pointer in virConnectGetVersion
2023-12-06 05:09:05,701 INFO  [cloud.agent.Agent] (Agent Timer:null) 
(logid:) Connected to the host: 80.240.28.190
2023-12-06 05:09:05,701 INFO  [cloud.agent.Agent] (Agent Timer:null) 
(logid:) The startup command is now cancelled
2023-12-06 05:09:05,701 INFO  [cloud.agent.Agent] (Agent Timer:null) 
(logid:) Lost connection to host: 80.240.28.190. Attempting reconnection 
while we still have 0 commands in progress.
2023-12-06 05:09:05,701 INFO  [utils.nio.NioClient] (Agent Timer:null) 
(logid:) NioClient connection closed
2023-12-06 05:09:05,701 INFO  [cloud.agent.Agent] (Agent Timer:null) 
(logid:) Reconnecting to host:80.240.28.190
2023-12-06 05:09:05,701 INFO  [utils.nio.NioClient] (Agent Timer:null) 
(logid:) Connecting to 80.240.28.190:8250
2023-12-06 05:09:05,708 INFO  [utils.nio.Link] (Agent Timer:null) 
(logid:) Conf file found: /etc/cloudstack/agent/agent.properties
2023-12-06 05:09:05,790 INFO  [utils.nio.NioClient] (Agent Timer:null) 
(logid:) SSL: Handshake done
2023-12-06 05:09:05,790 INFO  [utils.nio.NioClient] (Agent Timer:null) 
(logid:) Connected to 80.240.28.190:8250
2023-12-06 05:09:05,817 INFO  [utils.linux.KVMHostInfo] 
(Agent-Handler-1:null) (logid:) Fetching CPU speed from command "lscpu".
2023-12-06 05:09:05,823 INFO  [utils.linux.KVMHostInfo] 
(Agent-Handler-1:null) (logid:) Command [lscpu | grep -i 'Model name' | 
head -n 1 | egrep -o '[[:digit:]].[[:digit:]]+GHz' | sed 's/GHz//g'] 
resulted in the value [3800] for CPU speed.
2023-12-06 05:09:05,858 ERROR [kvm.resource.LibvirtConnection] 
(Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: 
invalid connection pointer in virConnectGetVersion
2023-12-06 05:09:10,791 INFO  [cloud.agent.Agent] (Agent Timer:null) 
(logid:) Connected to the host: 80.240.28.190



Please give me any idea what is issue my environment.

--

*Thanks & Regards.*

*Support Admin*



*Facebook  | Twitter 
 | YouTube 
 | LinkedIn 
*


*Address : *116/1 West Malibagh, D. I. T Road

Dhaka-1217, Bangladesh

*Mob :* +88 01716915504

*Email :* support.ad...@technologyrss.com

*Web :* www.technologyrss.com

Re: [DISCUSS] Adopting Github Discusssions Users Forum

[Nux]

Hey Rohit,

The argument applies, indeed, but it's too late for those... Isn't it? 



On 5 December 2023 14:23:53 GMT, Rohit Yadav  wrote:
>Lucian, all,
>
>Your argument pretty would also apply to also our current use of Github issues 
>and pull requests (and milestones, CI/github actions etc), which have become 
>are daily drivers.
>
>I had another round of checks - from an ASF/mailing lists point of view, in 
>case Github goes the wrong path, all such discussions will still be available 
>on users@ ML (archive) and possibly a migration path would be determined by 
>the ASF infra (such as to Gitlab etc).
>
>
>Regards.
>
>
>From: Nux 
>Sent: Tuesday, November 28, 2023 15:40
>To: dev@cloudstack.apache.org 
>Cc: Rohit Yadav 
>Subject: Re: [DISCUSS] Adopting Github Discusssions Users Forum
>
>Personally I'm against that, as it will dilute the community and once
>the mailing lists will get inactive they'll stay that way.
>
>Also github/discussions is a proprietary platform at Microsoft's whim, I
>think this goes against the spirit of the project as free software.
>
>That said, I'll be "voting" -0, don't want to get in the way of
>"progress".
>
>On 2023-11-28 09:28, Rohit Yadav wrote:
>> All,
>>
>> It's been a while since I had last proposed adopting and trying the
>> Github Discussions feature for our users community. Since then, the ASF
>> infra seems to have enabled integration and allowing Discussions
>> integrated with mailing lists:
>> https://github.com/search?q=.asf.yaml+discussions=code
>>
>> Following discussions with both technical and non-technical users from
>> the CCC, I believe we should try this out and use it for users to
>> discuss their ideas, questions, and problems, all that traditionally
>> has happened on the users@ ML; while been integrating such discussions
>> on the users@ ML. The Discussions platform could be used by developers
>> too to get feedback from users.
>>
>> That said, we MUST continue to use our mailing lists for any project
>> governance related matters such as releases related discussions,
>> releases voting, and any form of consensus and decision making.
>>
>> I've proposed a PR for this here where the discussions feature is tied
>> to users@ ML:
>> https://github.com/apache/cloudstack/pull/8274/files
>>
>> Thoughts and feedback?
>>
>>
>> Regards.
>
> 
>

Re: [DISCUSS] log guidelines

[João Jandre Paraquetti]

Hello all,

As someone who has worked a lot on logging in this project, I feel like 
a set of log guidelines are a good addition. I generally agree with 
Daan's ideas; however, I think that the error level was oversimplified. 
As Daan already said, there are two main reasons for error logs: "the 
system can not execute a user request or part of the system is degraded".


When the system cannot execute a user request, a simple message 
explaining why it's not possible to execute the request is often enough. 
However, when the error happens because of system degradation, there are 
times when having a stacktrace can save hours of debugging, as the error 
might be hard to reproduce. Also, if the error is occurring in a 
production environment, changing the log level to debug means restarting 
ACS's components, possibly leading to downtime and/or more errors. The 
second issue will be solved with the log4j2 PR, but the first one can 
still be a pain.


In summary, a hard rule would not address all situations, but a 
guideline or good practices guide would be a great addition to ACS.


Best regards,
João Jandre


On 12/4/23 10:51, Daan Hoogland wrote:

There have been some discussions on github PRs about the subject of
proper logging and I want to use this to start a discussion and come
to some guidelines that hopefully everybody can agree to.

My idea is the following

Fatal:
- include a reason why the system can not function anymore,
- be followed by a System.exit() call,
- include a stack trace if it is reasonable to expect this would give
properly helpful information.
I did a quick search and we have 2 fatal calls in the system. Neither
is followed by a System.exit() and I think they can be replaced by
error()/debug() combinations

Error:
- include a reason why the system can not execute a user request or
why part of the system is degraded.
- should *not* include a stack trace

Warn:
- include a reason why the system might not behave as the user is
expecting. (configuration or integration missing for example,)
- should *not* include a stack trace

Info:
- is for informationals to the operator like resource lifecycle
messages or deployment planning considderations
- should *not* include a stack trace

Debug:
-  information to be turned on when trouble shooting or developing.
This information should not be needed for normal operation
- if a thrown exception is caught and not rethrown, the stack trace of
such exception

Trace:
- whatever you feel helps you during development of a
feature/enhancement/fix/improvement that is not needed in any kind of
operational way.

As I think the two fatal()s we have are not genuine, I think stack
traces are only for Debug and Trace level, where Debug can be
temporarily turned on in production and Trace is fro developers
exclusively,

I realise the current state of the system is far from this behaviour,
but i like to think we can grow in the direction as I describe and I
hope we can refine this to a generic guideline to be used in reviews.

4.20 plans

[Daan Hoogland]

devs,

Other than we all have great new plans for integrations and other
features for 4.20 and we have about 300 issues to solve, There are
some platform issues that need addressing. So far I can think of
- the outstanding logging PR
- java 11 is out of support and we'll need to support a higher version

I think we must address these as soon as we have a release.
Are there any other issues to address?

-- 
Daan

Re: [VOTE] Adopt Github Discusssions as Users Forum

[Wido den Hollander]

-0: Agree with Nux (see his concern in another e-mail)

Op 04/12/2023 om 22:56 schreef Nux:

-0 - I have voiced my concerns already.


On 2023-12-04 08:01, Rohit Yadav wrote:

All,

Following the discussion thread on adopting Github Discussions as 
users forum [1], I put the following proposal for a vote:



  1.  Adopt and use Github Discussions as user forums.
  2.  The Github Discussions feature is tied with the 
us...@cloudstack.apache.org mailing list (PR: 
https://github.com/apache/cloudstack/pull/8274).
  3.  Any project governance and decision-making thread such as 
voting, releases etc. should continue to use the project mailing lists.


Vote will be open for 120 hours (by Friday, 8th Dec).

For sanity in tallying the vote, can PMC members please be sure to 
indicate "(binding)" with their vote?


[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8


Regards.

Re: [VOTE] Adopt Github Discusssions as Users Forum

[Boris Stoyanov]

+1

From: Wido den Hollander 
Date: Tuesday, 5 December 2023 at 8:19
To: us...@cloudstack.apache.org , Nux 
, dev@cloudstack.apache.org 
Cc: priv...@cloudstack.apache.org 
Subject: Re: [VOTE] Adopt Github Discusssions as Users Forum
-0: Agree with Nux (see his concern in another e-mail)

Op 04/12/2023 om 22:56 schreef Nux:
> -0 - I have voiced my concerns already.
>
>
> On 2023-12-04 08:01, Rohit Yadav wrote:
>> All,
>>
>> Following the discussion thread on adopting Github Discussions as
>> users forum [1], I put the following proposal for a vote:
>>
>>
>>   1.  Adopt and use Github Discussions as user forums.
>>   2.  The Github Discussions feature is tied with the
>> us...@cloudstack.apache.org mailing list (PR:
>> https://github.com/apache/cloudstack/pull/8274).
>>   3.  Any project governance and decision-making thread such as
>> voting, releases etc. should continue to use the project mailing lists.
>>
>> Vote will be open for 120 hours (by Friday, 8th Dec).
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>> indicate "(binding)" with their vote?
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8
>>
>>
>> Regards.

 

Re: [DISCUSS] Adopting Github Discusssions Users Forum

[Rohit Yadav]

Lucian, all,

Your argument pretty would also apply to also our current use of Github issues 
and pull requests (and milestones, CI/github actions etc), which have become 
are daily drivers.

I had another round of checks - from an ASF/mailing lists point of view, in 
case Github goes the wrong path, all such discussions will still be available 
on users@ ML (archive) and possibly a migration path would be determined by the 
ASF infra (such as to Gitlab etc).


Regards.


From: Nux 
Sent: Tuesday, November 28, 2023 15:40
To: dev@cloudstack.apache.org 
Cc: Rohit Yadav 
Subject: Re: [DISCUSS] Adopting Github Discusssions Users Forum

Personally I'm against that, as it will dilute the community and once
the mailing lists will get inactive they'll stay that way.

Also github/discussions is a proprietary platform at Microsoft's whim, I
think this goes against the spirit of the project as free software.

That said, I'll be "voting" -0, don't want to get in the way of
"progress".

On 2023-11-28 09:28, Rohit Yadav wrote:
> All,
>
> It's been a while since I had last proposed adopting and trying the
> Github Discussions feature for our users community. Since then, the ASF
> infra seems to have enabled integration and allowing Discussions
> integrated with mailing lists:
> https://github.com/search?q=.asf.yaml+discussions=code
>
> Following discussions with both technical and non-technical users from
> the CCC, I believe we should try this out and use it for users to
> discuss their ideas, questions, and problems, all that traditionally
> has happened on the users@ ML; while been integrating such discussions
> on the users@ ML. The Discussions platform could be used by developers
> too to get feedback from users.
>
> That said, we MUST continue to use our mailing lists for any project
> governance related matters such as releases related discussions,
> releases voting, and any form of consensus and decision making.
>
> I've proposed a PR for this here where the discussions feature is tied
> to users@ ML:
> https://github.com/apache/cloudstack/pull/8274/files
>
> Thoughts and feedback?
>
>
> Regards.

 

Re: [PR] Documentation for Object Storage feature [cloudstack-documentation]

[via GitHub]

vladimirpetrov commented on PR #338:
URL: 
https://github.com/apache/cloudstack-documentation/pull/338#issuecomment-1840437001

   The link for one of the images is wrong, currently it is:
   
   ```
   
https://qa.cloudstack.cloud/builds/docs-build/pr/338/installguide/_static/images/add-object-storage.png
   ```
   
   but the png is called 
   
   ```
   source/_static/images/add-object-store.png
   ```
   
   
![image](https://github.com/apache/cloudstack-documentation/assets/12384665/8afb101a-7c60-4f0e-891a-09981092f298)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Add missing license to github action workflow [cloudstack-documentation]

[via GitHub]

rohityadavcloud merged PR #362:
URL: https://github.com/apache/cloudstack-documentation/pull/362


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Documentation for Object Storage feature [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #338:
URL: 
https://github.com/apache/cloudstack-documentation/pull/338#issuecomment-1840337200

   QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/338. 
(QA-JID 174)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Docs for KVM Ingestion feature [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #356:
URL: 
https://github.com/apache/cloudstack-documentation/pull/356#issuecomment-1840337078

   QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/356. 
(QA-JID 175)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Docs for KVM Ingestion feature [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #356:
URL: 
https://github.com/apache/cloudstack-documentation/pull/356#issuecomment-1840333864

   @rohityadavcloud a Jenkins job has been kicked to build the document. I'll 
keep you posted as I make progress.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Documentation for Object Storage feature [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #338:
URL: 
https://github.com/apache/cloudstack-documentation/pull/338#issuecomment-1840333725

   @vladimirpetrov a Jenkins job has been kicked to build the document. I'll 
keep you posted as I make progress.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Documentation for Object Storage feature [cloudstack-documentation]

[via GitHub]

vladimirpetrov commented on PR #338:
URL: 
https://github.com/apache/cloudstack-documentation/pull/338#issuecomment-1840319022

   @blueorangutan docbuild


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Docs for KVM Ingestion feature [cloudstack-documentation]

[via GitHub]

rohityadavcloud commented on PR #356:
URL: 
https://github.com/apache/cloudstack-documentation/pull/356#issuecomment-1840318166

   @blueorangutan docbuild


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Import VMware VMs into KVM - Documentation [cloudstack-documentation]

[via GitHub]

DaanHoogland closed pull request #342: Import VMware VMs into KVM - 
Documentation
URL: https://github.com/apache/cloudstack-documentation/pull/342


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Kvm networking examples with "netplan" [cloudstack-documentation]

[via GitHub]

DaanHoogland closed pull request #341: Kvm networking examples with "netplan"
URL: https://github.com/apache/cloudstack-documentation/pull/341


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Update ssh key path on VMware envs [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #347:
URL: 
https://github.com/apache/cloudstack-documentation/pull/347#issuecomment-1840307150

   QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/347. 
(QA-JID 173)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Update ssh key path on VMware envs [cloudstack-documentation]

[via GitHub]

DaanHoogland closed pull request #347: Update ssh key path on VMware envs
URL: https://github.com/apache/cloudstack-documentation/pull/347


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] remove Juniper plugin references [cloudstack-documentation]

[via GitHub]

DaanHoogland closed pull request #348: remove Juniper plugin references
URL: https://github.com/apache/cloudstack-documentation/pull/348


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Docs for KVM Ingestion feature [cloudstack-documentation]

[via GitHub]

DaanHoogland closed pull request #356: Docs for KVM Ingestion feature
URL: https://github.com/apache/cloudstack-documentation/pull/356


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] veeam: update API commands and versions in doc [cloudstack-documentation]

[via GitHub]

DaanHoogland closed pull request #357: veeam: update API commands and versions 
in doc
URL: https://github.com/apache/cloudstack-documentation/pull/357


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Documentation for Object Storage feature [cloudstack-documentation]

[via GitHub]

blueorangutan commented on PR #338:
URL: 
https://github.com/apache/cloudstack-documentation/pull/338#issuecomment-1840282562

   @vladimirpetrov a Jenkins job has been kicked to build the document. I'll 
keep you posted as I make progress.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Documentation for Object Storage feature [cloudstack-documentation]

[via GitHub]

vladimirpetrov commented on PR #338:
URL: 
https://github.com/apache/cloudstack-documentation/pull/338#issuecomment-1840280815

   @blueorangutan docbuild


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org