Softaculous


Topic : Libvirt - error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error


Posted By: murmaider on August 23, 2018, 12:04 pm
Has anyone come across this issue.

Envrionment:
AMD Epyc Processor
64GB RAM
CentOS 7.5
Virtualizor
Linux-kvm

/dev/sdb1 = 2TB SSD with GPT partition set with lvm flag.

Code

# pvdisplay
  --- Physical volume ---
  PV Name              /dev/sdb1
  VG Name              kvmvg
  PV Size              1.86 TiB / not usable 0
  Allocatable          yes
  PE Size              4.00 MiB
  Total PE              488855
  Free PE              483735
  Allocated PE          5120
  PV UUID              rHjOmT-PhY6-W7b7-SPAQ-kEjp-cIZA-qGIfxC

# vgdisplay
  --- Volume group ---
  VG Name              kvmvg
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access            read/write
  VG Status            resizable
  MAX LV                0
  Cur LV                1
  Open LV              1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size              1.86 TiB
  PE Size              4.00 MiB
  Total PE              488855
  Alloc PE / Size      5120 / 20.00 GiB
  Free  PE / Size      483735 / <1.85 TiB
  VG UUID              GaZyC4-sfDi-Zql3-oJ6j-7c0p-guYH-YI6ppZ

# lvdisplay
  --- Logical volume ---
  LV Path                /dev/kvmvg/vsv1011-dhqwhk57rczjxwag-uuony3jsqpe7zrvc
  LV Name                vsv1011-dhqwhk57rczjxwag-uuony3jsqpe7zrvc
  VG Name                kvmvg
  LV UUID                3muRja-xZnH-PxZL-eUiH-2ymr-35xz-jWU2cj
  LV Write Access        read/write
  LV Creation host, time amd-02, 2018-08-23 13:31:44 +0200
  LV Status              available
  # open                2
  LV Size                20.00 GiB
  Current LE            5120
  Segments              1
  Allocation            inherit
  Read ahead sectors    auto
  - currently set to    8192
  Block device          253:0

# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/sdb: 2050.4 GB, 2050408636416 bytes, 4004704368 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
Disk identifier: DF789DCA-88F3-4828-A66D-B1C857FBD8F2


#        Start          End    Size  Type            Name
1        2048  4004704255    1.9T  Linux LVM      primary

Disk /dev/mapper/kvmvg-vsv1011--dhqwhk57rczjxwag--uuony3jsqpe7zrvc: 21.5 GB, 21474836480 bytes, 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000b136f

                                                        Device Boot      Start        End      Blocks  Id  System
/dev/mapper/kvmvg-vsv1011--dhqwhk57rczjxwag--uuony3jsqpe7zrvc1  *        2048    39847935    19922944  83  Linux
/dev/mapper/kvmvg-vsv1011--dhqwhk57rczjxwag--uuony3jsqpe7zrvc2        39847936    41943039    1047552  82  Linux swap / Solaris




When the "/usr/local/emps/bin/php /usr/local/virtualizor/scripts/cronm.php" cron runs on a linux-kvm host, we see these errors in the /var/log/messages:

Code

Aug 23 13:40:11 amd-02 libvirtd: 2018-08-23 11:40:11.537+0000: 1428: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error
Aug 23 13:40:14 amd-02 libvirtd: 2018-08-23 11:40:14.594+0000: 1428: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error


Strangely enough, we have another Intel E5-2630v4 server that also produces this error, except the code is 1805 and not 1808:

Code

Aug 23 13:48:08 vnode01 libvirtd: 2018-08-23 11:48:08.704+0000: 24948: error : virNetSocketReadWire:1805 : End of file while reading data: Input/output error
Aug 23 13:48:11 vnode01 libvirtd: 2018-08-23 11:48:11.749+0000: 24948: error : virNetSocketReadWire:1805 : End of file while reading data: Input/output error



Has anyone else encountered this?


Posted By: murmaider on August 24, 2018, 12:30 pm | Post: 1
I been doing some research into this error and it appears to be a bug in this virtualizor cron script.

This error seems to occur if libvirt connection object is not deallocated before the script (or process / call inside the script) exits. There seems to be other software solutions which have also come across this.

Virtualizor, please can you dev's look into this further.

Posted By: wolke on September 7, 2018, 11:38 am | Post: 2
I do have the same issue here on a KVM Host running under Centos7.

Posted By: kaushal on September 25, 2018, 10:05 am | Post: 3
Hi,

Please open a support ticket.

We will check and update you on your ticket.

-----------------------
-----------------------
Regards,
Kaushal Vora
Virtualizor Team.
http://virtualizor.com/

Posted By: shubham1337 on November 22, 2019, 10:28 am | Post: 4
I am also getting the same error on my nodes, though VMs are working fine. Anybody figure out the reason or fix?

Powered By AEF 1.0.8 © 2007-2008 Electron Inc.