[ovirt-users] Re: [CFP] Virtualization & IaaS Devroom

2020-12-11 Thread Piotr Kliczewski
Friendly reminder that submission deadline for Virtualization & IaaS dev
room is on 20th of December. Please submit your talks!

On Tue, Dec 1, 2020 at 6:37 PM Piotr Kliczewski  wrote:

> We are excited to announce that the call for proposals is now open for the
> Virtualization & IaaS devroom at the upcoming FOSDEM 2021, to be hosted
> virtually on February 6th 2021.
>
> This year will mark FOSDEM’s 21th anniversary as one of the
> longest-running free and open source software developer events, attracting
> thousands of developers and users from all over the world. Due to Covid-19,
> FOSDEM will be held virtually this year on February 6th & 7th, 2021.
>
> About the Devroom
>
> The Virtualization & IaaS devroom will feature session topics such as
> open source hypervisors and virtual machine managers such as Xen Project,
> KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such
> as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and
> OpenNebula.
>
> This devroom will host presentations that focus on topics of shared
> interest, such as KVM; libvirt; shared storage; virtualized networking;
> cloud security; clustering and high availability; interfacing with multiple
> hypervisors; hyperconverged deployments; and scaling across hundreds or
> thousands of servers.
>
> Presentations in this devroom will be aimed at users or developers
> working on these platforms who are looking to collaborate and improve
> shared infrastructure or solve common problems. We seek topics that
> encourage dialog between projects and continued work post-FOSDEM.
>
> Important Dates
>
> Submission deadline: 20th of December
>
> Acceptance notifications: 25th of December
>
> Final schedule announcement: 31st of December
>
> Recorded presentations upload deadline: 15th of January
>
> Devroom: 6th February 2021
>
> Submit Your Proposal
>
> All submissions must be made via the Pentabarf event planning site[1]. If
> you have not used Pentabarf before, you will need to create an account. If
> you submitted proposals for FOSDEM in previous years, you can use your
> existing account.
>
> After creating the account, select Create Event to start the submission
> process. Make sure to select Virtualization and IaaS devroom from the
> Track list. Please fill out all the required fields, and provide a
> meaningful abstract and description of your proposed session.
>
> Submission Guidelines
>
> We expect more proposals than we can possibly accept, so it is vitally
> important that you submit your proposal on or before the deadline. Late
> submissions are unlikely to be considered.
>
> All presentation slots are 30 minutes, with 20 minutes planned for
> presentations, and 10 minutes for Q
>
> All presentations will need to be pre-recorded and put into our system at
> least a couple of weeks before the event.
>
> The presentations should be uploaded by 15th of January and made
> available under Creative
>
> Commons licenses. In the Submission notes field, please indicate that you
> agree that your presentation will be licensed under the CC-By-SA-4.0 or
> CC-By-4.0 license and that you agree to have your presentation recorded.
> For example:
>
> "If my presentation is accepted for FOSDEM, I hereby agree to license all
> recordings, slides, and other associated materials under the Creative
> Commons Attribution Share-Alike 4.0 International License. Sincerely,
> ."
>
> In the Submission notes field, please also confirm that if your talk is
> accepted, you will be able to attend the virtual FOSDEM event for the
> Q We will not consider proposals from prospective speakers who are
> unsure whether they will be able to attend the FOSDEM virtual event.
>
> If you are experiencing problems with Pentabarf, the proposal submission
> interface, or have other questions, you can email our devroom mailing
> list[2] and we will try to help you.
>
>
> Code of Conduct
>
> Following the release of the updated code of conduct for FOSDEM, we'd
> like to remind all speakers and attendees that all of the presentations and
> discussions in our devroom are held under the guidelines set in the CoC
> and we expect attendees, speakers, and volunteers to follow the CoC at all
> times.
>
> If you submit a proposal and it is accepted, you will be required to
> confirm that you accept the FOSDEM CoC. If you have any questions about
> the CoC or wish to have one of the devroom organizers review your
> presentation slides or any other content for CoC compliance, please email
> us and we will do our best to assist you.
>
> Call for Volunteers
>
> We are also looking for volunteers to help run the devroom. We n

[ovirt-users] [CFP] Virtualization & IaaS Devroom

2020-12-01 Thread Piotr Kliczewski
We are excited to announce that the call for proposals is now open for the
Virtualization & IaaS devroom at the upcoming FOSDEM 2021, to be hosted
virtually on February 6th 2021.

This year will mark FOSDEM’s 21th anniversary as one of the longest-running
free and open source software developer events, attracting thousands of
developers and users from all over the world. Due to Covid-19, FOSDEM will
be held virtually this year on February 6th & 7th, 2021.

About the Devroom

The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors and virtual machine managers such as Xen Project, KVM,
bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula.

This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.

Presentations in this devroom will be aimed at users or developers working
on these platforms who are looking to collaborate and improve shared
infrastructure or solve common problems. We seek topics that encourage
dialog between projects and continued work post-FOSDEM.

Important Dates

Submission deadline: 20th of December

Acceptance notifications: 25th of December

Final schedule announcement: 31st of December

Recorded presentations upload deadline: 15th of January

Devroom: 6th February 2021

Submit Your Proposal

All submissions must be made via the Pentabarf event planning site[1]. If
you have not used Pentabarf before, you will need to create an account. If
you submitted proposals for FOSDEM in previous years, you can use your
existing account.

After creating the account, select Create Event to start the submission
process. Make sure to select Virtualization and IaaS devroom from the Track
list. Please fill out all the required fields, and provide a meaningful
abstract and description of your proposed session.

Submission Guidelines

We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.

All presentation slots are 30 minutes, with 20 minutes planned for
presentations, and 10 minutes for Q

All presentations will need to be pre-recorded and put into our system at
least a couple of weeks before the event.

The presentations should be uploaded by 15th of January and made available
under Creative

Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
For example:

"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License. Sincerely,
."

In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend the virtual FOSDEM event for the Q
We will not consider proposals from prospective speakers who are unsure
whether they will be able to attend the FOSDEM virtual event.

If you are experiencing problems with Pentabarf, the proposal submission
interface, or have other questions, you can email our devroom mailing
list[2] and we will try to help you.


Code of Conduct

Following the release of the updated code of conduct for FOSDEM, we'd like
to remind all speakers and attendees that all of the presentations and
discussions in our devroom are held under the guidelines set in the CoC and
we expect attendees, speakers, and volunteers to follow the CoC at all
times.

If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.

Call for Volunteers

We are also looking for volunteers to help run the devroom. We need
assistance with helping speakers to record the presentation as well as
helping with streaming and chat moderation for the devroom. Please contact
devroom mailing list [2] for more information.

Questions?

If you have any questions about this devroom, please send your questions to
our devroom mailing list. You can also subscribe to the list to receive
updates about important dates, session announcements, and to connect with
other attendees.

See you all at FOSDEM!

[1] https://penta.fosdem
.org/submission/FOSDEM21

[2] iaas-virt-devroom at lists.fosdem.org
___
Users mailing list -- users@ovirt.org
To 

[ovirt-users] FOSDEM 2020 Virtualization & IaaS Devroom CfP

2019-11-18 Thread Piotr Kliczewski
Friendly reminder that there are 2 weeks before the submission deadline.

Room day update:
This year Virt and IaaS room will be on the 2nd of February.

See you all at FOSDEM!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LMESSKQKS5PU5PJY3JP4DNSNFNIP67AS/


[ovirt-users] FOSDEM 2020 Virtualization & IaaS Devroom CfP

2019-10-11 Thread Piotr Kliczewski
We are excited to announce that the

call for proposals is now open for the Virtualization & IaaS devroom at the

upcoming FOSDEM 2020, to be hosted on February 1st 2020.

This year will mark FOSDEM’s 20th anniversary as one of the longest-running

free and open source software developer events, attracting thousands of

developers and users from all over the world. FOSDEM will be held once

again in Brussels, Belgium, on February 1st & 2nd, 2020.

This devroom is a collaborative effort, and is organized by dedicated folks

from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, and

Foreman. We would like to invite all those who are involved in these fields

to submit your proposals by December 1st, 2019.

About the Devroom

The Virtualization & IaaS devroom will feature session topics such as open

source hypervisors and virtual machine managers such as Xen Project, KVM,

bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt,

Apache CloudStack, OpenStack, oVirt, QEMU and OpenNebula.

This devroom will host presentations that focus on topics of shared

interest, such as KVM; libvirt; shared storage; virtualized networking;

cloud security; clustering and high availability; interfacing with multiple

hypervisors; hyperconverged deployments; and scaling across hundreds or

thousands of servers.

Presentations in this devroom will be aimed at developers working on these

platforms who are looking to collaborate and improve shared infrastructure

or solve common problems. We seek topics that encourage dialog between

projects and continued work post-FOSDEM.

Important Dates

Submission deadline: 1 December 2019

Acceptance notifications: 10 December 2019

Final schedule announcement: 15th December 2019

Devroom: 1st February 2020

Submit Your Proposal

All submissions must be made via the Pentabarf event planning site[1]. If

you have not used Pentabarf before, you will need to create an account. If

you submitted proposals for FOSDEM in previous years, you can use your

existing account.

After creating the account, select Create Event to start the submission

process. Make sure to select Virtualization and IaaS devroom from the Track

list. Please fill out all the required fields, and provide a meaningful

abstract and description of your proposed session.

Submission Guidelines

We expect more proposals than we can possibly accept, so it is vitally

important that you submit your proposal on or before the deadline. Late

submissions are unlikely to be considered.

All presentation slots are 30 minutes, with 20 minutes planned for

presentations, and 10 minutes for Q

All presentations will be recorded and made available under Creative

Commons licenses. In the Submission notes field, please indicate that you

agree that your presentation will be licensed under the CC-By-SA-4.0 or

CC-By-4.0 license and that you agree to have your presentation recorded.

For example:

"If my presentation is accepted for FOSDEM, I hereby agree to license all

recordings, slides, and other associated materials under the Creative

Commons Attribution Share-Alike 4.0 International License. Sincerely,

."

In the Submission notes field, please also confirm that if your talk is

accepted, you will be able to attend FOSDEM and deliver your presentation.

We will not consider proposals from prospective speakers who are unsure

whether they will be able to secure funds for travel and lodging to attend

FOSDEM. (Sadly, we are not able to offer travel funding for prospective

speakers.)

Submission Guidelines

Mentored presentations will have 25-minute slots, where 20 minutes will

include the presentation and 5 minutes will be reserved for questions.

The number of newcomer session slots is limited, so we will probably not be

able to accept all applications.

You must submit your talk and abstract to apply for the mentoring program,

our mentors are volunteering their time and will happily provide feedback

but won't write your presentation for you!

If you are experiencing problems with Pentabarf, the proposal submission

interface, or have other questions, you can email our devroom mailing

list[2] and we will try to help you.

How to Apply

In addition to agreeing to video recording and confirming that you can

attend FOSDEM in case your session is accepted, please write "speaker

mentoring program application" in the "Submission notes" field, and list

any prior speaking experience or other relevant information for your

application.

Code of Conduct

Following the release of the updated code of conduct for FOSDEM, we'd like

to remind all speakers and attendees that all of the presentations and

discussions in our devroom are held under the guidelines set in the CoC and

we expect attendees, speakers, and volunteers to follow the CoC at all

times.

If you submit a proposal and it is accepted, you will be required to

confirm that you accept the FOSDEM CoC. If you have any questions about the

[ovirt-users] Re: vdsm ssl errors

2019-05-15 Thread Piotr Kliczewski
Gianluca,

Please share the engine log. We shoukd find more info about the issue there.

Thanks,
Piotr

7 paź 2016 20:09 "Gianluca Cecchi"  napisał(a):

>
> On Mon, Jul 25, 2016 at 12:07 PM, Nir Soffer  wrote:
>
>>
>>
>> This log is not very useful as is, we must show the relevant remote
>> address.
>>
>> Should be improved in
>> https://gerrit.ovirt.org/61303
>>
>> Can you try this patch and share the log?
>>
>
> Hello,
> I take on this as I have the same problem.
> I'm in 4.0.3 and it seems that the gerrit above was not inside.
> So I applied and restarted vdsmd.
>
> Now I have
> Oct 07 19:54:10 ovirt01.lutwyn.org vdsm[11306]: vdsm vds.dispatcher ERROR
> SSL error receiving from  192.168.1.211:36296 at 0x359c5f0>: unexpected eof
>
> In my case single host environment with Self Hosted Engine
> Ip of host is 192.168.1.211
> Ip of engine is 192.168.1.212
>
> Let me know if you need full logs and which ones.
>
> in the mean time 1000 line around in vdsm.log here:
> https://drive.google.com/file/d/0BwoPbcrMv8mvTk9SYTF0UDZUMUU/
> view?usp=sharing
>
> Thanks,
> Gianluca
>
>

--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HNUERDH37YZVRQSLDS4Y3CXLYRJWPNZO/


[ovirt-users] Re: vdsm ssl errors

2019-05-14 Thread Piotr Kliczewski
Gianluca,

In the log provided I only see plenty of:

2016-10-07 23:24:43,159 ERROR
[org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
Query 'GetUserProfileQuery' failed: PreparedStatementCallback; bad SQL
grammar [select * from  getuserprofilebyuserid(?)]; nested exception
is org.postgresql.util.PSQLException: The column name
user_portal_vm_auto_login was not found in this ResultSet.
2016-10-07 23:24:43,159 ERROR
[org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
Exception: org.springframework.jdbc.BadSqlGrammarException:
PreparedStatementCallback; bad SQL grammar [select * from
getuserprofilebyuserid(?)]; nested exception is
org.postgresql.util.PSQLException: The column name
user_portal_vm_auto_login was not found in this ResultSet.

This could be not related but I do not see any other exception in there.

@Eli can you please take a look?

Thanks,
Piotr

On Fri, Oct 7, 2016 at 11:28 PM, Gianluca Cecchi
 wrote:
>
> On Fri, Oct 7, 2016 at 10:14 PM, Piotr Kliczewski 
> wrote:
>>
>> Gianluca,
>>
>> Please share the engine log. We shoukd find more info about the issue
>> there.
>>
>> Thanks,
>> Piotr
>>
>>
>
> here it is
> https://drive.google.com/file/d/0BwoPbcrMv8mvQlVwVDlGTVEtR00/view?usp=sharing
>
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PKHNFWVXNQWG3IVQJXKPZ3I3B43GCST4/


[ovirt-users] Re: JSON internal error setting bonding using vdsm-client

2019-01-10 Thread Piotr Kliczewski
Callum,

Do you see any backtraces in vdsm.log or supervdsm.log?

Thanks,
Piotr

On Thu, Jan 10, 2019 at 10:23 AM Callum Smith  wrote:
>
> Dear All,
>
> I’m getting the error: “(code=32603, message=Internal JSON-RPC error: 
> {‘reason’: “‘unicode’ object has no attribute ’sort’”})
> when trying to apply networking configuration with vdsm-client -f bond.json 
> Host setupNetworks
>
> bond.json contains:
>
> {
>   “networks”: {},
>   “bondings”: {
> “bond0”: {
>   “nics”: “eno1+eno2”,
>   “options”: “mode=4”
> }
>   },
>   “options”: {}
> }
>
> Of course python is handling all the arguments as unicode entities rather 
> than strings. Any idea what might be wrong?
>
> Regards,
> Callum
>
> --
>
> Callum Smith
> Research Computing Core
> Wellcome Trust Centre for Human Genetics
> University of Oxford
> e. cal...@well.ox.ac.uk
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UON6H2RCEUY37KIYYUEK7TPNZ6SPHB7L/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CJT74CXB4MI5CS24KS2BBB4V346HTWTX/


[ovirt-users]Fwd: FOSDEM‘19 Virtualization & IaaS Devroom CfP

2018-11-22 Thread Piotr Kliczewski
A friendly reminder that Cfp is due by 1st of December.

Please submit your proposal using:

https://penta.fosdem.org/submission/FOSDEM19

-- Forwarded message -
From: Piotr Kliczewski 
Date: Tue, Oct 16, 2018 at 9:32 AM
Subject: [ovirt-users] FOSDEM‘19 Virtualization & IaaS Devroom CfP
To: users 
Cc: Doron Fediuck 


We are excited to announce that the

call for proposals is now open for the Virtualization & IaaS devroom at the

upcoming FOSDEM 2019, to be hosted on February 2nd 2019.

This year will mark FOSDEM’s 19th anniversary as one of the longest-running

free and open source software developer events, attracting thousands of

developers and users from all over the world. FOSDEM will be held once

again in Brussels, Belgium, on February 2nd & 3rd, 2019.

This devroom is a collaborative effort, and is organized by dedicated folks

from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, and

Foreman. We would like to invite all those who are involved in these fields

to submit your proposals by December 1st, 2018.

About the Devroom

The Virtualization & IaaS devroom will feature session topics such as open

source hypervisors and virtual machine managers such as Xen Project, KVM,

bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt,

Apache CloudStack, OpenStack, oVirt, QEMU and OpenNebula.

This devroom will host presentations that focus on topics of shared

interest, such as KVM; libvirt; shared storage; virtualized networking;

cloud security; clustering and high availability; interfacing with multiple

hypervisors; hyperconverged deployments; and scaling across hundreds or

thousands of servers.

Presentations in this devroom will be aimed at developers working on these

platforms who are looking to collaborate and improve shared infrastructure

or solve common problems. We seek topics that encourage dialog between

projects and continued work post-FOSDEM.

Important Dates

Submission deadline: 1 December 2019

Acceptance notifications: 14 December 2019

Final schedule announcement: 21 December 2019

Devroom: 2nd February 2019

Submit Your Proposal

All submissions must be made via the Pentabarf event planning site[1]. If

you have not used Pentabarf before, you will need to create an account. If

you submitted proposals for FOSDEM in previous years, you can use your

existing account.

After creating the account, select Create Event to start the submission

process. Make sure to select Virtualization and IaaS devroom from the Track

list. Please fill out all the required fields, and provide a meaningful

abstract and description of your proposed session.

Submission Guidelines

We expect more proposals than we can possibly accept, so it is vitally

important that you submit your proposal on or before the deadline. Late

submissions are unlikely to be considered.

All presentation slots are 30 minutes, with 20 minutes planned for

presentations, and 10 minutes for Q

All presentations will be recorded and made available under Creative

Commons licenses. In the Submission notes field, please indicate that you

agree that your presentation will be licensed under the CC-By-SA-4.0 or

CC-By-4.0 license and that you agree to have your presentation recorded.

For example:

"If my presentation is accepted for FOSDEM, I hereby agree to license all

recordings, slides, and other associated materials under the Creative

Commons Attribution Share-Alike 4.0 International License. Sincerely,

."

In the Submission notes field, please also confirm that if your talk is

accepted, you will be able to attend FOSDEM and deliver your presentation.

We will not consider proposals from prospective speakers who are unsure

whether they will be able to secure funds for travel and lodging to attend

FOSDEM. (Sadly, we are not able to offer travel funding for prospective

speakers.)

Speaker Mentoring Program

As a part of the rising efforts to grow our communities and encourage a

diverse and inclusive conference ecosystem, we're happy to announce that

we'll be offering mentoring for new speakers. Our mentors can help you with

tasks such as reviewing your abstract, reviewing your presentation outline

or slides, or practicing your talk with you.

You may apply to the mentoring program as a newcomer speaker if you:

Never presented before or

Presented only lightning talks or

Presented full-length talks at small meetups (<50 ppl)

Submission Guidelines

Mentored presentations will have 25-minute slots, where 20 minutes will

include the presentation and 5 minutes will be reserved for questions.

The number of newcomer session slots is limited, so we will probably not be

able to accept all applications.

You must submit your talk and abstract to apply for the mentoring program,

our mentors are volunteering their time and will happily provide feedback

but won't write your presentation for you!

If you are experiencing problems

[ovirt-users] FOSDEM‘19 Virtualization & IaaS Devroom CfP

2018-10-16 Thread Piotr Kliczewski
We are excited to announce that the

call for proposals is now open for the Virtualization & IaaS devroom at the

upcoming FOSDEM 2019, to be hosted on February 2nd 2019.

This year will mark FOSDEM’s 19th anniversary as one of the longest-running

free and open source software developer events, attracting thousands of

developers and users from all over the world. FOSDEM will be held once

again in Brussels, Belgium, on February 2nd & 3rd, 2019.

This devroom is a collaborative effort, and is organized by dedicated folks

from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, and

Foreman. We would like to invite all those who are involved in these fields

to submit your proposals by December 1st, 2018.

About the Devroom

The Virtualization & IaaS devroom will feature session topics such as open

source hypervisors and virtual machine managers such as Xen Project, KVM,

bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt,

Apache CloudStack, OpenStack, oVirt, QEMU and OpenNebula.

This devroom will host presentations that focus on topics of shared

interest, such as KVM; libvirt; shared storage; virtualized networking;

cloud security; clustering and high availability; interfacing with multiple

hypervisors; hyperconverged deployments; and scaling across hundreds or

thousands of servers.

Presentations in this devroom will be aimed at developers working on these

platforms who are looking to collaborate and improve shared infrastructure

or solve common problems. We seek topics that encourage dialog between

projects and continued work post-FOSDEM.

Important Dates

Submission deadline: 1 December 2019

Acceptance notifications: 14 December 2019

Final schedule announcement: 21 December 2019

Devroom: 2nd February 2019

Submit Your Proposal

All submissions must be made via the Pentabarf event planning site[1]. If

you have not used Pentabarf before, you will need to create an account. If

you submitted proposals for FOSDEM in previous years, you can use your

existing account.

After creating the account, select Create Event to start the submission

process. Make sure to select Virtualization and IaaS devroom from the Track

list. Please fill out all the required fields, and provide a meaningful

abstract and description of your proposed session.

Submission Guidelines

We expect more proposals than we can possibly accept, so it is vitally

important that you submit your proposal on or before the deadline. Late

submissions are unlikely to be considered.

All presentation slots are 30 minutes, with 20 minutes planned for

presentations, and 10 minutes for Q

All presentations will be recorded and made available under Creative

Commons licenses. In the Submission notes field, please indicate that you

agree that your presentation will be licensed under the CC-By-SA-4.0 or

CC-By-4.0 license and that you agree to have your presentation recorded.

For example:

"If my presentation is accepted for FOSDEM, I hereby agree to license all

recordings, slides, and other associated materials under the Creative

Commons Attribution Share-Alike 4.0 International License. Sincerely,

."

In the Submission notes field, please also confirm that if your talk is

accepted, you will be able to attend FOSDEM and deliver your presentation.

We will not consider proposals from prospective speakers who are unsure

whether they will be able to secure funds for travel and lodging to attend

FOSDEM. (Sadly, we are not able to offer travel funding for prospective

speakers.)

Speaker Mentoring Program

As a part of the rising efforts to grow our communities and encourage a

diverse and inclusive conference ecosystem, we're happy to announce that

we'll be offering mentoring for new speakers. Our mentors can help you with

tasks such as reviewing your abstract, reviewing your presentation outline

or slides, or practicing your talk with you.

You may apply to the mentoring program as a newcomer speaker if you:

Never presented before or

Presented only lightning talks or

Presented full-length talks at small meetups (<50 ppl)

Submission Guidelines

Mentored presentations will have 25-minute slots, where 20 minutes will

include the presentation and 5 minutes will be reserved for questions.

The number of newcomer session slots is limited, so we will probably not be

able to accept all applications.

You must submit your talk and abstract to apply for the mentoring program,

our mentors are volunteering their time and will happily provide feedback

but won't write your presentation for you!

If you are experiencing problems with Pentabarf, the proposal submission

interface, or have other questions, you can email our devroom mailing

list[2] and we will try to help you.

How to Apply

In addition to agreeing to video recording and confirming that you can

attend FOSDEM in case your session is accepted, please write "speaker

mentoring program application" in the "Submission notes" field, 

[ovirt-users] Re: Gluster JSON-RPC errors

2018-10-08 Thread Piotr Kliczewski
This error was raised on vdsm side here [1]. I was unable to find
'getiterator' in vdsm code based.
Please provide gluster related logs.

This error means that 'bool' object had no attribute 'getiterator' and
the call failed with runtime issue.

Thanks,
Piotr

[1] 
https://github.com/oVirt/vdsm/blob/ce0721dbf5fbdd2a9a6ee6fd30e0e2bc9e138ef9/lib/yajsonrpc/__init__.py#L351
On Mon, Oct 8, 2018 at 7:32 AM Maton, Brett  wrote:
>
> Sure, log attached this one does have the JSON_RPC errors in it.
>
> Thanks,
> Brett
>
> On Mon, 8 Oct 2018 at 06:08, Kaustav Majumder  wrote:
>>
>> Hi ,
>> I don't see any errors in the vdsm logs you have sent. Can you forward  
>> engine.log as well
>>
>> On Fri, Oct 5, 2018 at 11:56 AM Sahina Bose  wrote:
>>>
>>> Can you provide the vdsm.log and supervdsm.log with the relevant log.
>>> Adding Kaustav to look into this
>>>
>>> On Fri, Oct 5, 2018 at 11:00 AM Maton, Brett  
>>> wrote:


 I'm seeing the following errors appear in the event log every 10 minutes 
 for each participating host in the gluster cluster

 GetGlusterVolumeHealInfoVDS failed: Internal JSON-RPC error: {'reason': 
 "'bool' object has no attribute 'getiterator'"}

 Gluster brick health is good

 Any ideas ?

 oVirt 4.2.7.2-1.el7
 CentOS 7

 ___
 Users mailing list -- users@ovirt.org
 To unsubscribe send an email to users-le...@ovirt.org
 Privacy Statement: https://www.ovirt.org/site/privacy-policy/
 oVirt Code of Conduct: 
 https://www.ovirt.org/community/about/community-guidelines/
 List Archives: 
 https://lists.ovirt.org/archives/list/users@ovirt.org/message/2KLFU2C5UHDFLTH3XUHZ5DGF7WVNGNJZ/
>>
>>
>>
>> Thanks,
>> Kaustav
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IQBRQLRUEIDVMJTNZWWB3SHFDM5RJXNE/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XFMRCDIOIUDXEA2ZNNQKOUH3SEXR4WMC/


[ovirt-users] Re: oVirt 4.2.4: Enable only strong ciphers/Disable TLS versions < 1.2

2018-06-28 Thread Piotr Kliczewski
On Wed, Jun 27, 2018 at 8:13 PM, Nir Soffer  wrote:

> On Tue, Jun 26, 2018 at 5:52 PM Matthias Leopold <
> matthias.leop...@meduniwien.ac.at> wrote:
>
>> Hi,
>>
>> i decided to update my test environment (4.2.2) today and noticed oVirt
>> 4.2.4 is out ;-)
>>
>> i have some dumb questions concerning
>> - BZ 1582527 Enable only strong ciphers from engine to VDSM
>> communication for hosts in cluster level >= 4.2
>> - BZ 1577593 Disable TLS versions < 1.2 for hosts with cluster level >=
>> 4.1
>>
>> Is simply updating a host from 4.2.2 to 4.2.4 enough to apply the
>> changes mentioned above?
>>
>
> Updating is enough, no reinstall is needed.
>
> Piotr, do we need any additional configuration on the host?
>

In order to enable it please follow a doc text from [1] or [2]

[1] https://bugzilla.redhat.com/1582527
[2] https://bugzilla.redhat.com/1577593


> Nir
>
>
>> Or do i have to reinstall hosts in addition to upgrading? Before or
>> after the upgrade?
>>
>> My cluster was on cluster level 4.2 when i started.
>> My hosts are type: Enterprise Linux (CentOS)
>>
>> thx
>> matthias
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
>> guidelines/
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
>> message/REL7JFGVC3D263USMF73HK2GIFNFND5I/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMU5RYWHSZJV3KEF3NFS3IGIXAPT4A6C/


Re: [ovirt-users] General SSLEngine problem

2018-04-30 Thread Piotr Kliczewski
Hi,

Can you please share your engine log?

Thanks,
Piotr

On Wed, Apr 25, 2018 at 12:51 PM, gss...@pku.edu.cn  wrote:
> Hi,
>
> I got this err log when I start my engine service.
>
> 2018-04-25 18:40:21,012+08 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.122.187
> 2018-04-25 18:40:21,019+08 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
>
>
> And loggin my engine GUI, got this err
>
> Missing parameter: 'client_secret'
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] SSL Workflow for oVirt

2018-01-29 Thread Piotr Kliczewski
Gabriel,

I suggest to follow steps from [1]. It should help you to understand
why get "General SSLEngine problem".

Thanks,
Piotr

[1] http://lists.ovirt.org/pipermail/users/2017-September/084320.html

On Tue, Jan 23, 2018 at 1:54 PM, Gabriel Stein  wrote:
> Hi all,
>
> I think that I found a way to solve the problem from:
> http://lists.ovirt.org/pipermail/users/2018-January/086441.html and I'm
> trying to fix it.
>
> But my servers are in Production(50%) and I found that are some errors with
> my SSL Certificates.
>
> ## What I need now? Fixes all certificates problems using my Freeipa
> generated certificates: vdsmclient* on hosts, ovirt-engine communication ssl
> certificates on  hosted-engine.
>
> I made with Freeipa(internal) the certificates for ovirt-engine( only apache
> - self hosted) and Hosts(vsdmclient and vdsmkey) and replaced using this
> howto:
>
> https://gist.github.com/qrkourier/9c9ac3e8b190dcb91d3767179d5a39ea
>
> ## Now ovirt-engine can't contact a Host(Non Responsive) with the
> errors(Yes, I have a Backup from all old certificates):
>
> VDSM host.domain.tld command GetCapabilitiesVDS failed: General SSLEngine
> problem
>
> On engine.log:
>
> 2018-01-23 13:33:40,160+01 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Command
> 'GetAllVmStatsVDSCommand(HostName = host.domain.tld,
> VdsIdVDSCommandParametersBase:{hostId='d6bc650b-7edd-4019-b316-54313217880f'})'
> execution failed: VDSGenericException: VDSNetworkException: General
> SSLEngine problem
> 2018-01-23 13:33:40,160+01 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to fetch vms
> info for host 'host.domain.tld' - skipping VMs monitoring.
>
>
> ## I read, that ovirt-engine generates certificates for all hosts and it
> uses his own CA.
>
>
> Questions:
>
> - How can I fix the communication from hosted-engine and vsdm on hosts?
> Should I copy my Freeipa ca.crt and replace the ca.der file on
> /etc/pki/ovirt-engine/certs?
>
> - Should I  change the engine.cer certificate from
> /etc/pki/ovirt-engine/certs with my Certificate made using Freeipa?
>
> - How to do that properly?
>
> - Where can I find a complete workflow from SSL Certificates from oVirt?
> What certificates should I change?
>
> ## I found some links that to me are confusing(or I'm just dumb), I will
> take my end solution and do a howto to all:
>
> - https://www.ovirt.org/develop/release-management/features/infra/pki/ - how
> updated is that? I can't overwrite a ca from ovirt-engine?
>
> - https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/ -
> Note: Using a commercially issued certificate for HTTPS connections does not
> affect the certificate used for authentication between your Engine and
> hosts. They will continue to use the self-signed certificate generated by
> the Engine...
>
> ... Well, why I keep receiving errors with the self-signed CA from
> ovirt-engine and the disk uploads?(Unable to upload image to disk a-b-c-d-e
> due to a network error. Make sure ovirt-imageio-proxy service is installed
> and configured, and ovirt-engine's certificate is registered as a valid CA
> in the browser. The certificate can be fetched from
> https:///ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA)
>
> Thanks in Advance!
>
> Best Regards,
>
> Gabriel
> PS: I would help with the oVirt Wiki if needed, I would follow the rhce path
> and do the rhcs certification too, will be nice to study a lot.
>
>
>
>
>
>
>
>
>
>
> Gabriel Stein
> --
> Gabriel Ferraz Stein
> Tel.: +49 (0)  170 2881531
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] [ovirt-devel] FOSDEM 2018 - CFP is almost closed!

2017-12-07 Thread Piotr Kliczewski
All,

FOSDEM 18's Virt and IaaS CFP ends today at midnight UTC.
This is your last chance to submit your session, so do not wait any longer.
You can find more details in [1].

Thanks,
Piotr

[1] https://www.ovirt.org/blog/2017/10/come-to-fosdem-event/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Hosts flapping between non-responive and active

2017-11-24 Thread Piotr Kliczewski
Please share engine log.

