subject:"\[ovirt\-users\] Unknown libvirterror \- where to start\?"

[ovirt-users] Unknown libvirterror - where to start?

2015-11-02 Thread Christophe TREFOIS

Hi,

I checked the logs on my hypervisor that contains also the overt-engine 
(self-hosted) and I see strange unknown libvirterrors that come periodically in 
the vdsm.log file. The storage is glusterFS running on the hypervisor as well, 
one NFS export domain and an ISO domain. A NFS domain from another place is in 
maintenance mode.

I am running oVirt 3.5.3.

Thank you for any pointers as to where to start fixing this issue.

— log excerpt --

Thread-1947641::DEBUG::2015-11-03 
08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
Thread-8108::DEBUG::2015-11-03 
08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata 
element is not present
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) dd 
if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox 
iflag=direct,fullblock count=1 bs=1024000 (cwd None)
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB) 
copied, 0.00331278 s, 309 MB/s\n';  = 0
Thread-7913::DEBUG::2015-11-03 
08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata 
element is not present
Thread-5682::DEBUG::2015-11-03 
08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata 
element is not present
Detector thread::DEBUG::2015-11-03 
08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
 Adding connection from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
 Connection removed from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
 Detected protocol xml from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml over http 
detected from ('127.0.0.1', 44671)
Thread-1947642::DEBUG::2015-11-03 
08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init -> state 
preparing
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect: 
repoStats(options=None)
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect: repoStats, 
Return response: {u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 
'actual': True, 'version': 0, 'acquired': True, 'delay': '0.000373613', 
'lastCheck': '2.5', 'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': 
{'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay': 
'0.000409446', 'lastCheck': '6.4', 'valid': True}, 
u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0, 'actual': True, 'version': 
3, 'acquired': True, 'delay': '0.000520671', 'lastCheck': '1.8', 'valid': 
True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0, 'actual': True, 
'version': 3, 'acquired': True, 'delay': '0.000424445', 'lastCheck': '6.5', 
'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished: 
{u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': True, 
'version': 0, 'acquired': True, 'delay': '0.000373613', 'lastCheck': '2.5', 
'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': 
True, 'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': 
'6.4', 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0, 
'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000520671', 
'lastCheck': '1.8', 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': 
{'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay': 
'0.000424445', 'lastCheck': '6.5', 'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state preparing -> 
state finished
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll) 
Owner.releaseAll requests {} resources {}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::resourceManager::977::Storage.ResourceManager.Owner::(cancelAll) 
Owner.cancelAll requests {}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::task::993::Storage.TaskManager.Task::(_decref) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::ref 0 aborting False
Thread-6348::DEBUG::2015-11-03 
08:47:33,261::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 mess

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-03 Thread Sahina Bose

Could you also attach the glusterfs and gluster mount logs from the 
hypervisor? (Logs would be at /var/log/glusterfs)


On 11/03/2015 01:22 PM, Christophe TREFOIS wrote:

Hi,

I checked the logs on my hypervisor that contains also the 
overt-engine (self-hosted) and I see strange unknown libvirterrors 
that come periodically in the vdsm.log file. The storage is glusterFS 
running on the hypervisor as well, one NFS export domain and an ISO 
domain. A NFS domain from another place is in maintenance mode.


I am running oVirt 3.5.3.

Thank you for any pointers as to where to start fixing this issue.

— log excerpt --

Thread-1947641::DEBUG::2015-11-03 
08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending 
response
Thread-8108::DEBUG::2015-11-03 
08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown 
libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not found: 
Requested metadata element is not present
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
dd 
if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox 
iflag=direct,fullblock count=1 bs=1024000 (cwd None)
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 
MB) copied, 0.00331278 s, 309 MB/s\n';  = 0
Thread-7913::DEBUG::2015-11-03 
08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown 
libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not found: 
Requested metadata element is not present
Thread-5682::DEBUG::2015-11-03 
08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown 
libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not found: 
Requested metadata element is not present
Detector thread::DEBUG::2015-11-03 
08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) 
Adding connection from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) 
Connection removed from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read) 
Detected protocol xml from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml 
over http detected from ('127.0.0.1', 44671)
Thread-1947642::DEBUG::2015-11-03 
08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init -> 
state preparing
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect: 
repoStats(options=None)
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect: 
repoStats, Return response: {u'de9eb737-691f-4622-9070-891531d599a0': 
{'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay': 
'0.000373613', 'lastCheck': '2.5', 'valid': True}, 
u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': True, 
'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': 
'6.4', 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': 
{'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay': 
'0.000520671', 'lastCheck': '1.8', 'valid': True}, 
'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0, 'actual': True, 
'version': 3, 'acquired': True, 'delay': '0.000424445', 'lastCheck': 
'6.5', 'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished: 
{u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': True, 
'version': 0, 'acquired': True, 'delay': '0.000373613', 'lastCheck': 
'2.5', 'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': 
{'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay': 
'0.000409446', 'lastCheck': '6.4', 'valid': True}, 
u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0, 'actual': True, 
'version': 3, 'acquired': True, 'delay': '0.000520671', 'lastCheck': 
'1.8', 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': 
{'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay': 
'0.000424445', 'lastCheck': '6.5', 'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state 
preparing -> state finished
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll) 
Owner.releaseAll requests {} resources {}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::resourceManager::977::Storage.ResourceManager.Owner::(cancelAll) 
Owner.cancelAll requests {}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::task::993::Storage.TaskManager.Task::(_decref) 
Task=`1d99a166-cb9a-4025-8211-

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-03 Thread Yaniv Kaul

On Tue, Nov 3, 2015 at 9:52 AM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:

> Hi,
>
> I checked the logs on my hypervisor that contains also the overt-engine
> (self-hosted) and I see strange unknown libvirterrors that come
> periodically in the vdsm.log file. The storage is glusterFS running on the
> hypervisor as well, one NFS export domain and an ISO domain. A NFS domain
> from another place is in maintenance mode.
>
> I am running oVirt 3.5.3.
>
> Thank you for any pointers as to where to start fixing this issue.
>
> — log excerpt --
>
> Thread-1947641::DEBUG::2015-11-03
> 08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending
> response
> Thread-8108::DEBUG::2015-11-03
> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
> element is not present
>

This (depending on your host OS version, 6.x or 7.x) is either
https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
https://bugzilla.redhat.com/show_bug.cgi?id=1260864
Y.

Dummy-1895260::DEBUG::2015-11-03
> 08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) dd
> if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox
> iflag=direct,fullblock count=1 bs=1024000 (cwd None)
> Dummy-1895260::DEBUG::2015-11-03
> 08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail)
> SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB)
> copied, 0.00331278 s, 309 MB/s\n';  = 0
> Thread-7913::DEBUG::2015-11-03
> 08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
> element is not present
> Thread-5682::DEBUG::2015-11-03
> 08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
> element is not present
> Detector thread::DEBUG::2015-11-03
> 08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
> Adding connection from 127.0.0.1:44671
> Detector thread::DEBUG::2015-11-03
> 08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
> Connection removed from 127.0.0.1:44671
> Detector thread::DEBUG::2015-11-03
> 08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
> Detected protocol xml from 127.0.0.1:44671
> Detector thread::DEBUG::2015-11-03
> 08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml over
> http detected from ('127.0.0.1', 44671)
> Thread-1947642::DEBUG::2015-11-03
> 08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState)
> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init ->
> state preparing
> Thread-1947642::INFO::2015-11-03
> 08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect:
> repoStats(options=None)
> Thread-1947642::INFO::2015-11-03
> 08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect:
> repoStats, Return response: {u'de9eb737-691f-4622-9070-891531d599a0':
> {'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay':
> '0.000373613', 'lastCheck': '2.5', 'valid': True},
> u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': True,
> 'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': '6.4',
> 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0,
> 'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000520671',
> 'lastCheck': '1.8', 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066':
> {'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay':
> '0.000424445', 'lastCheck': '6.5', 'valid': True}}
> Thread-1947642::DEBUG::2015-11-03
> 08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare)
> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished:
> {u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': True,
> 'version': 0, 'acquired': True, 'delay': '0.000373613', 'lastCheck': '2.5',
> 'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0,
> 'actual': True, 'version': 0, 'acquired': True, 'delay': '0.000409446',
> 'lastCheck': '6.4', 'valid': True},
> u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0, 'actual': True,
> 'version': 3, 'acquired': True, 'delay': '0.000520671', 'lastCheck': '1.8',
> 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0,
> 'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000424445',
> 'lastCheck': '6.5', 'valid': True}}
> Thread-1947642::DEBUG::2015-11-03
> 08:47:32,603::task::595::Storage.TaskManager.Task::(_updateState)
> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state preparing ->
> state finished
> Thread-1947642::DEBUG::2015-11-03
> 08:47:32,604::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll)
> Owner.releaseAll requests {} resources {}
> Thread-1947642::DEBUG::2015-11-03
> 08:47:32,604::resourceManager::977:

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-03 Thread Christophe TREFOIS

Dear Sahina,

I attached the logs from the glusterfs folder.


thank you for your help,

Kind regards,

—
Christophe


On 03 Nov 2015, at 09:04, Sahina Bose 
mailto:sab...@redhat.com>> wrote:

Could you also attach the glusterfs and gluster mount logs from the hypervisor? 
(Logs would be at /var/log/glusterfs)

On 11/03/2015 01:22 PM, Christophe TREFOIS wrote:
Hi,

I checked the logs on my hypervisor that contains also the overt-engine 
(self-hosted) and I see strange unknown libvirterrors that come periodically in 
the vdsm.log file. The storage is glusterFS running on the hypervisor as well, 
one NFS export domain and an ISO domain. A NFS domain from another place is in 
maintenance mode.

I am running oVirt 3.5.3.

Thank you for any pointers as to where to start fixing this issue.

— log excerpt --

Thread-1947641::DEBUG::2015-11-03 
08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
Thread-8108::DEBUG::2015-11-03 
08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata 
element is not present
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) dd 
if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox 
iflag=direct,fullblock count=1 bs=1024000 (cwd None)
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB) 
copied, 0.00331278 s, 309 MB/s\n';  = 0
Thread-7913::DEBUG::2015-11-03 
08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata 
element is not present
Thread-5682::DEBUG::2015-11-03 
08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata 
element is not present
Detector thread::DEBUG::2015-11-03 
08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
 Adding connection from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
 Connection removed from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
 Detected protocol xml from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml over http 
detected from ('127.0.0.1', 44671)
Thread-1947642::DEBUG::2015-11-03 
08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init -> state 
preparing
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect: 
repoStats(options=None)
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect: repoStats, 
Return response: {u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 
'actual': True, 'version': 0, 'acquired': True, 'delay': '0.000373613', 
'lastCheck': '2.5', 'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': 
{'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay': 
'0.000409446', 'lastCheck': '6.4', 'valid': True}, 
u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0, 'actual': True, 'version': 
3, 'acquired': True, 'delay': '0.000520671', 'lastCheck': '1.8', 'valid': 
True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0, 'actual': True, 
'version': 3, 'acquired': True, 'delay': '0.000424445', 'lastCheck': '6.5', 
'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished: 
{u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': True, 
'version': 0, 'acquired': True, 'delay': '0.000373613', 'lastCheck': '2.5', 
'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': 
True, 'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': 
'6.4', 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0, 
'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000520671', 
'lastCheck': '1.8', 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': 
{'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay': 
'0.000424445', 'lastCheck': '6.5', 'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state preparing -> 
state finished
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll) 
Owner.releaseAll requests {} resources {}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,604::resourceManager::977::Storage.Resou

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-03 Thread Sven Kieske

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 03/11/15 09:30, Yaniv Kaul wrote:
> This (depending on your host OS version, 6.x or 7.x) is either 
> https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or 
> https://bugzilla.redhat.com/show_bug.cgi?id=1260864 Y.

Those bugs are marked as private and thus can't be displayed by mere
mortals.

- -- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +495772 293100
F: +495772 29
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhaus
en
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
Oeynhausen
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJWOLmsAAoJEMby9TMDAbQRbeYP/0mOi74azrEPhp46juxpMZc3
vzZ7ciftMtsln86rKTuQGBUcJ0Sqb0RBWZ8bsDex9+Ngx9rTiwpDwfzWxV5zmraa
9SFnsw3pz1nL/C2swTQQEfN2uq54U6WEvPlyW0dlDwrlKsVRtD7qQka81aspZHA/
PPCej64mRSKUnP4c0s8sDfzNyzEdJW75x67kksP7FNZSuYDRO6qk3ciLbRV21vBi
A6Rp54Tedw/2y+zra7KqkRzP4DwiL55k0/5FAxssSw0hoeRzjHCf4Y6wiScXBtRK
Naocwp+LL/0LgvtVfbS5CGTGvPGmpqCjb4uLWWXIIhnAaZ3AB4XNFKctOKqE3DMj
qp+m5+vgzhNqyQbdQuiGIP64nesuI3z16ov03pjqxZGZvszyLCT8+cRAzI5vhBIb
5CiWors+az9buraLOfXiuZNHrawpvP+h/q3o/a974c3CvJ2U8ZiPIhg21cxpziP4
Xi9z1PoAbghoEwceVas5+t04rPHIqgL2k7SowyU3wDFD8cfWTd0b1fics5ryoR7g
CEjJIT3hRmc2/TT2wZoxmp60WYwTH3n2bRKiCdZM3V0lO/3XOL6EL3qPYp4qX8Xl
k3yj5zqugkuM5efXlr5I7NIQkNQD1KWvB/QjhWzFaSq2HJ9C2XiHV003DmgoPfkH
GkwO4mp9RF1f126JHNCG
=QtoB
-END PGP SIGNATURE-
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-03 Thread Yaniv Kaul

On Tue, Nov 3, 2015 at 3:42 PM, Sven Kieske  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/11/15 09:30, Yaniv Kaul wrote:
> > This (depending on your host OS version, 6.x or 7.x) is either
> > https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
>

*Bug 1220474*  - libvirt:
Error 'metadata not found: Requested metadata element is not present'
flooding journal
Fixed in libvirt 1.2.16, for RHEL 7.2.


> > https://bugzilla.redhat.com/show_bug.cgi?id=1260864 Y.
>

*Bug 1260864*  - libvirt:
Error 'metadata not found: Requested metadata element is not present'
flooding journal
Fixed in libvirt 1.2.16, for RHEL 6.8.


>
> Those bugs are marked as private and thus can't be displayed by mere
> mortals.
>

My apologies.
Upstream fix:

commit ecc997fd43b1b1987dadb45fb0ef987d56638476
Author: Peter Krempa 
Date:   Tue May 12 13:55:30 2015 +0200

daemon: Suppress logging of VIR_ERR_NO_DOMAIN_METADATA

 Y.


> - --
> Mit freundlichen Grüßen / Regards
>
> Sven Kieske
>
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +495772 293100
> F: +495772 29
> https://www.mittwald.de
> Geschäftsführer: Robert Meyer
> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhaus
> en
> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
> Oeynhausen
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBAgAGBQJWOLmsAAoJEMby9TMDAbQRbeYP/0mOi74azrEPhp46juxpMZc3
> vzZ7ciftMtsln86rKTuQGBUcJ0Sqb0RBWZ8bsDex9+Ngx9rTiwpDwfzWxV5zmraa
> 9SFnsw3pz1nL/C2swTQQEfN2uq54U6WEvPlyW0dlDwrlKsVRtD7qQka81aspZHA/
> PPCej64mRSKUnP4c0s8sDfzNyzEdJW75x67kksP7FNZSuYDRO6qk3ciLbRV21vBi
> A6Rp54Tedw/2y+zra7KqkRzP4DwiL55k0/5FAxssSw0hoeRzjHCf4Y6wiScXBtRK
> Naocwp+LL/0LgvtVfbS5CGTGvPGmpqCjb4uLWWXIIhnAaZ3AB4XNFKctOKqE3DMj
> qp+m5+vgzhNqyQbdQuiGIP64nesuI3z16ov03pjqxZGZvszyLCT8+cRAzI5vhBIb
> 5CiWors+az9buraLOfXiuZNHrawpvP+h/q3o/a974c3CvJ2U8ZiPIhg21cxpziP4
> Xi9z1PoAbghoEwceVas5+t04rPHIqgL2k7SowyU3wDFD8cfWTd0b1fics5ryoR7g
> CEjJIT3hRmc2/TT2wZoxmp60WYwTH3n2bRKiCdZM3V0lO/3XOL6EL3qPYp4qX8Xl
> k3yj5zqugkuM5efXlr5I7NIQkNQD1KWvB/QjhWzFaSq2HJ9C2XiHV003DmgoPfkH
> GkwO4mp9RF1f126JHNCG
> =QtoB
> -END PGP SIGNATURE-
> ___
> 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] Unknown libvirterror - where to start?

2015-11-04 Thread Sahina Bose

Ok, so the mount logs do not have any errors - only messages regarding 
dir creation and file renames.


Yaniv's already answered regarding the log messages.

On 11/03/2015 06:14 PM, Christophe TREFOIS wrote:

Dear Sahina,

I attached the logs from the glusterfs folder.


thank you for your help,

Kind regards,

—
Christophe

On 03 Nov 2015, at 09:04, Sahina Bose > wrote:


Could you also attach the glusterfs and gluster mount logs from the 
hypervisor? (Logs would be at /var/log/glusterfs)


On 11/03/2015 01:22 PM, Christophe TREFOIS wrote:

Hi,

I checked the logs on my hypervisor that contains also the 
overt-engine (self-hosted) and I see strange unknown libvirterrors 
that come periodically in the vdsm.log file. The storage is 
glusterFS running on the hypervisor as well, one NFS export domain 
and an ISO domain. A NFS domain from another place is in maintenance 
mode.


I am running oVirt 3.5.3.

Thank you for any pointers as to where to start fixing this issue.

— log excerpt --

Thread-1947641::DEBUG::2015-11-03 
08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) 
Sending response
Thread-8108::DEBUG::2015-11-03 
08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown 
libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not 
found: Requested metadata element is not present
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
dd 
if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox 
iflag=direct,fullblock count=1 bs=1024000 (cwd None)
Dummy-1895260::DEBUG::2015-11-03 
08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes 
(1.0 MB) copied, 0.00331278 s, 309 MB/s\n';  = 0
Thread-7913::DEBUG::2015-11-03 
08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown 
libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not 
found: Requested metadata element is not present
Thread-5682::DEBUG::2015-11-03 
08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown 
libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not 
found: Requested metadata element is not present
Detector thread::DEBUG::2015-11-03 
08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) 
Adding connection from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) 
Connection removed from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read) 
Detected protocol xml from 127.0.0.1:44671
Detector thread::DEBUG::2015-11-03 
08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml 
over http detected from ('127.0.0.1', 44671)
Thread-1947642::DEBUG::2015-11-03 
08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init 
-> state preparing
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect: 
repoStats(options=None)
Thread-1947642::INFO::2015-11-03 
08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect: 
repoStats, Return response: 
{u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': 
True, 'version': 0, 'acquired': True, 'delay': '0.000373613', 
'lastCheck': '2.5', 'valid': True}, 
u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': True, 
'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': 
'6.4', 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': 
{'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay': 
'0.000520671', 'lastCheck': '1.8', 'valid': True}, 
'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0, 'actual': True, 
'version': 3, 'acquired': True, 'delay': '0.000424445', 'lastCheck': 
'6.5', 'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished: 
{u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': 
True, 'version': 0, 'acquired': True, 'delay': '0.000373613', 
'lastCheck': '2.5', 'valid': True}, 
u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': True, 
'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': 
'6.4', 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': 
{'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay': 
'0.000520671', 'lastCheck': '1.8', 'valid': True}, 
'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0, 'actual': True, 
'version': 3, 'acquired': True, 'delay': '0.000424445', 'lastCheck': 
'6.5', 'valid': True}}
Thread-1947642::DEBUG::2015-11-03 
08:47:32,603::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state 
preparing -> state finished
Thread-1947642::DEBUG:

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-06 Thread Nir Soffer

On Tue, Nov 3, 2015 at 10:30 AM, Yaniv Kaul  wrote:
> On Tue, Nov 3, 2015 at 9:52 AM, Christophe TREFOIS
>  wrote:
>>
>> Hi,
>>
>> I checked the logs on my hypervisor that contains also the overt-engine
>> (self-hosted) and I see strange unknown libvirterrors that come periodically
>> in the vdsm.log file. The storage is glusterFS running on the hypervisor as
>> well, one NFS export domain and an ISO domain. A NFS domain from another
>> place is in maintenance mode.
>>
>> I am running oVirt 3.5.3.
>>
>> Thank you for any pointers as to where to start fixing this issue.
>>
>> — log excerpt --
>>
>> Thread-1947641::DEBUG::2015-11-03
>> 08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending
>> response
>> Thread-8108::DEBUG::2015-11-03
>> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
>> element is not present
>
>
> This (depending on your host OS version, 6.x or 7.x) is either
> https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
> https://bugzilla.redhat.com/show_bug.cgi?id=1260864
> Y.

The error about missing metadata is just noise in the log, nothing to
worry about.

Adding Martin

>
>> Dummy-1895260::DEBUG::2015-11-03
>> 08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) dd
>> if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox
>> iflag=direct,fullblock count=1 bs=1024000 (cwd None)
>> Dummy-1895260::DEBUG::2015-11-03
>> 08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail)
>> SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB)
>> copied, 0.00331278 s, 309 MB/s\n';  = 0
>> Thread-7913::DEBUG::2015-11-03
>> 08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
>> element is not present
>> Thread-5682::DEBUG::2015-11-03
>> 08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
>> element is not present
>> Detector thread::DEBUG::2015-11-03
>> 08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
>> Adding connection from 127.0.0.1:44671
>> Detector thread::DEBUG::2015-11-03
>> 08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
>> Connection removed from 127.0.0.1:44671
>> Detector thread::DEBUG::2015-11-03
>> 08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
>> Detected protocol xml from 127.0.0.1:44671
>> Detector thread::DEBUG::2015-11-03
>> 08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml over http
>> detected from ('127.0.0.1', 44671)
>> Thread-1947642::DEBUG::2015-11-03
>> 08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState)
>> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init -> state
>> preparing
>> Thread-1947642::INFO::2015-11-03
>> 08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect:
>> repoStats(options=None)
>> Thread-1947642::INFO::2015-11-03
>> 08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect:
>> repoStats, Return response: {u'de9eb737-691f-4622-9070-891531d599a0':
>> {'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay':
>> '0.000373613', 'lastCheck': '2.5', 'valid': True},
>> u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': True,
>> 'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': '6.4',
>> 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0,
>> 'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000520671',
>> 'lastCheck': '1.8', 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066':
>> {'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay':
>> '0.000424445', 'lastCheck': '6.5', 'valid': True}}
>> Thread-1947642::DEBUG::2015-11-03
>> 08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare)
>> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished:
>> {u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': True,
>> 'version': 0, 'acquired': True, 'delay': '0.000373613', 'lastCheck': '2.5',
>> 'valid': True}, u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0,
>> 'actual': True, 'version': 0, 'acquired': True, 'delay': '0.000409446',
>> 'lastCheck': '6.4', 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383':
>> {'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay':
>> '0.000520671', 'lastCheck': '1.8', 'valid': True},
>> 'b18eb29e-8bb1-45b9-a60e-a8e07210e066': {'code': 0, 'actual': True,
>> 'version': 3, 'acquired': True, 'delay': '0.000424445', 'lastCheck': '6.5',
>> 'valid': True}}
>> Thread-1947642::DEBUG::2015-11-03
>> 08:47:32,603::task::595::Storage.TaskManager.Task::(_updateState)
>> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state preparing ->
>> state finished
>> Threa

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-06 Thread Christophe TREFOIS

Dear Nir,

Thank you for your help. I shall ignore the messages then :)

Kind regards,

—
Christophe

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
http://www.uni.lu/lcsb




This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  

> On 06 Nov 2015, at 12:23, Nir Soffer  wrote:
> 
> On Tue, Nov 3, 2015 at 10:30 AM, Yaniv Kaul  wrote:
>> On Tue, Nov 3, 2015 at 9:52 AM, Christophe TREFOIS
>>  wrote:
>>> 
>>> Hi,
>>> 
>>> I checked the logs on my hypervisor that contains also the overt-engine
>>> (self-hosted) and I see strange unknown libvirterrors that come periodically
>>> in the vdsm.log file. The storage is glusterFS running on the hypervisor as
>>> well, one NFS export domain and an ISO domain. A NFS domain from another
>>> place is in maintenance mode.
>>> 
>>> I am running oVirt 3.5.3.
>>> 
>>> Thank you for any pointers as to where to start fixing this issue.
>>> 
>>> — log excerpt --
>>> 
>>> Thread-1947641::DEBUG::2015-11-03
>>> 08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending
>>> response
>>> Thread-8108::DEBUG::2015-11-03
>>> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
>>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
>>> element is not present
>> 
>> 
>> This (depending on your host OS version, 6.x or 7.x) is either
>> https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
>> https://bugzilla.redhat.com/show_bug.cgi?id=1260864
>> Y.
> 
> The error about missing metadata is just noise in the log, nothing to
> worry about.
> 
> Adding Martin
> 
>> 
>>> Dummy-1895260::DEBUG::2015-11-03
>>> 08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) dd
>>> if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox
>>> iflag=direct,fullblock count=1 bs=1024000 (cwd None)
>>> Dummy-1895260::DEBUG::2015-11-03
>>> 08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail)
>>> SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB)
>>> copied, 0.00331278 s, 309 MB/s\n';  = 0
>>> Thread-7913::DEBUG::2015-11-03
>>> 08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
>>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
>>> element is not present
>>> Thread-5682::DEBUG::2015-11-03
>>> 08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
>>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
>>> element is not present
>>> Detector thread::DEBUG::2015-11-03
>>> 08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
>>> Adding connection from 127.0.0.1:44671
>>> Detector thread::DEBUG::2015-11-03
>>> 08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
>>> Connection removed from 127.0.0.1:44671
>>> Detector thread::DEBUG::2015-11-03
>>> 08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
>>> Detected protocol xml from 127.0.0.1:44671
>>> Detector thread::DEBUG::2015-11-03
>>> 08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml over http
>>> detected from ('127.0.0.1', 44671)
>>> Thread-1947642::DEBUG::2015-11-03
>>> 08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState)
>>> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init -> state
>>> preparing
>>> Thread-1947642::INFO::2015-11-03
>>> 08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect:
>>> repoStats(options=None)
>>> Thread-1947642::INFO::2015-11-03
>>> 08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect:
>>> repoStats, Return response: {u'de9eb737-691f-4622-9070-891531d599a0':
>>> {'code': 0, 'actual': True, 'version': 0, 'acquired': True, 'delay':
>>> '0.000373613', 'lastCheck': '2.5', 'valid': True},
>>> u'fe4fd19a-8714-44e0-ae41-663a4b62da7a': {'code': 0, 'actual': True,
>>> 'version': 0, 'acquired': True, 'delay': '0.000409446', 'lastCheck': '6.4',
>>> 'valid': True}, u'8253a89b-651e-4ff4-865b-57adef05d383': {'code': 0,
>>> 'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000520671',
>>> 'lastCheck': '1.8', 'valid': True}, 'b18eb29e-8bb1-45b9-a60e-a8e07210e066':
>>> {'code': 0, 'actual': True, 'version': 3, 'acquired': True, 'delay':
>>> '0.000424445', 'lastCheck': '6.5', 'valid': True}}
>>> Thread-1947642::DEBUG::2015-11-03
>>> 08:47:32,603::task::1191::Storage.TaskManager.Task::(prepare)
>>> Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::finished:
>>> {u'de9eb737-691f-4622-9070-891531d599a0': {'code': 0, 'actual': True,
>>> 'version': 0, 'acqui

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-06 Thread Martin Sivak

Hi,

> Thread-8108::DEBUG::2015-11-03 
> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
> ecode: 80 edom: 20 level: 2
> message: metadata not found: Requested metadata element is not present

we fixed this on vdsm side of oVirt 3.6 too:

https://gerrit.ovirt.org/#/c/45799/

But Nir is correct. This was just noise, it went away when any QoS was
defined for the VM and was not important otherwise.

> > VM Channels Listener::DEBUG::2015-11-03 
> > 08:47:34,386::vmchannels::96::vds::(_handle_timeouts) Timeout on fileno 125.
> We've seen this as well. I don't think there's a specific bug filed on this 
> issue. I wonder if they related.

No relation to the metadata log messages. Can't help here.

Best regards

--
Martin Sivak
SLA / oVirt


On Fri, Nov 6, 2015 at 1:14 PM, Christophe TREFOIS
 wrote:
> Dear Nir,
>
> Thank you for your help. I shall ignore the messages then :)
>
> Kind regards,
>
> —
> Christophe
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124
> F: +352 46 66 44 6949
> http://www.uni.lu/lcsb
>
>
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the 
> original message and any copies.
> 
>
>
>
>> On 06 Nov 2015, at 12:23, Nir Soffer  wrote:
>>
>> On Tue, Nov 3, 2015 at 10:30 AM, Yaniv Kaul  wrote:
>>> On Tue, Nov 3, 2015 at 9:52 AM, Christophe TREFOIS
>>>  wrote:

 Hi,

 I checked the logs on my hypervisor that contains also the overt-engine
 (self-hosted) and I see strange unknown libvirterrors that come 
 periodically
 in the vdsm.log file. The storage is glusterFS running on the hypervisor as
 well, one NFS export domain and an ISO domain. A NFS domain from another
 place is in maintenance mode.

 I am running oVirt 3.5.3.

 Thank you for any pointers as to where to start fixing this issue.

 — log excerpt --

 Thread-1947641::DEBUG::2015-11-03
 08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending
 response
 Thread-8108::DEBUG::2015-11-03
 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
 ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
 element is not present
>>>
>>>
>>> This (depending on your host OS version, 6.x or 7.x) is either
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1260864
>>> Y.
>>
>> The error about missing metadata is just noise in the log, nothing to
>> worry about.
>>
>> Adding Martin
>>
>>>
 Dummy-1895260::DEBUG::2015-11-03
 08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) dd
 if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox
 iflag=direct,fullblock count=1 bs=1024000 (cwd None)
 Dummy-1895260::DEBUG::2015-11-03
 08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail)
 SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB)
 copied, 0.00331278 s, 309 MB/s\n';  = 0
 Thread-7913::DEBUG::2015-11-03
 08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
 ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
 element is not present
 Thread-5682::DEBUG::2015-11-03
 08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown libvirterror:
 ecode: 80 edom: 20 level: 2 message: metadata not found: Requested metadata
 element is not present
 Detector thread::DEBUG::2015-11-03
 08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
 Adding connection from 127.0.0.1:44671
 Detector thread::DEBUG::2015-11-03
 08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
 Connection removed from 127.0.0.1:44671
 Detector thread::DEBUG::2015-11-03
 08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
 Detected protocol xml from 127.0.0.1:44671
 Detector thread::DEBUG::2015-11-03
 08:47:32,599::BindingXMLRPC::1173::XmlDetector::(handleSocket) xml over 
 http
 detected from ('127.0.0.1', 44671)
 Thread-1947642::DEBUG::2015-11-03
 08:47:32,602::task::595::Storage.TaskManager.Task::(_updateState)
 Task=`1d99a166-cb9a-4025-8211-a48e210b5234`::moving from state init -> 
 state
 preparing
 Thread-1947642::INFO::2015-11-03
 08:47:32,603::logUtils::44::dispatcher::(wrapper) Run and protect:
 repoStats(options=None)
 Thread-1947642::INFO::2015-11-03
 08:47:32,603::logUtils::47::dispatcher::(wrapper) Run and protect:
 repoStats, Return resp

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-11-06 Thread Michal Skrivanek


> On 06 Nov 2015, at 13:35, Martin Sivak  wrote:
> 
> Hi,
> 
>> Thread-8108::DEBUG::2015-11-03 
>> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown libvirterror: 
>> ecode: 80 edom: 20 level: 2
>> message: metadata not found: Requested metadata element is not present
> 
> we fixed this on vdsm side of oVirt 3.6 too:
> 
> https://gerrit.ovirt.org/#/c/45799/
> 
> But Nir is correct. This was just noise, it went away when any QoS was
> defined for the VM and was not important otherwise.
> 
>>> VM Channels Listener::DEBUG::2015-11-03 
>>> 08:47:34,386::vmchannels::96::vds::(_handle_timeouts) Timeout on fileno 125.
>> We've seen this as well. I don't think there's a specific bug filed on this 
>> issue. I wonder if they related.

nope
unless there is a ridiculous number of them
they are about ovirt agent connectivity (which breaks around time of 
start/stop/migration, etc) but normally should not happen, when you run 
ovirt-guest-agent inside guest
When you don’t you’ll see it every so often per each VM


> 
> No relation to the metadata log messages. Can't help here.
> 
> Best regards
> 
> --
> Martin Sivak
> SLA / oVirt
> 
> 
> On Fri, Nov 6, 2015 at 1:14 PM, Christophe TREFOIS
>  wrote:
>> Dear Nir,
>> 
>> Thank you for your help. I shall ignore the messages then :)
>> 
>> Kind regards,
>> 
>> —
>> Christophe
>> 
>> Dr Christophe Trefois, Dipl.-Ing.
>> Technical Specialist / Post-Doc
>> 
>> UNIVERSITÉ DU LUXEMBOURG
>> 
>> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>> Campus Belval | House of Biomedicine
>> 6, avenue du Swing
>> L-4367 Belvaux
>> T: +352 46 66 44 6124
>> F: +352 46 66 44 6949
>> http://www.uni.lu/lcsb
>> 
>> 
>> 
>> 
>> This message is confidential and may contain privileged information.
>> It is intended for the named recipient only.
>> If you receive it in error please notify me and permanently delete the 
>> original message and any copies.
>> 
>> 
>> 
>> 
>>> On 06 Nov 2015, at 12:23, Nir Soffer  wrote:
>>> 
>>> On Tue, Nov 3, 2015 at 10:30 AM, Yaniv Kaul  wrote:
 On Tue, Nov 3, 2015 at 9:52 AM, Christophe TREFOIS
  wrote:
> 
> Hi,
> 
> I checked the logs on my hypervisor that contains also the overt-engine
> (self-hosted) and I see strange unknown libvirterrors that come 
> periodically
> in the vdsm.log file. The storage is glusterFS running on the hypervisor 
> as
> well, one NFS export domain and an ISO domain. A NFS domain from another
> place is in maintenance mode.
> 
> I am running oVirt 3.5.3.
> 
> Thank you for any pointers as to where to start fixing this issue.
> 
> — log excerpt --
> 
> Thread-1947641::DEBUG::2015-11-03
> 08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send) Sending
> response
> Thread-8108::DEBUG::2015-11-03
> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown 
> libvirterror:
> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested 
> metadata
> element is not present
 
 
 This (depending on your host OS version, 6.x or 7.x) is either
 https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
 https://bugzilla.redhat.com/show_bug.cgi?id=1260864
 Y.
>>> 
>>> The error about missing metadata is just noise in the log, nothing to
>>> worry about.
>>> 
>>> Adding Martin
>>> 
 
> Dummy-1895260::DEBUG::2015-11-03
> 08:47:31,477::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail) 
> dd
> if=/rhev/data-center/0002-0002-0002-0002-03d5/mastersd/dom_md/inbox
> iflag=direct,fullblock count=1 bs=1024000 (cwd None)
> Dummy-1895260::DEBUG::2015-11-03
> 08:47:31,501::storage_mailbox::731::Storage.Misc.excCmd::(_checkForMail)
> SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB)
> copied, 0.00331278 s, 309 MB/s\n';  = 0
> Thread-7913::DEBUG::2015-11-03
> 08:47:32,298::libvirtconnection::143::root::(wrapper) Unknown 
> libvirterror:
> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested 
> metadata
> element is not present
> Thread-5682::DEBUG::2015-11-03
> 08:47:32,417::libvirtconnection::143::root::(wrapper) Unknown 
> libvirterror:
> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested 
> metadata
> element is not present
> Detector thread::DEBUG::2015-11-03
> 08:47:32,591::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection)
> Adding connection from 127.0.0.1:44671
> Detector thread::DEBUG::2015-11-03
> 08:47:32,598::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection)
> Connection removed from 127.0.0.1:44671
> Detector thread::DEBUG::2015-11-03
> 08:47:32,599::protocoldetector::247::vds.MultiProtocolAcceptor::(_handle_connection_read)
> Detected protocol xml from 127.0.0.1:44671
> Detector thread::DEBUG::2015-11-03
> 08:47:32,599::BindingXMLRPC::1173::XmlDetecto

Re: [ovirt-users] Unknown libvirterror - where to start?

2015-12-06 Thread Christophe TREFOIS

HI michal,

Thanks for the tips. We're now deploying the agents on all VMs (around 60) and 
will see for similar entries in the logs.

Have a nice evening,

--
Christophe

> -Original Message-
> From: Michal Skrivanek [mailto:mskri...@redhat.com]
> Sent: vendredi 6 novembre 2015 14:33
> To: Christophe TREFOIS 
> Cc: users@ovirt.org
> Subject: Re: [ovirt-users] Unknown libvirterror - where to start?
> 
> 
> > On 06 Nov 2015, at 13:35, Martin Sivak  wrote:
> >
> > Hi,
> >
> >> Thread-8108::DEBUG::2015-11-03
> >> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown
> >> libvirterror: ecode: 80 edom: 20 level: 2
> >> message: metadata not found: Requested metadata element is not
> >> present
> >
> > we fixed this on vdsm side of oVirt 3.6 too:
> >
> > https://gerrit.ovirt.org/#/c/45799/
> >
> > But Nir is correct. This was just noise, it went away when any QoS was
> > defined for the VM and was not important otherwise.
> >
> >>> VM Channels Listener::DEBUG::2015-11-03
> 08:47:34,386::vmchannels::96::vds::(_handle_timeouts) Timeout on fileno
> 125.
> >> We've seen this as well. I don't think there's a specific bug filed on this
> issue. I wonder if they related.
> 
> nope
> unless there is a ridiculous number of them they are about ovirt agent
> connectivity (which breaks around time of start/stop/migration, etc) but
> normally should not happen, when you run ovirt-guest-agent inside guest
> When you don’t you’ll see it every so often per each VM
> 
> 
> >
> > No relation to the metadata log messages. Can't help here.
> >
> > Best regards
> >
> > --
> > Martin Sivak
> > SLA / oVirt
> >
> >
> > On Fri, Nov 6, 2015 at 1:14 PM, Christophe TREFOIS
> >  wrote:
> >> Dear Nir,
> >>
> >> Thank you for your help. I shall ignore the messages then :)
> >>
> >> Kind regards,
> >>
> >> —
> >> Christophe
> >>
> >> Dr Christophe Trefois, Dipl.-Ing.
> >> Technical Specialist / Post-Doc
> >>
> >> UNIVERSITÉ DU LUXEMBOURG
> >>
> >> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE Campus Belval |
> House of
> >> Biomedicine 6, avenue du Swing
> >> L-4367 Belvaux
> >> T: +352 46 66 44 6124
> >> F: +352 46 66 44 6949
> >> http://www.uni.lu/lcsb
> >>
> >>
> >>
> >> 
> >> This message is confidential and may contain privileged information.
> >> It is intended for the named recipient only.
> >> If you receive it in error please notify me and permanently delete the
> original message and any copies.
> >> 
> >>
> >>
> >>
> >>> On 06 Nov 2015, at 12:23, Nir Soffer  wrote:
> >>>
> >>> On Tue, Nov 3, 2015 at 10:30 AM, Yaniv Kaul  wrote:
> >>>> On Tue, Nov 3, 2015 at 9:52 AM, Christophe TREFOIS
> >>>>  wrote:
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> I checked the logs on my hypervisor that contains also the
> >>>>> overt-engine
> >>>>> (self-hosted) and I see strange unknown libvirterrors that come
> >>>>> periodically in the vdsm.log file. The storage is glusterFS
> >>>>> running on the hypervisor as well, one NFS export domain and an
> >>>>> ISO domain. A NFS domain from another place is in maintenance
> mode.
> >>>>>
> >>>>> I am running oVirt 3.5.3.
> >>>>>
> >>>>> Thank you for any pointers as to where to start fixing this issue.
> >>>>>
> >>>>> — log excerpt --
> >>>>>
> >>>>> Thread-1947641::DEBUG::2015-11-03
> >>>>> 08:47:31,398::stompReactor::163::yajsonrpc.StompServer::(send)
> >>>>> Sending response
> >>>>> Thread-8108::DEBUG::2015-11-03
> >>>>> 08:47:31,410::libvirtconnection::143::root::(wrapper) Unknown
> libvirterror:
> >>>>> ecode: 80 edom: 20 level: 2 message: metadata not found: Requested
> >>>>> metadata element is not present
> >>>>
> >>>>
> >>>> This (depending on your host OS version, 6.x or 7.x) is either
> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1220474 or
> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1260864
> >>>> Y.
> >>>
> >>> The

[ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

Re: [ovirt-users] Unknown libvirterror - where to start?

12 matches

Site Navigation

Mail list logo

Footer information