On 18 August 2010 13:10, Ben <[email protected]> wrote: > A recently set up RHEL5.5 64-bit box Xen Dom0 (fully updated) with Debian > DomUs recently sent an email with the subject line above and the message > below: > > libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainFetch failed > to find this domain > Traceback (most recent call last): > File "/usr/share/rhn/virtualization/poller.py", line 302, in ? > domain.save_unknown_domain_configs(uuid_list) > File "/usr/share/rhn/virtualization/domain_directory.py", line 134, in > save_unknown_domain_configs > xml = domain.XMLDesc(0) > File "/usr/lib64/python2.4/site-packages/libvirt.py", line 231, in XMLDesc > if ret is None: raise libvirtError ('virDomainGetXMLDesc() failed', > dom=self) > libvirt.libvirtError: failed Xen syscall xenDaemonDomainFetch failed to > find this domain > > Does anyone have any idea what it's talking about? > > Is it something to do with files in /etc/xen/ not matching the list of > running Xen DomUs? >
No, it won't be that. Wast it a one-off message? If so then it's most likely that a domain went away between the time its name was discovered and the time poller.py tried to do something with it. jch
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