On Fri, Nov 24, 2017 at 3:38 PM, Matt .  wrote:
> The only thing I can find so far that might be related is this:
>
> 2017-11-24 15:25:07,046+01 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
> (org.ovirt.thread.pool-6-thread-9) [] Executing with domain map:
> {02ad86f9-1da3-44ad-be2f-cbd85376e35a=active}
> 2017-11-24 15:25:07,060+01 WARN
> [org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (SSL Stomp
> Reactor) [] Retry failed
> 2017-11-24 15:25:07,060+01 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
> (DefaultQuartzScheduler4) [14a68b50] Exception during connection
>
> 2017-11-24 14:55 GMT+01:00 Matt . :
>> Hi guys,
>>
>> I have a problem with hosts tha are flapping between NON-responsive
>> and Active. The network is performing well, the VM's are running fine
>> when it happens all the time.
>>
>> I also move a host to a Local Storage DC only without any NFS share
>> attached and even there it happens.
>>
>> In the logs, vdsm.log on the hosts and the engine.log on the engine
>> does not show anything wrong what refers to this behaviour.
>>
>> Where can I look for more information ?
>>
>> My hosts are on the latest 4.1 VDSM versions:
>> Engine: oVirt Engine Version: 4.1.7.6-1.el7.centos
>>
>> Cheers,
>>
>> Matt
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Non-responsive host, VM's are still running - how to resolve?

2017-11-14 Thread Piotr Kliczewski
On Tue, Nov 14, 2017 at 7:09 PM, Artem Tambovskiy
 wrote:
> Thanks, Darrell!
>
> Restarted vdsmd but it didn't helped.
> systemctl status vdsmd -l showing following:
>
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Tue 2017-11-14 21:01:31 MSK; 4min 53s ago
>   Process: 54674 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 54677 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=0/SUCCESS)
>  Main PID: 54971 (vdsm)
>CGroup: /system.slice/vdsmd.service
>├─54971 /usr/bin/python2 /usr/share/vdsm/vdsm
>└─55099 /usr/libexec/ioprocess --read-pipe-fd 84 --write-pipe-fd
> 83 --max-threads 10 --max-queued-requests 10
>
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
> ignoring event u'|virt|VM_status|e0970bbf-11d8-4517-acff-0f8dccbb10a9'
> args={u'e0970bbf-11d8-4517-acff-0f8dccbb10a9': {'status': 'Up',
> 'displayInfo': [{'tlsPort': '5901', 'ipAddress': '80.239.162.106', 'type':
> u'spice', 'port': '-1'}], 'hash': '-6982259661244130819', 'displayIp':
> '80.239.162.106', 'displayPort': '-1', 'displaySecurePort': '5901',
> 'timeOffset': u'0', 'pauseCode': 'NOERR', 'vcpuQuota': '-1', 'cpuUser':
> '0.00', 'monitorResponse': '0', 'elapsedTime': '370019', 'displayType':
> 'qxl', 'cpuSys': '0.00', 'clientIp': '172.16.11.6', 'vcpuPeriod': 10L}}
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
> ignoring event u'|virt|VM_status|b366e466-b0ea-4a09-866b-d0248d7523a6'
> args={u'b366e466-b0ea-4a09-866b-d0248d7523a6': {'status': 'Up',
> 'displayInfo': [{'tlsPort': '5900', 'ipAddress': '0', 'type': u'spice',
> 'port': '-1'}], 'hash': '1858968312777883492', 'displayIp': '0',
> 'displayPort': '-1', 'displaySecurePort': '5900', 'timeOffset': '0',
> 'pauseCode': 'NOERR', 'vcpuQuota': '-1', 'cpuUser': '0.00',
> 'monitorResponse': '0', 'elapsedTime': '453444', 'displayType': 'qxl',
> 'cpuSys': '0.00', 'clientIp': '', 'vcpuPeriod': 10L}}
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
> ignoring event u'|virt|VM_status|ca2815c5-f815-469d-869d-a8fe1cb8c2e7'
> args={u'ca2815c5-f815-469d-869d-a8fe1cb8c2e7': {'status': 'Up',
> 'displayInfo': [{'tlsPort': '5904', 'ipAddress': '80.239.162.106', 'type':
> u'spice', 'port': '-1'}], 'hash': '1149212890076264321', 'displayIp':
> '80.239.162.106', 'displayPort': '-1', 'displaySecurePort': '5904',
> 'timeOffset': u'0', 'pauseCode': 'NOERR', 'vcpuQuota': '-1', 'cpuUser':
> '0.00', 'monitorResponse': '0', 'elapsedTime': '105160', 'displayType':
> 'qxl', 'cpuSys': '0.00', 'clientIp': '172.16.11.6', 'vcpuPeriod': 10L}}
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
> ignoring event u'|virt|VM_status|a083da47-3e39-458c-8822-459af3d2d93a'
> args={u'a083da47-3e39-458c-8822-459af3d2d93a': {'status': 'Up',
> 'displayInfo': [{'tlsPort': '5902', 'ipAddress': '80.239.162.106', 'type':
> u'spice', 'port': '-1'}], 'hash': '5529949835126538749', 'displayIp':
> '80.239.162.106', 'displayPort': '-1', 'displaySecurePort': '5902',
> 'timeOffset': u'0', 'pauseCode': 'NOERR', 'vcpuQuota': '-1', 'cpuUser':
> '0.00', 'monitorResponse': '0', 'elapsedTime': '365326', 'displayType':
> 'qxl', 'cpuSys': '0.00', 'clientIp': '', 'vcpuPeriod': 10L}}
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
> ignoring event u'|virt|VM_status|0b7d02df-0286-4e0e-a50b-1d02915ba81c'
> args={u'0b7d02df-0286-4e0e-a50b-1d02915ba81c': {'status': 'Up',
> 'displayInfo': [{'tlsPort': '5903', 'ipAddress': '80.239.162.106', 'type':
> u'spice', 'port': '-1'}], 'hash': '3267121054607612619', 'displayIp':
> '80.239.162.106', 'displayPort': '-1', 'displaySecurePort': '5903',
> 'timeOffset': '-1', 'pauseCode': 'NOERR', 'vcpuQuota': '-1', 'cpuUser':
> '0.00', 'monitorResponse': '0', 'elapsedTime': '275708', 'displayType':
> 'qxl', 'cpuSys': '0.00', 'clientIp': '', 'vcpuPeriod': 10L}}
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm throttled WARN MOM not
> available.
> Nov 14 21:01:33 ovirt2.telia.ru vdsm[54971]: vdsm throttled WARN MOM not
> available, KSM stats will be missing.
> Nov 14 21:01:34 ovirt2.telia.ru vdsm[54971]: vdsm vds WARN Not ready yet,
> ignoring event u'|virt|VM_status|0b7d02df-0286-4e0e-a50b-1d02915ba81c'
> args={u'0b7d02df-0286-4e0e-a50b-1d02915ba81c': {'status': 'Up', 'username':
> 'Unknown', 'memUsage': '36', 'guestFQDN': '', 'memoryStats': {u'swap_out':
> '0', u'majflt': '0', u'swap_usage': '0', u'mem_cached': '548192',
> u'mem_free': '2679664', u'mem_buffers': '231016', u'swap_in': '0',
> u'swap_total': '786428', u'pageflt': '4346', u'mem_total': '3922564',
> u'mem_unused': '1900456'}, 'session': 'Unknown', 'netIfaces': [],
> 'guestCPUCount': -1, 'appsList': (), 'guestIPs': '', 

Re: [ovirt-users] FOSDEM18 Virt & IaaS Devroom CFP

2017-10-16 Thread Piotr Kliczewski
On Mon, Oct 16, 2017 at 3:54 PM, Piotr Kliczewski <pklic...@redhat.com>
wrote:

> On behalf of oVirt and the Xen Project, we are excited to announce that the
> call for proposals is now open for the Virtualization & IaaS devroom at the
> upcoming FOSDEM 2018, to be hosted on February 3 and 4, 2017.
>
> This year will mark FOSDEM’s 18th anniversary as one of the longest-running
> free and open source software developer events, attracting thousands of
> developers and users from all over the world. FOSDEM will be held once
> again in Brussels, Belgium, on February 3 & 4, 2018.
>
> This devroom is a collaborative effort, and is organized by dedicated folks
> from projects such as OpenStack, Xen Project,, oVirt, QEMU, and
> Foreman. We would like to invite all those who are involved in these fields
> to submit your proposals by December 1st, 2017.
>
> About the Devroom
>
> The Virtualization & IaaS devroom will feature session topics such as open
> source hypervisors and virtual machine managers such as Xen Project, KVM,
> bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
> Apache CloudStack, OpenStack, oVirt, QEMU, OpenNebula, and Ganeti.
>
> This devroom will host presentations that focus on topics of shared
> interest, such as KVM; libvirt; shared storage; virtualized networking;
> cloud security; clustering and high availability; interfacing with multiple
> hypervisors; hyperconverged deployments; and scaling across hundreds or
> thousands of servers.
>
> Presentations in this devroom will be aimed at developers working on these
> platforms who are looking to collaborate and improve shared infrastructure
> or solve common problems. We seek topics that encourage dialog between
> projects and continued work post-FOSDEM.
>
> Important Dates
>
> Submission deadline: 01 December 2017
> Acceptance notifications: 14 December 2017
> Final schedule announcement: 21 December 2017
> Devroom: 03 and 04 February 2018 (two days- different rooms)
>
> Submit Your Proposal
>
> All submissions must be made via the Pentabarf event planning site[1]. If
> you have not used Pentabarf before, you will need to create an account. If
> you submitted proposals for FOSDEM in previous years, you can use your
> existing account.
>
> After creating the account, select Create Event to start the submission
> process. Make sure to select Virtualization and IaaS devroom from the Track
> list. Please fill out all the required fields, and provide a meaningful
> abstract and description of your proposed session.
>
> Submission Guidelines
>
> We expect more proposals than we can possibly accept, so it is vitally
> important that you submit your proposal on or before the deadline. Late
> submissions are unlikely to be considered.
>
> All presentation slots are 45 minutes, with 35 minutes planned for
> presentations, and 10 minutes for Q
>
> All presentations will be recorded and made available under Creative
> Commons licenses. In the Submission notes field, please indicate that you
> agree that your presentation will be licensed under the CC-By-SA-4.0 or
> CC-By-4.0 license and that you agree to have your presentation recorded.
> For example:
>
> "If my presentation is accepted for FOSDEM, I hereby agree to license all
> recordings, slides, and other associated materials under the Creative
> Commons Attribution Share-Alike 4.0 International License. Sincerely,
> ."
>
> In the Submission notes field, please also confirm that if your talk is
> accepted, you will be able to attend FOSDEM and deliver your presentation.
> We will not consider proposals from prospective speakers who are unsure
> whether they will be able to secure funds for travel and lodging to attend
> FOSDEM. (Sadly, we are not able to offer travel funding for prospective
> speakers.)
>
> Speaker Mentoring Program
>
> As a part of the rising efforts to grow our communities and encourage a
> diverse and inclusive conference ecosystem, we're happy to announce that
> we'll be offering mentoring for new speakers. Our mentors can help you with
> tasks such as reviewing your abstract, reviewing your presentation outline
> or slides, or practicing your talk with you.
>
> You may apply to the mentoring program as a newcomer speaker if you:
>
> Never presented before or
> Presented only lightning talks or
> Presented full-length talks at small meetups (<50 ppl)
>
> Submission Guidelines
>
> Mentored presentations will have 25-minute slots, where 20 minutes will
> include the presentation and 5 minutes will be reserved for questions.
>
> The number of newcomer session slots is limited, so we will probably not be
> able to accept all applicat

Re: [ovirt-users] MoM is failing!!!

2017-10-16 Thread Piotr Kliczewski
On Mon, Oct 16, 2017 at 4:51 PM, Erekle Magradze
<erekle.magra...@recogizer.de> wrote:
> That's the problem, at that time nobody has restarted the server.

Please provide engine log from this time so we could see whether it
was trigger by it.

>
> Is there any scenario when the hypervisor is restarted by engine?
>
> Cheers
>
> Erekle
>
>
>
> On 10/16/2017 04:45 PM, Piotr Kliczewski wrote:
>>
>> Erekle,
>>
>> For the time period you mentioned I do not see anything wrong on vdsm
>> side except of a restart at 2017-10-15 16:28:50,993+0200. It looks
>> like manual restart.
>> The engine log starts at 2017-10-16 03:49:04,092+02 so not able to say
>> whether there was anything else except of heartbeat issue caused by
>> the restart.
>>
>> The restart was the cause of "connection reset by peer" on mom side.
>>
>> Thanks,
>> Piotr
>>
>> On Mon, Oct 16, 2017 at 4:21 PM, Erekle Magradze
>> <erekle.magra...@recogizer.de> wrote:
>>>
>>> Hi Piotr,
>>>
>>> Several times I've restarted vdsm daemon on certain nods, that could be
>>> the
>>> reason.
>>>
>>> The failure, I've mentioned, has happened yesterday from 15:00 to 17:00
>>>
>>> Cheers
>>>
>>> Erekle
>>>
>>>
>>>
>>> On 10/16/2017 04:13 PM, Piotr Kliczewski wrote:
>>>>
>>>> Erekle,
>>>>
>>>> In the logs you provided I see:
>>>>
>>>> IOError: [Errno 5] _handleRequests._checkForMail - Could not read
>>>> mailbox:
>>>>
>>>> /rhev/data-center/6d52512e-1c02-4509-880a-bf57cbad4bdf/mastersd/dom_md/inbox
>>>>
>>>> and
>>>>
>>>> StorageDomainMasterError: Error validating master storage domain: ('MD
>>>> read error',)
>>>>
>>>> which seems to be cause for vdsm being killed by sanlock which caused
>>>> connection reset by peer.
>>>>
>>>> After vdsm restart storage looks good.
>>>>
>>>> @Nir can you take a look?
>>>>
>>>> Thanks,
>>>> Piotr
>>>>
>>>> On Mon, Oct 16, 2017 at 3:59 PM, Erekle Magradze
>>>> <erekle.magra...@recogizer.de> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> The issue is the following, after installation of ovirt 4.1 on three
>>>>> nodes
>>>>> with glusterFS as a storage, oVirt engine reported the failed events,
>>>>> with
>>>>> the following message
>>>>>
>>>>> VDSM hostname command GetStatsVDS failed: Connection reset by peer
>>>>>
>>>>> after that oVirt was trying to fence the affected host and it was
>>>>> excluded
>>>>> from production, luckily I am not running any VMs on it yet.
>>>>>
>>>>> The logs are attached, don't be surprised with the hostnames :)
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Cheers
>>>>>
>>>>> Erekle
>>>>>
>>>>>
>>>>> On 10/16/2017 03:37 PM, Dafna Ron wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Can you please tell us what is the issue that you are actually facing?
>>>>> :)
>>>>> it
>>>>> would be easier to debug an issue and not an error message that can be
>>>>> cause
>>>>> by several things.
>>>>>
>>>>> Also, can you provide the engine and the vdsm logs?
>>>>>
>>>>> thank you,
>>>>> Dafna
>>>>>
>>>>>
>>>>> On 10/16/2017 02:30 PM, Erekle Magradze wrote:
>>>>>
>>>>> It's was a typo in the failure message,
>>>>>
>>>>> that's what I was getting:
>>>>>
>>>>> VDSM hostname command GetStatsVDS failed: Connection reset by peer
>>>>>
>>>>>
>>>>> On 10/16/2017 03:21 PM, Erekle Magradze wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> It's getting clear now, indeed momd service is disabled
>>>>>
>>>>> ● momd.service - Memory Overcommitment Manager Daemon
>>>>>  Loaded: loaded (/usr/lib/systemd/system/momd.service; static;
>>>>> vendor
>>>>> preset: disabled)
>>

Re: [ovirt-users] MoM is failing!!!

2017-10-16 Thread Piotr Kliczewski
Erekle,

For the time period you mentioned I do not see anything wrong on vdsm
side except of a restart at 2017-10-15 16:28:50,993+0200. It looks
like manual restart.
The engine log starts at 2017-10-16 03:49:04,092+02 so not able to say
whether there was anything else except of heartbeat issue caused by
the restart.

The restart was the cause of "connection reset by peer" on mom side.

Thanks,
Piotr

On Mon, Oct 16, 2017 at 4:21 PM, Erekle Magradze
<erekle.magra...@recogizer.de> wrote:
> Hi Piotr,
>
> Several times I've restarted vdsm daemon on certain nods, that could be the
> reason.
>
> The failure, I've mentioned, has happened yesterday from 15:00 to 17:00
>
> Cheers
>
> Erekle
>
>
>
> On 10/16/2017 04:13 PM, Piotr Kliczewski wrote:
>>
>> Erekle,
>>
>> In the logs you provided I see:
>>
>> IOError: [Errno 5] _handleRequests._checkForMail - Could not read
>> mailbox:
>> /rhev/data-center/6d52512e-1c02-4509-880a-bf57cbad4bdf/mastersd/dom_md/inbox
>>
>> and
>>
>> StorageDomainMasterError: Error validating master storage domain: ('MD
>> read error',)
>>
>> which seems to be cause for vdsm being killed by sanlock which caused
>> connection reset by peer.
>>
>> After vdsm restart storage looks good.
>>
>> @Nir can you take a look?
>>
>> Thanks,
>> Piotr
>>
>> On Mon, Oct 16, 2017 at 3:59 PM, Erekle Magradze
>> <erekle.magra...@recogizer.de> wrote:
>>>
>>> Hi,
>>>
>>> The issue is the following, after installation of ovirt 4.1 on three
>>> nodes
>>> with glusterFS as a storage, oVirt engine reported the failed events,
>>> with
>>> the following message
>>>
>>> VDSM hostname command GetStatsVDS failed: Connection reset by peer
>>>
>>> after that oVirt was trying to fence the affected host and it was
>>> excluded
>>> from production, luckily I am not running any VMs on it yet.
>>>
>>> The logs are attached, don't be surprised with the hostnames :)
>>>
>>> Thanks in advance
>>>
>>> Cheers
>>>
>>> Erekle
>>>
>>>
>>> On 10/16/2017 03:37 PM, Dafna Ron wrote:
>>>
>>> Hi,
>>>
>>> Can you please tell us what is the issue that you are actually facing? :)
>>> it
>>> would be easier to debug an issue and not an error message that can be
>>> cause
>>> by several things.
>>>
>>> Also, can you provide the engine and the vdsm logs?
>>>
>>> thank you,
>>> Dafna
>>>
>>>
>>> On 10/16/2017 02:30 PM, Erekle Magradze wrote:
>>>
>>> It's was a typo in the failure message,
>>>
>>> that's what I was getting:
>>>
>>> VDSM hostname command GetStatsVDS failed: Connection reset by peer
>>>
>>>
>>> On 10/16/2017 03:21 PM, Erekle Magradze wrote:
>>>
>>> Hi,
>>>
>>> It's getting clear now, indeed momd service is disabled
>>>
>>> ● momd.service - Memory Overcommitment Manager Daemon
>>> Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor
>>> preset: disabled)
>>> Active: inactive (dead)
>>>
>>> mom-vdsm is enable and running.
>>>
>>> ● mom-vdsm.service - MOM instance configured for VDSM purposes
>>> Loaded: loaded (/usr/lib/systemd/system/mom-vdsm.service; enabled;
>>> vendor
>>> preset: enabled)
>>> Active: active (running) since Mon 2017-10-16 15:14:35 CEST; 1min 3s
>>> ago
>>>   Main PID: 27638 (python)
>>> CGroup: /system.slice/mom-vdsm.service
>>> └─27638 python /usr/sbin/momd -c /etc/vdsm/mom.conf
>>>
>>> The reason why I came up with digging in mom problems is the following
>>> problem
>>>
>>>
>>> VDSM hostname command GetStatsVDSThanks failed: Connection reset by peer
>>>
>>> that is causing fencing of the node where the failure is happening, what
>>> could be the reason of GetStatsVDS failure?
>>>
>>> Best Regards
>>> Erekle
>>>
>>>
>>> On 10/16/2017 03:11 PM, Martin Sivak wrote:
>>>
>>> Hi,
>>>
>>> how do you start MOM? MOM is supposed to talk to vdsm, we do not talk
>>> to libvirt directly. The line you posted comes from vdsm and vdsm is
>>> telling you it can't talk to MOM.
>>>
>>> Which MOM service is enabled? Because there are two

Re: [ovirt-users] MoM is failing!!!

2017-10-16 Thread Piotr Kliczewski
Erekle,

In the logs you provided I see:

IOError: [Errno 5] _handleRequests._checkForMail - Could not read
mailbox: 
/rhev/data-center/6d52512e-1c02-4509-880a-bf57cbad4bdf/mastersd/dom_md/inbox

and

StorageDomainMasterError: Error validating master storage domain: ('MD
read error',)

which seems to be cause for vdsm being killed by sanlock which caused
connection reset by peer.

After vdsm restart storage looks good.

@Nir can you take a look?

Thanks,
Piotr

On Mon, Oct 16, 2017 at 3:59 PM, Erekle Magradze
 wrote:
> Hi,
>
> The issue is the following, after installation of ovirt 4.1 on three nodes
> with glusterFS as a storage, oVirt engine reported the failed events, with
> the following message
>
> VDSM hostname command GetStatsVDS failed: Connection reset by peer
>
> after that oVirt was trying to fence the affected host and it was excluded
> from production, luckily I am not running any VMs on it yet.
>
> The logs are attached, don't be surprised with the hostnames :)
>
> Thanks in advance
>
> Cheers
>
> Erekle
>
>
> On 10/16/2017 03:37 PM, Dafna Ron wrote:
>
> Hi,
>
> Can you please tell us what is the issue that you are actually facing? :) it
> would be easier to debug an issue and not an error message that can be cause
> by several things.
>
> Also, can you provide the engine and the vdsm logs?
>
> thank you,
> Dafna
>
>
> On 10/16/2017 02:30 PM, Erekle Magradze wrote:
>
> It's was a typo in the failure message,
>
> that's what I was getting:
>
> VDSM hostname command GetStatsVDS failed: Connection reset by peer
>
>
> On 10/16/2017 03:21 PM, Erekle Magradze wrote:
>
> Hi,
>
> It's getting clear now, indeed momd service is disabled
>
> ● momd.service - Memory Overcommitment Manager Daemon
>Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor
> preset: disabled)
>Active: inactive (dead)
>
> mom-vdsm is enable and running.
>
> ● mom-vdsm.service - MOM instance configured for VDSM purposes
>Loaded: loaded (/usr/lib/systemd/system/mom-vdsm.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Mon 2017-10-16 15:14:35 CEST; 1min 3s ago
>  Main PID: 27638 (python)
>CGroup: /system.slice/mom-vdsm.service
>└─27638 python /usr/sbin/momd -c /etc/vdsm/mom.conf
>
> The reason why I came up with digging in mom problems is the following
> problem
>
>
> VDSM hostname command GetStatsVDSThanks failed: Connection reset by peer
>
> that is causing fencing of the node where the failure is happening, what
> could be the reason of GetStatsVDS failure?
>
> Best Regards
> Erekle
>
>
> On 10/16/2017 03:11 PM, Martin Sivak wrote:
>
> Hi,
>
> how do you start MOM? MOM is supposed to talk to vdsm, we do not talk
> to libvirt directly. The line you posted comes from vdsm and vdsm is
> telling you it can't talk to MOM.
>
> Which MOM service is enabled? Because there are two momd and mom-vdsm,
> the second one is the one that should be enabled.
>
> Best regards
>
> Martin Sivak
>
>
> On Mon, Oct 16, 2017 at 3:04 PM, Erekle Magradze
>  wrote:
>
> Hi Martin,
>
> Thanks for the answer, unfortunately this warning message persists, does it
> mean that mom cannot communicate with libvirt? how critical is it?
>
> Best
>
> Erekle
>
>
>
> On 10/16/2017 03:03 PM, Martin Sivak wrote:
>
> Hi,
>
> it is just a warning, there is nothing you have to solve unless it
> does not resolve itself within a minute or so. If it happens only once
> or twice after vdsm or mom restart then you are fine.
>
> Best regards
>
> --
> Martin Sivak
> SLA / oVirt
>
> On Mon, Oct 16, 2017 at 2:44 PM, Erekle Magradze
>  wrote:
>
> Hi,
>
> after running
>
> systemctl status vdsm I am getting that it's running and this message at
> the
> end.
>
> Oct 16 14:26:52 hostname vdsmd[2392]: vdsm throttled WARN MOM not
> available.
> Oct 16 14:26:52 hostname vdsmd[2392]: vdsm throttled WARN MOM not
> available,
> KSM stats will be missing.
> Oct 16 14:26:57 hostname vdsmd[2392]: vdsm root WARN ping was deprecated
> in
> favor of ping2 and confirmConnectivity
>
> how critical it is? and how to solve that warning?
>
> I am using libvirt
>
> Cheers
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> --
> Recogizer Group GmbH
>
> Dr.rer.nat. Erekle Magradze
> Lead Big Data Engineering & DevOps
> Rheinwerkallee 2, 53227 Bonn
> Tel: +49 228 29974555
>
> E-Mail erekle.magra...@recogizer.de
> Web: www.recogizer.com
>
> Recogizer auf LinkedIn https://www.linkedin.com/company-beta/10039182/
> Folgen Sie uns auf Twitter https://twitter.com/recogizer
>
> -
> Recogizer Group GmbH
> Geschäftsführer: Oliver Habisch, Carsten Kreutze
> 

[ovirt-users] FOSDEM18 Virt & IaaS Devroom CFP

2017-10-16 Thread Piotr Kliczewski
On behalf of oVirt and the Xen Project, we are excited to announce that the
call for proposals is now open for the Virtualization & IaaS devroom at the
upcoming FOSDEM 2018, to be hosted on February 3 and 4, 2017.

This year will mark FOSDEM’s 18th anniversary as one of the longest-running
free and open source software developer events, attracting thousands of
developers and users from all over the world. FOSDEM will be held once
again in Brussels, Belgium, on February 3 & 4, 2018.

This devroom is a collaborative effort, and is organized by dedicated folks
from projects such as OpenStack, Xen Project,, oVirt, QEMU, and
Foreman. We would like to invite all those who are involved in these fields
to submit your proposals by December 1st, 2017.

About the Devroom

The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors and virtual machine managers such as Xen Project, KVM,
bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
Apache CloudStack, OpenStack, oVirt, QEMU, OpenNebula, and Ganeti.

This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.

Presentations in this devroom will be aimed at developers working on these
platforms who are looking to collaborate and improve shared infrastructure
or solve common problems. We seek topics that encourage dialog between
projects and continued work post-FOSDEM.

Important Dates

Submission deadline: 01 December 2017
Acceptance notifications: 14 December 2017
Final schedule announcement: 21 December 2017
Devroom: 03 and 04 February 2018 (two days- different rooms)

Submit Your Proposal

All submissions must be made via the Pentabarf event planning site[1]. If
you have not used Pentabarf before, you will need to create an account. If
you submitted proposals for FOSDEM in previous years, you can use your
existing account.

After creating the account, select Create Event to start the submission
process. Make sure to select Virtualization and IaaS devroom from the Track
list. Please fill out all the required fields, and provide a meaningful
abstract and description of your proposed session.

Submission Guidelines

We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.

All presentation slots are 45 minutes, with 35 minutes planned for
presentations, and 10 minutes for Q

All presentations will be recorded and made available under Creative
Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
For example:

"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License. Sincerely,
."

In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend FOSDEM and deliver your presentation.
We will not consider proposals from prospective speakers who are unsure
whether they will be able to secure funds for travel and lodging to attend
FOSDEM. (Sadly, we are not able to offer travel funding for prospective
speakers.)

Speaker Mentoring Program

As a part of the rising efforts to grow our communities and encourage a
diverse and inclusive conference ecosystem, we're happy to announce that
we'll be offering mentoring for new speakers. Our mentors can help you with
tasks such as reviewing your abstract, reviewing your presentation outline
or slides, or practicing your talk with you.

You may apply to the mentoring program as a newcomer speaker if you:

Never presented before or
Presented only lightning talks or
Presented full-length talks at small meetups (<50 ppl)

Submission Guidelines

Mentored presentations will have 25-minute slots, where 20 minutes will
include the presentation and 5 minutes will be reserved for questions.

The number of newcomer session slots is limited, so we will probably not be
able to accept all applications.

You must submit your talk and abstract to apply for the mentoring program,
our mentors are volunteering their time and will happily provide feedback
but won't write your presentation for you!

If you are experiencing problems with Pentabarf, the proposal submission
interface, or have other questions, you can email our devroom mailing
list[2] and we will try to help you.

How to Apply

In addition to agreeing to video recording and confirming that you can
attend FOSDEM in case your session is accepted, please write "speaker
mentoring program application" in the "Submission 

Re: [ovirt-users] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-22 Thread Piotr Kliczewski
On Fri, Sep 22, 2017 at 10:35 AM, Martin Perina <mper...@redhat.com> wrote:
>
>
> On Fri, Sep 22, 2017 at 10:18 AM, Neil <nwilson...@gmail.com> wrote:
>>
>> Hi Piotr,
>>
>> Thank you for the information.
>>
>> It looks like something has expired looking in the server.log now that
>> debug is enabled.
>>
>> 2017-09-22 09:35:26,462 INFO  [stdout] (MSC service thread 1-4)   Version:
>> V3
>> 2017-09-22 09:35:26,464 INFO  [stdout] (MSC service thread 1-4)   Subject:
>> CN=engine01.mydomain.za, O=mydomain, C=US
>> 2017-09-22 09:35:26,467 INFO  [stdout] (MSC service thread 1-4)
>> Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
>> 2017-09-22 09:35:26,471 INFO  [stdout] (MSC service thread 1-4)
>> 2017-09-22 09:35:26,472 INFO  [stdout] (MSC service thread 1-4)   Key:
>> Sun RSA public key, 1024 bits
>> 2017-09-22 09:35:26,474 INFO  [stdout] (MSC service thread 1-4)   modulus:
>> 96670613185023785772001656613227416922514371649313203413281121371175732119596513752882171306045450346018887835032223373125981220753972276294203593174404470265593368091683564110524316403260121331609213962612618181708680331850541390318868926054438078223371655800890725486783860059873397983318033852172060923531
>> 2017-09-22 09:35:26,476 INFO  [stdout] (MSC service thread 1-4)   public
>> exponent: 65537
>> 2017-09-22 09:35:26,477 INFO  [stdout] (MSC service thread 1-4)
>> Validity: [From: Sun Oct 14 22:26:46 SAST 2012,
>> 2017-09-22 09:35:26,478 INFO  [stdout] (MSC service thread 1-4)
>> To: Tue Sep 19 18:26:49 SAST 2017]
>> 2017-09-22 09:35:26,479 INFO  [stdout] (MSC service thread 1-4)   Issuer:
>> CN=CA-engine01.mydomain.za.47472, O=mydomain, C=US
>>
>> Any idea how I can generate a new one and what cert it is that's expired?
>
>
> It seems that your engine certificate has expired, but AFAIK this
> certificate should be automatically renewed during engine-setup. So when did
> you execute engine-setup for last time? Any info/warning about this shown
> during invocation?

Correct, Martin was a bit faster then me :)

>
> Also looking at server.log I found JBoss 7.1.1, so you are using really
> ancient oVirt, version, right?
>
>>
>> Please see the attached log for more info.
>>
>> Thank you so much for your assistance.
>>
>> Regards.
>>
>> Neil Wilson.
>>
>>
>>
>>
>>
>>
>> On Thu, Sep 21, 2017 at 8:41 PM, Piotr Kliczewski
>> <piotr.kliczew...@gmail.com> wrote:
>>>
>>> Neil,
>>>
>>> It seems that your engine certificate(s) is/are not ok. I would
>>> suggest to enable ssl debug in the engine by:
>>> - add '-Djavax.net.debug=all' to ovirt-engine.py file here [1].
>>> - restart your engine
>>> - check your server.log and check what is the issue.
>>>
>>> Hopefully we will be able to understand what happened in your setup.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> [1]
>>> https://github.com/oVirt/ovirt-engine/blob/master/packaging/services/ovirt-engine/ovirt-engine.py#L341
>>>
>>> On Thu, Sep 21, 2017 at 4:42 PM, Neil <nwilson...@gmail.com> wrote:
>>> > Further to the logs sent, on the nodes I'm also seeing the following
>>> > error
>>> > under /var/log/messages...
>>> >
>>> > Sep 20 03:43:12 node01 vdsm root ERROR invalid client certificate with
>>> > subject "/C=US/O=UKDM/CN=engine01.mydomain.za"^C
>>> > Sep 20 03:43:12 node01 vdsm vds ERROR xml-rpc handler
>>> > exception#012Traceback
>>> > (most recent call last):#012  File "/usr/share/vdsm/BindingXMLRPC.py",
>>> > line
>>> > 80, in threaded_start#012self.server.handle_request()#012  File
>>> > "/usr/lib64/python2.6/SocketServer.py", line 278, in handle_request#012
>>> > self._handle_request_noblock()#012  File
>>> > "/usr/lib64/python2.6/SocketServer.py", line 288, in
>>> > _handle_request_noblock#012request, client_address =
>>> > self.get_request()#012  File "/usr/lib64/python2.6/SocketServer.py",
>>> > line
>>> > 456, in get_request#012return self.socket.accept()#012  File
>>> > "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line
>>> > 136,
>>> > in accept#012raise SSL.SSLError("%s, client %s" % (e,
>>> > address[0]))#012SSLError: no certificate returned, client 10.251.193.5
>>> >
>>> > Not sure i

Re: [ovirt-users] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Piotr Kliczewski
Neil,

It seems that your engine certificate(s) is/are not ok. I would
suggest to enable ssl debug in the engine by:
- add '-Djavax.net.debug=all' to ovirt-engine.py file here [1].
- restart your engine
- check your server.log and check what is the issue.

Hopefully we will be able to understand what happened in your setup.

Thanks,
Piotr

[1] 
https://github.com/oVirt/ovirt-engine/blob/master/packaging/services/ovirt-engine/ovirt-engine.py#L341

On Thu, Sep 21, 2017 at 4:42 PM, Neil <nwilson...@gmail.com> wrote:
> Further to the logs sent, on the nodes I'm also seeing the following error
> under /var/log/messages...
>
> Sep 20 03:43:12 node01 vdsm root ERROR invalid client certificate with
> subject "/C=US/O=UKDM/CN=engine01.mydomain.za"^C
> Sep 20 03:43:12 node01 vdsm vds ERROR xml-rpc handler exception#012Traceback
> (most recent call last):#012  File "/usr/share/vdsm/BindingXMLRPC.py", line
> 80, in threaded_start#012self.server.handle_request()#012  File
> "/usr/lib64/python2.6/SocketServer.py", line 278, in handle_request#012
> self._handle_request_noblock()#012  File
> "/usr/lib64/python2.6/SocketServer.py", line 288, in
> _handle_request_noblock#012request, client_address =
> self.get_request()#012  File "/usr/lib64/python2.6/SocketServer.py", line
> 456, in get_request#012return self.socket.accept()#012  File
> "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 136,
> in accept#012raise SSL.SSLError("%s, client %s" % (e,
> address[0]))#012SSLError: no certificate returned, client 10.251.193.5
>
> Not sure if this is any further help in diagnosing the issue?
>
> Thanks, any assistance is appreciated.
>
> Regards.
>
> Neil Wilson.
>
>
> On Thu, Sep 21, 2017 at 4:31 PM, Neil <nwilson...@gmail.com> wrote:
>>
>> Hi Piotr,
>>
>> Thank you for the reply. After sending the email I did go and check the
>> engine one too
>>
>> [root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/ca.pem -enddate
>> -noout
>> notAfter=Oct 13 16:26:46 2022 GMT
>>
>> I'm not sure if this one below is meant to verify or if this output is
>> expected?
>>
>> [root@engine01 /]# openssl x509 -in /etc/pki/ovirt-engine/private/ca.pem
>> -enddate -noout
>> unable to load certificate
>> 140642165552968:error:0906D06C:PEM routines:PEM_read_bio:no start
>> line:pem_lib.c:703:Expecting: TRUSTED CERTIFICATE
>>
>> My date is correct too Thu Sep 21 16:30:15 SAST 2017
>>
>> Any ideas?
>>
>> Googling surprisingly doesn't come up with much.
>>
>> Thank you.
>>
>> Regards.
>>
>> Neil Wilson.
>>
>> On Thu, Sep 21, 2017 at 4:16 PM, Piotr Kliczewski
>> <piotr.kliczew...@gmail.com> wrote:
>>>
>>> Neil,
>>>
>>> You checked both nodes what about the engine? Can you check engine certs?
>>> You can find more info where they are located here [1].
>>>
>>> Thanks,
>>> Piotr
>>>
>>> [1]
>>> https://www.ovirt.org/develop/release-management/features/infra/pki/#ovirt-engine
>>>
>>> On Thu, Sep 21, 2017 at 3:26 PM, Neil <nwilson...@gmail.com> wrote:
>>> > Hi guys,
>>> >
>>> > Please could someone assist, my cluster is down and I can't access my
>>> > vm's
>>> > to switch some of them back on.
>>> >
>>> > I'm seeing the following error in the engine.log however I've checked
>>> > my
>>> > certs on my hosts (as some of the goolge results said to check), but
>>> > the
>>> > certs haven't expired...
>>> >
>>> >
>>> > 2017-09-21 15:09:45,077 ERROR
>>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>>> > (DefaultQuartzScheduler_Worker-4) Command
>>> > GetCapabilitiesVDSCommand(HostName
>>> > = node02.mydomain.za, HostId = d2debdfe-76e7-40cf-a7fd-78a0f50f14d4,
>>> > vds=Host[node02.mydomain.za]) execution failed. Exception:
>>> > VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received
>>> > fatal
>>> > alert: certificate_expired
>>> > 2017-09-21 15:09:45,086 ERROR
>>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>>> > (DefaultQuartzScheduler_Worker-10) Command
>>> > GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
>>> > b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
>>> > execution failed. Exception: VDSNetworkE

Re: [ovirt-users] SSLHandshakeException: Received fatal alert: certificate_expired

2017-09-21 Thread Piotr Kliczewski
Neil,

You checked both nodes what about the engine? Can you check engine certs?
You can find more info where they are located here [1].

Thanks,
Piotr

[1] 
https://www.ovirt.org/develop/release-management/features/infra/pki/#ovirt-engine

On Thu, Sep 21, 2017 at 3:26 PM, Neil  wrote:
> Hi guys,
>
> Please could someone assist, my cluster is down and I can't access my vm's
> to switch some of them back on.
>
> I'm seeing the following error in the engine.log however I've checked my
> certs on my hosts (as some of the goolge results said to check), but the
> certs haven't expired...
>
>
> 2017-09-21 15:09:45,077 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-4) Command GetCapabilitiesVDSCommand(HostName
> = node02.mydomain.za, HostId = d2debdfe-76e7-40cf-a7fd-78a0f50f14d4,
> vds=Host[node02.mydomain.za]) execution failed. Exception:
> VDSNetworkException: javax.net.ssl.SSLHandshakeException: Received fatal
> alert: certificate_expired
> 2017-09-21 15:09:45,086 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-10) Command
> GetCapabilitiesVDSCommand(HostName = node01.mydomain.za, HostId =
> b108549c-1700-11e2-b936-9f5243b8ce13, vds=Host[node01.mydomain.za])
> execution failed. Exception: VDSNetworkException:
> javax.net.ssl.SSLHandshakeException: Received fatal alert:
> certificate_expired
> 2017-09-21 15:09:48,173 ERROR
>
> My engine and host info is below...
>
> [root@engine01 ovirt-engine]# rpm -qa | grep -i ovirt
> ovirt-engine-lib-3.4.0-1.el6.noarch
> ovirt-engine-restapi-3.4.0-1.el6.noarch
> ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
> ovirt-engine-3.4.0-1.el6.noarch
> ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
> ovirt-host-deploy-java-1.2.0-1.el6.noarch
> ovirt-engine-setup-3.4.0-1.el6.noarch
> ovirt-host-deploy-1.2.0-1.el6.noarch
> ovirt-engine-backend-3.4.0-1.el6.noarch
> ovirt-image-uploader-3.4.0-1.el6.noarch
> ovirt-engine-tools-3.4.0-1.el6.noarch
> ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch
> ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch
> ovirt-engine-cli-3.4.0.5-1.el6.noarch
> ovirt-engine-setup-base-3.4.0-1.el6.noarch
> ovirt-iso-uploader-3.4.0-1.el6.noarch
> ovirt-engine-userportal-3.4.0-1.el6.noarch
> ovirt-log-collector-3.4.1-1.el6.noarch
> ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch
> ovirt-engine-dbscripts-3.4.0-1.el6.noarch
> [root@engine01 ovirt-engine]# cat /etc/redhat-release
> CentOS release 6.5 (Final)
>
>
> [root@node02 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -enddate
> -noout ; date
> notAfter=May 27 08:36:17 2019 GMT
> Thu Sep 21 15:18:22 SAST 2017
> CentOS release 6.5 (Final)
> [root@node02 ~]# rpm -qa | grep vdsm
> vdsm-4.14.6-0.el6.x86_64
> vdsm-python-4.14.6-0.el6.x86_64
> vdsm-cli-4.14.6-0.el6.noarch
> vdsm-xmlrpc-4.14.6-0.el6.noarch
> vdsm-python-zombiereaper-4.14.6-0.el6.noarch
>
>
> [root@node01 ~]# openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -enddate
> -noout ; date
> notAfter=Jun 13 16:09:41 2018 GMT
> Thu Sep 21 15:18:52 SAST 2017
> CentOS release 6.5 (Final)
> [root@node01 ~]# rpm -qa | grep -i vdsm
> vdsm-4.14.6-0.el6.x86_64
> vdsm-xmlrpc-4.14.6-0.el6.noarch
> vdsm-cli-4.14.6-0.el6.noarch
> vdsm-python-zombiereaper-4.14.6-0.el6.noarch
> vdsm-python-4.14.6-0.el6.x86_64
>
> Please could I have some assistance, I'm rater desperate.
>
> Thank you.
>
> Regards.
>
> Neil Wilson
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Server Not Responding

2017-09-19 Thread Piotr Kliczewski
)

On Mon, Sep 18, 2017 at 6:43 PM, Bryan Sockel <bryan.soc...@altn.com> wrote:
> Here are the logs as requested.
>
>
> Bryan Sockel
> Systems Administrator
> Alt-N Technologies | Grapevine, TX
> Office 817.601.3222 x233
>
> Sent using Alt-N's own MDaemon Messaging Server
> Get to know the Alt-N family by liking us on Facebook!
>
>
>
> -Original Message-----
> From: "piotr.kliczew...@gmail.com -- Piotr Kliczewski"
> <piotr.kliczew...@gmail.com>
> To: Bryan Sockel <bryan.soc...@altn.com>
> Cc: "users@ovirt.org" <users@ovirt.org>
> Date: Thu, 14 Sep 2017 21:30:19 +0200
> Subject: Re: [ovirt-users] Server Not Responding
>
> Bryan,
>
> In your engine logs I see :
>
> 2017-09-13 04:07:07,599-05 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler3) [] Command 'GetAllVmStatsVDSCommand(HostName
> = vm-host-colo-1, VdsIdVDSCommandParametersBase:{runAsync='true',
> hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66'})' execution failed:
> VDSGenericzException: VDSNetworkException: Heartbeat exceeded
>
> It would br great to understand what happened on vdsm side because the
> engine was still trying to connect at: 2017-09-13 09:30:46,275-05
>
> In vdsm logs you provided I see that they start at 2017-09-13
> 09:01:08,895-0500 and end at 2017-09-13 09:53:24,760-0500.
>
> Please provide vdsm logs from the time the issue occurred.
>
> Thanks,
> Piotr
>
> On Wed, Sep 13, 2017 at 5:09 PM, Bryan Sockel <bryan.soc...@altn.com> wrote:
>>
>> Hi
>>
>> Having an issue where i frequently have a server that is set to not
>> responsive.  VM's are set to unknown status, but still continue to run.
>> This issue is isolated to just a single host.  My Setup is currently a 2
>> Data Center Configuration with 2 servers in each data center.  Issue is
>> occurring at my remote site.
>>
>> The primary storage volumes are setup on dedicated hardware, with the
>> arbiter running on the server that is having issues.  There is also
>> another
>> gluster replica volume hosted on this box, the replica is the other
>> dedicated server.
>>
>> The logs are showing:
>>
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>> (DefaultQuartzScheduler8) [] Command 'GetCapabilitiesVDSCommand(HostName =
>> vm-host-colo-1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66',
>> vds='Host[vm-host-colo-1,e75d4446-9bfc-47cb-8bf8-a2e681720b66]'})'
>> execution
>> failed: java.rmi.ConnectException: Connection timeout
>>
>> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
>> (DefaultQuartzScheduler8) [] Failure to refresh host 'vm-host-colo-1'
>> runtime info: java.rmi.ConnectException: Connection timeout.
>>
>>
>> I have attached the vdsm.log from the server with issues and the
>> engine.log.
>>
>> Thanks
>>
>> Bryan Sockel
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Ovirt overview presentation

2017-09-18 Thread Piotr Kliczewski
All,

I am going to give a presentation about ovirt [1]. It will be an
introductory (entry level) presentation and looking for some
information. Has anyone some slides or info that I could/should
present?
So far I got a presentation from Yaniv B. [2]

