Bug 21832 - Verbindungsabbruch uvmm <-> libvirtd mit Xen
Verbindungsabbruch uvmm <-> libvirtd mit Xen
Status: CLOSED DUPLICATE of bug 20024
Product: UCS
Classification: Unclassified
Component: Virtualization - UVMM
UCS 2.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Bugzilla Mailingliste
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-15 07:05 CET by Stefan Gohmann
Modified: 2023-06-28 10:46 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2011-03-15 07:05:18 CET
Zwei Systeme mit Xen und libvirtd. Auf einem läuft zusätzlich UVMM.

Beim Anlegen einer neuen Instanz auf dem zweiten Xen-System kommt es zur Resynchronisationsanzeige in UVMM.

In der Logdatei konnte ich das sehen:
2011-03-15 07:29:08,140 - uvmmd.node - WARNING - 'xen://xen16.xen.local/' broken? next check in 0:00:30.000. The specified session has been invalidated for some reason.
libvir: Remote error : The specified session has been invalidated for some reason.
2011-03-15 07:29:08,141 - uvmmd.node - ERROR - Exception The specified session has been invalidated for some reason.: Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/univention/uvmm/node.py", line 530, in update_autoreconnect
    self.conn.domainEventDeregister(self.domainCB)
  File "/usr/lib/python2.4/site-packages/libvirt.py", line 1992, in domainEventDeregister
    if ret == -1: raise libvirtError ('virConnectDomainEventDeregister() failed', conn=self)
libvirtError: The specified session has been invalidated for some reason.

2011-03-15 07:29:38,273 - uvmmd.node - INFO - Connected to 'xen://xen16.xen.local/'
libvir: error : this function is not supported by the connection driver: virDomainHasManagedSaveImage
libvir: error : this function is not supported by the connection driver: virDomainSnapshotNum
libvir: Remote error : unable to connect to libvirtd at 'xen15.xen.local': Connection refused
2011-03-15 07:30:47,458 - uvmmd.node - WARNING - 'xen://xen15.xen.local/' broken? next check in 0:00:30.000. unable to connect to libvirtd at 'xen15.xen.local': Connection refused
libvir: Remote error : unable to resolve hostname 'xen16.xen.local': Name or service not known
2011-03-15 07:30:47,498 - uvmmd.node - WARNING - 'xen://xen16.xen.local/' broken? next check in 0:00:30.000. unable to resolve hostname 'xen16.xen.local': Name or service not known
2011-03-15 07:31:17,268 - uvmmd.node - INFO - Connected to 'xen://xen15.xen.local/'

libvirt-bin                     0.8.7-1.54.201103141255
xen-3.4                         3.4.3-17.51.201103032051
univention-virtual-machine-manager-daemon  0.9.180-1.184.201103110906
Linux xen16 2.6.32-ucs37-xen-amd64 #1 SMP Fri Feb 4 02:36:44 UTC 2011 x86_64 GNU/Linux

Ich habe auf dem System jetzt libvirt Debug aktiviert.
Comment 1 Stefan Gohmann univentionstaff 2011-03-15 07:08:02 CET
Das scheint Bug #20024 zu sein.

*** This bug has been marked as a duplicate of bug 20024 ***