Bug 966786 - nternal error received hangup / error event on socket
nternal error received hangup / error event on socket
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Libvirt Maintainers
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-23 21:10 EDT by changyoushi
Modified: 2013-05-23 22:12 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-23 22:12:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description changyoushi 2013-05-23 21:10:12 EDT
Description of problem:

encounter "internal error received hangup / error event on socket" problem
,this problem arise when connect libivrtd daemon,but sometimes, the connect call work well.

Version-Release number of selected component (if applicable):

the libvirtd runing on Red Hat enterprise server 5.5 and the libvirt version is 0.9.0

my test is runing on win7, the lbvirt lib version is 0.8.4

How reproducible:

Steps to Reproduce:
1. my simple test is start in win7 system,
2. call the virtConnectAuth to open the libvirtd runing on rhes5.5
3.sometimes the call goes well, sometimes the problem occur
4. the output is "libvir: Remote error : internal error received hangup / error event on socket"
5. i try restart the libvirtd, but no work.

Actual results:

Expected results:

Additional info:
Comment 1 Laine Stump 2013-05-23 22:12:22 EDT
This bugzilla component is only for reporting bugs occurring in the Fedora builds of libvirt, not generic builds on other platforms.

Additionally it appears that the libvirt you are running on RHEL5.5 is the not official version that is supported on RHEL5 (RHEL5 has never had a supported 0.9.x version of libvirt).

I have two recommendations:

1) before anything else, find/build/install newer versions of libvirt on both your client and your server. You can find information about running libvirt on Windows (including where to get *much* newer libvirt binaries) here:


As for RHEL5, if you're using RHEL you should really be using the supported libvirt that you would get with yum update, or alternately getting the latest release (currently 1.0.5) from libvirt.org and building it yourself - either of these is a much better alternative than using the "very old and also not officially supported on RHEL5" libvirt-0.9.0

2) Once you have more up to date binaries, try your test again and if you still encounter problems, rather than opening a Fedora bug report, instead send email to libvir-list@redhat.com (or open a ticket with Red Hat support if you're using the officially supported libvirt version on your RHEL5 system).

Note You need to log in before you can comment on or make changes to this bug.