Thanks in advance,
Piotr

[1] https://jesien.org/2017/en/agenda/
[2] https://www.slideshare.net/bronhaim/fossasia-16-ovirt-overview
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Server Not Responding

2017-09-14 Thread Piotr Kliczewski
Bryan,

In your engine logs I see :

2017-09-13 04:07:07,599-05 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(DefaultQuartzScheduler3) [] Command 'GetAllVmStatsVDSCommand(HostName
= vm-host-colo-1, VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66'})' execution failed:
VDSGenericzException: VDSNetworkException: Heartbeat exceeded

It would br great to understand what happened on vdsm side because the
engine was still trying to connect at: 2017-09-13 09:30:46,275-05

In vdsm logs you provided I see that they start at 2017-09-13
09:01:08,895-0500 and end at 2017-09-13 09:53:24,760-0500.

Please provide vdsm logs from the time the issue occurred.

Thanks,
Piotr

On Wed, Sep 13, 2017 at 5:09 PM, Bryan Sockel  wrote:
>
> Hi
>
> Having an issue where i frequently have a server that is set to not
> responsive.  VM's are set to unknown status, but still continue to run.
> This issue is isolated to just a single host.  My Setup is currently a 2
> Data Center Configuration with 2 servers in each data center.  Issue is
> occurring at my remote site.
>
> The primary storage volumes are setup on dedicated hardware, with the
> arbiter running on the server that is having issues.  There is also another
> gluster replica volume hosted on this box, the replica is the other
> dedicated server.
>
> The logs are showing:
>
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler8) [] Command 'GetCapabilitiesVDSCommand(HostName =
> vm-host-colo-1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66',
> vds='Host[vm-host-colo-1,e75d4446-9bfc-47cb-8bf8-a2e681720b66]'})' execution
> failed: java.rmi.ConnectException: Connection timeout
>
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (DefaultQuartzScheduler8) [] Failure to refresh host 'vm-host-colo-1'
> runtime info: java.rmi.ConnectException: Connection timeout.
>
>
> I have attached the vdsm.log from the server with issues and the engine.log.
>
> Thanks
>
> Bryan Sockel
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages General SSLEngine problem

2017-09-03 Thread Piotr Kliczewski
Gary,

Looking at your engine log I see this: Unable to process messages
General SSLEngine problem.
It means that you have an issue with establishing secure connection.
In order to understand more details about your failure please set log
level to debug by doing [1].
Once you enable it please provide more information why engine fails to
talk to vdsm.

Thanks,
Piotr

[1] 
http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/#enable-debug-log---restart-required

On Fri, Sep 1, 2017 at 10:40 PM, Gary Balliet  wrote:
> Good day all.
>
> Just playing with ovirt. New to it but seems quite good.
>
> Single instance/nfs share/centos7/ovirt 4.1
>
>
>
> Had a power outage and this error message is in my logs whilst trying to
> activate a downed host.  The snippet below is from engine.log.
>
> 2017-09-01 13:32:03,092-07 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.1.147
> 2017-09-01 13:32:03,097-07 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
> 2017-09-01 13:32:04,547-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler5) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'GetAllVmStatsVDSCommand(HostName = DellServer,
> VdsIdVDSCommandParametersBase:{runAsync='true',
> hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd'})' execution failed:
> VDSGenericException: VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:04,547-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
> (DefaultQuartzScheduler5) [77a871f9-4947-46c9-977f-db5f76cac358] Failed to
> fetch vms info for host 'DellServer' - skipping VMs monitoring.
> 2017-09-01 13:32:19,548-07 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.1.147
> 2017-09-01 13:32:19,552-07 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
> 2017-09-01 13:32:23,115-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), Correlation ID: null, Call Stack: null,
> Custom Event ID: -1, Message: VDSM DellServer command GetCapabilitiesVDS
> failed: General SSLEngine problem
> 2017-09-01 13:32:23,115-07 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand' return
> value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@65b16430'
> 2017-09-01 13:32:23,115-07 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] HostName =
> DellServer
> 2017-09-01 13:32:23,116-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'GetCapabilitiesVDSCommand(HostName = DellServer,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd',
> vds='Host[DellServer,b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd]'})' execution
> failed: VDSGenericException: VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:23,116-07 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Failure to
> refresh host 'DellServer' runtime info: VDSGenericException:
> VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:26,118-07 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.1.147
> 2017-09-01 13:32:26,122-07 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
> 2017-09-01 13:32:39,550-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler1) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'GetAllVmStatsVDSCommand(HostName = DellServer,
> VdsIdVDSCommandParametersBase:{runAsync='true',
> hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd'})' execution failed:
> VDSGenericException: VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:39,551-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
> (DefaultQuartzScheduler1) [77a871f9-4947-46c9-977f-db5f76cac358] Failed to
> fetch vms info for host 'DellServer' - skipping VMs monitoring.
> 2017-09-01 13:32:46,125-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler7) [77a871f9-4947-46c9-977f-db5f76cac358] EVENT_ID:
> 

Re: [ovirt-users] Communication Problems between Engine and Hosts

2017-08-16 Thread Piotr Kliczewski
Fernando,

Do you know how log it took when you had connection issues between
data centers? Please collect the logs when it will happen again.

Thanks,
Piotr

On Wed, Aug 16, 2017 at 3:20 PM, FERNANDO FREDIANI
<fernando.fredi...@upx.com> wrote:
> Hello Piotr. Thanks for your reply
>
> I was running version 4.1.1, but since that day I have upgraded to 4.1.5
> (the Engine because the hosts remain on 4.1.1). I am not sure the logs still
> exists (how long they are kept normally).
>
> Just to clarify the hosts didn't become unresponsive, but the communication
> between the Engine and the Hosts in question (each in a different Datacenter
> was interrupted - but locally the hosts were fine and accessible). What was
> strange was that since the Hosts could not talk to the Engine they seem to
> have got 'confused' and started several VM live migrations which was not
> expected. As a note I don't have any Fencing policy enabled.
>
> Regards
> Fernando
>
>
>
> On 16/08/2017 07:00, Piotr Kliczewski wrote:
>>
>> Fernando,
>>
>> Which ovirt version are you running? Please share the logs so I could
>> check what caused the hosts to become unresponsive.
>>
>> Thanks,
>> Piotr
>>
>> On Wed, Aug 2, 2017 at 5:11 PM, FERNANDO FREDIANI
>> <fernando.fredi...@upx.com> wrote:
>>>
>>> Hello.
>>>
>>> Yesterday I had a pretty strange problem in one of our architectures. My
>>> oVirt which runs in one Datacenter and controls Nodes locally and also
>>> remotelly lost communication with the remote Nodes in another Datacenter.
>>> To this point nothing wrong as the Nodes can continue working as expected
>>> and running their Virtual Machines each without dependency of the oVirt
>>> Engine.
>>>
>>> What happened at some point is that when the communication between Engine
>>> and Hosts came back Hosts got confused and initiated a Live Migration of
>>> ALL
>>> VMs from one of the other. I had also to restart vdsmd agent on all Hosts
>>> in
>>> order to get sanity my environment.
>>> What adds up even more strangeness to this scenario is that one of the
>>> Hosts
>>> affected doesn't belong to the same Cluster as the others and had to have
>>> the vdsmd restarted.
>>>
>>> I understand the Hosts can survive without the Engine online with reduced
>>> possibilities but can communicated between them, but without affecting
>>> the
>>> VMs or even needing to do what happened in this scenario.
>>>
>>> Am I wrong on any of the assumptions ?
>>>
>>> Fernando
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Communication Problems between Engine and Hosts

2017-08-16 Thread Piotr Kliczewski
Fernando,

Which ovirt version are you running? Please share the logs so I could
check what caused the hosts to become unresponsive.

Thanks,
Piotr

On Wed, Aug 2, 2017 at 5:11 PM, FERNANDO FREDIANI
 wrote:
> Hello.
>
> Yesterday I had a pretty strange problem in one of our architectures. My
> oVirt which runs in one Datacenter and controls Nodes locally and also
> remotelly lost communication with the remote Nodes in another Datacenter.
> To this point nothing wrong as the Nodes can continue working as expected
> and running their Virtual Machines each without dependency of the oVirt
> Engine.
>
> What happened at some point is that when the communication between Engine
> and Hosts came back Hosts got confused and initiated a Live Migration of ALL
> VMs from one of the other. I had also to restart vdsmd agent on all Hosts in
> order to get sanity my environment.
> What adds up even more strangeness to this scenario is that one of the Hosts
> affected doesn't belong to the same Cluster as the others and had to have
> the vdsmd restarted.
>
> I understand the Hosts can survive without the Engine online with reduced
> possibilities but can communicated between them, but without affecting the
> VMs or even needing to do what happened in this scenario.
>
> Am I wrong on any of the assumptions ?
>
> Fernando
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Timeout for Hosts

2017-05-29 Thread Piotr Kliczewski
Sven,

This config value is hidden. You can update it by running:

su - postgres -c "psql engine -c "UPDATE vdc_options set option_value
= '' where option_name =
'vdsHeartbeatInSeconds'""

Please note that the default value is 30 seconds.

and next you need to restart your engine.

Thanks,
Piotr

On Mon, May 29, 2017 at 10:30 AM, Sven Achtelik <sven.achte...@eps.aero> wrote:
> oVirt Engine Version: 4.1.2.2-1.el7.centos
>
>
> -----Ursprüngliche Nachricht-
> Von: Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
> Gesendet: Montag, 29. Mai 2017 10:30
> An: Sven Achtelik <sven.achte...@eps.aero>
> Cc: Oved Ourfali <oourf...@redhat.com>; users@ovirt.org
> Betreff: Re: [ovirt-users] Timeout for Hosts
>
> Sven,
>
> Which version of ovirt-engine do you use?
>
> Thanks,
> Piotr
>
> On Mon, May 29, 2017 at 10:26 AM, Sven Achtelik <sven.achte...@eps.aero> 
> wrote:
>> Hi Piotr,
>>
>> I can't find that in the list of variables to set if I do an "engine-config 
>> -a" Is this something I have to setup first ?
>>
>> Thank you,
>> Sven
>>
>> -Ursprüngliche Nachricht-
>> Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im
>> Auftrag von Sven Achtelik
>> Gesendet: Donnerstag, 27. April 2017 10:04
>> An: Piotr Kliczewski <piotr.kliczew...@gmail.com>; Oved Ourfali
>> <oourf...@redhat.com>
>> Cc: users@ovirt.org
>> Betreff: Re: [ovirt-users] Timeout for Hosts
>>
>> Ok, I'll try that one.
>>
>> Thank you
>>
>> -Ursprüngliche Nachricht-
>> Von: Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
>> Gesendet: Donnerstag, 27. April 2017 09:59
>> An: Oved Ourfali <oourf...@redhat.com>
>> Cc: Sven Achtelik <sven.achte...@eps.aero>; users@ovirt.org
>> Betreff: Re: [ovirt-users] Timeout for Hosts
>>
>> I think that you are looking for vdsHeartbeatInSeconds which specifies 
>> acceptable time of no activity.
>> You can increase it which would make it more resilient to network 
>> fluctuations.
>>
>> Please note that it is part of the host life cycle and too big value would 
>> limit our ability to detect real network issues.
>>
>> Thanks,
>> Piotr
>>
>> On Thu, Apr 27, 2017 at 8:36 AM, Oved Ourfali <oourf...@redhat.com> wrote:
>>> Hi Sven,
>>>
>>> Relevant configuration items are:
>>> vdsTimeout (which is set by default to 180 seconds, so you should be
>>> good) vdsHeartbeatInSeconds (this one should be increased)
>>>
>>> iirc no other changes are needed, but CC-ing Martin just in case i'm wrong.
>>>
>>> Best regards,
>>> Oved
>>>
>>> On Thu, Apr 27, 2017 at 9:30 AM, Sven Achtelik
>>> <sven.achte...@eps.aero>
>>> wrote:
>>>>
>>>> Hi All,
>>>>
>>>>
>>>>
>>>> I have 2 hosts which are at remote locations where the ISP is
>>>> forcing a connection reset after some days. During that reset the
>>>> connection will be down for at most 2 minutes and the engine starts
>>>> to complain about the hosts not being reachable. What is the right value 
>>>> to tweak to compensate this ?
>>>>
>>>> Is it on of these: TimeoutToResetVdsInSeconds, VdsRefreshRate,
>>>> vdsTimeout ? And is it possible to only apply this for a certain
>>>> cluster or DC or is it global ?
>>>>
>>>>
>>>>
>>>> Thank you,
>>>>
>>>>
>>>>
>>>> Sven
>>>>
>>>>
>>>> ___
>>>> Users mailing list
>>>> Users@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Timeout for Hosts

2017-05-29 Thread Piotr Kliczewski
Sven,

Which version of ovirt-engine do you use?

Thanks,
Piotr

On Mon, May 29, 2017 at 10:26 AM, Sven Achtelik <sven.achte...@eps.aero> wrote:
> Hi Piotr,
>
> I can't find that in the list of variables to set if I do an "engine-config 
> -a" Is this something I have to setup first ?
>
> Thank you,
> Sven
>
> -Ursprüngliche Nachricht-
> Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
> Sven Achtelik
> Gesendet: Donnerstag, 27. April 2017 10:04
> An: Piotr Kliczewski <piotr.kliczew...@gmail.com>; Oved Ourfali 
> <oourf...@redhat.com>
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Timeout for Hosts
>
> Ok, I'll try that one.
>
> Thank you
>
> -Ursprüngliche Nachricht-
> Von: Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
> Gesendet: Donnerstag, 27. April 2017 09:59
> An: Oved Ourfali <oourf...@redhat.com>
> Cc: Sven Achtelik <sven.achte...@eps.aero>; users@ovirt.org
> Betreff: Re: [ovirt-users] Timeout for Hosts
>
> I think that you are looking for vdsHeartbeatInSeconds which specifies 
> acceptable time of no activity.
> You can increase it which would make it more resilient to network 
> fluctuations.
>
> Please note that it is part of the host life cycle and too big value would 
> limit our ability to detect real network issues.
>
> Thanks,
> Piotr
>
> On Thu, Apr 27, 2017 at 8:36 AM, Oved Ourfali <oourf...@redhat.com> wrote:
>> Hi Sven,
>>
>> Relevant configuration items are:
>> vdsTimeout (which is set by default to 180 seconds, so you should be
>> good) vdsHeartbeatInSeconds (this one should be increased)
>>
>> iirc no other changes are needed, but CC-ing Martin just in case i'm wrong.
>>
>> Best regards,
>> Oved
>>
>> On Thu, Apr 27, 2017 at 9:30 AM, Sven Achtelik
>> <sven.achte...@eps.aero>
>> wrote:
>>>
>>> Hi All,
>>>
>>>
>>>
>>> I have 2 hosts which are at remote locations where the ISP is forcing
>>> a connection reset after some days. During that reset the connection
>>> will be down for at most 2 minutes and the engine starts to complain
>>> about the hosts not being reachable. What is the right value to tweak to 
>>> compensate this ?
>>>
>>> Is it on of these: TimeoutToResetVdsInSeconds, VdsRefreshRate,
>>> vdsTimeout ? And is it possible to only apply this for a certain
>>> cluster or DC or is it global ?
>>>
>>>
>>>
>>> Thank you,
>>>
>>>
>>>
>>> Sven
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Info on host not responding event and related actions

2017-05-23 Thread Piotr Kliczewski
+Marin to answer fencing configuration settings

On Tue, May 23, 2017 at 3:03 PM, Gianluca Cecchi
 wrote:
> Hello,
> I have an oVirt 4.1.1 environment with:
>
> - engine is a vSphere CentOS 7.3 VM with its nic on say vlan1
> - 2 x hosts (CentOS 7.3) with their ovirtmgmt lan on a bonding
> (active-backup) on say vlan2
>
> network architecture layout is to put hypervisors and mgmt servers in
> different vlans
>
> Today we had these 4 events below shown in our engine, with root cause
> apparently a maintenance network routing activity (it should have been
> transparent, network guys told..., but this is another story ;-)
> No alert message inside VMs
>
> 4) May 23, 2017 1:43:58 PM Host ov300 power management was verified
> successfully.
> 3) May 23, 2017 1:43:58 PM Status of host ov300 was set to Up.
> 2) May 23, 2017 1:43:55 PM Executing power management status on Host ov300
> using Proxy Host ov301 and Fence Agent ipmilan:10.10.193.103.
> 1) May 23, 2017 1:43:37 PM Host ov300 is not responding. It will stay in
> Connecting state for a grace period of 61 seconds and after that an attempt
> to fence the host will be issued.

Can you check in the logs what caused the host to become not responding?

>
> Can anyone tell exactly the meaning of the different lines?
> Is the 1) detected because the engine, from only a network point of view,
> was not able to ping/reach the hostname of the host ov300, or the "not
> responding" is any particular specific check?
> Is the "61 seconds" delay tunable?
> Is 2) an additional check to verify status of ov300?
> In case of failure of test in 2) would the fencing have been immediate or
> the delay described in 1) would have taken place?
> Are 3) and 4) messages independent from the engine being able to reach ov300
> or the 61 seconds delay would have been true anyway?
>
> Hope I have explained my doubts related to events that could determine a
> potential fencing of an active node with its running VMs... with the "only"
> temporary problem of connectivity between the engine and one of the nodes...
>
> Thanks in advance,
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 4.0 : hosts connecting/non responsive and data domains inactive

2017-05-11 Thread Piotr Kliczewski
>From provided log snippets I see that engine was unable to connect to both
of your hosts. Is the network OK?

In vdsm log it seems that there is an issue with you storage domain.

I am not able to say anything about the issue you are facing without having
more complete logs.

On Thu, May 11, 2017 at 6:28 PM, Oved Ourfali  wrote:

> What 4.0 version do you use?
> Can you attach complete engine and vdsm logs?
> CC-ing Piotr as well.
>
>
> On May 11, 2017 6:44 PM, "Alexis HAUSER" 
> wrote:
>
>> After rebooting the manager VM,  hosts are connecting/non responsive and
>> data domains inactive. Here are the engine and vdsmd logs. Any ideas ?
>>
>>
>>
>>
>> Engine logs :
>>
>>
>>
>> 2017-05-11 17:28:09,302 WARN  [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler5)
>> [55f1aab5] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
>> Message: Failed to verify Power Management configuration for Host
>> rhvserv-05.
>> 2017-05-11 17:28:09,346 INFO  
>> [org.ovirt.engine.core.bll.HandleVdsVersionCommand]
>> (DefaultQuartzScheduler5) [48bc69cd] Running command:
>> HandleVdsVersionCommand internal: true. Entities affected :  ID:
>> 04565f10-9abf-4709-9445-9dc6ed97e136 Type: VDS
>> 2017-05-11 17:28:09,349 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager]
>> (org.ovirt.thread.pool-6-thread-27) [639977e4] Host 'rhvserv-05' is not
>> responding.
>> 2017-05-11 17:28:09,364 WARN  [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-27)
>> [639977e4] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
>> Message: Host rhvserv-05 is not responding. Host cannot be fenced
>> automatically because power management for the host is disabled.
>> 2017-05-11 17:28:11,299 ERROR [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler3)
>> [c0e6a2e] Command 'GetCapabilitiesVDSCommand(HostName = rhvserv-03,
>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='4036f027-8e90-49c0-8ca5-3ddb8d586916',
>> vds='Host[rhvserv-03,4036f027-8e90-49c0-8ca5-3ddb8d586916]'})' execution
>> failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
>> Connection failed
>> 2017-05-11 17:28:11,299 ERROR 
>> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
>> (DefaultQuartzScheduler3) [c0e6a2e] Failure to refresh host 'rhvserv-03'
>> runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
>> Connection failed
>> 2017-05-11 17:28:11,327 INFO  
>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
>> (SSL Stomp Reactor) [] Connecting to rhvserv-04.mydomain.com/192.16
>> 8.93.214
>> 2017-05-11 17:28:12,484 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler3)
>> [c0e6a2e] START, GetHardwareInfoVDSCommand(HostName = rhvserv-05,
>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='04565f10-9abf-4709-9445-9dc6ed97e136',
>> vds='Host[rhvserv-05,04565f10-9abf-4709-9445-9dc6ed97e136]'}), log id:
>> f807ece
>> 2017-05-11 17:28:12,487 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler3)
>> [c0e6a2e] FINISH, GetHardwareInfoVDSCommand, log id: f807ece
>> 2017-05-11 17:28:12,532 INFO  [org.ovirt.engine.core.bll.Han
>> dleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler3)
>> [4e882ea0] Running command: HandleVdsCpuFlagsOrClusterChangedCommand
>> internal: true. Entities affected :  ID: 04565f10-9abf-4709-9445-9dc6ed97e136
>> Type: VDS
>> 2017-05-11 17:28:12,539 INFO  [org.ovirt.engine.core.bll.InitVdsOnUpCommand]
>> (DefaultQuartzScheduler3) [75f25b35] Running command: InitVdsOnUpCommand
>> internal: true. Entities affected :  ID: 58f8df36-019f-02bc-00e7-0023
>> Type: StoragePool
>> 2017-05-11 17:28:12,545 INFO  [org.ovirt.engine.core.bll.sto
>> rage.pool.ConnectHostToStoragePoolServersCommand]
>> (DefaultQuartzScheduler3) [46cc3f58] Running command:
>> ConnectHostToStoragePoolServersCommand internal: true. Entities affected
>> :  ID: 58f8df36-019f-02bc-00e7-0023 Type: StoragePool
>> 2017-05-11 17:28:12,556 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.ConnectStorageServerVDSCommand] (DefaultQuartzScheduler3)
>> [46cc3f58] START, ConnectStorageServerVDSCommand(HostName = rhvserv-05,
>> StorageServerConnectionManagementVDSParameters:{runAsync='true',
>> hostId='04565f10-9abf-4709-9445-9dc6ed97e136',
>> storagePoolId='58f8df36-019f-02bc-00e7-0023',
>> storageType='ISCSI', connectionList='[StorageServer
>> Connections:{id='10c0528b-f08d-4d1d-8c63-8a05fd9d58b9',
>> connection='10.35.21.1', iqn='iqn.1984-05.com.dell:powe
>> rvault.md3200i.6782bcb00073e3324edde164', vfsType='null',
>> mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
>> iface='null', netIfaceName='null'}]'}), log id: 1beb27b6
>> 2017-05-11 17:28:13,031 

Re: [ovirt-users] Timeout for Hosts

2017-04-27 Thread Piotr Kliczewski
I think that you are looking for vdsHeartbeatInSeconds which specifies
acceptable time of no activity.
You can increase it which would make it more resilient to network fluctuations.

Please note that it is part of the host life cycle and too big value
would limit our ability to detect real network issues.

Thanks,
Piotr

On Thu, Apr 27, 2017 at 8:36 AM, Oved Ourfali  wrote:
> Hi Sven,
>
> Relevant configuration items are:
> vdsTimeout (which is set by default to 180 seconds, so you should be good)
> vdsHeartbeatInSeconds (this one should be increased)
>
> iirc no other changes are needed, but CC-ing Martin just in case i'm wrong.
>
> Best regards,
> Oved
>
> On Thu, Apr 27, 2017 at 9:30 AM, Sven Achtelik 
> wrote:
>>
>> Hi All,
>>
>>
>>
>> I have 2 hosts which are at remote locations where the ISP is forcing a
>> connection reset after some days. During that reset the connection will be
>> down for at most 2 minutes and the engine starts to complain about the hosts
>> not being reachable. What is the right value to tweak to compensate this ?
>>
>> Is it on of these: TimeoutToResetVdsInSeconds, VdsRefreshRate, vdsTimeout
>> ? And is it possible to only apply this for a certain cluster or DC or is it
>> global ?
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Sven
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Latency threshold between Hosted Engine and Hosts

2017-04-18 Thread Piotr Kliczewski
Fernando,

We use heartbeats to understand health of the connection. Potentially
you may see heartbeat exceeded exceptions
so you may want to increase vdsHeartbeatInSeconds. I would not change
it in advance but as you see the issue
and slowly increase the value.

Thanks,
Piotr

On Tue, Apr 18, 2017 at 10:20 AM, Edward Haas  wrote:
> Hello Fernando,
>
> There is no known problem with such delay figures.
> The heartbeat to the hosts is of several seconds.
>
> Thanks,
> Edy.
>
> On Mon, Apr 17, 2017 at 5:11 PM, FERNANDO FREDIANI
>  wrote:
>>
>> Hello.
>>
>> I have a Engine which is hosted in a optimal location for the people who
>> access it and this Engine manage multiple Datacenters, some close by and
>> some far away in terms of latency.
>>
>> What is the maximum latency advised between the Engine and the hosts for a
>> healthy operation or that doesn't matter much as long the Engine can always
>> reach the hosts ?
>>
>> Currently the maximum latency I have between Engine and Hosts is 110ms and
>> sometimes when there is a non-optimal route latency goes up to 170ms. Should
>> I be concerned about this ?
>>
>> Thanks
>> Fernando
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm issues between engine and host

2017-02-21 Thread Piotr Kliczewski
On Mon, Feb 20, 2017 at 9:47 PM, cmc  wrote:
> Hi,
>
> Due to networking and DNS issues. our engine was offlined (it is
> physical machine currently, will be converting it to a VM in the
> future when time allows). When service was restored, I noticed that
> all the VMs were listed as being in an unknown state on one host. The
> VMs were fine, but the engine could not ascertain their status as the
> host itself was in an unknown state. vdsm was reporting errors and was
> not running on the engine (or at least was in status 'failed' in
> systemd). I tried starting vdsmd on the engine but it would not start.
> I decided to try to restart vdsmd on the host and that did allow the
> state of the VMs to be discovered, and the engine listed the host as
> up again. However, there are still errors with vdsmd on both the host
> and the engine, and the engine cannot start vdsmd. I guess it is able
> to monitor the hosts in a limited way as it says they are both up.
> There are communication errors between one of the hosts and the
> engine: the host is refusing connections by the look of it
>
> from the engine log:
>
> 2017-02-20 18:41:51,226Z ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler2) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
> Command 'GetCapabilitiesVDSCommand(HostName = k
> vm-ldn-01, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='e050c27f-8709-404c-b03e-59c0167a824b',
> vds='Host[kvm-ldn-01,e050c27f-8709-404c-b03e-59c0167a824b]'})'
> execution failed: java.net.ConnectExce
> ption: Connection refused
> 2017-02-20 18:41:51,226Z ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (DefaultQuartzScheduler2) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
> Failure to refresh host 'kvm-ldn-01' runtime info: java.n
> et.ConnectException: Connection refused
> 2017-02-20 18:41:52,772Z ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler6) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
> Command 'GetAllVmStatsVDSCommand(HostName = kvm-ldn-01,
> VdsIdVDSCommandParametersBase:{runAsync='true',
> hostId='e050c27f-8709-404c-b03e-59c0167a824b'})' execution failed:
> VDSGenericException: VDSNetworkException: Connection reset by peer
> 2017-02-20 18:41:54,256Z ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler7) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
> Command 'GetCapabilitiesVDSCommand(HostName = kvm-ldn-01,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='e050c27f-8709-404c-b03e-59c0167a824b',
> vds='Host[kvm-ldn-01,e050c27f-8709-404c-b03e-59c0167a824b]'})'
> execution failed: java.net.ConnectException: Connection refused
>

I checked your engine logs and I saw dns issues much later then the error above:

2017-02-20 19:47:56,516Z ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(DefaultQuartzScheduler6) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
Failure to refresh host 'kvm-ldn-01' runtime info:
java.net.UnknownHostException: kvm-ldn-01

> from the vdsm.log on the host:
>
>
> Feb 20 18:44:20 kvm-ldn-01 vdsm[42308]: vdsm vds.dispatcher ERROR SSL
> error receiving from  (':::172.16.75.16', 38350, 0, 0) at 0x33b9bd8>: unexpected eof
> Feb 20 18:44:24 kvm-ldn-01 vdsm[42308]: vdsm jsonrpc.JsonRpcServer
> ERROR Internal server error
> Traceback (most recent call last):
>   File
> "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 547, in
> _handle_request...
>
> Any ideas what might be going on here?

I see that ~13 vm was move to up state.

Can you please say which host is causing issues and provide the logs.

>
> Thanks,
>
> Cam
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] EventProcessingPoolSize

2016-12-27 Thread Piotr Kliczewski
Hi,

This pool is responsible for event processing. There are not so many events
that we send from vdsm. At the moment we send vm status changes. The
default value may be not enough when we provision, delete, stop etc many
vms at the same time. If your environment is static the default value
should be good enough.

Thanks,
Piotr



21 gru 2016 14:55  napisał(a):

Hi All, there is an engine config option named EventProcessingPoolSize:
default value is 10.
I am wondering how to determine what it is and if the setting is right for
my setup.

I have around 36 dc's at the moment with two hosts running between 2 -3 vm;s

should this value be increased?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [Feture discussion] Full vacuum tool

2016-12-07 Thread Piotr Kliczewski
On Wed, Dec 7, 2016 at 9:57 AM, Roy Golan  wrote:
> Hi all,
>
> This is a discussion on the RFE[1] to provide a tool to perform full vacuum
> on our DBs.
>
> First if you are not familiar with vacuum please read this [2]
>
> # Backgroud
> ovirt 'engine' DB have several busy table with 2 differnt usage patten. One
> is audit_log and the others are the 'v*_statistics' tables and the
> difference between them is mostly inserts vs mostly hot updates.
> Tables with tons of updates creates garbage or 'dead' records that should be
> removed, and for this postgres have the aforementioned autovacuum cleaner.
> It will make the db reuse its already allocated space to perform future
> updates/inserts and so on.
> Autovacuum is essential for a db to function optimally and tweaking it is
> out of the scope of the feature.
>
> Full vacuum is designed to reclaim the disk space and reset the table
> statistics. It is a heavy maintenance task, it takes an exclusive lock on
> the table and may take seconds to minutes. In some situations it is
> effectively a downtime due to the long table lock and should not be running
> when the engine is running.
>
> # Critiria
> Provide a way to reclaim disk space claimed by the garbage created over time
> by the engine db and dwh.

What about not storing this data in db? Do we need it all the time or
just for some amount of time?

>
> # Usage
> Either use it as part of the upgrade procedure (after all dbscipts
> execution)
> or just provide the tool and admin will run in on demand
> - engine db credentials read from /etc/ovirt-engine/engine.conf.d/
> - invocation:
>  ```
>  tool: [dbname(default engine)] [table: (default all)]
>  ```
> - if we invoke it on upgrade than an installation plugin should be added to
> invoke with default, no interaction
> - since VACUUM ANALYZE is consider a recommended maintenance task we can to
> it by default and ask the user for FULL.
> - remote db is supported as well, doesn't have to be local
>
> # Questions
>  - Will remote dwh have the credentials under
> /etc/ovirt-engine/engine.conf.d?
>  - Should  AAA schema be taken into account as well?
>
> Please review, thanks
> Roy
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1388430
> [2]
> https://www.postgresql.org/docs/9.2/static/runtime-config-autovacuum.html
> [3] https://www.postgresql.org/docs/devel/static/sql-vacuum.html
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unexpected SSL errors (unexpected eof) in vdsm log?

2016-11-14 Thread Piotr Kliczewski
On Thu, Nov 10, 2016 at 5:18 PM, Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
>
> On Thu, November 10, 2016 11:04 am, Piotr Kliczewski wrote:
> [snip]
>>> Could you explain the above error?  I'm not sure I understand what it
>>> means.  I do, however, know what the following error is about.  I
>>> attempted to import an OVA file and the file was mode 600 root:root and
>>> therefore was not readable by VDSM.  Hence the "Errno 13: Permission
>>> Denied":
>>>
>>
>> I added the stack traces to the email because I want someone from
>> storage and virt to take a look
>> at those failures. Maybe both were fixed already.
>
> The second stack trace, I presume, is due to my permission problem.  If so
>  then that's my own doing and not something to fix in oVirt.  (Unless my
> assumption is incorrect, but at the time the .ova file *was* unreadable).
>
>>>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
>>>> VDSGenericException: VDSErrorException: Failed to GetOvaInfoVDS, error
>>>> = [Errno 13] Permission denied:
>>>> u'/ovirt/import/openafs-fc23-64.ihtfp.org.ova', code = -32603 (Failed
>>>> with error unexpected and code 16)
>>>> at
>>> [snip]
>>>>
>>>> both not related to reconnects.
>>>
>>> Agreed.
>>>
>>>> I see that from time to time there are connections reset by peer
>>>>
>>>> 2016-11-04 10:58:43,442 ERROR
>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsVDSCommand]
>>>> (DefaultQuartzScheduler6) [77387d45] Command
>>>> 'GetStatsVDSCommand(HostName = ovirt-0,
>>>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>>>> hostId='62b75bb9-fbd9-405f-b479-b6ad8cffd5b1',
>>>> vds='Host[ovirt-0,62b75bb9-fbd9-405f-b479-b6ad8cffd5b1]'})' execution
>>>> failed: VDSGenericException: VDSNetworkException: Connection reset by
>>>> peer
>>>>
>>>> which means that vdsm or the host was stopped. Vdsm log you provided
>>>> do not cover this time so I am not able to say what is the cause of
>>>> it.
>>>
>>> Yeah, Nov 4 was approximately the time I was installing the systems, so
>>> yes, it's not surprising to see some up and down times around then.
>>>
>>>>
>>>> There are more 'unexpected eof' in the logs but they seems not to be
>>>> triggered by the engine. It looks like those connection are triggered
>>>> from local host.
>>>> This seems to be related to https://bugzilla.redhat.com/1349829
>>>
>>> Is there something I can do to test/verify this?
>>
>> It needs to be fixed first. I added it as reference for you.
>
> Thanks.  I was more asking if there is some way to verify that this *is*
> the bug I'm hitting?  Otherwise I have to wait for the fix for this bug
> and only then can I see if it actually fixes this issue or if it's
> something else.

I think we need to wait

>
> I'm not sure why not re-using the session would cause an EOF Error.
>
> Thanks,
>
> -derek
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unexpected SSL errors (unexpected eof) in vdsm log?

2016-11-10 Thread Piotr Kliczewski
On Thu, Nov 10, 2016 at 3:20 PM, Derek Atkins <de...@ihtfp.com> wrote:
> Piotr,
>
> On Thu, November 10, 2016 7:01 am, Piotr Kliczewski wrote:
>> Derek,
>>
>> I see 2 issues in the engine logs:
>>
>> 2016-11-02 09:53:13,767 WARN
>> [org.ovirt.engine.core.bll.storage.disk.image.GetUnregisteredDiskQuery]
>> (org.ovirt.thread.pool-8-thread-47) [1e5f014c] Exception while parsing
>> JSON for disk. Exception: '{}':
>> org.codehaus.jackson.JsonParseException: Unexpected character ('H'
>> (code 72)): expected a valid value (number, String, array, object,
>> 'true', 'false' or 'null')
>>  at [Source: java.io.StringReader@482fe2d8; line: 1, column: 2]
>> at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433)
>> [jackson-core-asl-1.9.13.jar:1.9.13]
>> at
>> org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521)
>> [jackson-core-asl-1.9.13.jar:1.9.13]
>> at
>> org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:442)
>> [jackson-core-asl-1.9.13.jar:1.9.13]
>> at
>> org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1198)
>> [jackson-core-asl-1.9.13.jar:1.9.13]
>> at
>> org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:485)
>> [jackson-core-asl-1.9.13.jar:1.9.13]
>> at
>> org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2770)
>> [jackson-mapper-asl-1.9.13.jar:1.9.13]
>> at
>> org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)
>> [jackson-mapper-asl-1.9.13.jar:1.9.13]
>> at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1877)
>> [jackson-mapper-asl-1.9.13.jar:1.9.13]
>> at org.ovirt.engine.core.utils.JsonHelper.jsonToMap(JsonHelper.java:41)
>> [utils.jar:]
>> at
>> org.ovirt.engine.core.bll.storage.disk.image.MetadataDiskDescriptionHandler.enrichDiskByJsonDescription(MetadataDiskDescriptionHandler.java:247)
>> [bll.jar:]
>
>
> Could you explain the above error?  I'm not sure I understand what it
> means.  I do, however, know what the following error is about.  I
> attempted to import an OVA file and the file was mode 600 root:root and
> therefore was not readable by VDSM.  Hence the "Errno 13: Permission
> Denied":
>

I added the stack traces to the email because I want someone from
storage and virt to take a look
at those failures. Maybe both were fixed already.

>
>>
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
>> VDSGenericException: VDSErrorException: Failed to GetOvaInfoVDS, error
>> = [Errno 13] Permission denied:
>> u'/ovirt/import/openafs-fc23-64.ihtfp.org.ova', code = -32603 (Failed
>> with error unexpected and code 16)
>> at
> [snip]
>>
>> both not related to reconnects.
>
> Agreed.
>
>> I see that from time to time there are connections reset by peer
>>
>> 2016-11-04 10:58:43,442 ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsVDSCommand]
>> (DefaultQuartzScheduler6) [77387d45] Command
>> 'GetStatsVDSCommand(HostName = ovirt-0,
>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='62b75bb9-fbd9-405f-b479-b6ad8cffd5b1',
>> vds='Host[ovirt-0,62b75bb9-fbd9-405f-b479-b6ad8cffd5b1]'})' execution
>> failed: VDSGenericException: VDSNetworkException: Connection reset by
>> peer
>>
>> which means that vdsm or the host was stopped. Vdsm log you provided
>> do not cover this time so I am not able to say what is the cause of
>> it.
>
> Yeah, Nov 4 was approximately the time I was installing the systems, so
> yes, it's not surprising to see some up and down times around then.
>
>>
>> There are more 'unexpected eof' in the logs but they seems not to be
>> triggered by the engine. It looks like those connection are triggered
>> from local host.
>> This seems to be related to https://bugzilla.redhat.com/1349829
>
> Is there something I can do to test/verify this?

It needs to be fixed first. I added it as reference for you.

>
>> Thanks,
>> Piotr
>
> -derek
>
>>
>> On Tue, Nov 8, 2016 at 4:29 PM, Derek Atkins <de...@ihtfp.com> wrote:
>>> Hi,
>>>
>>> I'm not sure if you want my logs here or on the bug report (you didn't
>>> specify).  But here you go.  I had to gzip them to get them down to
>>> size -- the VDSM log is 18MB just from today (man is it chatty!)
>>>
>>> -derek
>>>
>>> Piotr Kliczewski <piotr.kliczew...@gmail.com> w

Re: [ovirt-users] Unexpected SSL errors (unexpected eof) in vdsm log?

2016-11-10 Thread Piotr Kliczewski
Derek,

I see 2 issues in the engine logs:

