Learn more about these different git repos.
Other Git URLs
If you update or otherwise restart libvirt while kojivmd is running, then kojivmd's connection to libvirt becomes invalid. This connection is created at startup and used throughout the run. It seems like we should be able to reconnect in such cases.
PR #3679
Metadata Update from @tkopecek: - Custom field Size adjusted to None
Metadata Update from @tkopecek: - Issue set to the milestone: 1.33
I was able to find an example traceback from the issue that prompted this.
/usr/sbin/kojivmd:229 [ERROR] Error in main loop Traceback (most recent call last): File "/usr/sbin/kojivmd", line 213, in main taken = tm.getNextTask() File "/usr/lib/python2.6/site-packages/koji/daemon.py", line 819, in getNextTask self.ready = self.readyForTask() File "/usr/lib/python2.6/site-packages/koji/daemon.py", line 1142, in readyForTask if not self.checkSpace(): File "/usr/sbin/kojivmd", line 964, in checkSpace return self.checkDisk() and self.checkMem() File "/usr/sbin/kojivmd", line 944, in checkMem for vm_id in self.libvirt_conn.listDomainsID(): File "/usr/lib64/python2.6/site-packages/libvirt.py", line 3459, in listDomainsID if ret is None: raise libvirtError ('virConnectListDomainsID() failed', conn=self) libvirtError: internal error client socket is closed
I'm seem similar tracebacks more recently.
Also seen
libvirt.libvirtError: Cannot write data: Broken pipe
Metadata Update from @tkopecek: - Issue tagged with: testing-ready
Metadata Update from @tkopecek: - Issue untagged with: testing-ready - Issue tagged with: no_qe
Commit 6d80b3b fixes this issue
Commit 22c88fc relates to this ticket
Login to comment on this ticket.