2016-11-02 09:53:13,767 WARN
[org.ovirt.engine.core.bll.storage.disk.image.GetUnregisteredDiskQuery]
(org.ovirt.thread.pool-8-thread-47) [1e5f014c] Exception while parsing
JSON for disk. Exception: '{}':
org.codehaus.jackson.JsonParseException: Unexpected character ('H'
(code 72)): expected a valid value (number, String, array, object,
'true', 'false' or 'null')
 at [Source: java.io.StringReader@482fe2d8; line: 1, column: 2]
at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433)
[jackson-core-asl-1.9.13.jar:1.9.13]
at 
org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521)
[jackson-core-asl-1.9.13.jar:1.9.13]
at 
org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:442)
[jackson-core-asl-1.9.13.jar:1.9.13]
at 
org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1198)
[jackson-core-asl-1.9.13.jar:1.9.13]
at 
org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:485)
[jackson-core-asl-1.9.13.jar:1.9.13]
at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2770)
[jackson-mapper-asl-1.9.13.jar:1.9.13]
at 
org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)
[jackson-mapper-asl-1.9.13.jar:1.9.13]
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1877)
[jackson-mapper-asl-1.9.13.jar:1.9.13]
at org.ovirt.engine.core.utils.JsonHelper.jsonToMap(JsonHelper.java:41)
[utils.jar:]
at 
org.ovirt.engine.core.bll.storage.disk.image.MetadataDiskDescriptionHandler.enrichDiskByJsonDescription(MetadataDiskDescriptionHandler.java:247)
[bll.jar:]


org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed to GetOvaInfoVDS, error
= [Errno 13] Permission denied:
u'/ovirt/import/openafs-fc23-64.ihtfp.org.ova', code = -32603 (Failed
with error unexpected and code 16)
at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:114)
[bll.jar:]
at 
org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33)
[bll.jar:]
at 
org.ovirt.engine.core.bll.QueriesCommandBase.runVdsCommand(QueriesCommandBase.java:257)
[bll.jar:]
at 
org.ovirt.engine.core.bll.GetVmFromOvaQuery.getVmInfoFromOvaFile(GetVmFromOvaQuery.java:24)
[bll.jar:]
at 
org.ovirt.engine.core.bll.GetVmFromOvaQuery.executeQueryCommand(GetVmFromOvaQuery.java:20)
[bll.jar:]


both not related to reconnects.

I see that from time to time there are connections reset by peer

2016-11-04 10:58:43,442 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsVDSCommand]
(DefaultQuartzScheduler6) [77387d45] Command
'GetStatsVDSCommand(HostName = ovirt-0,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='62b75bb9-fbd9-405f-b479-b6ad8cffd5b1',
vds='Host[ovirt-0,62b75bb9-fbd9-405f-b479-b6ad8cffd5b1]'})' execution
failed: VDSGenericException: VDSNetworkException: Connection reset by
peer

which means that vdsm or the host was stopped. Vdsm log you provided
do not cover this time so I am not able to say what is the cause of
it.

There are more 'unexpected eof' in the logs but they seems not to be
triggered by the engine. It looks like those connection are triggered
from local host.
This seems to be related to https://bugzilla.redhat.com/1349829

Thanks,
Piotr

On Tue, Nov 8, 2016 at 4:29 PM, Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
>
> I'm not sure if you want my logs here or on the bug report (you didn't
> specify).  But here you go.  I had to gzip them to get them down to
> size -- the VDSM log is 18MB just from today (man is it chatty!)
>
> -derek
>
> Piotr Kliczewski <piotr.kliczew...@gmail.com> writes:
>
>> Derek,
>>
>> This error may occur from time to time due to [1] but in your listing
>> it is much to often.
>> Please share engine and vdsm logs so we could see why.
>>
>> Thanks,
>> Piotr
>>
>>
>> [1] https://bugzilla.redhat.com/1349829
>
>
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unexpected SSL errors (unexpected eof) in vdsm log?

2016-11-08 Thread Piotr Kliczewski
Derek,

This error may occur from time to time due to [1] but in your listing
it is much to often.
Please share engine and vdsm logs so we could see why.

Thanks,
Piotr


[1] https://bugzilla.redhat.com/1349829

On Mon, Nov 7, 2016 at 7:04 PM, Derek Atkins  wrote:
> Trying to track down some issues I'm seeing and I've noticed a log full
> of SSL Errors:
>
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:04,402::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:08,135::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:11,896::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:15,532::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:29,155::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:36,418::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:36,612::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:40,418::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:44,158::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-11-07 
> 13:03:47,878::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: unexpected eof
>
> Any idea where this is coming from, and how to fix it?
>
> -derek
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm vds.dispatcher ERROR SSL

2016-10-21 Thread Piotr Kliczewski
Baptiste,

It would be great if you could provide engine log with debug log level enabled.

In ovirt-engine.xml.in file please update following entries:

  
  


  


  

Please provide vdsm log from the same time as well.

Thanks,
Piotr


On Fri, Oct 21, 2016 at 11:43 AM, Baptiste Agasse
 wrote:
> Hi all,
>
> I think we have the same or similar problem than Gianluca describe in this 
> thread [1]. I've applied patches [2] and [3] to improve logging on vdsm side. 
> It seems that the "vdsm vds.dispatcher ERROR SSL error" occurs only on the 
> SPM node as we noticed that these logs disappears when another host is 
> selected as SPM, and we can find these errors on the new SPM host. We have 
> multiple DCs, one with the hosted engine, and others with only simple hosts. 
> The problem don't occurs on the hosted engine cluster in our deployment. This 
> problem seems related to instability on this cluster, the SPM host fall in 
> unresponsive state mostly every 4 minutes and comeback during the grace 
> period most of the time (but was fenced 1 or 2 times last 2 weeks).
>
> Information about our setup:
>
> * All hosts, including engine, are CentOS 7 x86_64
> * All hosts share the same ntp server and are in sync
> * Firewalls are disabled on all hosts
> * All storage domains are on ISCSI backends
> * All DC are located in the same room. We created multiple DC because we have 
> multiple storage backends on separated SANs and we didn't notice any network 
> issues between the engine and the SPM hosts of the problematic cluster.
>
> Engine packages:
> ovirt-image-uploader-4.0.1-1.el7.centos.noarch
> ovirt-engine-tools-backup-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-extension-aaa-misc-1.0.1-1.el7.noarch
> ovirt-engine-extension-aaa-jdbc-1.1.0-1.el7.noarch
> ovirt-engine-dashboard-1.0.3-1.el7.centos.noarch
> ovirt-engine-dwh-4.0.2-1.el7.centos.noarch
> ovirt-host-deploy-java-1.5.2-1.el7.centos.noarch
> ovirt-engine-userportal-4.0.4.4-1.el7.centos.noarch
> ovirt-host-deploy-1.5.2-1.el7.centos.noarch
> ovirt-engine-setup-plugin-ovirt-engine-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch
> ovirt-engine-tools-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-4.0.4.4-1.el7.centos.noarch
> ovirt-guest-agent-common-1.0.12-3.el7.noarch
> ovirt-vmconsole-proxy-1.0.4-1.el7.centos.noarch
> ovirt-engine-cli-3.6.8.1-1.el7.centos.noarch
> ovirt-engine-extension-aaa-ldap-1.2.1-1.el7.noarch
> ovirt-engine-wildfly-10.0.0-1.el7.x86_64
> ovirt-engine-lib-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-vmconsole-proxy-helper-4.0.4.4-1.el7.centos.noarch
> ovirt-iso-uploader-4.0.1-1.el7.centos.noarch
> ovirt-engine-webadmin-portal-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-restapi-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-jboss-as-7.1.1-1.el7.centos.x86_64
> ovirt-engine-dwh-setup-4.0.2-1.el7.centos.noarch
> ovirt-guest-tools-iso-4.0-1.fc23.noarch
> ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch
> python-ovirt-engine-sdk4-4.0.1-1.el7.centos.x86_64
> ovirt-engine-setup-plugin-ovirt-engine-common-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-setup-plugin-websocket-proxy-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-websocket-proxy-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-setup-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-extensions-api-impl-4.0.4.4-1.el7.centos.noarch
> ovirt-engine-backend-4.0.4.4-1.el7.centos.noarch
> ovirt-release35-005-1.noarch
> ovirt-setup-lib-1.0.2-1.el7.centos.noarch
> ovirt-imageio-common-0.4.0-1.el7.noarch
> ovirt-imageio-proxy-setup-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch
> ovirt-release40-4.0.4-1.noarch
> ovirt-engine-dbscripts-4.0.4.4-1.el7.centos.noarch
> ovirt-vmconsole-1.0.4-1.el7.centos.noarch
> ovirt-release36-3.6.7-1.noarch
> ovirt-engine-extension-aaa-ldap-setup-1.2.1-1.el7.noarch
> ovirt-engine-setup-base-4.0.4.4-1.el7.centos.noarch
> ovirt-imageio-proxy-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch
>
> Virtualization host packages:
> ovirt-vmconsole-1.0.4-1.el7.centos.noarch
> vdsm-4.18.13-1.el7.centos.x86_64
> vdsm-infra-4.18.13-1.el7.centos.noarch
> vdsm-xmlrpc-4.18.13-1.el7.centos.noarch
> ovirt-release40-4.0.4-1.noarch
> vdsm-jsonrpc-4.18.13-1.el7.centos.noarch
> vdsm-api-4.18.13-1.el7.centos.noarch
> vdsm-python-4.18.13-1.el7.centos.noarch
> ovirt-imageio-common-0.4.0-1.el7.noarch
> vdsm-hook-vmfex-dev-4.18.13-1.el7.centos.noarch
> ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch
> vdsm-yajsonrpc-4.18.13-1.el7.centos.noarch
> vdsm-cli-4.18.13-1.el7.centos.noarch
> ovirt-imageio-daemon-0.4.0-1.el7.noarch
>
> In the logs:
> oVirt engine: engine.foo.example.com, 192.168.1.10
> virtualization host: virt03.foo.example.com, 192.168.1.11
>
> Attached files:
> /var/log/ovirt-engine/engine.log
> /var/log/vdsm/vdsm.log
> /var/log/messages (for virtualization host)
>
>
> Have a nice day.
>
> Regards
>
> [1] 

Re: [ovirt-users] vdsm ssl errors

2016-10-13 Thread Piotr Kliczewski
Gianluca,

The port needs to be open on machines where vdsm is installed.

@Simone can you take a look why after running host deploy at 2016-10-03
23:28:47,891
we are not able to talk to vdsm anymore?

Thanks,
Piotr

On Thu, Oct 13, 2016 at 11:15 AM, Gianluca Cecchi <gianluca.cec...@gmail.com
> wrote:

>
>
> On Thu, Oct 13, 2016 at 11:13 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Il 13/Ott/2016 11:00, "Piotr Kliczewski" <pklic...@redhat.com> ha
>> scritto:
>> >
>> > Gianluca,
>> >
>> > Checking the log it seems that we do not configure firewall:
>> >
>> > NETWORK/firewalldEnable=bool:'False'
>> > NETWORK/iptablesEnable=bool:'False'
>> >
>> > Please make sure that you reconfigure your firewall to open 54321 port
>> or let host deploy to do it for you.
>> >
>> > Thanks,
>> > Piotr
>>
>> Hi,
>> at this moment Ihave:
>> On hypervisor iptables service configured and active.
>> On engine firewalld service configured and active.
>> Do I have to open port 54321 on host?
>>
> Actually it is already...
>
> root@ovirt01 ~]# iptables -L -n
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT udp  --  0.0.0.0/00.0.0.0/0udp dpt:53
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:53
> ACCEPT udp  --  0.0.0.0/00.0.0.0/0udp dpt:67
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:67
> ACCEPT all  --  192.168.1.2120.0.0.0/0
> ACCEPT all  --  0.0.0.0/00.0.0.0/0state
> RELATED,ESTABLISHED
> ACCEPT icmp --  0.0.0.0/00.0.0.0/0
> ACCEPT all  --  0.0.0.0/00.0.0.0/0
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0tcp
> dpt:54321
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:111
> ACCEPT udp  --  0.0.0.0/00.0.0.0/0udp dpt:111
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:22
> ACCEPT udp  --  0.0.0.0/00.0.0.0/0udp dpt:161
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0tcp
> dpt:16514
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0multiport
> dports 2223
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0multiport
> dports 5900:6923
> ACCEPT tcp  --  0.0.0.0/00.0.0.0/0multiport
> dports 49152:49216
> REJECT all  --  0.0.0.0/00.0.0.0/0reject-with
> icmp-host-prohibited
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
> ACCEPT all  --  0.0.0.0/0192.168.122.0/24 ctstate
> RELATED,ESTABLISHED
> ACCEPT all  --  192.168.122.0/24 0.0.0.0/0
> ACCEPT all  --  0.0.0.0/00.0.0.0/0
> REJECT all  --  0.0.0.0/00.0.0.0/0reject-with
> icmp-port-unreachable
> REJECT all  --  0.0.0.0/00.0.0.0/0reject-with
> icmp-port-unreachable
> REJECT all  --  0.0.0.0/00.0.0.0/0PHYSDEV
> match ! --physdev-is-bridged reject-with icmp-host-prohibited
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT udp  --  0.0.0.0/00.0.0.0/0udp dpt:68
> [root@ovirt01 ~]#
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-13 Thread Piotr Kliczewski
Gianluca,

Checking the log it seems that we do not configure firewall:

NETWORK/firewalldEnable=bool:'False'
NETWORK/iptablesEnable=bool:'False'

Please make sure that you reconfigure your firewall to open 54321 port or
let host deploy to do it for you.

Thanks,
Piotr


On Wed, Oct 12, 2016 at 7:14 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

>
>
> On Wed, Oct 12, 2016 at 5:39 PM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>
>> This log did not help me either because during this specific time there
>> was no logs in the engine.
>>
>> 2016-10-12 09:51:35,296 INFO  [org.ovirt.engine.core.bll.sto
>> rage.domain.IsoDomainListSyncronizer] (org.ovirt.thread.pool-8-thread-13)
>> [141b5168] Finished automatic refresh process for 'ISO' file type with
>> success, for storage domain id 'fd5754f1-bd00-4337-ad64-1abde35438ae'.
>> 2016-10-12 10:42:49,188 INFO  
>> [org.ovirt.engine.core.bll.EngineBackupAwarenessManager]
>> (DefaultQuartzScheduler8) [63f92190] Backup check started.
>>
>> This means that it is not the engine attempting to connect.
>> @Simone can you please check whether this is hosted engine?
>>
>> Looking more in to the logs I see that after hostdeploy there are no more
>> attempts to connect from the engine:
>>
>> 2016-10-03 23:28:47,891 INFO  [org.ovirt.engine.core.uutils.ssh.SSHDialog]
>> (DefaultQuartzScheduler8) [4afdc494] SSH execute 'root@ractor.mynewdomain'
>> 'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t
>> ovirt-XX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm
>> -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C
>> "${MYTMP}" -x &&  "${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
>> DIALOG/customization=bool:True'
>>
>> Later in the logs I can see bunch of redeploys but no sign of attempt to
>> connect.
>>
>> Can you please share one of the host deploy logs?
>>
>> According to the logs this is the last one: /var/log/ovirt-engine/host-dep
>> loy/ovirt-host-mgmt-20161011233340-ractor.mynewdomain-23718eb3.log
>>
>> Thanks,
>> Piotr
>>
>
> Here the file
> ovirt-host-mgmt-20161011233340-ractor.mynewdomain-23718eb3.log
> https://drive.google.com/file/d/0BwoPbcrMv8mvUTVMa1h3cVA2cGs/
> view?usp=sharing
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-12 Thread Piotr Kliczewski
This log did not help me either because during this specific time there was
no logs in the engine.

2016-10-12 09:51:35,296 INFO
[org.ovirt.engine.core.bll.storage.domain.IsoDomainListSyncronizer]
(org.ovirt.thread.pool-8-thread-13) [141b5168] Finished automatic refresh
process for 'ISO' file type with success, for storage domain id
'fd5754f1-bd00-4337-ad64-1abde35438ae'.
2016-10-12 10:42:49,188 INFO
[org.ovirt.engine.core.bll.EngineBackupAwarenessManager]
(DefaultQuartzScheduler8) [63f92190] Backup check started.

This means that it is not the engine attempting to connect.
@Simone can you please check whether this is hosted engine?

Looking more in to the logs I see that after hostdeploy there are no more
attempts to connect from the engine:

2016-10-03 23:28:47,891 INFO  [org.ovirt.engine.core.uutils.ssh.SSHDialog]
(DefaultQuartzScheduler8) [4afdc494] SSH execute 'root@ractor.mynewdomain'
'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t
ovirt-XX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm
-fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C
"${MYTMP}" -x &&  "${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
DIALOG/customization=bool:True'

Later in the logs I can see bunch of redeploys but no sign of attempt to
connect.

Can you please share one of the host deploy logs?

According to the logs this is the last one:
/var/log/ovirt-engine/host-deploy/ovirt-host-mgmt-20161011233340-ractor.mynewdomain-23718eb3.log

Thanks,
Piotr

On Wed, Oct 12, 2016 at 4:23 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> On Wed, Oct 12, 2016 at 3:59 PM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>
>> As you listed engine logs end 14 minutes before vdsm logs start. It
>> should be enough if you sent older vdsm log which covers
>> engine logs time frame.
>>
>> Thanks,
>> Piotr
>>
>>
> Here it is the vdsm.log.6.xz file:
>
> https://drive.google.com/file/d/0BwoPbcrMv8mvUlhvdnd4QW9GSUk/
> view?usp=sharing
>
> that covers the previous hour from
>
> jsonrpc.Executor/4::DEBUG::2016-10-12 10:01:01,928::__init__::530::
> jsonrpc.JsonRpcServer::(_handle_request) Calling 'Host.getHardwareInfo'
> in bridge with {}
>
> to
>
> mailbox.SPMMonitor::DEBUG::2016-10-12 11:01:00,542::storage_mailbox:
> :733::Storage.Misc.excCmd::(_checkForMail) SUCCESS:  = '1+0 records
> in\n1+0 records out\n1024000 bytes (1.0 MB) copied, 0.00410016 s, 250
> MB/s\n';  = 0
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-12 Thread Piotr Kliczewski
As you listed engine logs end 14 minutes before vdsm logs start. It should
be enough if you sent older vdsm log which covers
engine logs time frame.

Thanks,
Piotr

On Wed, Oct 12, 2016 at 2:46 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> On Wed, Oct 12, 2016 at 2:03 PM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>
>> What I meant is that you sent logs created at different times so I was
>> unable to match both ends (engine and vdsm.
>>
>> It would be great if you could sent the logs from the same time.
>>
>>
>>
> Probably there is something I don't understand...
>
> I collect logs at 11:05
> I copy both current engine.log and current vdsmd.log and update them to
> google drive
>
> Due to how ovirt-engine and vdsmd are logging and to how they are rotating
> I have
>
> 1) the current engine.log initial and final lines at that time are
>
> 2016-09-27 03:16:08,460 INFO  
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
> (DefaultQuartzScheduler1) [1e566c35] Fetched 5 VMs from VDS
> '0d6cfc43-99bb-468e-92d8-f615ef3362ae'
> ...
> 2016-10-12 10:51:36,336 INFO  
> [org.ovirt.engine.core.bll.storage.domain.IsoDomainListSyncronizer]
> (org.ovirt.thread.pool-8-thread-3) [da0fb3b] Finished automatic refresh
> process for 'ISO' file type with success, for storage domain id
> 'fd5754f1-bd00-4337-ad64-1abde35438ae'.
>
> quite obviously no more logging during latest 14 minutes and so no
> more lines inside the file...
>
>
> 2) the current vdsmd.log initial and final lines are instead
>
> mailbox.SPMMonitor::DEBUG::2016-10-12 11:01:02,558::storage_mailbox:
> :733::Storage.Misc.excCmd::(_checkForMail) /us
> r/bin/taskset --cpu-list 0-31 dd if=/rhev/data-center/0001-
> 0001-0001-0001-00ec/mastersd/dom_md/inbox i
> flag=direct,fullblock count=1 bs=1024000 (cwd None)
> ...
> mailbox.SPMMonitor::DEBUG::2016-10-12 11:05:25,507::storage_mailbox:
> :733::Storage.Misc.excCmd::(_checkForMail) SUCCESS:  = '1+0 records
> in\n1+0 records out\n1024000 bytes (1.0 MB) copied, 0.00455719 s, 225
> MB/s\n';  = 0
>
> tipically vdsmd.log rotation happens every 1 hour and in fact that
> particular vdsmd is now named (at 14:43) vdsm.log.3.xz and in total
> contains from the already shown line
>
> mailbox.SPMMonitor::DEBUG::2016-10-12 11:01:02,558::storage_mailbox:
> :733::Storage.Misc.excCmd::(_checkForMail) /usr/bin/taskset --cpu-list
> 0-31 dd 
> if=/rhev/data-center/0001-0001-0001-0001-00ec/mastersd/dom_md/inbox
> iflag=direct,fullblock count=1 bs=1024000 (cwd None)
>
> up to
>
> Thread-642572::INFO::2016-10-12 12:01:00,744::xmlrpc::91::vds.
> XMLRPCServer::(_process_requests) Request handler for 127.0.0.1:47818
> stopped
>
> when it has been rotated
>
> Please explain what is wrong with my approach giving you the information
> needed Do you need more vdsmd.log files in the past?
>
> Gianluca
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-12 Thread Piotr Kliczewski
What I meant is that you sent logs created at different times so I was
unable to match both ends (engine and vdsm.

It would be great if you could sent the logs from the same time.


On Wed, Oct 12, 2016 at 1:22 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> On Wed, Oct 12, 2016 at 1:08 PM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>
>> Is it possible to login to the system and take a look at the logs.
>> If so please send me details offline.
>>
>>
>>
> Unfortunately not to this particular system. The other one is one of my
> home systems and I can manage something perhaps.
> But are you interested in any particular log? I can upload without
> problems.
> The strange thing is that I have the same situation on two environments
> that are configured the same way (single host with self hosted engine) and
> both passed from initial configuration in 3.6.x to 4.0.x.
> Possibly I made the same configuration errors on both, or the problem is
> passing from 3. to 4.0.
> But the original originator of the thread perhaps had this problem
> (solved?) with diect installation in 4.0.
> He said in one of his posts:
>
> "
> all nodes and engines are synced to the same timeserver.
>
> as far as i can tell, the connection is from the node itself, to the vdsm
> on the node, so no time difference can occur.
>
> the certificate that get's presented be vdsm on port 54321 looks ok.
>
> For what it is worth, I changed the certificate of the hosted-engine web
> interface by reconfiguring apaches mod_ssl, not touching any certificate in
> hosted-engine:/etc/pki/ovirt-*
> "
>
> Does 3.6 to 4.0 involve anything similar to his situation?
>
> Gianluca
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-12 Thread Piotr Kliczewski
Is it possible to login to the system and take a look at the logs.
If so please send me details offline.

On Wed, Oct 12, 2016 at 1:07 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> On Wed, Oct 12, 2016 at 12:52 PM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>
>> It would be great if you could provide vdsm and engine from the same time.
>>
>> I see that engine logs end at 2016-10-12 10:51:36,336 and vdsm logs start
>> at 2016-10-12 11:01:02,558
>>
>> Thanks,
>> Piotr
>>
>>
>>
> Hello,
> vdsm writes Tb of logs... don't you remember? ;-)
>
> The next line in engine.log was after my collection, at 11:11...
>
> 2016-10-12 10:51:36,336 INFO  
> [org.ovirt.engine.core.bll.storage.domain.IsoDomainListSyncronizer]
> (org.ovirt.thread.pool-8-thread-3) [da0fb3b] Finished automatic refresh
> process for 'ISO' file type with success, for storage domain id
> 'fd5754f1-bd00-4337-ad64-1abde35438ae'.
> 2016-10-12 11:11:15,117 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils]
> (default task-44) [] Session expired please try again.
>
> BTW: the system keeps 100 vdsm logs in copressed format. Each file
> uncompressed is about 40Mbytes. This makes up a total of about 4Gb
> And the oldest line is "2016-10-08 10:01:02,638". This means about 4 days
> ago.
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-12 Thread Piotr Kliczewski
It would be great if you could provide vdsm and engine from the same time.

I see that engine logs end at 2016-10-12 10:51:36,336 and vdsm logs start
at 2016-10-12 11:01:02,558

Thanks,
Piotr

On Wed, Oct 12, 2016 at 11:15 AM, Gianluca Cecchi <gianluca.cec...@gmail.com
> wrote:

>
> On Wed, Oct 12, 2016 at 8:55 AM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>
>> Gianluca,
>>
>> Please share engine log as well.
>>
>> Thanks,
>> Piotr
>>
>>
> Hello, I have not access right now to that server, but I have another
> quite similar environment (here the server is a Dell M910) with same
> behavior. It is at 4.0.4 too.
> And also this environment was created in 3.6.x and then updated to various
> 4.0.x up to 4.0.4 now
> vdsm version is now vdsm-4.18.13-1.el7.centos.x86_64
>
> here vdsm.log in gzip format
> https://drive.google.com/file/d/0BwoPbcrMv8mvUThnOEVqM21JSTg/
> view?usp=sharing
>
> and here engine.log in gzip format
> https://drive.google.com/file/d/0BwoPbcrMv8mvUUVnZnQ5cGN0NHM/
> view?usp=sharing
>
> [root@ractor ~]# systemctl status vdsmd
> . vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/etc/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Mon 2016-10-03 22:56:11 CEST; 1 weeks 1
> days ago
>   Process: 30970 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 30974 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=0/SUCCESS)
>  Main PID: 31166 (vdsm)
>CGroup: /system.slice/vdsmd.service
>├─31166 /usr/bin/python /usr/share/vdsm/vdsm
>├─31265 /usr/libexec/ioprocess --read-pipe-fd 61
> --write-pipe-fd 59 --max-threads 10 --max-queued-req...
>├─31280 /usr/libexec/ioprocess --read-pipe-fd 77
> --write-pipe-fd 76 --max-threads 10 --max-queued-req...
>├─31371 /usr/libexec/ioprocess --read-pipe-fd 105
> --write-pipe-fd 103 --max-threads 10 --max-queued-r...
>├─33870 /usr/libexec/ioprocess --read-pipe-fd 40
> --write-pipe-fd 39 --max-threads 10 --max-queued-req...
>├─33889 /usr/libexec/ioprocess --read-pipe-fd 48
> --write-pipe-fd 47 --max-threads 10 --max-queued-req...
>├─33896 /usr/libexec/ioprocess --read-pipe-fd 58
> --write-pipe-fd 55 --max-threads 10 --max-queued-req...
>├─33904 /usr/libexec/ioprocess --read-pipe-fd 73
> --write-pipe-fd 72 --max-threads 10 --max-queued-req...
>└─33911 /usr/libexec/ioprocess --read-pipe-fd 98
> --write-pipe-fd 96 --max-threads 10 --max-queued-req...
>
> Oct 12 11:11:49 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:11:50 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:11:56 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:01 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:07 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:22 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:33 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:34 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:39 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Oct 12 11:12:45 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL
> error during reading d...eof
> Hint: Some lines were ellipsized, use -l to show in full.
> [root@ractor ~]#
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-12 Thread Piotr Kliczewski
Gianluca,

Please share engine log as well.

Thanks,
Piotr

On Wed, Oct 12, 2016 at 12:33 AM, Gianluca Cecchi  wrote:

> Il 09/Ott/2016 09:51, "Oved Ourfali"  ha scritto:
> >
> > Fixed in "Bug 1371515 - Exception on GetUserProfileQuery (unknown cause)
> : "The column name user_portal_vm_auto_login was not found in this
> ResultSet".
> > Please upgrade to latest 4.0.
> >
>
> Hello, updated to 4.0.4, I don't see the message about resultSet. But I
> continue to see the SSL errors, it doesn't change much.
>
> All seems running: 3 VMs included the Hosted Engine.
>
> Here the vdsm.log in gzip format:
>
> https://drive.google.com/file/d/0BwoPbcrMv8mvdDFFOEhTQ3o1ZXM/
> view?usp=sharing
>
> [root@ovirt01 vdsm]# systemctl status vdsmd
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/etc/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Tue 2016-10-11 23:59:02 CEST; 17min ago
>   Process: 19335 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 19338 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=0/SUCCESS)
>  Main PID: 19421 (vdsm)
>CGroup: /system.slice/vdsmd.service
>├─19421 /usr/bin/python /usr/share/vdsm/vdsm
>├─19539 /usr/libexec/ioprocess --read-pipe-fd 69
> --write-pipe-fd 67 --max-threads 10 --max-queued-requests 10
>├─19599 /usr/libexec/ioprocess --read-pipe-fd 98
> --write-pipe-fd 97 --max-threads 10 --max-queued-requests 10
>├─19621 /usr/libexec/ioprocess --read-pipe-fd 109
> --write-pipe-fd 108 --max-threads 10 --max-queued-requests 10
>├─23421 /usr/libexec/ioprocess --read-pipe-fd 44
> --write-pipe-fd 43 --max-threads 10 --max-queued-requests 10
>├─23432 /usr/libexec/ioprocess --read-pipe-fd 52
> --write-pipe-fd 51 --max-threads 10 --max-queued-requests 10
>├─23440 /usr/libexec/ioprocess --read-pipe-fd 59
> --write-pipe-fd 57 --max-threads 10 --max-queued-requests 10
>├─23448 /usr/libexec/ioprocess --read-pipe-fd 71
> --write-pipe-fd 69 --max-threads 10 --max-queued-requests 10
>├─23457 /usr/libexec/ioprocess --read-pipe-fd 85
> --write-pipe-fd 83 --max-threads 10 --max-queued-requests 10
>└─23629 /usr/libexec/ioprocess --read-pipe-fd 117
> --write-pipe-fd 116 --max-threads 10 --max-queued-requests 10
>
> Oct 12 00:15:44 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:15:46 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:15:49 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:15:51 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:16:03 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:16:07 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:16:07 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:16:10 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:16:12 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
> Oct 12 00:16:14 ovirt01.mydomain vdsm[19421]: vdsm vds.dispatcher ERROR
> SSL error during reading data: unexpected eof
>
>
> It seems that the "unexpected eof" errors I see in vdsm.log are always
> after an RPC call that apparently completes ok, such as
>
> jsonrpc.Executor/1::INFO::2016-10-12 00:16:38,513::__init__::513::
> jsonrpc.JsonRpcServer::(_serveRequest) RPC call Host.getHardwareInfo
> succeeded in 0.00 seconds
> JsonRpc (StompReactor)::ERROR::2016-10-12 
> 00:16:38,514::betterAsyncore::113::vds.dispatcher::(recv)
> SSL error during reading data: unexpected eof
> Reactor thread::INFO::2016-10-12 00:16:38,734::protocoldetector::72::
> ProtocolDetector.AcceptorImpl::(handle_accept) Accepting connection from
> 127.0.0.1:59686
>
> or
>
> jsonrpc.Executor/7::INFO::2016-10-12 00:16:36,277::__init__::513::
> jsonrpc.JsonRpcServer::(_serveRequest) RPC call Volume.getInfo succeeded
> in 0.00 seconds
> JsonRpc (StompReactor)::ERROR::2016-10-12 
> 00:16:36,283::betterAsyncore::113::vds.dispatcher::(recv)
> SSL error during reading data: unexpected eof
> Reactor thread::INFO::2016-10-12 00:16:36,298::protocoldetector::72::
> ProtocolDetector.AcceptorImpl::(handle_accept) Accepting connection from
> 127.0.0.1:59676
>
> Thanks,
>
> Gianluca
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-09 Thread Piotr Kliczewski
Gianluca,

In the log provided I only see plenty of:

2016-10-07 23:24:43,159 ERROR
[org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
Query 'GetUserProfileQuery' failed: PreparedStatementCallback; bad SQL
grammar [select * from  getuserprofilebyuserid(?)]; nested exception
is org.postgresql.util.PSQLException: The column name
user_portal_vm_auto_login was not found in this ResultSet.
2016-10-07 23:24:43,159 ERROR
[org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
Exception: org.springframework.jdbc.BadSqlGrammarException:
PreparedStatementCallback; bad SQL grammar [select * from
getuserprofilebyuserid(?)]; nested exception is
org.postgresql.util.PSQLException: The column name
user_portal_vm_auto_login was not found in this ResultSet.

This could be not related but I do not see any other exception in there.

@Eli can you please take a look?

Thanks,
Piotr

On Fri, Oct 7, 2016 at 11:28 PM, Gianluca Cecchi
<gianluca.cec...@gmail.com> wrote:
>
> On Fri, Oct 7, 2016 at 10:14 PM, Piotr Kliczewski <pklic...@redhat.com>
> wrote:
>>
>> Gianluca,
>>
>> Please share the engine log. We shoukd find more info about the issue
>> there.
>>
>> Thanks,
>> Piotr
>>
>>
>
> here it is
> https://drive.google.com/file/d/0BwoPbcrMv8mvQlVwVDlGTVEtR00/view?usp=sharing
>
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-10-07 Thread Piotr Kliczewski
Gianluca,

Please share the engine log. We shoukd find more info about the issue there.

Thanks,
Piotr

7 paź 2016 20:09 "Gianluca Cecchi"  napisał(a):

>
> On Mon, Jul 25, 2016 at 12:07 PM, Nir Soffer  wrote:
>
>>
>>
>> This log is not very useful as is, we must show the relevant remote
>> address.
>>
>> Should be improved in
>> https://gerrit.ovirt.org/61303
>>
>> Can you try this patch and share the log?
>>
>
> Hello,
> I take on this as I have the same problem.
> I'm in 4.0.3 and it seems that the gerrit above was not inside.
> So I applied and restarted vdsmd.
>
> Now I have
> Oct 07 19:54:10 ovirt01.lutwyn.org vdsm[11306]: vdsm vds.dispatcher ERROR
> SSL error receiving from  192.168.1.211:36296 at 0x359c5f0>: unexpected eof
>
> In my case single host environment with Self Hosted Engine
> Ip of host is 192.168.1.211
> Ip of engine is 192.168.1.212
>
> Let me know if you need full logs and which ones.
>
> in the mean time 1000 line around in vdsm.log here:
> https://drive.google.com/file/d/0BwoPbcrMv8mvTk9SYTF0UDZUMUU/
> view?usp=sharing
>
> Thanks,
> Gianluca
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Vds time out occured

2016-08-30 Thread Piotr Kliczewski
Looking at the logs I see that some calls timeout due to reconnect because
other calls timeout before.
This behavior seems to create a loop. I do not see original issue in the
logs.

Is it possible that you could send logs from the time it started to occur?

As workaround you could restart the engine which should break the loop but
this won't fix the issue
which caused it.

Thanks,
Piotr

On Tue, Aug 30, 2016 at 9:25 AM, Piotr Kliczewski <pklic...@redhat.com>
wrote:

> Please make sure that we can access the logs.
>
> On Tue, Aug 30, 2016 at 9:23 AM, knarra <kna...@redhat.com> wrote:
>
>> On 08/30/2016 12:36 PM, Nir Soffer wrote:
>>
>> On Tue, Aug 30, 2016 at 9:20 AM, knarra <kna...@redhat.com> wrote:
>>
>>> On 08/30/2016 11:47 AM, knarra wrote:
>>>
>>>> Hi,
>>>>
>>>> I have installed the latest bits of ovirt and i see that my events
>>>> tab in the UI is flodded with the following error messages for all the
>>>> hosts in the cluster. Can some help me understand why are these ?
>>>>
>>>> VDSM  command failed: Message timeout which can be caused by
>>>> communication issues
>>>>
>>>> VDSM command failed: Vds timeout occured
>>>>
>>>> Thanks
>>>>
>>>> kasturi
>>>>
>>>> ___
>>>> Users mailing list
>>>> Users@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>
>>> I am monitoring some vms and i see there are warnings related to these
>>> saying "Vm not responding" though my vms are up and running fine.
>>
>>
>> We will need engine and vdsm logs to check this.
>>
>> Nir
>>
>> Hi Nir,
>>
>> I have uploaded the logs to google drive and shared it with you.
>> Below is the link
>>
>> https://drive.google.com/drive/u/0/folders/0B1PSZZ4Ki3DnWTdsazZwUWhfdWc
>>
>> Thanks
>>
>> kasturi
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Vds time out occured

2016-08-30 Thread Piotr Kliczewski
Please make sure that we can access the logs.

On Tue, Aug 30, 2016 at 9:23 AM, knarra  wrote:

> On 08/30/2016 12:36 PM, Nir Soffer wrote:
>
> On Tue, Aug 30, 2016 at 9:20 AM, knarra  wrote:
>
>> On 08/30/2016 11:47 AM, knarra wrote:
>>
>>> Hi,
>>>
>>> I have installed the latest bits of ovirt and i see that my events
>>> tab in the UI is flodded with the following error messages for all the
>>> hosts in the cluster. Can some help me understand why are these ?
>>>
>>> VDSM  command failed: Message timeout which can be caused by
>>> communication issues
>>>
>>> VDSM command failed: Vds timeout occured
>>>
>>> Thanks
>>>
>>> kasturi
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>> I am monitoring some vms and i see there are warnings related to these
>> saying "Vm not responding" though my vms are up and running fine.
>
>
> We will need engine and vdsm logs to check this.
>
> Nir
>
> Hi Nir,
>
> I have uploaded the logs to google drive and shared it with you.
> Below is the link
>
> https://drive.google.com/drive/u/0/folders/0B1PSZZ4Ki3DnWTdsazZwUWhfdWc
>
> Thanks
>
> kasturi
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt 4.0 installation

2016-08-17 Thread Piotr Kliczewski
On Wed, Aug 17, 2016 at 1:35 PM, knarra  wrote:

> On 08/17/2016 04:57 PM, Nir Soffer wrote:
>
>> On Wed, Aug 17, 2016 at 10:16 AM, knarra  wrote:
>>
>>> Hi,
>>>
>>>I see the below error  logged in vdsm.log file . can some one help me
>>> understand what this error is and do we have any bug for this error?
>>>
>>>
This is not a failure. This line is logged when client closes the
connection.
I can happen at anytime and from vdsm perspective the closure occurred
during reading data.

Please check the engine logs to understand who the connection was closed.


>   JsonRpc (StompReactor)::ERROR::2016-08-17
>>> 12:32:05,348::betterAsyncore::113::vds.dispatcher::(recv) SSL error
>>> during
>>> reading data: unexpected eof
>>>
>> This means the client disconnected in unclean way, Is this a hosted engine
>> setup?
>>
>> Nir
>>
>
> yes, this is  a hosted engine setup.
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Some question about vdsm rpc

2016-07-27 Thread Piotr Kliczewski
On Tue, Jul 26, 2016 at 12:46 PM, lifuqiong  wrote:
> 1.   We know that xmlrpc and jsonrpc are enabled default in vdsm, vdsm
> supply these two service in one port or two? What’s the port number and how
> we can change it?
>

We use single port for both protocols. There is a code which peeks the
data stream and
decides which part of the code should handle the connection.

In config.py you can find 'management_port' option which defines which
port will be used.

>
>
> 2.   How can we know a vdsm host can supply an xmlrpc service or a
> jsonrpc service?
>

In config.py we have 'xmlrpc_enable' and 'jsonrpc_enable' which
determine protocols
available during runtime. With the latest vdsm both are enabled but
keep in mind that
xmlrpc is deprecated and will be removed soon.

>
>
> 3.   I found that while ovirt engine installing a vdsm host, engine will
> check whether we are connecting to vdsm which supports xmlrpc only, engine
> send a ‘Host.ping’ jsonrpc request,  why the code will enter into
> bindingxmlrpc.py?
>
> Did both jsonrpc and xmlrpc will call bindingxmlrpc.py?
>

During host installation we attempt to connect to a host using jsonrpc first and
if it fails we we attempt to use xmlrpc. Older vdsms provide only xmlrpc so
this behavior is for backward compatibility.

There are two binding modules bindingjsonrpc.py and bindingxmlrpc.py.
Common module for both bindings is API.py

>
>
> 4.   Then, I just get an json return with code = 0 or code = 99. What
> does these error code mean ? I can’t find detail in rpcjson
> Specification(http://www.jsonrpc.org/specification)
>

There is a time when vdsm is not able to handle requests due to recovery logic
which may take several seconds during this time we return code 99. Once the
recovery is done vdsm returns correct codes like 0.

Recovery occurs only during start of vdsm.

>
>
> 5.   When installing vdsm, I got an “Host server117 installation failed.
> Host is not reachable” error. Debugging code as follows:
>
> Bindingxmlrpc.py
>
> line637  def ping(self):
>
> line638   # print 'os.getuid()',os.getuid() = 0
>
> line639   # print 'os.getegit()',os.getegid() =0
>
> line640api = API.Global()
>
> line641return api.ping()
>

Can you share the logs with above failure?

>
>
> the api.ping() just open an file and update the file updating time, why
> these will throw an error code 0 or 99? And I see the ping() function
> created file /var/run/vdsm/client.log already exists in os,
>

ping verb was reused to detect whether vdsm is able to use jsonrpc.
This verb originally is used to make sure that any network reconfiguration
did not break connection to the engine. During the process of reconfiguration
engine call ping and vdsm based on file update time can restore old network
configuration in case of failure.

> the only difference is the file is owned by root:root , not the vdsm:kvm?
> Why?
>

There are 2 vdsm processes running with different user permissions.

>
>
> Thank you.
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm ssl errors

2016-07-26 Thread Piotr Kliczewski
Christoph,

Please apply [1] we would know exactly what verbs were called by this local
client.

Thanks,
Piotr

[1] https://gerrit.ovirt.org/#/c/61367/

On Mon, Jul 25, 2016 at 9:50 PM, Piotr Kliczewski <
piotr.kliczew...@gmail.com> wrote:

> On Mon, Jul 25, 2016 at 6:18 PM, Nir Soffer <nsof...@redhat.com> wrote:
> > On Mon, Jul 25, 2016 at 6:22 PM, C. Handel <ov...@macht-blau.org> wrote:
> >> two nodes (x.x.138.208, x.x.138.210), hosted-engine on x.x.139.240.
> >>
> >> the vdsm logs are from x.x.138.208 and the connection is from the node
> >> itself.
> >>
> >>> Running tcpdump it is a connect from the node to itself. I can't figure
> >>> out what is wrong. Can someone ?> give me a hint?
> >>
> >> so i know they are coming from the node itself. The process connecting
> is
> >> terminating too fast. the moment i see it in tcpdump, it is gone from
> the
> >> process table.
> >
> > I think this is ovirt hosted agent - check its logs, you will probably
> find that
> > it make some request in the same time you see the errors in your logs.
> >
> > Adding Martin, maintaining this project.
> >
> > These are the interesting events in the logs:
> >
> > $ grep 37678 vdsm.log
> > JsonRpc (StompReactor)::ERROR::2016-07-25
> > 13:48:58,074::betterAsyncore::113::vds.dispatcher::(recv) SSL error
> > during reading data from  > connected (':::140.181.138.208', 37678, 0, 0) at 0x42c9b90>:
> > unexpected eof
> >
> > $ grep 37684 vdsm.log
> > Reactor thread::INFO::2016-07-25
> >
> 13:49:00,205::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
> > Accepting connection from :::140.181.138.208:37684
> > Reactor thread::INFO::2016-07-25
> >
> 13:49:00,211::protocoldetector::121::ProtocolDetector.Detector::(handle_read)
> > Detected protocol stomp from :::140.181.138.208:37684
> > Reactor thread::DEBUG::2016-07-25
> >
> 13:49:00,211::stompreactor::492::protocoldetector.StompDetector::(handle_socket)
> > Stomp detected from (':::140.181.138.208', 37684)
> > JsonRpc (StompReactor)::ERROR::2016-07-25
> > 13:49:01,824::betterAsyncore::113::vds.dispatcher::(recv) SSL error
> > during reading data from  > connected (':::140.181.138.208', 37684, 0, 0) at 0x42b0758>:
> > unexpected eof
> >
> > The log is too small, we see only one full request.
> >
> > Pitor, can you understand from this log what the request coming from
> > :::140.181.138.208:37684
> > is doing?
> >
>
> I stated above there are 2 verbs that were called each time:
>
>  Host.getStats and Host.getHardwareInfo
>
> >>
> >> Greetings
> >>Christoph
> >>
> >> On Mon, Jul 25, 2016 at 4:53 PM, Piotr Kliczewski
> >> <piotr.kliczew...@gmail.com> wrote:
> >>>
> >>> Christoph,
> >>>
> >>> In log snippets you provided I can see 2 occurrences of the log entry.
> >>> There is 3 seconds between the calls.
> >>>
> >>> Each time I see calls to Host.getStats and Host.getHardwareInfo both
> >>> from x.x.138.208.
> >>> I do not see any log entries in the engine log so it not engine who
> >>> connected.
> >>>
> >>> What host is it?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>>
> >>> On Mon, Jul 25, 2016 at 3:45 PM, C. Handel <ov...@macht-blau.org>
> wrote:
> >>> > patch applied, The connection is from the node itself.
> >>> >
> >>> > logfiles with the last 100k (hope this is enough, the error happens
> >>> > every
> >>> > few seconds) of data attached.
> >>> >
> >>> > Greetings
> >>> >   Christoph
> >>> >
> >>> > On Mon, Jul 25, 2016 at 12:07 PM, Nir Soffer <nsof...@redhat.com>
> wrote:
> >>> >>
> >>> >> On Thu, Jul 21, 2016 at 10:00 AM, C. Handel <ov...@macht-blau.org>
> >>> >> wrote:
> >>> >> > longer logs attached, excerpts:
> >>> >> >
> >>> >> > ---+ vdsm
> >>> >> >
> >>> >> > Reactor thread::INFO::2016-07-21
> >>> >> >
> >>> >> >
> >>> >> >
> 08:01:19,544::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
> >>> >> > Accepting connection from :::140

Re: [ovirt-users] vdsm ssl errors

2016-07-25 Thread Piotr Kliczewski
On Mon, Jul 25, 2016 at 6:18 PM, Nir Soffer <nsof...@redhat.com> wrote:
> On Mon, Jul 25, 2016 at 6:22 PM, C. Handel <ov...@macht-blau.org> wrote:
>> two nodes (x.x.138.208, x.x.138.210), hosted-engine on x.x.139.240.
>>
>> the vdsm logs are from x.x.138.208 and the connection is from the node
>> itself.
>>
>>> Running tcpdump it is a connect from the node to itself. I can't figure
>>> out what is wrong. Can someone ?> give me a hint?
>>
>> so i know they are coming from the node itself. The process connecting is
>> terminating too fast. the moment i see it in tcpdump, it is gone from the
>> process table.
>
> I think this is ovirt hosted agent - check its logs, you will probably find 
> that
> it make some request in the same time you see the errors in your logs.
>
> Adding Martin, maintaining this project.
>
> These are the interesting events in the logs:
>
> $ grep 37678 vdsm.log
> JsonRpc (StompReactor)::ERROR::2016-07-25
> 13:48:58,074::betterAsyncore::113::vds.dispatcher::(recv) SSL error
> during reading data from  connected (':::140.181.138.208', 37678, 0, 0) at 0x42c9b90>:
> unexpected eof
>
> $ grep 37684 vdsm.log
> Reactor thread::INFO::2016-07-25
> 13:49:00,205::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
> Accepting connection from :::140.181.138.208:37684
> Reactor thread::INFO::2016-07-25
> 13:49:00,211::protocoldetector::121::ProtocolDetector.Detector::(handle_read)
> Detected protocol stomp from :::140.181.138.208:37684
> Reactor thread::DEBUG::2016-07-25
> 13:49:00,211::stompreactor::492::protocoldetector.StompDetector::(handle_socket)
> Stomp detected from (':::140.181.138.208', 37684)
> JsonRpc (StompReactor)::ERROR::2016-07-25
> 13:49:01,824::betterAsyncore::113::vds.dispatcher::(recv) SSL error
> during reading data from  connected (':::140.181.138.208', 37684, 0, 0) at 0x42b0758>:
> unexpected eof
>
> The log is too small, we see only one full request.
>
> Pitor, can you understand from this log what the request coming from
> :::140.181.138.208:37684
> is doing?
>

I stated above there are 2 verbs that were called each time:

 Host.getStats and Host.getHardwareInfo

>>
>> Greetings
>>Christoph
>>
>> On Mon, Jul 25, 2016 at 4:53 PM, Piotr Kliczewski
>> <piotr.kliczew...@gmail.com> wrote:
>>>
>>> Christoph,
>>>
>>> In log snippets you provided I can see 2 occurrences of the log entry.
>>> There is 3 seconds between the calls.
>>>
>>> Each time I see calls to Host.getStats and Host.getHardwareInfo both
>>> from x.x.138.208.
>>> I do not see any log entries in the engine log so it not engine who
>>> connected.
>>>
>>> What host is it?
>>>
>>> Thanks,
>>> Piotr
>>>
>>>
>>> On Mon, Jul 25, 2016 at 3:45 PM, C. Handel <ov...@macht-blau.org> wrote:
>>> > patch applied, The connection is from the node itself.
>>> >
>>> > logfiles with the last 100k (hope this is enough, the error happens
>>> > every
>>> > few seconds) of data attached.
>>> >
>>> > Greetings
>>> >   Christoph
>>> >
>>> > On Mon, Jul 25, 2016 at 12:07 PM, Nir Soffer <nsof...@redhat.com> wrote:
>>> >>
>>> >> On Thu, Jul 21, 2016 at 10:00 AM, C. Handel <ov...@macht-blau.org>
>>> >> wrote:
>>> >> > longer logs attached, excerpts:
>>> >> >
>>> >> > ---+ vdsm
>>> >> >
>>> >> > Reactor thread::INFO::2016-07-21
>>> >> >
>>> >> >
>>> >> > 08:01:19,544::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
>>> >> > Accepting connection from :::140.181.138.208:59502
>>> >> > Reactor thread::DEBUG::2016-07-21
>>> >> >
>>> >> >
>>> >> > 08:01:19,551::protocoldetector::85::ProtocolDetector.Detector::(__init__)
>>> >> > Using required_size=11
>>> >> > Reactor thread::INFO::2016-07-21
>>> >> >
>>> >> >
>>> >> > 08:01:19,553::protocoldetector::121::ProtocolDetector.Detector::(handle_read)
>>> >> > Detected protocol stomp from :::140.181.138.208:59502
>>> >> > Reactor thread::INFO::2016-07-21
>>> >> > 08:01:19,553::stompreactor::101::Broker.StompAdapter::(_cm

Re: [ovirt-users] vdsm ssl errors

2016-07-25 Thread Piotr Kliczewski
Christoph,

In log snippets you provided I can see 2 occurrences of the log entry.
There is 3 seconds between the calls.

Each time I see calls to Host.getStats and Host.getHardwareInfo both
from x.x.138.208.
I do not see any log entries in the engine log so it not engine who connected.

What host is it?

Thanks,
Piotr


On Mon, Jul 25, 2016 at 3:45 PM, C. Handel  wrote:
> patch applied, The connection is from the node itself.
>
> logfiles with the last 100k (hope this is enough, the error happens every
> few seconds) of data attached.
>
> Greetings
>   Christoph
>
> On Mon, Jul 25, 2016 at 12:07 PM, Nir Soffer  wrote:
>>
>> On Thu, Jul 21, 2016 at 10:00 AM, C. Handel  wrote:
>> > longer logs attached, excerpts:
>> >
>> > ---+ vdsm
>> >
>> > Reactor thread::INFO::2016-07-21
>> >
>> > 08:01:19,544::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
>> > Accepting connection from :::140.181.138.208:59502
>> > Reactor thread::DEBUG::2016-07-21
>> >
>> > 08:01:19,551::protocoldetector::85::ProtocolDetector.Detector::(__init__)
>> > Using required_size=11
>> > Reactor thread::INFO::2016-07-21
>> >
>> > 08:01:19,553::protocoldetector::121::ProtocolDetector.Detector::(handle_read)
>> > Detected protocol stomp from :::140.181.138.208:59502
>> > Reactor thread::INFO::2016-07-21
>> > 08:01:19,553::stompreactor::101::Broker.StompAdapter::(_cmd_connect)
>> > Processing CONNECT request
>> > Reactor thread::DEBUG::2016-07-21
>> >
>> > 08:01:19,554::stompreactor::492::protocoldetector.StompDetector::(handle_socket)
>> > Stomp detected from (':::140.181.138.208', 59502)
>> > JsonRpc (StompReactor)::INFO::2016-07-21
>> > 08:01:19,554::stompreactor::128::Broker.StompAdapter::(_cmd_subscribe)
>> > Subscribe command received
>> > ...
>> >
>> > JsonRpc (StompReactor)::ERROR::2016-07-21
>> > 08:01:21,411::betterAsyncore::113::vds.dispatcher::(recv) SSL error
>> > during
>> > reading data: unexpected eof
>>
>> This log is not very useful as is, we must show the relevant remote
>> address.
>>
>> Should be improved in
>> https://gerrit.ovirt.org/61303
>>
>> Can you try this patch and share the log?
>>
>> >
>> >
>> > ---+ engine
>> >
>> >
>> > 2016-07-20 08:00:48,445 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler1) [1cff1b56] Fetched 7 VMs from VDS
>> > 'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
>> > 2016-07-20 08:01:03,460 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler3) [78d8aa89] Fetched 0 VMs from VDS
>> > '6f7a9201-e753-4875-b89d-024120067687'
>> > 2016-07-20 08:01:03,473 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler2) [71a27a96] Fetched 7 VMs from VDS
>> > 'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
>> > 2016-07-20 08:01:18,488 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler2) [71a27a96] Fetched 0 VMs from VDS
>> > '6f7a9201-e753-4875-b89d-024120067687'
>> > 2016-07-20 08:01:18,500 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler9) [47c419da] Fetched 7 VMs from VDS
>> > 'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
>> > 2016-07-20 08:01:33,514 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler8) [735789] Fetched 0 VMs from VDS
>> > '6f7a9201-e753-4875-b89d-024120067687'
>> > 2016-07-20 08:01:33,527 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler3) [78d8aa89] Fetched 7 VMs from VDS
>> > 'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
>> > 2016-07-20 08:01:48,543 INFO
>> > [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
>> > (DefaultQuartzScheduler8) [735789] Fetched 0 VMs from VDS
>> > '6f7a9201-e753-4875-b89d-024120067687'
>> >
>> >
>> > Greetings
>> >Christoph
>> >
>> > On Thu, Jul 21, 2016 at 8:47 AM, Yaniv Kaul  wrote:
>> >>
>> >> Can you share engine and VDSM logs please?
>> >> TIA,
>> >> Y.
>> >>
>> >> On Thu, Jul 21, 2016 at 9:22 AM, C. Handel 
>> >> wrote:
>> >>>
>> >>> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
>> >>> storage backend.
>> >>>
>> >>> For some reason the vdsmd on the nodes is logging an error every few
>> >>> seconds:
>> >>>
>> >>>
>> >>> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected
>> >>> eof
>> >>>
>> >>>
>> >>> Running tcpdump it is a connect from the node to itself. I can't
>> >>> figure
>> >>> out what is wrong. Can someone give me a hint?
>> >>>
>> >>> Greetings
>> >>>Christoph
>> >>>
>> >>> ___
>> >>> Users mailing list
>> >>> Users@ovirt.org
>> >>> http://lists.ovirt.org/mailman/listinfo/users
>> >>>
>> >>
>> >
>> >
>> > ___
>> > Users 

Re: [ovirt-users] stuck host in hosted engine migration 3.6->4.0

2016-07-25 Thread Piotr Kliczewski
Gervais,

I checked the logs and I see:

jsonrpc.Executor/1::ERROR::2016-07-19
16:19:10,283::task::868::Storage.TaskManager.Task::(_setError)
Task=`b27c8bbd-ca35-44ca-97ae-88c4e91f6eec`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 875, in _run
return fn(*args, **kargs)
  File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper
res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 2700, in getStorageDomainInfo
dom = self.validateSdUUID(sdUUID)
  File "/usr/share/vdsm/storage/hsm.py", line 285, in validateSdUUID
sdDom.validate()
  File "/usr/share/vdsm/storage/fileSD.py", line 485, in validate
raise se.StorageDomainAccessError(self.sdUUID)
StorageDomainAccessError: Domain is either partially accessible or
entirely inaccessible: (u'248f46f0-d793-4581-9810-c9d965e2f286',)

Thread-21821::ERROR::2016-07-19
16:19:14,348::api::195::root::(_getHaInfo) failed to retrieve Hosted
Engine HA info
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 174,
in _getHaInfo
stats = instance.get_all_stats()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 103, in get_all_stats
self._configure_broker_conn(broker)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 180, in _configure_broker_conn
dom_type=dom_type)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 176, in set_storage_domain
.format(sd_type, options, e))
RequestError: Failed to set storage domain FilesystemBackend, options
{'dom_type': 'nfs3', 'sd_uuid':
'248f46f0-d793-4581-9810-c9d965e2f286'}: Request failed: 


after couple of above issues vdsm was restarted and 'Connection reset
by peer' started to occur. In between connect reset I can see:

Thread-76::ERROR::2016-07-19
16:21:25,024::api::195::root::(_getHaInfo) failed to retrieve Hosted
Engine HA info
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 174,
in _getHaInfo
stats = instance.get_all_stats()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 102, in get_all_stats
with broker.connection(self._retries, self._wait):
  File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 99, in connection
self.connect(retries, wait)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 78, in connect
raise BrokerConnectionError(error_msg)
BrokerConnectionError: Failed to connect to broker, the number of
errors has exceeded the limit (1)

and

Thread-315::ERROR::2016-07-19
16:26:58,541::vm::765::virt.vm::(_startUnderlyingVm)
vmId=`4013c829-c9d7-4b72-90d5-6fe58137504c`::The vm start process
failed
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 706, in _startUnderlyingVm
self._run()
  File "/usr/share/vdsm/virt/vm.py", line 1995, in _run
self._connection.createXML(domxml, flags),
  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
line 123, in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 916, in wrapper
return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3611, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: resource busy: Failed to acquire lock: error -243

and

Thread-6834::ERROR::2016-07-20
17:18:10,030::task::868::Storage.TaskManager.Task::(_setError)
Task=`f6d8d5df-a55f-4ccb-af11-f1b44b9757d0`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 875, in _run
return fn(*args, **kargs)
  File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper
res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 3473, in stopMonitoringDomain
raise se.StorageDomainIsMemberOfPool(sdUUID)
StorageDomainIsMemberOfPool: Storage domain is member of pool:
'domain=248f46f0-d793-4581-9810-c9d965e2f286'

In the logs I can see that vdsm was restarted on 2016-07-21
14:55:03,607 and any issues stopped occurring.

Was there any hardware (storage) issue?

I can see from your previous email that the issues started to occur
again on 2016-07-22.
Do you see any errors like those above?

Thanks,
Piotr

On Fri, Jul 22, 2016 at 3:05 PM, Gervais de Montbrun
 wrote:
> Hi Simone,
>
> I did have the issue you link to below when doing a `hosted-engine --deploy`
> on this server when I was setting it up to run 3.6. I've commented on the
> bug with my experiences. I did get the host working in 3.6 and there were no
> errors, but this one has cropped up since upgrading to 4.0.1.
>
> I 

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-25 Thread Piotr Kliczewski
I remember an issue that engine upgrade corrupted certificates and
"General SSLEngine problem" may be indication that you saw it.
I asked to open BZ for it but was unable to find it.

@Sandro @Simone was it fixed already?

On Thu, Jul 21, 2016 at 3:18 PM, Martin Perina  wrote:
> Thanks a lot for you effort, I'm glad that you were able to upgrade
> successfully although we were not able to find the cause for the issue :-(
>
> On Thu, Jul 21, 2016 at 2:30 PM,  wrote:
>>
>> So I gave it another try and this time it worked without any issue (with
>> 4.0.1.1 version). Strange, maybe the first upgrade failure left system in a
>> weird state? Anyhow almost everything ([1]) is working fine now. Thanks for
>> the help!
>>
>>   [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1358737
>
>
> Adding Tomas about this one
>
>>
>>
>> El 2016-07-20 20:23, Martin Perina escribió:
>>>
>>> On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:
>>>
 El 20/07/16 a las 16:45, Martin Perina escribió:

 On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:

 Hi Martin,

 Actually, up until now we had that cert configured in httpd and in
 websocket proxy. Seems that now in 4.0.x it's not enough, as opening
 the https://fqdn [1] complains about the cert not being imported in
 the key chain.

 Yes, there's an updated procedure on using external CA in 4.0,
 for details please take a look at Doc Text in

 https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]

 So I imported it via keytool, but I don't want to use it in the
 engine <-> VDSM communication.

 Hmm, so that would imply that we have some issue with existing
 internal enigne CA during upgrade ...

 The strange thing is that we test upgrades a lot but so far we
 haven't seen any issues which will broke

 SSL setup between engine and VDSM. You said that you had to
 downgrade back to 3.6.7 (so unfortunately for us we cannot
 investigate your nonworking setup more), but how did you do that?

 Removing all engine packages and configuration, installing back
 3.6.7 packaging and restoring configuration form backup?

 I'm asking to know what changed in your setup between not working
 4.0 and working 3.6.7 ...
>>>
>>>
>>>  Indeed, those are the steps I followed to the point.
>>>
>>>  To add more strangeness, previously to upgrading this oVirt
>>> infrastructure, we upgraded another one that we have (also using own
>>> cert, a different one but from the same CA) and everything went
>>> smoothly. And what's more, previously to upgrading the engine that
>>> failed, I created a copy of that engine machine in a sandbox
>>> environment to see if upgrade process would or not success, and it
>>> worked perfectly.
>>>
>>>  The only difference between the sandbox and the real machine's
>>> process was that when upgrading the real one, the first time I run
>>> "engine-setup" it failed because 'systemd' reported PostgreSQL as it
>>> was not running (actually it was, thougg), so everything rolled back.
>>> I had to kill the PostgreSQL process, start it again with systemctl
>>> and then run "engine-setup", where the process completed successfully
>>> but the SSL issue appeared. Not sure if this rollback could have
>>> shattered the whole thing...
>>>
>>>  Anyhow, tomorrow I'm going to create another copy of the engine
>>> machine to a sandbox environment and try again. If it works I'll cross
>>> my fingers and give another try on the real machine...
>>>
>>>  Thanks!
>>>
>>> Thanks a lot for you effort. I will try to perform same upgrade
>>> tomorrow in my test env.
>>>
>>>
 Thanks

 Martin

 Thanks!
 En 20/7/2016 2:48 p. m., Martin Perina 
 escribió:

 Hi,

 sorry for late response, I overlook your reply :-(

 I looked at your logs and it seems to me that there's SSL
 error when engine tries to contact VDSM.

 You have mentioned that your are using your own custom CA. Are
 you using it only for HTTPS certificate or do you want to use it
 also for Engine <-> VDSM communication?


 Martin Perina



 On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
 Any hints about this?

 El 2016-07-13 11:13, nico...@devels.es escribió:
 Hi,

 Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
 Actually, the error changed to 'General SSLEngine problem', but the
 result was the same, like this:

 2016-07-13 09:52:22,010 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
 Reactor) [] Connecting to /10.X.X.X
 2016-07-13 09:52:22,018 ERROR
 [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
 Reactor)
 [] Unable to process messages: General SSLEngine problem

 It's worth mentioning 

Re: [ovirt-users] vdsm ssl errors

2016-07-25 Thread Piotr Kliczewski
Based on the pieces of the logs that you provided it is hard to tell
what was the reason of a connection being closed.

This message is logged when python ssl library we use was reading the
data from the connection and it was closed by
the other side (engine). It is expected message in those situations.

Please provide more complete engine logs so we know why the connection
was closed.

On Thu, Jul 21, 2016 at 9:31 AM, C. Handel  wrote:
> all nodes and engines are synced to the same timeserver.
>
> as far as i can tell, the connection is from the node itself, to the vdsm on
> the node, so no time difference can occur.
>
> the certificate that get's presented be vdsm on port 54321 looks ok.
>
> For what it is worth, I changed the certificate of the hosted-engine web
> interface by reconfiguring apaches mod_ssl, not touching any certificate in
> hosted-engine:/etc/pki/ovirt-*
>
> On Thu, Jul 21, 2016 at 9:22 AM, Швыгин Алексей Михайлович
>  wrote:
>>
>> Check time/ntp settings on nodes and engine.
>>
>>
>>
>> --
>>
>> a.shvy...@grfc.ru
>>
>>
>>
>> From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf
>> Of C. Handel
>> Sent: Thursday, July 21, 2016 10:03 AM
>> To: Oved Ourfali
>> Cc: users
>> Subject: Re: [ovirt-users] vdsm ssl errors
>>
>>
>>
>> as far as i can tell, everything is fine.
>>
>>
>>
>> VMs are running, i can migrate them, they are restarted on crash, etc.
>>
>>
>>
>> No events in the dashboard, performance data is available.
>>
>>
>>
>> Greetings
>>
>>Christoph
>>
>>
>>
>> On Thu, Jul 21, 2016 at 8:59 AM, Oved Ourfali  wrote:
>>
>> Other than errors, anything that doesn't work on your environment?
>>
>> On Jul 21, 2016 09:48, "Yaniv Kaul"  wrote:
>>
>> Can you share engine and VDSM logs please?
>>
>> TIA,
>>
>> Y.
>>
>>
>>
>> On Thu, Jul 21, 2016 at 9:22 AM, C. Handel  wrote:
>>
>> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
>> storage backend.
>>
>>
>>
>> For some reason the vdsmd on the nodes is logging an error every few
>> seconds:
>>
>>
>>
>>
>>
>> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
>>
>>
>>
>>
>>
>> Running tcpdump it is a connect from the node to itself. I can't figure
>> out what is wrong. Can someone give me a hint?
>>
>>
>>
>> Greetings
>>
>>Christoph
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 4 Hosted Engine deploy on fc storage - [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 101] Network is unreachable

2016-07-25 Thread Piotr Kliczewski
This could be the issue here as well as for BZ #1358530

On Mon, Jul 25, 2016 at 10:53 AM,   wrote:
> Could this be due to the fact that the ovirt installer has changed network 
> configuration files (ifcfg-*, resolv.conf) ?
> After the error in ovirt installation process I see from resolv.conf 
> disappeared on my DNS servers entry and now the server is unable to resolve 
> names.
>
> 25.07.2016, 11:26, "Simone Tiraboschi" :
>> On Mon, Jul 25, 2016 at 10:22 AM,  wrote:
>>>  # vdsClient -s 0 getVdsCaps
>>>
>>>  Traceback (most recent call last):
>>>File "/usr/share/vdsm/vdsClient.py", line 2980, in 
>>>  code, message = commands[command][0](commandArgs)
>>>File "/usr/share/vdsm/vdsClient.py", line 543, in do_getCap
>>>  return self.ExecAndExit(self.s.getVdsCapabilities())
>>>File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__
>>>  return self.__send(self.__name, args)
>>>File "/usr/lib64/python2.7/xmlrpclib.py", line 1587, in __request
>>>  verbose=self.__verbose
>>>File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request
>>>  return self.single_request(host, handler, request_body, verbose)
>>>File "/usr/lib64/python2.7/xmlrpclib.py", line 1301, in single_request
>>>  self.send_content(h, request_body)
>>>File "/usr/lib64/python2.7/xmlrpclib.py", line 1448, in send_content
>>>  connection.endheaders(request_body)
>>>File "/usr/lib64/python2.7/httplib.py", line 975, in endheaders
>>>  self._send_output(message_body)
>>>File "/usr/lib64/python2.7/httplib.py", line 835, in _send_output
>>>  self.send(msg)
>>>File "/usr/lib64/python2.7/httplib.py", line 797, in send
>>>  self.connect()
>>>File "/usr/lib/python2.7/site-packages/vdsm/m2cutils.py", line 203, in 
>>> connect
>>>  sock = socket.create_connection((self.host, self.port), self.timeout)
>>>File "/usr/lib64/python2.7/socket.py", line 571, in create_connection
>>>  raise err
>>>  error: [Errno 101] Network is unreachable
>>
>> Yaniv, can you please take also a look to this one?
>> it's exactly the opposite of https://bugzilla.redhat.com/1358530
>> Here the jsonrpcclient works but not the xmlrpc one.
>>
>>>  25.07.2016, 11:17, "Simone Tiraboschi" :
  On Mon, Jul 25, 2016 at 7:51 AM,  wrote:
>   Simone, there is something interesting in the vdsm.log?

  For what I saw the issue is not related to the storage but to the network.
  ovirt-hosted-engine-setup uses the jsonrpc client, instead the code
  from ovirt-hosted-engine-ha still uses the xmlrpc client somewhere and
  this happens also when the setup asks to create the lockspace volume.
  It seams that in your case the xmlrpc client could not connect vdsm on
  the localhost.
  It could be somehow related to:
  https://bugzilla.redhat.com/1358530

  Can you please try executing
   sudo vdsClient -s 0 getVdsCaps
  on that host?

>   22.07.2016, 19:36, "aleksey.maksi...@it-kb.ru" 
> :
>>   Simone, thanks for link.
>>   vdsm.log attached
>>
>>   22.07.2016, 19:28, "Simone Tiraboschi" :
>>>On Fri, Jul 22, 2016 at 5:59 PM,  wrote:
 Thank you for your response, Simone.

 Log attached.
>>>
>>>It seams it comes from VDSM, can you please attach also vdsm.log?
>>>
 I don't use ovirt-engine-appliance because I have not found 
 "how-to" for ovirt-engine-appliance deployment in hosted engine 
 configuration.
>>>
>>>yum install ovirt-engine-appliance
>>>
>>>Then follow the instruction here:
>>>
>>> http://www.ovirt.org/develop/release-management/features/heapplianceflow/
>>>
 22.07.2016, 17:09, "Simone Tiraboschi" :
> Hi Aleksey,
> Can you please attach hosted-engine-setup logs?
>
> On Fri, Jul 22, 2016 at 3:46 PM,  
> wrote:
>
>>  Hello oVirt guru`s !
>>
>>  I have problem with initial deploy of ovirt 4.0 hosted engine.
>>
>>  My environment :
>>  
>>  * Two servers HP ProLiant DL 360 G5 with Qlogic FC HBA 
>> connected (with
>>  multipathd) to storage HP 3PAR 7200
>>  * On each server installed CentOS 7.2 Linux 
>> (3.10.0-327.22.2.el7.x86_64)
>>  * On 3PAR storage I created 2 LUNs for oVirt.
>>  - First LUN for oVirt Hosted Engine VM (60GB)
>>  - Second LUN for all other VMs (2TB)
>>
>>  # multipath -ll
>>
>>  3par-vv1 (360002ac0001bcec9) dm-0 

Re: [ovirt-users] ?==?utf-8?q? vds.dispatcher ERROR SSL in ovirt 4.0

2016-06-23 Thread Piotr Kliczewski
Please share the engine log.

On Thu, Jun 23, 2016 at 8:07 PM, Claude Durocher
<claude.duroc...@cptaq.gouv.qc.ca> wrote:
> I did a complete reinstall of ovirt 4.0 (with hosted engine appliance) and
> the error is there with a single host after minimum configuration (add a
> single nfs storage domain).
>
> The engine.log file doesn't content any irregularities.
>
>
>
> Le Mercredi, Juin 22, 2016 17:18 EDT, "Claude Durocher"
> <claude.duroc...@cptaq.gouv.qc.ca> a écrit:
>
>
>
>
> Here's a more complete log of vdsm with the error :
>
> https://drive.google.com/file/d/0B1CFwOEG9nMtcTR1Y3VWYjdJMnM/view?usp=sharing
>
> I inserted a few blank lines to highlight the errors.
>
>
>
>
> Le Vendredi, Juin 10, 2016 04:57 EDT, Piotr Kliczewski
> <piotr.kliczew...@gmail.com> a écrit:
>
>
> Claude,
>
> Please look for "ProtocolDetector.AcceptorImpl::(handle_accept)
> Accepting connection from ". The last part of this log message
> contains peername.
> I should help to understand which client is connecting.
>
> From the message I see that the client is disconnecting and as a
> result we get: 'Connection reset by peer'
>
> Please let us know about your findings.
>
> Thanks,
> Piotr
>
> On Wed, Jun 8, 2016 at 11:49 PM, Claude Durocher
> <claude.duroc...@cptaq.gouv.qc.ca> wrote:
>> I'm testing ovirt 4.0 rc1 on centos 7 (hosted engine on nfs). Every 15
>> seconds or so, I receive the following error:
>>
>> journal: vdsm vds.dispatcher ERROR SSL error during reading data: (104,
>> 'Connection reset by peer')
>>
>> Any ideas on how to debug this?
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ?==?utf-8?q? vds.dispatcher ERROR SSL in ovirt 4.0

2016-06-23 Thread Piotr Kliczewski
Please check your engine/engine.log why it is attempting to connect
every monitoring cycle.
Is the host in 'NonResponsive' state?

On Wed, Jun 22, 2016 at 11:18 PM, Claude Durocher
<claude.duroc...@cptaq.gouv.qc.ca> wrote:
> Here's a more complete log of vdsm with the error :
>
> https://drive.google.com/file/d/0B1CFwOEG9nMtcTR1Y3VWYjdJMnM/view?usp=sharing
>
> I inserted a few blank lines to highlight the errors.
>
>
>
>
> Le Vendredi, Juin 10, 2016 04:57 EDT, Piotr Kliczewski
> <piotr.kliczew...@gmail.com> a écrit:
>
>
> Claude,
>
> Please look for "ProtocolDetector.AcceptorImpl::(handle_accept)
> Accepting connection from ". The last part of this log message
> contains peername.
> I should help to understand which client is connecting.
>
> From the message I see that the client is disconnecting and as a
> result we get: 'Connection reset by peer'
>
> Please let us know about your findings.
>
> Thanks,
> Piotr
>
> On Wed, Jun 8, 2016 at 11:49 PM, Claude Durocher
> <claude.duroc...@cptaq.gouv.qc.ca> wrote:
>> I'm testing ovirt 4.0 rc1 on centos 7 (hosted engine on nfs). Every 15
>> seconds or so, I receive the following error:
>>
>> journal: vdsm vds.dispatcher ERROR SSL error during reading data: (104,
>> 'Connection reset by peer')
>>
>> Any ideas on how to debug this?
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Two ovirt-engine manage one hypervisor

2016-06-16 Thread Piotr Kliczewski
You had to test it with 3.5. In 3.6+ we support more clients so the
connection drop would be not the issue anymore.

There are number of logical issues that would make your env not usable
like Michal mentioned. Assuming at least two hosts it could happen
that different hosts would become SPM for different engines.
Engine is not designed to coexist with other engine and I suggest to
not take this path. You may want to consider using hosted engine or
use standalone engine which is able to recover after a crash.

On Thu, Jun 16, 2016 at 10:17 AM, Yedidyah Bar David  wrote:
> On Thu, Jun 16, 2016 at 10:13 AM, Michal Skrivanek
>  wrote:
>>
>> On 16 Jun 2016, at 09:07, Yaniv Kaul  wrote:
>>
>>
>>
>> On Thu, Jun 16, 2016 at 9:29 AM, Yedidyah Bar David  wrote:
>>>
>>> On Thu, Jun 16, 2016 at 9:10 AM, Yaniv Kaul  wrote:
>>> >
>>> >
>>> > On Thu, Jun 16, 2016 at 8:53 AM, Yedidyah Bar David 
>>> > wrote:
>>> >>
>>> >> On Thu, Jun 16, 2016 at 5:33 AM, Sandvik Agustin
>>> >>  wrote:
>>> >> > Hi users,
>>> >> >
>>> >> > Good day, is it possible to configure two ovirt-engine to manage one
>>> >> > hypervisor? My purpose for this is what if the first ovirt-engine
>>> >> > fails,
>>> >> > I
>>> >> > still have the 2nd ovirt-engine to manage hypervisor.
>>> >> >
>>> >> > is this possible? or any suggestion similar to my purpose?
>>> >>
>>> >> The "normal" solution is hosted-engine, which has HA - the engine
>>> >> runs in a VM, and HA daemons monitor it and the hosts, and if there
>>> >> is a problem they can start it on another host.
>>> >>
>>> >> There were discussions in the past, which you can find in the list
>>> >> archives,
>>> >> about running two engines against a single database, and current bottom
>>> >> line
>>> >> is that it's not supported, will not work, and iiuc will require some
>>> >> significant development investment to support.
>>> >>
>>> >> You might manage to have an active/passive solution - install an engine
>>> >> on two machines, configure both to use the same remote database, but
>>> >> make sure only one of them is active at any given time. Not sure if
>>> >> that's
>>> >> considered "fully supported", but might come close.
>>
>>
>> even when you make it work when cert issues are sorted out, you need to be
>> very careful not to bring both engines up managing a same host, they will
>> fight over it and the monitoring is going to be received only by one of the
>> engines, which in turn may cause HA VMs restart and split brains all over
>> the place.
>
> And, IIRC from previous discussions, also internal caches etc.
>
> But this is not something specific to ovirt-engine - many services
> have similar restrictions, and common clustering tools allow handling
> them.
>
>>
>>> >
>>> >
>>> > That's not enough - they need to share the same set of certificates...
>>>
>>> Best is to simply clone the machine after initial setup then change
>>> what's needed, or backup/restore only files (engine-backup --mode=backup
>>> --scope=files).
>>>
>>> Didn't check, but I do not think they actually need all the certs of
>>> all hosts - that is, that it's not mandatory to keep /etc/pki synced
>>> between them after initial setup. Didn't try that myself.
>>
>>
>> I'm not sure what happens when you provision a host from Mgmt A, then move
>> to Mgmt B and provision another from it:
>> 1. Mgmt A won't be aware of that host, from cert req perspective. May not be
>> such a big deal - donno.
>>
>> 2. Can Mgmt A provision another host? Need to ensure the certificate serial
>> numbers are OK, etc.
>>
>> They really need to share the CA DB.
>
> Even keeping /etc/pki synced, or mounted from each one before
> starting the engine and umounting when stopping, should not be
> too hard.
>
>> The backup-restore sounds like good approach  to me.
>> Y.
>>
>>>
>>> > Y.
>>> >
>>> >>
>>> >>
>>> >> You can find on the net docs/resources about creating a redundant
>>> >> postgresql cluster.
>>> >>
>>> >> Best,
>>> >> --
>>> >> Didi
>>> >> ___
>>> >> Users mailing list
>>> >> Users@ovirt.org
>>> >> http://lists.ovirt.org/mailman/listinfo/users
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Didi
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
>
> --
> Didi
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vds.dispatcher ERROR SSL in ovirt 4.0

2016-06-10 Thread Piotr Kliczewski
Claude,

Please look for "ProtocolDetector.AcceptorImpl::(handle_accept)
Accepting connection from ". The last part of this log message
contains peername.
I should help to understand which client is connecting.

>From the message I see that the client is disconnecting and as a
result we get: 'Connection reset by peer'

Please let us know about your findings.

Thanks,
Piotr

On Wed, Jun 8, 2016 at 11:49 PM, Claude Durocher
 wrote:
> I'm testing ovirt 4.0 rc1 on centos 7 (hosted engine on nfs). Every 15
> seconds or so, I receive the following error:
>
> journal: vdsm vds.dispatcher ERROR SSL error during reading data: (104,
> 'Connection reset by peer')
>
> Any ideas on how to debug this?
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Need help in starting a vm using vdsClient

2016-05-06 Thread Piotr Kliczewski
Hi,

You may want to experiment with [1]. Instead of writing a bash script
you can use python for your testing.
Here [2] is an example how to use it. Let me know if you need more
help with creating a script.

Thanks,
Piotr

[1] 
https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=lib/vdsm/jsonrpcvdscli.py;h=2720673d296831e1d6500c571a8c29b5950ba88b;hb=refs/heads/master
[2] 
https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=tests/functional/utils.py;h=9db8ae3a8ed5c38356fa35982c1570541074b9e5;hb=refs/heads/master

On Fri, May 6, 2016 at 2:05 PM, knarra  wrote:
> Hi All,
>
>I want to write a script to poweroff vms and start vms in a loop for my
> testing. I found the command to poweroff the vms by looking at the vdsClient
> -h, but can some one help me how to start the powered off vm using vdsClient
> command ??
>
> Thanks
> kasturi.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Piotr Kliczewski
Cam,

It is really hard to understand partial logs. Please send me directly
full logs and I will analyze.

Thanks,
Piotr

On Mon, May 2, 2016 at 4:35 PM, Cam Mac <iuco...@gmail.com> wrote:
> Hi Piotr,
>
> Attached are the vdsm log, the engine log and the supervdsm log. I've
> attached them as a .tgz.
>
> I noticed it is complaining about configuring an interface in one of the
> node logs. It shows as up in the engine web GUI though (and on the command
> line).
>
> Thanks for the help.
>
> -Cam
>
> On Mon, May 2, 2016 at 1:38 PM, Piotr Kliczewski
> <piotr.kliczew...@gmail.com> wrote:
>>
>> Cam,
>>
>> Please provide engine and failing vdsm logs.
>>
>> Thanks,
>> Piotr
>>
>> On Sun, May 1, 2016 at 4:05 PM, Cam Mac <iuco...@gmail.com> wrote:
>> > Hi,
>> >
>> > I have a two node + engine ovirt setup, and I was having problems
>> > doing a live migration between nodes. I looked in the vdsm logs and
>> > noticed selinux errors, so I checked the selinux config, and both the
>> > ovirt-engine host and one of the nodes had selinux disabled. So I
>> > thought I would enable it on these two hosts, as it is officially
>> > supported anyway. I started with the node, and put it into maintenance
>> > mode, which interestingly, migrated the VMs off to the other node
>> > without issue. After modifying the selinux config, I then rebooted
>> > that node, which came back up. I then tried to activate the node but
>> > it fails and marks it as unresponsive.
>> >
>> > --8<--
>> >
>> > 2016-04-28 16:34:31,326 INFO
>> > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>> > Reactor) [29acb18b] Connecting to
>> > kvm-ldn-02/172.16.23.12
>> > 2016-04-28 16:34:31,327 ERROR
>> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>> > (DefaultQuartzScheduler_Worker-32) [ac322cb] Command
>> > 'GetCapabilitiesVDSCommand(HostName = kvm-ldn-02,
>> > VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> > hostId='b12c0b80-d64d-42fd-8a55-94f92b9ca3aa',
>> > vds='Host[kvm-ldn-02,b12c0b80-d64d-42fd-8a55-94f92b9ca3aa]'})'
>> > execution failed:
>> > org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection
>> > failed
>> > 2016-04-28 16:34:31,327 ERROR
>> > [org.ovirt.engine.core.vdsbroker.HostMonitoring]
>> > (DefaultQuartzScheduler_Worker-32) [ac322cb] Failure to refresh Vds
>> > runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
>> > Connection failed
>> > 2016-04-28 16:34:31,327 ERROR
>> > [org.ovirt.engine.core.vdsbroker.HostMonitoring]
>> > (DefaultQuartzScheduler_Worker-32) [ac322cb] Exception:
>> > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
>> > org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection
>> > failed
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:157)
>> > [vdsbroker.jar:]
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:120)
>> > [vdsbroker.jar:]
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65)
>> > [vdsbroker.jar:]
>> > at
>> > org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
>> > [dal.jar:]
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:467)
>> > [vdsbroker.jar:]
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:652)
>> > [vdsbroker.jar:]
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:119)
>> > [vdsbroker.jar:]
>> > at
>> >
>> > org.ovirt.engine.core.vdsbroker.HostMonitoring.refresh(HostMonitoring.java:84)
>> > [vdsbroker.jar:]
>> > at
>> > org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:227)
>> > [vdsbroker.jar:]
>> > at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown
>> > Source) [:1.8.0_71]
>> > at
>> >
>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet

Re: [ovirt-users] node unresponsive after reboot

2016-05-02 Thread Piotr Kliczewski
Cam,

Please provide engine and failing vdsm logs.

Thanks,
Piotr

On Sun, May 1, 2016 at 4:05 PM, Cam Mac  wrote:
> Hi,
>
> I have a two node + engine ovirt setup, and I was having problems
> doing a live migration between nodes. I looked in the vdsm logs and
> noticed selinux errors, so I checked the selinux config, and both the
> ovirt-engine host and one of the nodes had selinux disabled. So I
> thought I would enable it on these two hosts, as it is officially
> supported anyway. I started with the node, and put it into maintenance
> mode, which interestingly, migrated the VMs off to the other node
> without issue. After modifying the selinux config, I then rebooted
> that node, which came back up. I then tried to activate the node but
> it fails and marks it as unresponsive.
>
> --8<--
>
> 2016-04-28 16:34:31,326 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
> Reactor) [29acb18b] Connecting to
> kvm-ldn-02/172.16.23.12
> 2016-04-28 16:34:31,327 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-32) [ac322cb] Command
> 'GetCapabilitiesVDSCommand(HostName = kvm-ldn-02,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='b12c0b80-d64d-42fd-8a55-94f92b9ca3aa',
> vds='Host[kvm-ldn-02,b12c0b80-d64d-42fd-8a55-94f92b9ca3aa]'})'
> execution failed:
> org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection
> failed
> 2016-04-28 16:34:31,327 ERROR
> [org.ovirt.engine.core.vdsbroker.HostMonitoring]
> (DefaultQuartzScheduler_Worker-32) [ac322cb] Failure to refresh Vds
> runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
> Connection failed
> 2016-04-28 16:34:31,327 ERROR
> [org.ovirt.engine.core.vdsbroker.HostMonitoring]
> (DefaultQuartzScheduler_Worker-32) [ac322cb] Exception:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection
> failed
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:157)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:120)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
> [dal.jar:]
> at
> org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:467)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:652)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:119)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.HostMonitoring.refresh(HostMonitoring.java:84)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:227)
> [vdsbroker.jar:]
> at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown
> Source) [:1.8.0_71]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_71]
> at java.lang.reflect.Method.invoke(Method.java:497)
> [rt.jar:1.8.0_71]
> at
> org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:81)
> [scheduler.jar:]
> at
> org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:52)
> [scheduler.jar:]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> [quartz.jar:]
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
> [quartz.jar:]
> Caused by: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
> Connection failed
> at
> org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.connect(ReactorClient.java:157)
> [vdsm-jsonrpc-java-client.jar:]
> at
> org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.getClient(JsonRpcClient.java:114)
> [vdsm-jsonrpc-java-client.jar:]
> at
> org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.call(JsonRpcClient.java:73)
> [vdsm-jsonrpc-java-client.jar:]
> at
> org.ovirt.engine.core.vdsbroker.jsonrpc.FutureMap.(FutureMap.java:68)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.jsonrpc.JsonRpcVdsServer.getCapabilities(JsonRpcVdsServer.java:268)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand.executeVdsBrokerCommand(GetCapabilitiesVDSCommand.java:15)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:110)
> [vdsbroker.jar:]
> ... 14 more
>
> --8<--
>
> Any ideas?
>
> Thanks for any help,
>
> Cam
>
> ___
> Users mailing list
> 

Re: [ovirt-users] oVirt 3.5 and SSLv3

2016-04-24 Thread Piotr Kliczewski
Robert,

Looking at the info you pasted I see:
"java.net.NoRouteToHostException: No route to host".
It usually mean that there is/was something wrong with your network.

Thanks,
Piotr

On Wed, Apr 20, 2016 at 3:28 PM, Robert Story  wrote:
> On Wed, 20 Apr 2016 08:52:49 -0400 Alexander wrote:
> AW> On Wednesday, April 20, 2016 08:39:14 AM Robert Story wrote:
> AW> > Yesterday I had to re-install a host node in my 3.5.6 cluster. After a 
> fresh
> AW> > install of CentOS 7.2, attempts to re-install failed, as did removing 
> and
> AW> > re-adding the node. Here is a log excerpt from the engine:
> AW> >
> AW> > [...]
> AW> > [org.ovirt.engine.core.vdsbroker.VdsManager]
> AW> > (DefaultQuartzScheduler_Worker-38) Host eclipse is not responding. It 
> will
> AW> > stay in Connecting state for a grace period of 120 seconds and after 
> that
> AW> > an attempt to fence the host will be issued. 2016-04-19 18:22:01,938 
> ERROR
> AW> > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
> AW> > (DefaultQuartzScheduler_Worker-38) Failure to refresh Vds runtime info:
> AW> > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> AW> > java.net.NoRouteToHostException: No route to host at
> AW> > 
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkExc
> AW> > eption(VdsBrokerCommand.java:126) [vdsbroker.jar:]
> AW> >
> AW> > Luckily seeing SSL+java in the log tickled my memory about java 
> disabling
> AW> > SSLv3, and google helped me find this workaround:
> AW> >
> AW> >  - edit /usr/lib/jvm/java/jre/lib/security/java.security
> AW> >  - look for jdk.tls.disabledAlgorithms
> AW> >  - remove SSLv3 from the list
> AW> >  - service ovirt-engine restart
> AW> >
> AW> > Google also tells me that this should be an issue for 3.5, and there is 
> a
> AW> > vdsm setting, VdsmSSLProtocol, that can be set to use TLS, but I can't 
> find
> AW> > how to change/set it. Anyone know the secret?
> AW>
> AW> Pretty much everything engine related can be configured with
> AW> engine-config. engine-config -l will give you a list of all the
> AW> options. engine-config -g  will get the current value,
> AW> engine-config -s = will set it. A quick grep indicates that
> AW> you are looking for the VdsmSSLProtocol key.
>
> Hmmm..
>
>   # engine-config -g VdsmSSLProtocol
>   VdsmSSLProtocol: TLSv1 version: general
>
> Looks like it's already set to TLS, making me wonder why I needed to remove 
> SSLv3.  I just put it back and restarted the engine, and it seems to be 
> communicating with all hosts ok. So maybe it's just some process/code using 
> during install that isn't using this setting...
>
>
> Robert
>
> --
> Senior Software Engineer @ Parsons
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] centos 7.1 and up & ixgbe

2016-03-19 Thread Piotr Kliczewski
Johan,

It there is temporary networking issue and you still want engine not to
fence the host you can
increase heartbeat interval in the engine configuration. It would tell
engine to wait longer
before assuming that the host is not responding.

Please provide the logs so we can understand why there is communication
issue in the first
place.

Thanks,
Piotr

On Thu, Mar 17, 2016 at 12:52 PM, Nir Soffer  wrote:

> On Thu, Mar 17, 2016 at 10:49 AM, Johan Kooijman 
> wrote:
> > Hi all,
> >
> > Since we upgraded to the latest ovirt node running 7.2, we're seeing that
> > nodes become unavailable after a while. It's running fine, with a couple
> of
> > VM's on it, untill it becomes non responsive. At that moment it doesn't
> even
> > respond to ICMP. It'll come back by itself after a while, but oVirt
> fences
> > the machine before that time and restarts VM's elsewhere.
> >
> > Engine tells me this message:
> >
> > VDSM host09 command failed: Message timeout which can be caused by
> > communication issues
> >
> > Is anyone else experiencing these issues with ixgbe drivers? I'm running
> on
> > Intel X540-AT2 cards.
>
> We will need engine and vdsm logs to understand this issue.
>
> Can you file a bug and attach ful logs?
>
> Nir
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] How does VDSM-Fake actually work?

2016-02-04 Thread Piotr Kliczewski
Eldad is working on making it working with engine 3.6. He should be able to
give you information you need.

On Wed, Feb 3, 2016 at 12:33 PM,   wrote:
> Anything?
>
> El 2016-02-02 10:18, Nicolás escribió:
>>
>> Hi,
>>
>>  I'm trying to set up VDSM-Fake
>> (git://gerrit.ovirt.org/ovirt-vdsmfake.git) for some tests, however,
>> I'm a bit confused about how does it actually work. As the
>> instructions say, I was able to build the project with Maven (however,
>> the org.ovirt.vdsm-jsonrpc-java dependency version had to be changed
>> to 1.1.5 instead of 1.1.2-SNAPSHOT in pom.xml as this latter is no
>> longer provided at the repository).
>>
>>  Once built, I run mvn jetty:run and the server started correctly:
>>
>>> 2016-02-02 11:01:51.957:INFO::jetty-6.1.26 [1]
>>> 2016-02-02 11:01:52.804:INFO::No [2] Transaction manager found - if
>>> your webapp requires one, please configure one.
>>> 2016-02-02 11:01:53,424 Application initialized.
>>> 2016-02-02 11:01:53,442 Opening a Stomp server localhost:54322
>>> 2016-02-02 11:01:53.702:INFO::Started [3]
>>> SelectChannelConnector@0.0.0.0:54321
>>> [INFO] Started Jetty Server
>>> [INFO] Starting scanner at interval of 10 seconds.
>>
>>  I could indeed verify it's listening on the VDSM port:
>>
>>> [root@host ovirt-vdsmfake]# netstat -atpn | grep 54321
>>> tcp6   0  0
>>> :::54321
>>> :::*LISTEN
>>> 44870/java
>>
>>  So the next step is to add a fake host via REST. I used scripts
>> provided here [4] and I successfully added the host, however, it
>> starts installing all the VDSM packages as it were a normal host and
>> therefore it tries to start vdsmd as well, which throws an error as
>> the Jetty Server is already listening on the 54321 port. I shut down
>> the Jetty Server and allowed oVirt Manager to install all the packages
>> properly, then stopped vdsmd and started the Jetty Server, but
>> expectedly oVirt Engine fails with message "Host xxx is non
>> responsive", so what I actually got is a real VDSM host and not a fake
>> one.
>>
>>  FWIW, the fake VDSM runs on a different host, ports are reacheable
>> from the oVirt engine, proper /etc/hosts has been added to the engine
>> to reach the host, and no further customization of web.xml has been
>> done.
>>
>>  I feel like I'm missing something here. Could someone shed some light
>> on what's wrong?
>>
>>  Thanks.
>>
>>  Nicolás
>>
>>
>> Links:
>> --
>> [1] INFO::jetty-6.1.26
>> [2] INFO::No
>> [3] INFO::Started
>> [4] http://www.ovirt.org/REST_API_Using_BASH_Automation
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Ovirt3.6

2015-10-26 Thread Piotr Kliczewski
bc4c-46c5-b924-69553b1f85c2 Type: VDS
> 2015-10-26 15:27:35,092 INFO
> [org.ovirt.engine.core.vdsbroker.HostMonitoring]
> (DefaultQuartzScheduler_Worker-68) [5a847352] Host
> 'infraesx2'(da97f61d-bc4c-46c5-b924-69553b1f85c2) is already in
> NonOperational status for reason
> 'EMULATED_MACHINES_INCOMPATIBLE_WITH_CLUSTER_LEVEL'. SetNonOperationalVds
> command is skipped.
> 2015-10-26 15:27:35,550 ERROR
> [org.ovirt.engine.core.bll.host.provider.foreman.SystemProviderFinder]
> (default task-9) [] Failed to find host on any provider by host name
> 'cstlb1'
> 2015-10-26 15:27:35,932 ERROR
> [org.ovirt.engine.core.bll.host.provider.foreman.SystemProviderFinder]
> (default task-1) [] Failed to find host on any provider by host name
> 'cstlb1'
>
>
>
> On Mon, Oct 26, 2015 at 3:19 PM, Piotr Kliczewski
> <piotr.kliczew...@gmail.com> wrote:
>>
>> In the engine log this time I can see:
>>
>> java.net.UnknownHostException: cstlb1: cstlb1: unknown error
>>
>> which means that the name of the host is not known and this is the
>> issue why the engine is not able to connect.
>>
>>
>> On Mon, Oct 26, 2015 at 10:37 AM, Budur Nagaraju <nbud...@gmail.com>
>> wrote:
>> > Attached is the log details.
>> >
>> > On Mon, Oct 26, 2015 at 1:35 PM, Piotr Kliczewski
>> > <piotr.kliczew...@gmail.com> wrote:
>> >>
>> >> I can see that the dates do not match with engine log that you
>> >> provided earlier. Please provided vdsm log from the same time frame so
>> >> we could see
>> >> why the connection failed. I only found this issue in vdsm logs that
>> >> you provided:
>> >>
>> >> Thread-493088::ERROR::2015-10-19
>> >> 07:24:26,102::config::103::ovirt_hosted_engine_ha.env.config::(_load)
>> >> Configuration file '/etc/ovirt-hosted-engine/hosted-engine.conf' not
>> >> available [[Errno 2] No such file or directory:
>> >> '/etc/ovirt-hosted-engine/hosted-engine.conf']
>> >> Thread-493088::ERROR::2015-10-19
>> >> 07:24:26,102::config::103::ovirt_hosted_engine_ha.env.config::(_load)
>> >> Configuration file '/etc/ovirt-hosted-engine/vm.conf' not available
>> >> [[Errno 2] No such file or directory:
>> >> '/etc/ovirt-hosted-engine/vm.conf']
>> >> Thread-493088::ERROR::2015-10-19
>> >> 07:24:26,103::API::1723::vds::(_getHaInfo) failed to retrieve Hosted
>> >> Engine HA info
>> >> Traceback (most recent call last):
>> >>   File "/usr/share/vdsm/API.py", line 1703, in _getHaInfo
>> >>   File
>> >>
>> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> >> line 100, in get_all_stats
>> >>   File
>> >>
>> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> >> line 173, in _configure_broker_conn
>> >>   File
>> >>
>> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/env/config.py",
>> >> line 129, in get
>> >> Exception: Configuration value not found:
>> >> file=/etc/ovirt-hosted-engine/hosted-engine.conf, key=sdUUID
>> >>
>> >> On Mon, Oct 26, 2015 at 9:00 AM, Budur Nagaraju <nbud...@gmail.com>
>> >> wrote:
>> >> > Below are the logs,
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > BVEFbYm5nbGFiLnBzZWN1cmUubmV0XV0+PC9Pcmdhbml6YXRpb24+DQogICAgICAgICAgICA8L1VzZXJEYXRhPg0KICAgICAgICAgICAgPEltYWdlSW5zdGFsbD4NCiAgICAgICAgICAgICAgICA8T1NJbWFnZT4NCiAgICAgICAgICAgICAgICAgICAgPEluc3RhbGxUb0F2YWlsYWJsZVBhcnRpdGlvbj50cnVlPC9JbnN0YWxsVG9BdmFpbGFibGVQYXJ0aXRpb24+DQogICAgICAgICAgICAgICAgPC9PU0ltYWdlPg0KICAgICAgICAgICAgPC9JbWFnZUluc3RhbGw+DQogICAgICAgIDwvY29tcG9uZW50Pg0KICAgICAgICA8Y29tcG9uZW50IG5hbWU9Ik1pY3Jvc29mdC1XaW5kb3dzLUludGVybmF0aW9uYWwtQ29yZS1XaW5QRSIgcHJvY2Vzc29yQXJjaGl0ZWN0dXJlPSJ4ODYiIHB1YmxpY0tleVRva2VuPSIzMWJmMzg1NmFkMzY0ZTM1IiBsYW5ndWFnZT0ibmV1dHJhbCIgdmVyc2lvblNjb3BlPSJub25TeFMiIHhtbG5zOndjbT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9XTUlDb25maWcvMjAwMi9TdGF0ZSIgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSI+DQogICAgICAgICAgICA8U2V0dXBVSUxhbmd1YWdlPg0KICAgICAgICAgICAgICAgIDxVSUxhbmd1YWdlPjwhW0NEQVRBW2VuX1VTXV0+PC9VSUxhbmd1YWdlPg0KICAgICAgICAgICAgPC9TZXR1cFVJTGFuZ3VhZ2U+DQogICAgICAgICAgICA8S

Re: [ovirt-users] Ovirt3.6

2015-10-26 Thread Piotr Kliczewski
Based on provided snippet of a log the engine is not able to connect
to your vdsm due to timeout (by default 2 seconds).
Please provide vdsm log so we can see why it failed.

On Mon, Oct 26, 2015 at 7:14 AM, Budur Nagaraju  wrote:
> HI
>
> After installing ovirt 3.6,unable to add ovirt node to the ovirt application
> ,below are the logs.
> The moment I add  to ovirt application network is getting disconnected prior
> to that ovirt node was able to reach the gateway without any issues.
>
>
> any solution that wold resolve my issues ?
>
>
>
> 2015-10-21 17:44:44,179 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to infraesx2.bnglab.psecure.net/10.206.68.97
> 2015-10-21 17:44:46,179 WARN
> [org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (SSL Stomp Reactor) []
> Retry failed
> 2015-10-21 17:44:46,179 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
> (DefaultQuartzScheduler_Worker-40) [] Exception during connection
> 2015-10-21 17:44:46,179 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler_Worker-40) [] Command
> 'GetAllVmStatsVDSCommand(HostName = infraesx2,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='2d74bd31-6894-4c9c-8260-97c305a6998c',
> vds='Host[infraesx2,2d74bd31-6894-4c9c-8260-97c305a6998c]'})' execution
> failed: java.rmi.ConnectException: Connection timeout
> 2015-10-21 17:44:46,179 INFO
> [org.ovirt.engine.core.vdsbroker.PollVmStatsRefresher]
> (DefaultQuartzScheduler_Worker-40) [] Failed to fetch vms info for host
> 'infraesx2' - skipping VMs monitoring.
> 2015-10-21 17:44:46,179 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to infraesx2.bnglab.psecure.net/10.206.68.97
> 2015-10-21 17:44:48,179 WARN
> [org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (SSL Stomp Reactor) []
> Retry failed
> 2015-10-21 17:44:48,179 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
> (DefaultQuartzScheduler_Worker-41) [] Exception during connection
> 2015-10-21 17:44:48,179 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-41) [] Command
> 'GetCapabilitiesVDSCommand(HostName = infraesx2,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='2d74bd31-6894-4c9c-8260-97c305a6998c',
> vds='Host[infraesx2,2d74bd31-6894-4c9c-8260-97c305a6998c]'})' execution
> failed: java.rmi.ConnectException: Connection timeout
> 2015-10-21 17:44:48,179 ERROR
> [org.ovirt.engine.core.vdsbroker.HostMonitoring]
> (DefaultQuartzScheduler_Worker-41) [] Failure to refresh Vds runtime info:
> java.rmi.ConnectException: Connection timeout
> 2015-10-21 17:44:48,179 ERROR
> [org.ovirt.engine.core.vdsbroker.HostMonitoring]
> (DefaultQuartzScheduler_Worker-41) [] Exception:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> java.rmi.ConnectException: Connection timeout
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:157)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:120)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
> [dal.jar:]
> at
> org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:467)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:634)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:119)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.HostMonitoring.refresh(HostMonitoring.java:84)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:226)
> [vdsbroker.jar:]
> at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
> [:1.7.0_85]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.7.0_85]
> at java.lang.reflect.Method.invoke(Method.java:606)
> [rt.jar:1.7.0_85]
> at
> org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:81)
> [scheduler.jar:]
> at
> org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:52)
> [scheduler.jar:]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> [quartz.jar:]
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
> [quartz.jar:]
> Caused by: java.rmi.ConnectException: Connection timeout
> at
> org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient$1.call(ReactorClient.java:116)
> [vdsm-jsonrpc-java-client.jar:]
> at
> 

Re: [ovirt-users] Ovirt3.6

2015-10-26 Thread Piotr Kliczewski
I can see that the dates do not match with engine log that you
provided earlier. Please provided vdsm log from the same time frame so
we could see
why the connection failed. I only found this issue in vdsm logs that
you provided:

Thread-493088::ERROR::2015-10-19
07:24:26,102::config::103::ovirt_hosted_engine_ha.env.config::(_load)
Configuration file '/etc/ovirt-hosted-engine/hosted-engine.conf' not
available [[Errno 2] No such file or directory:
'/etc/ovirt-hosted-engine/hosted-engine.conf']
Thread-493088::ERROR::2015-10-19
07:24:26,102::config::103::ovirt_hosted_engine_ha.env.config::(_load)
Configuration file '/etc/ovirt-hosted-engine/vm.conf' not available
[[Errno 2] No such file or directory:
'/etc/ovirt-hosted-engine/vm.conf']
Thread-493088::ERROR::2015-10-19
07:24:26,103::API::1723::vds::(_getHaInfo) failed to retrieve Hosted
Engine HA info
Traceback (most recent call last):
  File "/usr/share/vdsm/API.py", line 1703, in _getHaInfo
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 100, in get_all_stats
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 173, in _configure_broker_conn
  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/env/config.py",
line 129, in get
Exception: Configuration value not found:
file=/etc/ovirt-hosted-engine/hosted-engine.conf, key=sdUUID

On Mon, Oct 26, 2015 at 9:00 AM, Budur Nagaraju  wrote:
> Below are the logs,
>
>
> BVEFbYm5nbGFiLnBzZWN1cmUubmV0XV0+PC9Pcmdhbml6YXRpb24+DQogICAgICAgICAgICA8L1VzZXJEYXRhPg0KICAgICAgICAgICAgPEltYWdlSW5zdGFsbD4NCiAgICAgICAgICAgICAgICA8T1NJbWFnZT4NCiAgICAgICAgICAgICAgICAgICAgPEluc3RhbGxUb0F2YWlsYWJsZVBhcnRpdGlvbj50cnVlPC9JbnN0YWxsVG9BdmFpbGFibGVQYXJ0aXRpb24+DQogICAgICAgICAgICAgICAgPC9PU0ltYWdlPg0KICAgICAgICAgICAgPC9JbWFnZUluc3RhbGw+DQogICAgICAgIDwvY29tcG9uZW50Pg0KICAgICAgICA8Y29tcG9uZW50IG5hbWU9Ik1pY3Jvc29mdC1XaW5kb3dzLUludGVybmF0aW9uYWwtQ29yZS1XaW5QRSIgcHJvY2Vzc29yQXJjaGl0ZWN0dXJlPSJ4ODYiIHB1YmxpY0tleVRva2VuPSIzMWJmMzg1NmFkMzY0ZTM1IiBsYW5ndWFnZT0ibmV1dHJhbCIgdmVyc2lvblNjb3BlPSJub25TeFMiIHhtbG5zOndjbT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9XTUlDb25maWcvMjAwMi9TdGF0ZSIgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSI+DQogICAgICAgICAgICA8U2V0dXBVSUxhbmd1YWdlPg0KICAgICAgICAgICAgICAgIDxVSUxhbmd1YWdlPjwhW0NEQVRBW2VuX1VTXV0+PC9VSUxhbmd1YWdlPg0KICAgICAgICAgICAgPC9TZXR1cFVJTGFuZ3VhZ2U+DQogICAgICAgICAgICA8SW5wdXRMb2NhbGU+PCFbQ0RBVEFbZW5fVVNdXT4
 
8L0lucHV0TG9jYWxlPg0KICAgICAgICAgICAgPFVJTGFuZ3VhZ2U+PCFbQ0RBVEFbZW5fVVNdXT48L1VJTGFuZ3VhZ2U+DQogICAgICAgICAgICA8U3lzdGVtTG9jYWxlPjwhW0NEQVRBW2VuX1VTXV0+PC9TeXN0ZW1Mb2NhbGU+DQogICAgICAgICAgICA8VXNlckxvY2FsZT48IVtDREFUQVtlbl9VU11dPjwvVXNlckxvY2FsZT4NCiAgICAgICAgPC9jb21wb25lbnQ+DQogICAgPC9zZXR0aW5ncz4NCiAgICA8c2V0dGluZ3MgcGFzcz0ic3BlY2lhbGl6ZSI+DQogICAgICAgIDxjb21wb25lbnQgbmFtZT0iTWljcm9zb2Z0LVdpbmRvd3MtU2hlbGwtU2V0dXAiIHByb2Nlc3NvckFyY2hpdGVjdHVyZT0ieDg2IiBwdWJsaWNLZXlUb2tlbj0iMzFiZjM4NTZhZDM2NGUzNSIgbGFuZ3VhZ2U9Im5ldXRyYWwiIHZlcnNpb25TY29wZT0ibm9uU3hTIiB4bWxuczp3Y209Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vV01JQ29uZmlnLzIwMDIvU3RhdGUiIHhtbG5zOnhzaT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEtaW5zdGFuY2UiPg0KICAgICAgICAgICAgPERpc3BsYXk+DQogICAgICAgICAgICAgICAgPENvbG9yRGVwdGg+MzI8L0NvbG9yRGVwdGg+DQogICAgICAgICAgICAgICAgPERQST45NjwvRFBJPg0KICAgICAgICAgICAgICAgIDxIb3Jpem9udGFsUmVzb2x1dGlvbj4xMDI0PC9Ib3Jpem9udGFsUmVzb2x1dGlvbj4NCiAgICAgICAgICAgICAgICA8UmVmcmVzaFJhdGU+NzU8L1JlZnJl
 
c2hSYXRlPg0KICAgICAgICAgICAgICAgIDxWZXJ0aWNhbFJlc29sdXRpb24+NzY4PC9WZXJ0aWNhbFJlc29sdXRpb24+DQogICAgICAgICAgICA8L0Rpc3BsYXk+DQogICAgICAgICAgICA8Q29tcHV0ZXJOYW1lPjwhW0NEQVRBW1Rlc3Qtd2luOC0xXV0+PC9Db21wdXRlck5hbWU+DQogICAgICAgICAgICA8VGltZVpvbmU+PCFbQ0RBVEFbR01UIFN0YW5kYXJkIFRpbWVdXT48L1RpbWVab25lPg0KICAgICAgICA8L2NvbXBvbmVudD4NCiAgICAgICAgPGNvbXBvbmVudCBuYW1lPSJNaWNyb3NvZnQtV2luZG93cy1JbnRlcm5hdGlvbmFsLUNvcmUiIHByb2Nlc3NvckFyY2hpdGVjdHVyZT0ieDg2IiBwdWJsaWNLZXlUb2tlbj0iMzFiZjM4NTZhZDM2NGUzNSIgbGFuZ3VhZ2U9Im5ldXRyYWwiIHZlcnNpb25TY29wZT0ibm9uU3hTIiB4bWxuczp3Y209Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vV01JQ29uZmlnLzIwMDIvU3RhdGUiIHhtbG5zOnhzaT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEtaW5zdGFuY2UiPg0KICAgICAgICAgICAgPElucHV0TG9jYWxlPjwhW0NEQVRBW2VuX1VTXV0+PC9JbnB1dExvY2FsZT4NCiAgICAgICAgICAgIDxVc2VyTG9jYWxlPjwhW0NEQVRBW2VuX1VTXV0+PC9Vc2VyTG9jYWxlPg0KICAgICAgICAgICAgPFN5c3RlbUxvY2FsZT48IVtDREFUQVtlbl9VU11dPjwvU3lzdGVtTG9jYWxlPg0KICAgICAgICAgICAgPFVJTGFuZ3VhZ2U+PCFbQ0RBVEFbZW5fV
 

Re: [ovirt-users] Unstable hosted engine

2015-10-26 Thread Piotr Kliczewski
Jaret,

I can see in your engine log that there was exception raised on vdsm side:

VDSErrorException: Failed to GetAllVmStatsVDS, error = 'progress', code = -32603

but none of host logs contains this exception. Please provide a log
which contains the exception.

Thanks,
Piotr


On Sat, Oct 24, 2015 at 11:13 AM, Jaret Garcia  wrote:
>
> Hi Guys,
>
> A couple of days ago we added two hypervisors to an ovirt cluster where
> there were already two hypervisors, since then the engine became a bit
> unstable with some messages like VM is not responding, or sending the
> hypervisors as unreachable, trying to migrate VMs from one host to another
> and after a couple of minutes the hosts come back and are set to up. Seems
> like there is no real impact to the VMs yet however I'm afraid that it can
> crash. I notice that after I removed one hypervisor the system became a
> littler bit more stable.
>
> Attached is a log from the active hypervisors and the engine.
>
> ovirt hosted engine version 3.5.4
> hypervisors: centos 7.1
>
> Thanks in advance for any help on this.
>
> Regards
>
> Jaret Garcia
> Email sent using Packet Mail - Email, Groupware and Calendaring for the
> cloud!
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Concerns with increasing vdsTimeout value on engine?

2015-07-14 Thread Piotr Kliczewski
On Mon, Jul 13, 2015 at 5:12 PM, Groten, Ryan ryan.gro...@stantec.com wrote:
 Thanks for the responses everyone and for the RFE.  I do use HA in some 
 places at the moment, but I do see another timeout value called 
 vdsConnectionTimeout.  Would HA use this value or vdsTimeout (set to 2 by 
 default) when attempting to contact the host?


There is a difference between the two:

vdsConnectionTimeout - is a timeout used during connecting to a remote
host. By default it is 2 seconds.
vdsTimeout - high level command invocation timeout used by all
commands. By default it is 3 minutes.

As far as I understand you are looking for a possibility to customize
vdsTimeout for some of the commands.


 -Original Message-
 From: Shubhendu Tripathi [mailto:shtri...@redhat.com]
 Sent: Monday, July 13, 2015 2:25 AM
 To: Piotr Kliczewski
 Cc: Omer Frenkel; Groten, Ryan; users@ovirt.org
 Subject: Re: [ovirt-users] Concerns with increasing vdsTimeout value on 
 engine?

 On 07/13/2015 01:42 PM, Piotr Kliczewski wrote:
 On Mon, Jul 13, 2015 at 5:57 AM, Shubhendu Tripathi shtri...@redhat.com 
 wrote:
 On 07/12/2015 09:53 PM, Omer Frenkel wrote:

 - Original Message -
 From: Liron Aravot lara...@redhat.com
 To: Ryan Groten ryan.gro...@stantec.com
 Cc: users@ovirt.org
 Sent: Sunday, July 12, 2015 5:44:28 PM
 Subject: Re: [ovirt-users] Concerns with increasing vdsTimeout
 value on engine?



 - Original Message -
 From: Ryan Groten ryan.gro...@stantec.com
 To: users@ovirt.org
 Sent: Friday, July 10, 2015 10:45:11 PM
 Subject: [ovirt-users] Concerns with increasing vdsTimeout value
 on engine?



 When I try to attach new direct lun disks, the scan takes a very
 long time to complete because of the number of pvs presented to my
 hosts (there is already a bug on this, related to the pvcreate
 command taking a very long time -
 https://bugzilla.redhat.com/show_bug.cgi?id=1217401 )



 I discovered a workaround by setting the vdsTimeout value higher
 (it is
 180
 seconds by default). I changed it to 300 seconds and now the
 direct lun scan returns properly, but I’m hoping someone can warn
 me if this workaround is safe or if it’ll cause other potential
 issues? I made this change yesterday and so far so good.

 Hi, no serious issue can be caused by that.
 Keep in mind though that any other operation will have that amount
 of time to complete before failing on timeout - which will cause
 delays before failing (as the timeout was increased for all
 executions)
 when not everything is operational and up as expected (as in most
 of the time).
 I'd guess that a RFE could be opened to allow increasing the
 timeout of specific operations if a user want to do that.

 thanks,
 Liron.
 if you have HA vms and use power management (fencing), this might
 cause longer downtime for HA vms if host has network timeouts:
 the engine will wait for 3 network failures before trying to fence
 the host, so in case of timeouts, and increasing it to 5mins, you
 should expect 15mins before engine will decide host is
 non-responsive and fence, so if you have HA vm on this host, this
 will be the vm downtime as well, as the engine will restart HA vms
 only after fencing.

 you can read more on
 http://www.ovirt.org/Automatic_Fencing

 Even I am in a need where, I try to delete all the 256 gluster volume
 snapshots using a single gluster CLI command, and engine gets timed out.
 So, as Liron suggested it would be better if at VDSM verb level we
 are able to set timeout. That would be better option and caller needs
 to use the feature judicially :)

 Please open a RFE for being able to set operation timeout for single
 command call with description of use cases for which you would like to
 set the timeout.

 Piotr,

 I created an RFE BZ at https://bugzilla.redhat.com/show_bug.cgi?id=1242373.

 Thanks and Regards,
 Shubhendu

 Thanks,

 Ryan

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Concerns with increasing vdsTimeout value on engine?

2015-07-13 Thread Piotr Kliczewski
On Mon, Jul 13, 2015 at 5:57 AM, Shubhendu Tripathi shtri...@redhat.com wrote:
 On 07/12/2015 09:53 PM, Omer Frenkel wrote:


 - Original Message -

 From: Liron Aravot lara...@redhat.com
 To: Ryan Groten ryan.gro...@stantec.com
 Cc: users@ovirt.org
 Sent: Sunday, July 12, 2015 5:44:28 PM
 Subject: Re: [ovirt-users] Concerns with increasing vdsTimeout value on
 engine?



 - Original Message -

 From: Ryan Groten ryan.gro...@stantec.com
 To: users@ovirt.org
 Sent: Friday, July 10, 2015 10:45:11 PM
 Subject: [ovirt-users] Concerns with increasing vdsTimeout value on
 engine?



 When I try to attach new direct lun disks, the scan takes a very long
 time
 to
 complete because of the number of pvs presented to my hosts (there is
 already a bug on this, related to the pvcreate command taking a very
 long
 time - https://bugzilla.redhat.com/show_bug.cgi?id=1217401 )



 I discovered a workaround by setting the vdsTimeout value higher (it is
 180
 seconds by default). I changed it to 300 seconds and now the direct lun
 scan
 returns properly, but I’m hoping someone can warn me if this workaround
 is
 safe or if it’ll cause other potential issues? I made this change
 yesterday
 and so far so good.

 Hi, no serious issue can be caused by that.
 Keep in mind though that any other operation will have that amount of
 time to
 complete before failing on timeout - which will
 cause delays before failing (as the timeout was increased for all
 executions)
 when not everything is operational and up as expected (as in most of the
 time).
 I'd guess that a RFE could be opened to allow increasing the timeout of
 specific operations if a user want to do that.

 thanks,
 Liron.

 if you have HA vms and use power management (fencing),
 this might cause longer downtime for HA vms if host has network timeouts:
 the engine will wait for 3 network failures before trying to fence the
 host,
 so in case of timeouts, and increasing it to 5mins,
 you should expect 15mins before engine will decide host is non-responsive
 and fence,
 so if you have HA vm on this host, this will be the vm downtime as well,
 as the engine will restart HA vms only after fencing.

 you can read more on
 http://www.ovirt.org/Automatic_Fencing


 Even I am in a need where, I try to delete all the 256 gluster volume
 snapshots using a single gluster CLI command, and engine gets timed out.
 So, as Liron suggested it would be better if at VDSM verb level we are able
 to set timeout. That would be better option and caller needs to use the
 feature judicially :)


Please open a RFE for being able to set operation timeout for single
command call with description of use cases for which
you would like to set the timeout.



 Thanks,

 Ryan

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Communication errors between engine and nodes?

2015-03-17 Thread Piotr Kliczewski
Hi Roel,

You can change this setting in two ways.
- you can update it in db directly as you stated (not recommended)
- use engine-config -s vdsHeartbeatInSeconds=20 but prior to running
this command
  you need to update config file
/etc/ovirt-engine/engine-config/engine-config.properties
  with vdsHeartbeatInSeconds.type=Integer. This config value is not
exposed by default.

Thanks,
Piotr

On Mon, Mar 16, 2015 at 11:18 PM, Roel de Rooy rder...@motto.nl wrote:
 HI Piotr,

 Thanks for your reply!

 If I would like to change the heartbeat value, do I have to update the value 
 within the vdc_options table directly, or should this be done by another way 
 (e.g. config file)?

 Regards,
 Roel

 -Oorspronkelijk bericht-
 Van: Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
 Verzonden: maandag 16 maart 2015 12:16
 Aan: Roel de Rooy
 CC: Michal Skrivanek; users@ovirt.org
 Onderwerp: Re: [ovirt-users] Communication errors between engine and nodes?

 Unfortunately log entries that you copied give me almost no information about 
 nature of your issue.
 There are few things that we can do to understand what is going on with your 
 setup.

 Heartbeat functionality provides means to detect whether we still have 
 connection with a host. By default heartbeat timeout is set to 10 seconds but 
 it can be modified by setting vdsHeartbeatInSeconds.

 In general whenever there are no incoming responses nor heartbeat frame is 
 not received engine will invalidate the connection and will attempt to 
 recover. If reconnection was successful you want see any other consequences 
 of loosing single heartbeat. I would explore stability of your network so if 
 the network is busy or you loose network packets from time to time this kind 
 of entries in the log are expected. You can increase heatbeat value and see 
 whether it will work better for your env.

 If you confirm that your network is stable we could explore the issue further 
 by setting debug level logging for your engine to understand exactly how the 
 messages are processes by a host and when we receive responses.



 On Mon, Mar 16, 2015 at 11:34 AM, Roel de Rooy rder...@motto.nl wrote:
 Received the heartbeat exeeded continuously this morning (seems to be 
 quiet again for now).
 VM's still continue to work correctly and the storage domains (NFS shares) 
 are still connected and reachable on the nodes, at the exact time that this 
 issue is happening.

 Contacted our network engineer to see if he could see a load increase on our 
 network, or could see any latency, errors, etc.
 Unfortunately he could not detect anything yet (he is still investigating 
 this).


 I have attached both the engine and vdsm logs

 Engine.log:

 2015-03-16 10:10:10,506 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ListVDSCommand]
 (DefaultQuartzScheduler_Worker-45) [6d40f562] Command
 ListVDSCommand(HostName = HOST, HostId =
 3b87597e-081b-4c89-9b1e-cb04203259f5,
 vds=Host[HOST,3b87597e-081b-4c89-9b1e-cb04203259f5]) execution
 failed. Exception: VDSNetworkException: VDSGenericException:
 VDSNetworkException: Heartbeat exeeded
 2015-03-16 10:10:10,507 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
 (DefaultQuartzScheduler_Worker-35) [2c53103c] Command
 SpmStatusVDSCommand(HostName = HOST, HostId =
 3b87597e-081b-4c89-9b1e-cb04203259f5, storagePoolId =
 124ae76f-8acb-412e-91cc-dff9f6ec665d) execution failed. Exception:
 VDSNetworkException: VDSGenericException: VDSNetworkException:
 Heartbeat exeeded
 2015-03-16 10:10:10,506 WARN
 [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker]
 (ResponseWorker) Exception thrown during message processing
 2015-03-16 10:10:10,507 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager] 
 (DefaultQuartzScheduler_Worker-45) [6d40f562] Host HOST is not responding. 
 It will stay in Connecting state for a grace period of 88 seconds and after 
 that an attempt to fence the host will be issued.
 2015-03-16 10:10:10,510 INFO
 [org.ovirt.engine.core.bll.storage.SetStoragePoolStatusCommand]
 (DefaultQuartzScheduler_Worker-35) [7e61eee] Running command:
 SetStoragePoolStatusCommand internal: true. Entities affected :  ID:
 124ae76f-8acb-412e-91cc-dff9f6ec665d Type: StoragePool
 2015-03-16 10:10:10,512 INFO
 [org.ovirt.engine.core.vdsbroker.storage.StoragePoolDomainHelper]
 (DefaultQuartzScheduler_Worker-35) [7e61eee] Storage Pool
 124ae76f-8acb-412e-91cc-dff9f6ec665d - Updating Storage Domain
 bfa86142-6f2e-44fe-8a9c-cf4390f3b8ae status from Active to Unknown,
 reason : null
 2015-03-16 10:10:10,513 INFO
 [org.ovirt.engine.core.vdsbroker.storage.StoragePoolDomainHelper]
 (DefaultQuartzScheduler_Worker-35) [7e61eee] Storage Pool
 124ae76f-8acb-412e-91cc-dff9f6ec665d - Updating Storage Domain
 178a38d9-245c-43d3-bff9-6f3a5983bf03 status from Active to Unknown,
 reason : null
 2015-03-16 10:10:10,514 INFO
 [org.ovirt.engine.core.vdsbroker.storage.StoragePoolDomainHelper]
 (DefaultQuartzScheduler_Worker-35) [7e61eee] Storage Pool

Re: [ovirt-users] Communication errors between engine and nodes?

2015-03-16 Thread Piotr Kliczewski
  
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] 
 (DefaultQuartzScheduler_Worker-44) [64352136] FINISH, 
 ConnectStorageServerVDSCommand, return: 
 {6ca291fc-0a20-4047-9aac-9d166a4c5300=0, 
 65744a96-5f4c-4d5f-898b-932eaf97084c=0, 
 03ea1ab7-e96c-410b-911e-905e988b0dc7=0}, log id: 5369ca8f



 Corresponding vdsm.log: (these are the only lines around the same timeframe):

 Thread-52::DEBUG::2015-03-16 
 10:10:10,977::task::595::Storage.TaskManager.Task::(_updateState) 
 Task=`89a0021d-9d5a-4563-ad44-d320aacbc551`::moving from state init - state 
 preparing
 JsonRpc (StompReactor)::DEBUG::2015-03-16 
 10:10:10,982::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling 
 message StompFrame command='SEND'
 Thread-52::INFO::2015-03-16 10:10:10,983::logUtils::44::dispatcher::(wrapper) 
 Run and protect: 
 getVolumeSize(sdUUID=u'178a38d9-245c-43d3-bff9-6f3a5983bf03', 
 spUUID=u'124ae76f-8acb-412e-91cc-dff9f6ec665d', 
 imgUUID=u'fb58d38b-9965-40f3-af45-915a4968a3aa', 
 volUUID=u'0c28ab0e-b1a0-42b6-8eac-71de1faa6827', options=None)
 Thread-27::DEBUG::2015-03-16 
 10:10:10,985::fileSD::261::Storage.Misc.excCmd::(getReadDelay) /usr/bin/dd 
 if=/rhev/data-center/mnt/IP:_mnt_storage/178a38d9-245c-43d3-bff9-6f3a5983bf03/dom_md/metadata
  iflag=direct of=/dev/null bs=4096 count=1 (cwd None)


 -Oorspronkelijk bericht-
 Van: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Namens Piotr 
 Kliczewski
 Verzonden: 16 March 2015 08:39
 Aan: Michal Skrivanek
 CC: users@ovirt.org
 Onderwerp: Re: [ovirt-users] Communication errors between engine and nodes?

 Can you please provide logs from both ends?

 On Fri, Mar 13, 2015 at 3:17 PM, Michal Skrivanek 
 michal.skriva...@redhat.com wrote:

 On 13 Mar 2015, at 14:39, Chris Adams wrote:

 Once upon a time, Roel de Rooy rder...@motto.nl said:
 We are observing the same thing with our oVirt environment.
 At random moments (could be a couple of times a day , once a day or even 
 once every couple of days), we receive the VDSNetworkException message 
 on one of our nodes.
 Haven't seen the heartbeat exceeded message, but could be that I 
 overlooked it within our logs.
 At some rare occasions, we also do see Host cannot access the Storage 
 Domain(s) UNKNOWN attached to the Data Center, within the GUI.

 VM's will continue to run normally and most of the times the nodes will be 
 in UP state again within the same minute.

 Will still haven't found the root cause of this issue.
 Our engine is CentOS 6.6 based and it's happing with both Centos 6 and 
 Fedora 20 nodes.
 We are using a LCAP bond of 1Gbit ports for our management network.

 As we didn't see any reports about this before, we are currently looking 
 if something network related is causing this.

 I just opened a BZ on it (since it isn't just me):

 https://bugzilla.redhat.com/show_bug.cgi?id=1201779

 My cluster went a couple of days without hitting this (as soon as I
 posted to the list of course), but then it happened several times
 overnight.  Interestingly, one error logged was communicating with
 the node currently running my hosted engine.  That should rule out
 external network (e.g. switch and such) issues, as those packets
 should not have left the physical box.

 well, hosted engine complicates things as you'd need to be able to see
 the status of the engine guest running a standalone engine installation or 
 at least running that hosted engine on a single node without any other VM 
 may help….

 Thanks,
 michal


 --
 Chris Adams c...@cmadams.net
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Communication errors between engine and nodes?

2015-03-16 Thread Piotr Kliczewski
Can you please provide logs from both ends?

On Fri, Mar 13, 2015 at 3:17 PM, Michal Skrivanek
michal.skriva...@redhat.com wrote:

 On 13 Mar 2015, at 14:39, Chris Adams wrote:

 Once upon a time, Roel de Rooy rder...@motto.nl said:
 We are observing the same thing with our oVirt environment.
 At random moments (could be a couple of times a day , once a day or even 
 once every couple of days), we receive the VDSNetworkException message on 
 one of our nodes.
 Haven't seen the heartbeat exceeded message, but could be that I 
 overlooked it within our logs.
 At some rare occasions, we also do see Host cannot access the Storage 
 Domain(s) UNKNOWN attached to the Data Center, within the GUI.

 VM's will continue to run normally and most of the times the nodes will be 
 in UP state again within the same minute.

 Will still haven't found the root cause of this issue.
 Our engine is CentOS 6.6 based and it's happing with both Centos 6 and 
 Fedora 20 nodes.
 We are using a LCAP bond of 1Gbit ports for our management network.

 As we didn't see any reports about this before, we are currently looking if 
 something network related is causing this.

 I just opened a BZ on it (since it isn't just me):

 https://bugzilla.redhat.com/show_bug.cgi?id=1201779

 My cluster went a couple of days without hitting this (as soon as I
 posted to the list of course), but then it happened several times
 overnight.  Interestingly, one error logged was communicating with the
 node currently running my hosted engine.  That should rule out external
 network (e.g. switch and such) issues, as those packets should not have
 left the physical box.

 well, hosted engine complicates things as you'd need to be able to see the 
 status of the engine guest
 running a standalone engine installation or at least running that hosted 
 engine on a single node without any other VM may help….

 Thanks,
 michal


 --
 Chris Adams c...@cmadams.net
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Network error

2015-03-06 Thread Piotr Kliczewski
Alessandro,

The log that you sent starts at 2015-03-06 11:01:01,806 whereas the error
that you asked for occurred at 2015-03-05 15:02:18,725.
Please provide log form the time that your issue happened.

Thanks,
Piotr

On Fri, Mar 6, 2015 at 11:39 AM, RASTELLI Alessandro 
alessandro.raste...@skytv.it wrote:

  Hi,

 you may find it attached.

 Thank you

 A.



 *From:* Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
 *Sent:* venerdì 6 marzo 2015 10:29
 *To:* RASTELLI Alessandro
 *Cc:* users; MANCINO Dino
 *Subject:* Re: [ovirt-users] Network error



 Hi,



 Please provide vdsm.log for analysis?



 Thanks,

 Piotr



 On Thu, Mar 5, 2015 at 4:06 PM, RASTELLI Alessandro 
 alessandro.raste...@skytv.it wrote:

  Hi,

 I get this error when I try to add the second network to a host
 (management network is OK)

 VDSGenericException:   VDSErrorException: Failed to
 SetupNetworksVDS, error = Resource unavailable, code = 40

 see log below:

 I’m running ovirt-hosted-engine 3.5.1.1-1.el6





 2015-03-05 15:02:16,562 INFO
 [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] Running command: SetupNetworksCommand
 internal: false. Entities affected :  ID: 378b60dc
 -8f28-486f-9feb-0349df25c4a9 Type: VDSAction group CONFIGURE_HOST_NETWORK
 with role type ADMIN

 2015-03-05 15:02:16,577 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] START, SetupNetworksVDSCommand(HostName
 = beltorax, HostId = 378b60dc-8f28-486f-9f
 eb-0349df25c4a9, force=false, checkConnectivity=true,
 conectivityTimeout=120,

 networks=[Rete_40 {id=57f9f798-9bde-4b2f-aeee-8920f77169ac,
 description=null, comment=null, subnet=null, gateway=null, type=null,
 vlanId=null, stp=false, dataCenterId=0002-0002-0002-0002-03aa,
 mt  u=0, vmNetwork=true, cluster=NetworkCluster
 {id={clusterId=null, networkId=null}, status=NON_OPERATIONAL,
 display=false, required=true, migration=false}, providedBy=null, label=40,
 qosId=null}],

 bonds=[],

 interfaces=[bond0 {id=ac91d426-dbe3-480b-b1af-267f2d44ffa3,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=bond0,
 macAddress=28:80:23:df:8e:a0, networkName=Rete_40, bondOptions=miimon=100
 mode=4, bootProto  col=STATIC_IP, address=10.69.40.154,
 subnet=255.255.255.0, gateway=10.69.40.1, mtu=0, bridged=true, type=0,
 networkImplementationDetails=null},

 eno4 {id=d083cebe-07ec-4aab-b07b-a1014d3673be,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno4,
 macAddress=c4:34:6b:b7:a7:13, networkName=ovirtmgmt, bondName=null,
 bootProtocol=STATIC_IP, addre  ss=10.39.193.3,
 subnet=255.255.255.0, gateway=, mtu=1500, bridged=true, speed=1000, type=2,
 networkImplementationDetails={inSync=true, managed=true}},

 eno3 {id=b9fbeff5-64bc-45df-9c41-9b10ca3839f0,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno3,
 macAddress=c4:34:6b:b7:a7:12, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno2 {id=a332843c-a9ce-469f-8702-1c918e4b7358,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno2,
 macAddress=c4:34:6b:b7:a7:11, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno1 {id=cc27cada-8825-4268-97a0-acce2ef10543,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno1,
 macAddress=c4:34:6b:b7:a7:10, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno49 {id=de83b23c-ab3e-4fbe-b4af-85937ff60f16,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno49,
 macAddress=28:80:23:df:8e:a0, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null},

 eno50 {id=ae9237ca-d443-479c-abb4-a29e9efb1481,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno50,
 macAddress=28:80:23:df:8e:a8, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null}],

 removedNetworks=[],

 removedBonds=[]), log id: 731097e2

 2015-03-05 15:02:16,607 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] FINISH, SetupNetworksVDSCommand, log id:
 731097e2

 2015-03-05 15:02:16,608 WARN
 [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker)
 Exception thrown during

Re: [ovirt-users] Network error

2015-03-06 Thread Piotr Kliczewski
Hi,

Please provide vdsm.log for analysis?

Thanks,
Piotr

On Thu, Mar 5, 2015 at 4:06 PM, RASTELLI Alessandro 
alessandro.raste...@skytv.it wrote:

  Hi,

 I get this error when I try to add the second network to a host
 (management network is OK)

 VDSGenericException:   VDSErrorException: Failed to
 SetupNetworksVDS, error = Resource unavailable, code = 40

 see log below:

 I’m running ovirt-hosted-engine 3.5.1.1-1.el6





 2015-03-05 15:02:16,562 INFO
 [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] Running command: SetupNetworksCommand
 internal: false. Entities affected :  ID: 378b60dc
 -8f28-486f-9feb-0349df25c4a9 Type: VDSAction group CONFIGURE_HOST_NETWORK
 with role type ADMIN

 2015-03-05 15:02:16,577 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] START, SetupNetworksVDSCommand(HostName
 = beltorax, HostId = 378b60dc-8f28-486f-9f
 eb-0349df25c4a9, force=false, checkConnectivity=true,
 conectivityTimeout=120,

 networks=[Rete_40 {id=57f9f798-9bde-4b2f-aeee-8920f77169ac,
 description=null, comment=null, subnet=null, gateway=null, type=null,
 vlanId=null, stp=false, dataCenterId=0002-0002-0002-0002-03aa,
 mt  u=0, vmNetwork=true, cluster=NetworkCluster
 {id={clusterId=null, networkId=null}, status=NON_OPERATIONAL,
 display=false, required=true, migration=false}, providedBy=null, label=40,
 qosId=null}],

 bonds=[],

 interfaces=[bond0 {id=ac91d426-dbe3-480b-b1af-267f2d44ffa3,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=bond0,
 macAddress=28:80:23:df:8e:a0, networkName=Rete_40, bondOptions=miimon=100
 mode=4, bootProto  col=STATIC_IP, address=10.69.40.154,
 subnet=255.255.255.0, gateway=10.69.40.1, mtu=0, bridged=true, type=0,
 networkImplementationDetails=null},

 eno4 {id=d083cebe-07ec-4aab-b07b-a1014d3673be,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno4,
 macAddress=c4:34:6b:b7:a7:13, networkName=ovirtmgmt, bondName=null,
 bootProtocol=STATIC_IP, addre  ss=10.39.193.3,
 subnet=255.255.255.0, gateway=, mtu=1500, bridged=true, speed=1000, type=2,
 networkImplementationDetails={inSync=true, managed=true}},

 eno3 {id=b9fbeff5-64bc-45df-9c41-9b10ca3839f0,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno3,
 macAddress=c4:34:6b:b7:a7:12, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno2 {id=a332843c-a9ce-469f-8702-1c918e4b7358,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno2,
 macAddress=c4:34:6b:b7:a7:11, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno1 {id=cc27cada-8825-4268-97a0-acce2ef10543,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno1,
 macAddress=c4:34:6b:b7:a7:10, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno49 {id=de83b23c-ab3e-4fbe-b4af-85937ff60f16,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno49,
 macAddress=28:80:23:df:8e:a0, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null},

 eno50 {id=ae9237ca-d443-479c-abb4-a29e9efb1481,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno50,
 macAddress=28:80:23:df:8e:a8, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null}],

 removedNetworks=[],

 removedBonds=[]), log id: 731097e2

 2015-03-05 15:02:16,607 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] FINISH, SetupNetworksVDSCommand, log id:
 731097e2

 2015-03-05 15:02:16,608 WARN
 [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker)
 Exception thrown during message processing

 2015-03-05 15:02:16,608 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
 Connecting to beltorax.skytech.local/10.39.193.3

 2015-03-05 15:02:18,725 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] Failed in SetupNetworksVDS method

 2015-03-05 15:02:18,726 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d]
 org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
 VDSGenericException:  

Re: [ovirt-users] Host remains Non-Responsive after reboot

2015-01-27 Thread Piotr Kliczewski
Looking at the logs I can see that connection was lost at 2015-01-26
09:24:43,213
and I can see good number of reconnection attempts which end up with
timeout or 'no route to host'.
The connection was recovered at 2015-01-26 09:28:56,292.

Vdsm.log do not contain above connection loss (it starts at 2015-01-26
10:01:02,208).

It was lost again at 2015-01-26 11:54:58,741 and it was recovered at
2015-01-26 12:01:47,752.

I checked vdsm logs and I can see really weird lack of logs:

JsonRpc (StompReactor)::DEBUG::2015-01-26
11:52:35,893::stompReactor::98::Broker.StompAdapter::(handle_frame)
Handling message StompFMainThread::INFO::2015-01-26
12:01:45,183::vdsm::131::vds::(run) (PID: 7021) I am the actual vdsm
4.16.10-8.gitc937927.el6 love005.ovt.visionamics.com
(2.6.32-504.3.3.el6.x86_64)
MainThread::DEBUG::2015-01-26
12:01:45,184::resourceManager::421::Storage.ResourceManager::(registerNamespace)
Registering namespace 'Storage'

which covers having no connection from the engine perspective.

Usually when there are connectivity issues we see timeouts in the logs
but here there are 'no route to host' as well
which suggest networking issues.

@Dan - Do you know what caused lack of logs in vdsm?
@ILanit - What vdsm version do you use?

On Tue, Jan 27, 2015 at 4:57 PM, Piotr Kliczewski pklic...@redhat.com wrote:




 - Original Message -
 From: Eli Mesika emes...@redhat.com
 To: Piotr Kliczewski pklic...@redhat.com
 Cc: Artyom Lukianov aluki...@redhat.com, users@ovirt.org, 
 rabsh...@citytwist.net, ILanit Stein
 ist...@redhat.com
 Sent: Tuesday, January 27, 2015 4:39:26 PM
 Subject: Re: [ovirt-users] Host remains Non-Responsive after reboot



 - Original Message -
  From: ILanit Stein ist...@redhat.com
  To: Artyom Lukianov aluki...@redhat.com, Eli Mesika
  emes...@redhat.com
  Cc: users@ovirt.org, rabsh...@citytwist.net
  Sent: Tuesday, January 27, 2015 5:19:12 PM
  Subject: Fwd: [ovirt-users] Host remains Non-Responsive after reboot
 
 
  Hi Guys,
 
  Can you please look into this please?

 Hi
 From the logs I can see clearly that host is turned on in 2015-01-26
 11:56:51,191
 However, there is a stomp exception in 2015-01-26 11:56:53,544 and a
 connection timeout in 2015-01-26 11:56:53,553 that might be related

 Piotr, can you please have a look ?


 Sure. Can you please send me the logs?


 
  Thanks,
  Ilanit.
  - Forwarded Message -
  From: Rob Abshear rabsh...@citytwist.net
  To: ILanit Stein ist...@redhat.com
  Sent: Tuesday, January 27, 2015 3:05:56 PM
  Subject: Re: [ovirt-users] Host remains Non-Responsive after reboot
 
  Here are the logs. you requested.  The shutdown of the node was at 11:53
  and vdsmd was manually restarted at 12:01 to get the node back online.
 
  On Tue, Jan 27, 2015 at 2:05 AM, ILanit Stein ist...@redhat.com wrote:
 
   It might be a bug,
   Would you please attach the logs, I mentioned bellow,
   that can bring more details on the failure?
   Adding Eli, that may want to give some input on this issue.
  
   Thanks,
   Ilanit.
  
   - Original Message -
   From: Rob Abshear rabsh...@citytwist.net
   To: ILanit Stein ist...@redhat.com
   Cc: users@ovirt.org
   Sent: Monday, January 26, 2015 9:43:14 PM
   Subject: Re: [ovirt-users] Host remains Non-Responsive after reboot
  
   I have done a bit more investigating on this matter.  If I restart the
   node
   from within oVirt using the power management option restart, then the
   node restarts and vdsmd DOES NOT start.  If I go into the DRAC and issue
   the command to power cycle the machine, then the machine restarts and
   vdsmd
   DOES start.  I can run the following command from another node in the
   cluster:
   fence_drac5 -a 192.168.200.105 -l root -p password -x -o reboot
   and the node restarts and vdsmd DOES start.
  
   On Sun, Jan 25, 2015 at 1:56 AM, ILanit Stein ist...@redhat.com wrote:
  
Hi Rob,
   
Thanks for this report.
   
Would you please provide these logs, at the time frame, the host
failure
occur:
1. oVirt Engine: /var/log/ovirt-engine/engine.log
2. host: /var/log/vdsm/vdsm.log
   
If it is reproducible, please add this info as well.
   
You can also check vdsm service status, on host, while host reported as
Non responsive,
by running on host 'service vdsmd status'
There might some problem, that might have prevented from vdsm service
to
come up, on host.
   
Ilanit.
   
- Original Message -
From: Rob Abshear rabsh...@citytwist.net
To: users@ovirt.org
Sent: Friday, January 23, 2015 9:22:42 PM
Subject: [ovirt-users] Host remains Non-Responsive after reboot
   
   
I am running oVirt Engine Version 3.5.0.1-1.el6. I have 4 hosts in the
cluster. Each host has a drac5 and it is configured and working. I am
trying to simulate a node failure. I am running one HA VM on one of the
hosts for testing. I simulate the failure by powering off the host with
   the
VM running

Re: [ovirt-users] Power Management config on Ovirt

2015-01-27 Thread Piotr Kliczewski
Hi Mathew,

It seems like this is quite old version (September 2014). There were good 
number of fixes in this area.

Looking at provided logs I am not able to tell which call is exactly failing. 
Do you have any steps to reproduce?

Thanks,
Piotr

- Original Message -
From: Renchu Mathew ren...@cracknell.com
To: Piotr Kliczewski piotr.kliczew...@gmail.com
Cc: Eli Mesika emes...@redhat.com, Piotr Kliczewski 
pklic...@redhat.com, users@ovirt.org
Sent: Monday, January 26, 2015 5:15:46 AM
Subject: RE: [ovirt-users] Power Management config on Ovirt

Hi Piotr,
VDSM Version is vdsm-4.16.4-0.el6

Regards

Renchu Mathew
.

From: Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
Sent: Sunday, January 25, 2015 6:08 PM
To: Renchu Mathew
Cc: Eli Mesika; Piotr Kliczewski; users@ovirt.org
Subject: Re: [ovirt-users] Power Management config on Ovirt



On Sun, Jan 25, 2015 at 2:07 PM, Renchu Mathew 
ren...@cracknell.commailto:ren...@cracknell.com wrote:

Hi Eli,



I have 2 hypervisor host and both are installed with below iso file. Master 
data domain is glusterfs which is configured on another server. Is there any 
latest iso available?



ovirt-node-iso-3.5.0.ovirt35.20140912.el6 (Edited).

@Eli - Do we know which vdsm version is in this iso?




Please find below details.



[cid:image001.png@01D0393F.9A5CF2D0]



Thanks  Regards



Renchu Mathew



-Original Message-
From: Eli Mesika [mailto:emes...@redhat.commailto:emes...@redhat.com]
Sent: Sunday, January 25, 2015 4:46 PM
To: Renchu Mathew
Cc: Martin Perina; users@ovirt.orgmailto:users@ovirt.org; Piotr Kliczewski
Subject: Re: [ovirt-users] Power Management config on Ovirt







- Original Message -

 From: Renchu Mathew ren...@cracknell.commailto:ren...@cracknell.com

 To: Eli Mesika emes...@redhat.commailto:emes...@redhat.com

 Cc: Martin Perina mper...@redhat.commailto:mper...@redhat.com, 
 users@ovirt.orgmailto:users@ovirt.org

 Sent: Sunday, January 25, 2015 11:19:21 AM

 Subject: RE: [ovirt-users] Power Management config on Ovirt



 Hi Eli,



 Please use any details.



 Thanks for your support.



 Regards



 Renchu Mathew



Hi again



Looking in the logs I see that this is a issue we handled when we switched from 
XML RPC to JSON RPC protocol.

Which vdsm is installed in the proxy host ?

I am adding Piotr who is on charge of the JSON RPC protocol and who helped me 
in the past when I got a similar error on PM operations

It looks like marshaling issue but I am not sure whether it was already fixed 
or it is something new. I am not able to match a call when looking at 
engine.log.







 -Original Message-

 From: Eli Mesika [mailto:emes...@redhat.commailto:emes...@redhat.com]

 Sent: Sunday, January 25, 2015 12:58 PM

 To: Renchu Mathew

 Cc: Martin Perina; users@ovirt.orgmailto:users@ovirt.org

 Subject: Re: [ovirt-users] Power Management config on Ovirt



 Hi Renchu



 I am looking currently on he case and will respond later on today

 after investigating the logs.

 If I will not find anything, can I use the details for the host PM

 only for status command to try to debug and find the source of the problem ?



 Thanks



 Eli



 - Original Message -

  From: Renchu Mathew ren...@cracknell.commailto:ren...@cracknell.com

  To: Martin Perina mper...@redhat.commailto:mper...@redhat.com

  Cc: users@ovirt.orgmailto:users@ovirt.org, Eli Mesika 
  emes...@redhat.commailto:emes...@redhat.com

  Sent: Sunday, January 25, 2015 6:50:00 AM

  Subject: RE: [ovirt-users] Power Management config on Ovirt

 

  Hi Martin,

 

  I got the below output when I run the command and it works from both

  the nodes.

 

  fence_ipmilan -a 192.168.1.114 -l admin -p admin -o status -v -P

 

  Getting status of IPMI:192.168.1.114...Spawning: '/usr/bin/ipmitool

  -I lanplus -H '192.168.1.114' -U 'admin' -P '[set]' -v chassis power

  status'...

  Chassis power = On

  Done

 

  Thanks

 

  Renchu Mathew  |  Sr. IT Administrator

 

 

 

  CRACKNELL  DUBAI   |  P.O. Box 66231  |   United Arab Emirates  |  T

  +971 4

  3445417  |  F +971 4 3493675tel:%2B971%204%203493675 |  M +971 50 
  7386484tel:%2B971%2050%207386484 ABU DHABI | DUBAI

  | LONDON | MUSCAT | DOHA | JEDDAH EMAIL 
  ren...@cracknell.commailto:ren...@cracknell.com | WEB

  www.cracknell.comhttp://www.cracknell.com

 

  This email, its content and any files transmitted with it are

  intended solely for the addressee(s) and may be legally privileged

  and/or confidential. If you are not the intended recipient please

  let us know by email reply and delete it from the system. Please

  note that any views or opinions presented in this email do not

  necessarily represent those of the company. Email transmissions

  cannot be guaranteed to be secure or error-free as information could

  be intercepted, corrupted, lost, destroyed, arrive late or

  incomplete, or contain viruses. The company therefore does not

  accept liability for any errors

Re: [ovirt-users] Power Management config on Ovirt

2015-01-27 Thread Piotr Kliczewski




- Original Message -
 From: Renchu Mathew ren...@cracknell.com
 To: Piotr Kliczewski pklic...@redhat.com
 Cc: Piotr Kliczewski piotr.kliczew...@gmail.com, Eli Mesika 
 emes...@redhat.com, users@ovirt.org
 Sent: Tuesday, January 27, 2015 10:48:12 AM
 Subject: RE: [ovirt-users] Power Management config on Ovirt
 
 Hi Piotr,
 
 Can you please provide me the link to download the new node iso? I can see
 only ovirt live iso.
 

I saw that Douglas sent following links in other thread [1] on this list:

centos7:
http://jenkins.ovirt.org/job/ovirt-node_master_create-iso-el7_merged/

Fedora20:
http://jenkins.ovirt.org/job/ovirt-node_master_create-iso-fc20_merged/

Please note that We should share the official iso this week.

[1] http://lists.ovirt.org/pipermail/users/2015-January/030846.html


 Regards
 
 Renchu Mathew
 
 -Original Message-
 From: Piotr Kliczewski [mailto:pklic...@redhat.com]
 Sent: Tuesday, January 27, 2015 12:21 PM
 To: Renchu Mathew
 Cc: Piotr Kliczewski; Eli Mesika; users@ovirt.org
 Subject: Re: [ovirt-users] Power Management config on Ovirt
 
 Hi Mathew,
 
 It seems like this is quite old version (September 2014). There were good
 number of fixes in this area.
 
 Looking at provided logs I am not able to tell which call is exactly failing.
 Do you have any steps to reproduce?
 
 Thanks,
 Piotr
 
 - Original Message -
 From: Renchu Mathew ren...@cracknell.com
 To: Piotr Kliczewski piotr.kliczew...@gmail.com
 Cc: Eli Mesika emes...@redhat.com, Piotr Kliczewski
 pklic...@redhat.com, users@ovirt.org
 Sent: Monday, January 26, 2015 5:15:46 AM
 Subject: RE: [ovirt-users] Power Management config on Ovirt
 
 Hi Piotr,
 VDSM Version is vdsm-4.16.4-0.el6
 
 Regards
 
 Renchu Mathew
 .
 
 From: Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
 Sent: Sunday, January 25, 2015 6:08 PM
 To: Renchu Mathew
 Cc: Eli Mesika; Piotr Kliczewski; users@ovirt.org
 Subject: Re: [ovirt-users] Power Management config on Ovirt
 
 
 
 On Sun, Jan 25, 2015 at 2:07 PM, Renchu Mathew
 ren...@cracknell.commailto:ren...@cracknell.com wrote:
 
 Hi Eli,
 
 
 
 I have 2 hypervisor host and both are installed with below iso file. Master
 data domain is glusterfs which is configured on another server. Is there any
 latest iso available?
 
 
 
 ovirt-node-iso-3.5.0.ovirt35.20140912.el6 (Edited).
 
 @Eli - Do we know which vdsm version is in this iso?
 
 
 
 
 Please find below details.
 
 
 
 [cid:image001.png@01D0393F.9A5CF2D0]
 
 
 
 Thanks  Regards
 
 
 
 Renchu Mathew
 
 
 
 -Original Message-
 From: Eli Mesika [mailto:emes...@redhat.commailto:emes...@redhat.com]
 Sent: Sunday, January 25, 2015 4:46 PM
 To: Renchu Mathew
 Cc: Martin Perina; users@ovirt.orgmailto:users@ovirt.org; Piotr Kliczewski
 Subject: Re: [ovirt-users] Power Management config on Ovirt
 
 
 
 
 
 
 
 - Original Message -
 
  From: Renchu Mathew ren...@cracknell.commailto:ren...@cracknell.com
 
  To: Eli Mesika emes...@redhat.commailto:emes...@redhat.com
 
  Cc: Martin Perina mper...@redhat.commailto:mper...@redhat.com,
  users@ovirt.orgmailto:users@ovirt.org
 
  Sent: Sunday, January 25, 2015 11:19:21 AM
 
  Subject: RE: [ovirt-users] Power Management config on Ovirt
 
 
 
  Hi Eli,
 
 
 
  Please use any details.
 
 
 
  Thanks for your support.
 
 
 
  Regards
 
 
 
  Renchu Mathew
 
 
 
 Hi again
 
 
 
 Looking in the logs I see that this is a issue we handled when we switched
 from XML RPC to JSON RPC protocol.
 
 Which vdsm is installed in the proxy host ?
 
 I am adding Piotr who is on charge of the JSON RPC protocol and who helped me
 in the past when I got a similar error on PM operations
 
 It looks like marshaling issue but I am not sure whether it was already fixed
 or it is something new. I am not able to match a call when looking at
 engine.log.
 
 
 
 
 
 
 
  -Original Message-
 
  From: Eli Mesika [mailto:emes...@redhat.commailto:emes...@redhat.com]
 
  Sent: Sunday, January 25, 2015 12:58 PM
 
  To: Renchu Mathew
 
  Cc: Martin Perina; users@ovirt.orgmailto:users@ovirt.org
 
  Subject: Re: [ovirt-users] Power Management config on Ovirt
 
 
 
  Hi Renchu
 
 
 
  I am looking currently on he case and will respond later on today
 
  after investigating the logs.
 
  If I will not find anything, can I use the details for the host PM
 
  only for status command to try to debug and find the source of the problem
  ?
 
 
 
  Thanks
 
 
 
  Eli
 
 
 
  - Original Message -
 
   From: Renchu Mathew ren...@cracknell.commailto:ren...@cracknell.com
 
   To: Martin Perina mper...@redhat.commailto:mper...@redhat.com
 
   Cc: users@ovirt.orgmailto:users@ovirt.org, Eli Mesika
   emes...@redhat.commailto:emes...@redhat.com
 
   Sent: Sunday, January 25, 2015 6:50:00 AM
 
   Subject: RE: [ovirt-users] Power Management config on Ovirt
 
  
 
   Hi Martin,
 
  
 
   I got the below output when I run the command and it works from both
 
   the nodes.
 
  
 
   fence_ipmilan -a 192.168.1.114 -l admin

Re: [ovirt-users] Host remains Non-Responsive after reboot

2015-01-27 Thread Piotr Kliczewski




- Original Message -
 From: Eli Mesika emes...@redhat.com
 To: Piotr Kliczewski pklic...@redhat.com
 Cc: Artyom Lukianov aluki...@redhat.com, users@ovirt.org, 
 rabsh...@citytwist.net, ILanit Stein
 ist...@redhat.com
 Sent: Tuesday, January 27, 2015 4:39:26 PM
 Subject: Re: [ovirt-users] Host remains Non-Responsive after reboot
 
 
 
 - Original Message -
  From: ILanit Stein ist...@redhat.com
  To: Artyom Lukianov aluki...@redhat.com, Eli Mesika
  emes...@redhat.com
  Cc: users@ovirt.org, rabsh...@citytwist.net
  Sent: Tuesday, January 27, 2015 5:19:12 PM
  Subject: Fwd: [ovirt-users] Host remains Non-Responsive after reboot
  
  
  Hi Guys,
  
  Can you please look into this please?
 
 Hi
 From the logs I can see clearly that host is turned on in 2015-01-26
 11:56:51,191
 However, there is a stomp exception in 2015-01-26 11:56:53,544 and a
 connection timeout in 2015-01-26 11:56:53,553 that might be related
 
 Piotr, can you please have a look ?
 

Sure. Can you please send me the logs?

 
  
  Thanks,
  Ilanit.
  - Forwarded Message -
  From: Rob Abshear rabsh...@citytwist.net
  To: ILanit Stein ist...@redhat.com
  Sent: Tuesday, January 27, 2015 3:05:56 PM
  Subject: Re: [ovirt-users] Host remains Non-Responsive after reboot
  
  Here are the logs. you requested.  The shutdown of the node was at 11:53
  and vdsmd was manually restarted at 12:01 to get the node back online.
  
  On Tue, Jan 27, 2015 at 2:05 AM, ILanit Stein ist...@redhat.com wrote:
  
   It might be a bug,
   Would you please attach the logs, I mentioned bellow,
   that can bring more details on the failure?
   Adding Eli, that may want to give some input on this issue.
  
   Thanks,
   Ilanit.
  
   - Original Message -
   From: Rob Abshear rabsh...@citytwist.net
   To: ILanit Stein ist...@redhat.com
   Cc: users@ovirt.org
   Sent: Monday, January 26, 2015 9:43:14 PM
   Subject: Re: [ovirt-users] Host remains Non-Responsive after reboot
  
   I have done a bit more investigating on this matter.  If I restart the
   node
   from within oVirt using the power management option restart, then the
   node restarts and vdsmd DOES NOT start.  If I go into the DRAC and issue
   the command to power cycle the machine, then the machine restarts and
   vdsmd
   DOES start.  I can run the following command from another node in the
   cluster:
   fence_drac5 -a 192.168.200.105 -l root -p password -x -o reboot
   and the node restarts and vdsmd DOES start.
  
   On Sun, Jan 25, 2015 at 1:56 AM, ILanit Stein ist...@redhat.com wrote:
  
Hi Rob,
   
Thanks for this report.
   
Would you please provide these logs, at the time frame, the host
failure
occur:
1. oVirt Engine: /var/log/ovirt-engine/engine.log
2. host: /var/log/vdsm/vdsm.log
   
If it is reproducible, please add this info as well.
   
You can also check vdsm service status, on host, while host reported as
Non responsive,
by running on host 'service vdsmd status'
There might some problem, that might have prevented from vdsm service
to
come up, on host.
   
Ilanit.
   
- Original Message -
From: Rob Abshear rabsh...@citytwist.net
To: users@ovirt.org
Sent: Friday, January 23, 2015 9:22:42 PM
Subject: [ovirt-users] Host remains Non-Responsive after reboot
   
   
I am running oVirt Engine Version 3.5.0.1-1.el6. I have 4 hosts in the
cluster. Each host has a drac5 and it is configured and working. I am
trying to simulate a node failure. I am running one HA VM on one of the
hosts for testing. I simulate the failure by powering off the host with
   the
VM running.
   
Here is what is happening.
   
   
* Host is powered off
* ~4 minutes pass and the host is recognized as not responding
* Automatic fence runs and the VM migrates. Another host in the
node
is chosen as a proxy to execute Status command on the host.
* Same host is chosen as proxy to execute Start command on the
host.
* Same host is chosen as proxy to execute Status command on the
host.
* The host DOES physically start.
* The host never shows status of UP.
* I select “confirm host has been rebooted” and I see a manual
fence
start.
* Host stays non-responsive.
* I put the host in maintenance and then activate it.
* Host still non-responsive
* I put the host in maintenance and do a reinstall
* Reinstall finishes and host becomes UP
   
So, everything seems to go fine with the HA functionality, but the host
never recovers without being reinstalled. Please let me know which logs
   you
need to look at to help me out with this.
   
Thanks
   
   
Sent with Mixmax
   
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Power Management config on Ovirt

2015-01-25 Thread Piotr Kliczewski
On Sun, Jan 25, 2015 at 2:07 PM, Renchu Mathew ren...@cracknell.com wrote:

  Hi Eli,



 I have 2 hypervisor host and both are installed with below iso file.
 Master data domain is glusterfs which is configured on another server. Is
 there any latest iso available?



 ovirt-node-iso-3.5.0.ovirt35.20140912.el6 (Edited).


@Eli - Do we know which vdsm version is in this iso?




  Please find below details.





 Thanks  Regards



 Renchu Mathew



 -Original Message-
 From: Eli Mesika [mailto:emes...@redhat.com]
 Sent: Sunday, January 25, 2015 4:46 PM
 To: Renchu Mathew
 Cc: Martin Perina; users@ovirt.org; Piotr Kliczewski
 Subject: Re: [ovirt-users] Power Management config on Ovirt







 - Original Message -

  From: Renchu Mathew ren...@cracknell.com

  To: Eli Mesika emes...@redhat.com

  Cc: Martin Perina mper...@redhat.com, users@ovirt.org

  Sent: Sunday, January 25, 2015 11:19:21 AM

  Subject: RE: [ovirt-users] Power Management config on Ovirt

 

  Hi Eli,

 

  Please use any details.

 

  Thanks for your support.

 

  Regards

 

  Renchu Mathew



 Hi again



 Looking in the logs I see that this is a issue we handled when we switched
 from XML RPC to JSON RPC protocol.

 Which vdsm is installed in the proxy host ?

 I am adding Piotr who is on charge of the JSON RPC protocol and who helped
 me in the past when I got a similar error on PM operations


It looks like marshaling issue but I am not sure whether it was already
fixed or it is something new. I am not able to match a call when looking at
engine.log.





  

  -Original Message-

  From: Eli Mesika [mailto:emes...@redhat.com]

  Sent: Sunday, January 25, 2015 12:58 PM

  To: Renchu Mathew

  Cc: Martin Perina; users@ovirt.org

  Subject: Re: [ovirt-users] Power Management config on Ovirt

 

  Hi Renchu

 

  I am looking currently on he case and will respond later on today

  after investigating the logs.

  If I will not find anything, can I use the details for the host PM

  only for status command to try to debug and find the source of the
 problem ?

 

  Thanks

 

  Eli

 

  - Original Message -

   From: Renchu Mathew ren...@cracknell.com

   To: Martin Perina mper...@redhat.com

   Cc: users@ovirt.org, Eli Mesika emes...@redhat.com

   Sent: Sunday, January 25, 2015 6:50:00 AM

   Subject: RE: [ovirt-users] Power Management config on Ovirt

  

   Hi Martin,

  

   I got the below output when I run the command and it works from both

   the nodes.

  

   fence_ipmilan -a 192.168.1.114 -l admin -p admin -o status -v -P

  

   Getting status of IPMI:192.168.1.114...Spawning: '/usr/bin/ipmitool

   -I lanplus -H '192.168.1.114' -U 'admin' -P '[set]' -v chassis power

   status'...

   Chassis power = On

   Done

  

   Thanks

  

   Renchu Mathew  |  Sr. IT Administrator

  

  

  

   CRACKNELL  DUBAI   |  P.O. Box 66231  |   United Arab Emirates  |  T

   +971 4

   3445417  |  F +971 4 3493675 |  M +971 50 7386484 ABU DHABI | DUBAI

   | LONDON | MUSCAT | DOHA | JEDDAH EMAIL ren...@cracknell.com | WEB

   www.cracknell.com

  

   This email, its content and any files transmitted with it are

   intended solely for the addressee(s) and may be legally privileged

   and/or confidential. If you are not the intended recipient please

   let us know by email reply and delete it from the system. Please

   note that any views or opinions presented in this email do not

   necessarily represent those of the company. Email transmissions

   cannot be guaranteed to be secure or error-free as information could

   be intercepted, corrupted, lost, destroyed, arrive late or

   incomplete, or contain viruses. The company therefore does not

   accept liability for any errors or omissions in the contents of this

   message which arise as a result of email transmission.

  

  

   -Original Message-

   From: Martin Perina [mailto:mper...@redhat.com]

   Sent: Thursday, January 22, 2015 6:12 PM

   To: Renchu Mathew

   Cc: users@ovirt.org; Eli Mesika

   Subject: Re: [ovirt-users] Power Management config on Ovirt

  

  

  

   - Original Message -

From: Renchu Mathew ren...@cracknell.com

To: Martin Perina mper...@redhat.com

Cc: users@ovirt.org

Sent: Thursday, January 22, 2015 2:39:43 PM

Subject: RE: [ovirt-users] Power Management config on Ovirt

   

Hi Martin,

   

   

   

Yes. The vdsm host.log is from node-02.

  

   That's strange, I cannot find any call to fenceNode which should

   appear, if PM status is gathered.

  

   Eli, any idea?

  

I have checked the link and it says we need to install the sever

view management agent  net-snmp on the hosts.

Do we need to try this? How to install this on node? I used the

below irmc admin user.

  

   Not, AFAIK this is needed only from Clustersuite, but not for oVirt.

  

   But could you please execute this command on node-20 just to confirm

   that Fujitsu

Re: [ovirt-users] ?3.4: VDSM Memory consumption

2014-09-30 Thread Piotr Kliczewski




- Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Daniel Helgenberger daniel.helgenber...@m-box.de, pklic...@redhat.com
 Cc: Francesco Romani from...@redhat.com, users@ovirt.org
 Sent: Tuesday, September 30, 2014 1:11:42 AM
 Subject: Re: [ovirt-users]?3.4: VDSM Memory consumption
 
 On Mon, Sep 29, 2014 at 09:02:19PM +, Daniel Helgenberger wrote:
  Hello Francesco,
  
  --
  Daniel Helgenberger
  m box bewegtbild GmbH
  
  P: +49/30/2408781-22
  F: +49/30/2408781-10
  ACKERSTR. 19
  D-10115 BERLIN
  www.m-box.de  www.monkeymen.tv
  
   On 29.09.2014, at 22:19, Francesco Romani from...@redhat.com wrote:
   
   - Original Message -
   From: Daniel Helgenberger daniel.helgenber...@m-box.de
   To: Francesco Romani from...@redhat.com
   Cc: Dan Kenigsberg dan...@redhat.com, users@ovirt.org
   Sent: Monday, September 29, 2014 2:54:13 PM
   Subject: Re: [ovirt-users]3.4: VDSM Memory consumption
   
   Hello Francesco,
   
   On 29.09.2014 13:55, Francesco Romani wrote:
   - Original Message -
   From: Daniel Helgenberger daniel.helgenber...@m-box.de
   To: Dan Kenigsberg dan...@redhat.com
   Cc: users@ovirt.org
   Sent: Monday, September 29, 2014 12:25:22 PM
   Subject: Re: [ovirt-users]3.4: VDSM Memory consumption
   
   Dan,
   
   I just reply to the list since I do not want to clutter BZ:
   
   While migrating VMs is easy (and the sampling is already running), can
   someone tell me the correct polling port to block with iptables?
   
   Thanks,
   Hi Daniel,
   
   there is indeed a memory profiling patch under discussion:
   http://gerrit.ovirt.org/#/c/32019/
   
   but for your case we'll need a backport to 3.4.x and clearer install
   instructions,
   which I'll prepare as soon as possible.
   I updated the BZ (and are now blocking 54321/tcp on one of my hosts).
   and verified it is not reachable. As  general info: This system I am
   using is my LAB / Test / eval setup for a final deployment for ovirt
   (then 3.5) in production; so it will go away some time in the future (a
   few weeks / months). If I am the only one experiencing this problem then
   you might be better of allocating resources elsewhere ;)
   
   Thanks for your understanding :)
   
   Unfortunately it is true that developer resources aren't so abundant,
   but it is also true that memleaks should never be discarded easily and
   without
   due investigation, considering the nature and the role of VDSM.
   
   So, I'm all in for further investigation regarding this issue.
   
   As for your question: if I understood correctly what you are asking
   (still catching up the thread), if you are trying to rule out the stats
   polling
   made by Engine to this bad leak, one simple way to test is just to
   shutdown
   Engine,
   and let VDSMs run unguarded on hypervisors. You'll be able to command
   these
   VDSMs using vdsClient or restarting Engine.
   As I said in my BZ comment this is not an option right now, but if
   understand the matter correctly IPTABLES reject should ultimately do the
   same?
   
   Definitely yes! Just do whatever it is more convenient for you.
   
  As you might have already seen in the BZ comment the leak stopped after
  blocking the port. Though this is clearly no permanent option - please let
  me know if I can be of any more assistance!
 
 The immediate suspect in this situation is M2Crypto. Could you verify
 that by re-opening the firewall and setting ssl=False in vdsm.conf?
 
 You should disable ssl on Engine side and restart both Engine and Vdsm
 (too bad I do not recall how that's done on Engine: Piotr, can you help?).
 

In vdc_options table there is option EncryptHostCommunication.
Please to set it to false and restart the engine.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ?3.4: VDSM Memory consumption

2014-09-30 Thread Piotr Kliczewski




- Original Message -
 From: Daniel Helgenberger daniel.helgenber...@m-box.de
 To: Piotr Kliczewski pklic...@redhat.com, Dan Kenigsberg 
 dan...@redhat.com
 Cc: Francesco Romani from...@redhat.com, users@ovirt.org
 Sent: Tuesday, September 30, 2014 11:50:28 AM
 Subject: Re: [ovirt-users]?3.4: VDSM Memory consumption
 
 Hello Piotr,
 
 On 30.09.2014 08:37, Piotr Kliczewski wrote:
 
 
 
  - Original Message -
  From: Dan Kenigsberg dan...@redhat.com
  To: Daniel Helgenberger daniel.helgenber...@m-box.de,
  pklic...@redhat.com
  Cc: Francesco Romani from...@redhat.com, users@ovirt.org
  Sent: Tuesday, September 30, 2014 1:11:42 AM
  Subject: Re: [ovirt-users]?3.4: VDSM Memory consumption
 
  On Mon, Sep 29, 2014 at 09:02:19PM +, Daniel Helgenberger wrote:
  Hello Francesco,
 
  --
  Daniel Helgenberger
  m box bewegtbild GmbH
 
  P: +49/30/2408781-22
  F: +49/30/2408781-10
  ACKERSTR. 19
  D-10115 BERLIN
  www.m-box.de  www.monkeymen.tv
 
  On 29.09.2014, at 22:19, Francesco Romani from...@redhat.com wrote:
 
  - Original Message -
  From: Daniel Helgenberger daniel.helgenber...@m-box.de
  To: Francesco Romani from...@redhat.com
  Cc: Dan Kenigsberg dan...@redhat.com, users@ovirt.org
  Sent: Monday, September 29, 2014 2:54:13 PM
  Subject: Re: [ovirt-users]3.4: VDSM Memory consumption
 
  Hello Francesco,
 
  On 29.09.2014 13:55, Francesco Romani wrote:
  - Original Message -
  From: Daniel Helgenberger daniel.helgenber...@m-box.de
  To: Dan Kenigsberg dan...@redhat.com
  Cc: users@ovirt.org
  Sent: Monday, September 29, 2014 12:25:22 PM
  Subject: Re: [ovirt-users]3.4: VDSM Memory consumption
 
  Dan,
 
  I just reply to the list since I do not want to clutter BZ:
 
  While migrating VMs is easy (and the sampling is already running),
  can
  someone tell me the correct polling port to block with iptables?
 
  Thanks,
  Hi Daniel,
 
  there is indeed a memory profiling patch under discussion:
  http://gerrit.ovirt.org/#/c/32019/
 
  but for your case we'll need a backport to 3.4.x and clearer install
  instructions,
  which I'll prepare as soon as possible.
  I updated the BZ (and are now blocking 54321/tcp on one of my hosts).
  and verified it is not reachable. As  general info: This system I am
  using is my LAB / Test / eval setup for a final deployment for ovirt
  (then 3.5) in production; so it will go away some time in the future (a
  few weeks / months). If I am the only one experiencing this problem
  then
  you might be better of allocating resources elsewhere ;)
  Thanks for your understanding :)
 
  Unfortunately it is true that developer resources aren't so abundant,
  but it is also true that memleaks should never be discarded easily and
  without
  due investigation, considering the nature and the role of VDSM.
 
  So, I'm all in for further investigation regarding this issue.
 
  As for your question: if I understood correctly what you are asking
  (still catching up the thread), if you are trying to rule out the
  stats
  polling
  made by Engine to this bad leak, one simple way to test is just to
  shutdown
  Engine,
  and let VDSMs run unguarded on hypervisors. You'll be able to command
  these
  VDSMs using vdsClient or restarting Engine.
  As I said in my BZ comment this is not an option right now, but if
  understand the matter correctly IPTABLES reject should ultimately do
  the
  same?
  Definitely yes! Just do whatever it is more convenient for you.
 
  As you might have already seen in the BZ comment the leak stopped after
  blocking the port. Though this is clearly no permanent option - please
  let
  me know if I can be of any more assistance!
  The immediate suspect in this situation is M2Crypto. Could you verify
  that by re-opening the firewall and setting ssl=False in vdsm.conf?
 
  You should disable ssl on Engine side and restart both Engine and Vdsm
  (too bad I do not recall how that's done on Engine: Piotr, can you help?).
 
  In vdc_options table there is option EncryptHostCommunication.
 Please confirm the following procedure is correct:
 
 1. Change Postgres table value:
 # sudo -u postgres psql -U postgres engine -c update vdc_options set
 option_value = 'false' where option_name = 'EncryptHostCommunication';
 engine=# SELECT * from vdc_options where
 option_name='EncryptHostCommunication';
  option_id |   option_name| option_value | version
 ---+--+--+-
335 | EncryptHostCommunication | false| general
 (1 row)
 
 2. Restart engine
 3. On the hosts;
 grep ssl /etc/vdsm/vdsm.conf
 #ssl = true
 ssl = false
 
 4. restart VDSM
 
 I assume I have to set 'ssl = false' this on on all hosts?
  Please to set it to false and restart the engine.
 

I believe that you need to update a bit more on vdsm side.
Please follow [1] section Configure ovirt-engine and vdsm to work in 
non-secure mode

There is wrong name of the option and it should

Re: [ovirt-users] Gluster command [UNKNOWN] failed on server

2014-09-15 Thread Piotr Kliczewski
Sahina,

I opened the bug [1] some time ago.

Thanks,
Piotr

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1124481

- Original Message -
From: Sahina Bose sab...@redhat.com
To: Kanagaraj kmayi...@redhat.com, Nathan Stratton nat...@robotics.net, 
knarra kna...@redhat.com
Cc: users users@ovirt.org, Piotr Kliczewski pklic...@redhat.com
Sent: Monday, September 15, 2014 1:57:21 PM
Subject: Re: [ovirt-users] Gluster command [UNKNOWN] failed on server


On 09/15/2014 10:28 AM, Kanagaraj wrote:

 On 09/15/2014 02:24 AM, Nathan Stratton wrote:
 glusterd is running on all hosts and all peers are connected.

 Corresponding error messages in vdsm.log should help here.

 Do you see any command failure messages in vdsm.log or supervdsm.log?


The error seems to be due to the JSON protocol used while installing host.

Can you put the host to Maintenance, and edit the host - uncheck the Use 
JSON protocol, and activate host again?

Piotr, do you know what we are missing here?

thanks
sahina




 On Sunday, September 14, 2014, knarra kna...@redhat.com 
 mailto:kna...@redhat.com wrote:

 On 09/15/2014 12:09 AM, Nathan Stratton wrote:
 I gave up on trying to import my gluster config into ovirt so I
 tried a fresh install and just set the gluster peers without
 creating any volumes. However none of my hosts will activate,
 when I try I get:

 Gluster command [UNKNOWN] failed on server virt01a.

 The only thing I see in vdsm.log is:

 Thread-3542::DEBUG::2014-09-14
 14:35:26,946::__init__::467::jsonrpc.JsonRpcServer::(_serveRequest)
 Calling 'GlusterHost.list' in bridge with {}

 Nothing else, can anyone point me into the right direction on
 how to debug this with so little information?

 
 nathan stratton | vp technology | broadsoft, inc |
 +1-240-404-6580 | www.broadsoft.com http://www.broadsoft.com


 ___
 Users mailing list
 Users@ovirt.org  javascript:_e(%7B%7D,'cvml','Users@ovirt.org');
 http://lists.ovirt.org/mailman/listinfo/users

 Hi Nathan,

 Could you please check if glusterd is running on the hosts
 you are trying to install ? This issue occurs mostly due to
 glusterd being stopped on the nodes. Please start glusterd by
 running the command 'service glusterd start' and try activating
 the hosts.

 Hope this helps.

 Thanks
 kasturi



 -- 

 
 nathan stratton | vp technology | broadsoft, inc | +1-240-404-6580 | 
 www.broadsoft.com http://www.broadsoft.com


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] ODP: ovirt 3.5 rc2 and iscsi error with chap enabled during discovery

2014-09-14 Thread Piotr Kliczewski
Allon,

It looks like we pass more arguments than reqired. Will fix. Please open a bug.


Thanks,
Piotr

div Oryginalna wiadomość /divdivOd: Allon Mureinik 
amure...@redhat.com /divdivData:14.09.2014  09:28  (GMT+01:00) 
/divdivDo: Piotr Kliczewski pklic...@redhat.com /divdivDW: users 
users@ovirt.org,Gianluca Cecchi gianluca.cec...@gmail.com,Oved Ourfali 
ov...@redhat.com /divdivTemat: Re: [ovirt-users] ovirt 3.5 rc2 and iscsi 
error with chap enabled  during discovery /divdiv
/divPiotr, this looks like JSON-RPC mishap.
Can you take a look please?

From: Gianluca Cecchi gianluca.cec...@gmail.com
To: users users@ovirt.org
Sent: Saturday, September 13, 2014 1:15:50 AM
Subject: [ovirt-users] ovirt 3.5 rc2 and iscsi error with chap enabled
during discovery

Hello,
trying to configure iSCSI storage domain.

I have configured a CentOS 6.5 server as sw iSCSI target with chap 
authentication.
port 3260 is open for tcp connections.
I have an oVirt host that is CentOS 6.5 and when trying to discover targets I 
get in /var/log/messages 

Sep 12 23:50:19 ovnode04 vdsm jsonrpc.JsonRpcServer ERROR Internal server 
error#012Traceback (most recent call last):#012  File 
/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py, line 486, in 
_serveRequest#012 res = method(**params)#012  File 
/usr/share/vdsm/rpc/Bridge.py, line 264, in _dynamicMethod#012raise 
InvalidCall(fn, methodArgs, e)#012InvalidCall: Attempt to call function: bound 
method ISCSIConnection.discoverSendTargets of API.ISCSIConnection object at 
0x7f0a48145150 with arguments: (u'iscsiuser', u'iscsipwd') error: 
discoverSendTargets() takes exactly 1 argument (3 given)
Sep 12 23:50:22 ovnode04 vdsm jsonrpc.JsonRpcServer ERROR Internal server 
error#012Traceback (most recent call last):#012  File 
/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py, line 486, in 
_serveRequest#012 res = method(**params)#012  File 
/usr/share/vdsm/rpc/Bridge.py, line 264, in _dynamicMethod#012raise 
InvalidCall(fn, methodArgs, e)#012InvalidCall: Attempt to call function: bound 
method ISCSIConnection.discoverSendTargets of API.ISCSIConnection object at 
0x7f0a480e5ad0 with arguments: (u'iscsiuser', u'iscsipwd') error: 
discoverSendTargets() takes exactly 1 argument (3 given)

screenshot that returns no new devices found is here:
https://drive.google.com/file/d/0BwoPbcrMv8mvbVlycnJCTWJtNXc/edit?usp=sharing

BTW: chap user and password input fields could be wider, so that the whole 
words input can seen on the screen. there is plenty of space... Also password 
field should not be in clear text as it is now

The approach to successfully connect the LUN seems to be:
1) make discovery but with chap unchecked
2) the target then shows up 
see 
https://drive.google.com/file/d/0BwoPbcrMv8mvb1pET3VNMWJuRUk/edit?usp=sharing
3) now check the box for chap authentication and select login all
you now get the luns
https://drive.google.com/file/d/0BwoPbcrMv8mveExRMzN1Z0RtR1k/edit?usp=sharing
4) then select the lun(s) desired and select OK

is this correct? In case I think it should be disabled the chap option during 
discovery phase...
otherwise I have not configured correctly my iscsi target perhaps.
ovirt host network ip is 10.10.1.61

tgtadm --lld iscsi --mode target --op show
Target 1: iqn.2014-07.local.localdomain:store1
System information:
Driver: iscsi
State: ready
I_T nexus information:
I_T nexus: 1
Initiator: iqn.1994-05.com.redhat:5d9b31319a8e
Connection: 0
IP Address: 10.10.1.61
LUN information:
LUN: 0
Type: controller
SCSI ID: IET 0001
SCSI SN: beaf10
Size: 0 MB, Block size: 1
Online: Yes
Removable media: No
Prevent removal: No
Readonly: No
Backing store type: null
Backing store path: None
Backing store flags: 
LUN: 1
Type: disk
SCSI ID: p_iscsi_store1_l
SCSI SN: 6a41
Size: 214738 MB, Block size: 512
Online: Yes
Removable media: No
Prevent removal: No
Readonly: No
Backing store type: rdwr
Backing store path: /dev/drbd/by-res/iscsiha
Backing store flags: 
Account information:
iscsiuser
ACL information:
10.10.1.61
10.10.1.62
10.10.1.63

Gianluca

  

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] info about ovirtmgmt bridge config in master

2014-08-27 Thread Piotr Kliczewski




- Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Gianluca Cecchi gianluca.cec...@gmail.com, pklic...@redhat.com, 
 asegu...@redhat.com
 Cc: users users@ovirt.org
 Sent: Wednesday, August 27, 2014 1:28:41 PM
 Subject: Re: [ovirt-users] info about ovirtmgmt bridge config in master
 
 On Fri, Aug 15, 2014 at 01:01:50PM +0200, Gianluca Cecchi wrote:
  On Fri, Aug 15, 2014 at 12:30 PM, Dan Kenigsberg dan...@redhat.com wrote:
  
  
  
   ifcfg-ovirtmgmt network should be found on disk after a successful
   installation of a host. However, if network configuration phase fails,
   ifcfg files should be reverted to their original values.
  
  
  ok.
  
  
  
   Could you see your super/vdsm.log if that is the case?
   Could you explain when did hypervisor part goes in timeout. Can you
   correlate this to something in vdsm.log?
  
   Dan.
  
  
  So, initial config was no dns and I forgot the /etc/hosts part too.
  So engine-setup complained about hostname input and asked again.
  At this point I filled up /etc/hosts and confirmed hostname in engine-setup
  prompt.
  It complained about dns part but continued.
  As this is an all-in-one setup it arrived at the hypervisor config part.
  It gave in engine-setup output the message about time out in having
  hypervisor host up a few times and at the end
  
  [ INFO  ] Still waiting for VDSM host to become operational...
  [ ERROR ] Timed out while waiting for host to start. Please check the logs.
  
  During these recurring time-out warnings I see in vdsm.log
  Detector thread::ERROR::2014-08-13
  17:48:59,482::protocoldetector::104::vds.MultiProtocolAcceptor::(serve_forever)
  Unhandled exception
  Traceback (most recent call last):
File /usr/share/vdsm/protocoldetector.py, line 100, in serve_forever
  self._process_events()
File /usr/share/vdsm/protocoldetector.py, line 117, in _process_events
  self._accept_connection()
File /usr/share/vdsm/protocoldetector.py, line 180, in
  _accept_connection
  client_socket, _ = self._socket.accept()
File /usr/lib64/python2.6/site-packages/vdsm/sslutils.py, line 121, in
  accept
  raise SSL.SSLError(%s, client %s % (e, address[0]))
  SSLError: unexpected eof, client 192.168.122.51
 
 Gianluca, does this show repeatedly when `vdsClient -s 0 getVdsCaps` is
 called manually?
 
 Piotr, can you guess what may cause this?
 

Having information above it looks like ssl handshake failed or disconnect 
happened
during handshake. How easy it is to reproduce it?


  
  engine-setup went ahead with these messages:
  
  [WARNING] Local storage domain not added because the VDSM host was not up.
  Please add it manually.
  [ INFO  ] Stage: Clean up
Log file is located at
  /var/log/ovirt-engine/setup/ovirt-engine-setup-20140813173448-i47i1l.log
  [ INFO  ] Generating answer file
  '/var/lib/ovirt-engine/setup/answers/20140813174959-setup.conf'
  [ INFO  ] Stage: Pre-termination
  [ INFO  ] Stage: Termination
  [ INFO  ] Execution of setup completed successfully
  
  inside supervdsm.log no error message. See it here:
  https://drive.google.com/file/d/0BwoPbcrMv8mvRVpxR3UzYU9hUmM/edit?usp=sharing
 
 
 I don't think it's anyway related to your problem, but it does require
 Toni comment - supervdsm.log has traces of needless calls
 
 MainThread::DEBUG::2014-08-15
 10:38:02,570::vdsm-restore-net-config::56::root::(unified_restoration)
 Removing all networks ({}) and bonds ({}) in running config.
 
   and
 
 MainThread::DEBUG::2014-08-15
 10:38:02,642::api::640::setupNetworks::(setupNetworks) Setting up network
 according to configuration: networks:{}, bondings:{},
 options:{'_inRollback': True, 'connectivityCheck': False}
 MainThread::DEBUG::2014-08-15 10:38:02,642::api::644::root::(setupNetworks)
 Validating configuration
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [ovirt-devel] oVirt 3.5 beta2 - results

2014-07-30 Thread Piotr Kliczewski
On Wed, Jul 30, 2014 at 8:21 AM, Sahina Bose sab...@redhat.com wrote:
 Piotr,

 Thanks for the test report!


 On 07/29/2014 08:48 PM, Piotr Kliczewski wrote:

 Hi all,

 I tested gluster related features:


 Nagios Integration -
 http://www.ovirt.org/Features/Nagios_Integration#HOW_TO

 I installed Nagios dependencies on f20 which went smoothly but when I
 did the same for rhel6 I noticed that I had to install manually
 additional rpm which was not covered by howto.

 rrdtool-perl-1.3.8-6.el6.x86_64.rpm


 I will retry this and update the How_To




 During discovery of the Nagios server I got following issue:

 [root@rhel gluster]# /usr/lib64/nagios/plugins/gluster/discovery.py -c
 Default -H 192.168.1.9
 Failed to execute NRPE command 'discover_volume_list' in host
 '192.168.1.9'
 Error : Make sure NPRE server in host '192.168.1.9' is configured to
 accept requests from Nagios server


 Did you get this error even after following the step to edit allowed_hosts
 in /etc/nagios/nrpe.cfg?


Modifying nrpe.cfg fixed the issue.




 so I followed http://tecadmin.net/install-nrpe-on-centos-rhel/.

 Nagios server reported status of the cluster. When I had configured
 first nagios server I saw:

 OK : None of the Volumes in the cluster are in Critical State

 but for the second there was:

 (null).


 Do you mean configuring second cluster in the same Nagios server?


I mean that I configured Nagios server twice. Once on the host were I
had installed
gluster and the other one on the server. I wanted to check whether there are any
dependency issues so I tried on f20 and rhel6.



 I followed howto and installed oVirt UI plugin but after restart I was
 not able to see monitoring details tab so I opened:
 https://bugzilla.redhat.com/show_bug.cgi?id=1124371




 Volume performance stats -
 http://www.ovirt.org/Features/Gluster_Volume_Performance_Statistics#HOW_TO

 I reused already existing setup. I enabled stats and added a volume.
 When checking stats details I saw could not fetch stats.

 I wanted to generate some stats so I mount volume previously created
 using:

 mount -t nfs 192.168.1.9:/vol1 /media/volume

 I had to redo it several times do to:

 mount.nfs: requested NFS version or transport protocol is not supported

 After several attempts I lost connectivity to the machine. After host
 recovered I tried to run:

 mount -o mountproto=tcp -t nfs 192.168.1.9:/vol1 /media/volume

 but the result was the same.

 I opened: https://bugzilla.redhat.com/show_bug.cgi?id=1124376


 I checked whether gluster still works with jsonrpc. I removed the host
 that I installed before and added new one using jsonrpc protocol.
 After the installation I noticed that host was moved to Non-Operation
 state. In the logs I found:

 {jsonrpc: 2.0, id: 101bf460-6529-42d6-9370-a9629daad628,
 error: {message: The method does not exist / is not available.,
 code: -32601}}

 I checked what was the reason and there was no apiwrapper.py module so I
 opened:

 https://bugzilla.redhat.com/show_bug.cgi?id=1124481



 Thanks,
 Piotr
 ___
 Devel mailing list
 de...@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] CentOS dependencies on 3.5

2014-07-06 Thread Piotr Kliczewski
Sure

- Original Message -
From: Alon Bar-Lev alo...@redhat.com
To: Piotr Kliczewski pklic...@redhat.com
Cc: users@ovirt.org, Jonathan Archer j...@rosslug.org.uk
Sent: Friday, July 4, 2014 8:50:23 PM
Subject: Re: [ovirt-users] CentOS dependencies on 3.5

Piotr,

Please resolve the snapshot build, per what we discussed:

1. at master you always need to have a version of z+1 than last release with 
_master tag.

2. at snapshots always publish latest build.

This will make the snapshot usable for users.

Thanks,
Alon

- Original Message -
 From: Jonathan Archer j...@rosslug.org.uk
 To: Alon Bar-Lev alo...@redhat.com
 Cc: users@ovirt.org
 Sent: Friday, July 4, 2014 9:45:33 PM
 Subject: Re: [ovirt-users] CentOS dependencies on 3.5
 
 
 On 04/07/2014 16:31, Alon Bar-Lev wrote:
 
  - Original Message -
  From: Jon Archer j...@rosslug.org.uk
  To: users@ovirt.org
  Sent: Friday, July 4, 2014 5:56:59 PM
  Subject: [ovirt-users] CentOS dependencies on 3.5
 
  Hi,
 
  Just tried to run an update to 3.5 beta and i'm seeing dependencies that
  are not satisfied.
 
  Error: Package: vdsm-jsonrpc-java-1.0.0-0.0.master.el6.noarch
  (ovirt-3.5-pre)
   Requires: codehaus-jackson-core-asl
  Error: Package: vdsm-jsonrpc-java-1.0.0-0.0.master.el6.noarch
  (ovirt-3.5-pre)
   Requires: codehaus-jackson-mapper-asl
 
  Any ideas? I've done a bit of googling and not uncovered much. Looking
  at the specfile there seems to be a requirement for jackson, which isn't
  in the C6 repos but does seem to be in the C7 repos.
  this should be fixed in nightly[1] of vdsm-jsonrpc-java.
 
  [1] http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el6/noarch/
 
 Not seeing any newer version of vdsm-jsonrpc-java in that repo nor
 when enabling the ovirt-master repos in yum.
 
 Jon
  Thanks
 
  Jon
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Installing all in one ovirt server

2014-03-06 Thread Piotr Kliczewski
I am testing all-in-one as well and noticed that for local data center
I can only created data domain. Iso and export domains can only be
imported.

Is it by design?

During creation of local data domain it fails with permission error
but it runs successfully second time (I tried twice).

Piotr

On Thu, Mar 6, 2014 at 12:03 PM, Sven Kieske s.kie...@mittwald.de wrote:
 I'll take this as an opportunity to ask some questions:
 if and under what circumstances can the default DC
 be safely removed if you do not use it?

 Or can't you delete it, would it break something (what)?

 Why is there a default DC in the first place?

 Am 06.03.2014 11:54, schrieb Yedidyah Bar David:
 From: Andy Michielsen andy.michiel...@gmail.com
 To: users@ovirt.org
 Sent: Wednesday, March 5, 2014 6:23:33 PM
 Subject: [Users] Installing all in one ovirt server

 Hello,

 I just finnished installing a new ovirt all in one installation and I 
 noticed
 that I have 2 datacenters.

 A default one and a local_datacenter. I don't understand why I have 2
 datacenters but I suppose I can delete one.

 Default is always created. Normal setups start with just it, and others can 
 be created if needed.

 local_datacenter is all-in-one-specific - you were asked about it during 
 setup - name, location etc.
 It's local in that it uses a local directory on the host, so VMs on it 
 cannot be migrated to other
 hosts if/when you add them.

 --
 Mit freundlichen Grüßen / Regards

 Sven Kieske

 Systemadministrator
 Mittwald CM Service GmbH  Co. KG
 Königsberger Straße 6
 32339 Espelkamp
 T: +49-5772-293-100
 F: +49-5772-293-333
 https://www.mittwald.de
 Geschäftsführer: Robert Meyer
 St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
 Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Installing all in one ovirt server

2014-03-06 Thread Piotr Kliczewski
I am not sure whether this is all-in-one related but I am not able to
open spice console due to: Unable to connect to the graphic server.

I wanted to check the same from virt-manager and I got: viewer
connection to hypervisor host got refused or disconnected.

Piotr

On Thu, Mar 6, 2014 at 12:24 PM, Piotr Kliczewski
piotr.kliczew...@gmail.com wrote:
 I am testing all-in-one as well and noticed that for local data center
 I can only created data domain. Iso and export domains can only be
 imported.

 Is it by design?

 During creation of local data domain it fails with permission error
 but it runs successfully second time (I tried twice).

 Piotr

 On Thu, Mar 6, 2014 at 12:03 PM, Sven Kieske s.kie...@mittwald.de wrote:
 I'll take this as an opportunity to ask some questions:
 if and under what circumstances can the default DC
 be safely removed if you do not use it?

 Or can't you delete it, would it break something (what)?

 Why is there a default DC in the first place?

 Am 06.03.2014 11:54, schrieb Yedidyah Bar David:
 From: Andy Michielsen andy.michiel...@gmail.com
 To: users@ovirt.org
 Sent: Wednesday, March 5, 2014 6:23:33 PM
 Subject: [Users] Installing all in one ovirt server

 Hello,

 I just finnished installing a new ovirt all in one installation and I 
 noticed
 that I have 2 datacenters.

 A default one and a local_datacenter. I don't understand why I have 2
 datacenters but I suppose I can delete one.

 Default is always created. Normal setups start with just it, and others can 
 be created if needed.

 local_datacenter is all-in-one-specific - you were asked about it during 
 setup - name, location etc.
 It's local in that it uses a local directory on the host, so VMs on it 
 cannot be migrated to other
 hosts if/when you add them.

 --
 Mit freundlichen Grüßen / Regards

 Sven Kieske

 Systemadministrator
 Mittwald CM Service GmbH  Co. KG
 Königsberger Straße 6
 32339 Espelkamp
 T: +49-5772-293-100
 F: +49-5772-293-333
 https://www.mittwald.de
 Geschäftsführer: Robert Meyer
 St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
 Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


  1   2   >