Client Error when retrieve device List

Submitted by rapante on #1

Hello,
sometimes i get an Error from virtualhere console client on ubuntu while retrieving the device list.

Server and client are on the same Host. The client is only used, to get the device-list (for monitoring purposes) .
Every few minutes i do: "/usr/sbin/vhclienti386 -t List" and got the list, but sometimes i got an error: "Error, IPC pipe was broken before finishing read". The error persists for a while and some time later ist works again. A restart of the client did not help.

The server works as aspected all the time.

Do you have any idea what could be the problem here?

Submitted by Michael on Thu, 2020/04/09 - 20:07

#2

1. How are you starting the client daemon?

2. Are you using the latest version of the virtualhere client for i386 linux?

3. Can you grep /var/log/syslog and see if there is any error listed about" vhclienti386"

4. You are using the 32-bit client on a 32-bit linux and not a 64-bit linux?

Submitted by rapante on Thu, 2020/04/16 - 18:05

#3

Hello Michael,
thanks for your response. Probably you got the point. I obvously should use the 64-bit client on a 64-bit linux ;). I have changed this and updated to the latest version.

Submitted by mariaya on Mon, 2021/08/23 - 22:46

#4

1. How are you starting the client daemon? - -- /usr/sbin/vhclientx86_64 -n
2. Are you using the latest version of the virtualhere client for i386 linux? - - VirtualHere client 5.2.1
4. You are using the 32-bit client on a 32-bit linux and not a 64-bit linux? 64-bit linux (centos 7)

Submitted by mariaya on Mon, 2021/08/23 - 23:02

#5

1. Installed server for virtualhere server (Ubuntu)
2. Server with client virtualhere. (Centos7)
If 1 server is virtualhere client, no problem.
If you enable the second server with virtualhere client, then on two servers with virtualhere client the error "Error, IPC pipe was broken before finishing read" occurs when executing the command / usr / sbin / vhclientx86_64 --control = "LIST"

Submitted by Michael on Tue, 2021/08/24 - 08:30

#6

Centos 7 is way too buggy actually. You need to use a recent kernel in the 4.18+ range

Submitted by mariaya on Thu, 2021/09/02 - 19:42

#7

on centos 7 client the kernel is updated to 5.14 but the error persists.

Submitted by mariaya on Thu, 2021/09/02 - 19:46

#8

the problem described in the topic arises if you configure key binding on two clients. If configured on only one client, then there is no problem.

Submitted by Michael on Thu, 2021/09/02 - 20:04

#9

Can you grep syslog on the client machine and see if there are messages from "VirtualHere" or "vhclientx86_64" and post them here

Submitted by mariaya on Mon, 2021/09/06 - 22:46

#10

Sep 6 15:19:27 app1c journal: VirtualHere Client: Connection 4 remotely disconnected gracefully (rx)
Sep 6 15:38:19 app1c journal: VirtualHere Client: Connection 5 remotely disconnected gracefully (rx)
on client machines the problem:
vhci_hcd vhci_device speed not set

[root@app1c ~]# cat /var/log/messages | grep vhci_
Sep 6 15:19:28 app1c kernel: vhci_hcd: connection closed
Sep 6 15:19:28 app1c kernel: vhci_hcd: stop threads
Sep 6 15:19:28 app1c kernel: vhci_hcd: release socket
Sep 6 15:19:28 app1c kernel: vhci_hcd: disconnect device
Sep 6 15:19:28 app1c kernel: vhci_hcd: connection closed
Sep 6 15:19:28 app1c kernel: vhci_hcd: stop threads
Sep 6 15:19:28 app1c kernel: vhci_hcd: release socket
Sep 6 15:19:28 app1c kernel: vhci_hcd: disconnect device
Sep 6 15:20:36 app1c kernel: vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(7)
Sep 6 15:20:36 app1c kernel: vhci_hcd vhci_hcd.0: devid(4) speed(2) speed_str(full-speed)
Sep 6 15:20:36 app1c kernel: vhci_hcd vhci_hcd.0: Device attached
Sep 6 15:20:36 app1c kernel: vhci_hcd: vhci_device speed not set
Sep 6 15:20:36 app1c kernel: usb 3-1: new full-speed USB device number 10 using vhci_hcd
Sep 6 15:20:36 app1c kernel: vhci_hcd: vhci_device speed not set
Sep 6 15:20:36 app1c kernel: vhci_hcd vhci_hcd.0: pdev(0) rhport(1) sockfd(7)
Sep 6 15:20:36 app1c kernel: vhci_hcd vhci_hcd.0: devid(5) speed(1) speed_str(low-speed)
Sep 6 15:20:36 app1c kernel: vhci_hcd vhci_hcd.0: Device attached
Sep 6 15:20:37 app1c kernel: usb 3-2: new low-speed USB device number 11 using vhci_hcd
Sep 6 15:38:20 app1c kernel: vhci_hcd: connection closed
Sep 6 15:38:20 app1c kernel: vhci_hcd: stop threads
Sep 6 15:38:20 app1c kernel: vhci_hcd: release socket
Sep 6 15:38:20 app1c kernel: vhci_hcd: disconnect device
Sep 6 15:38:20 app1c kernel: vhci_hcd: connection closed
Sep 6 15:38:20 app1c kernel: vhci_hcd: stop threads
Sep 6 15:38:20 app1c kernel: vhci_hcd: release socket
Sep 6 15:38:20 app1c kernel: vhci_hcd: disconnect device
Sep 6 15:38:53 app1c kernel: vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(7)
Sep 6 15:38:53 app1c kernel: vhci_hcd vhci_hcd.0: devid(4) speed(2) speed_str(full-speed)
Sep 6 15:38:53 app1c kernel: vhci_hcd vhci_hcd.0: Device attached
Sep 6 15:38:53 app1c kernel: vhci_hcd: vhci_device speed not set
Sep 6 15:38:53 app1c kernel: usb 3-1: new full-speed USB device number 12 using vhci_hcd
Sep 6 15:38:53 app1c kernel: vhci_hcd: vhci_device speed not set
Sep 6 15:38:54 app1c kernel: vhci_hcd vhci_hcd.0: pdev(0) rhport(1) sockfd(7)
Sep 6 15:38:54 app1c kernel: vhci_hcd vhci_hcd.0: devid(5) speed(1) speed_str(low-speed)
Sep 6 15:38:54 app1c kernel: vhci_hcd vhci_hcd.0: Device attached
Sep 6 15:38:54 app1c kernel: usb 3-2: new low-speed USB device number 13 using vhci_hcd

Submitted by Michael on Tue, 2021/09/07 - 08:17

#11

Ok that log looks fine and also "vhci_device speed not set" is ok also because its not actually an error.

Can you send me the output of the LIST command when it works? Does it show devices perhaps with non-english characters

Submitted by mariaya on Tue, 2021/09/07 - 19:50

#12

okc-pps-usbsrv (okc-pps-usbsrv:7575)
--> USB 04 (okc-pps-usbsrv.11117)
--> USB 02 (okc-pps-usbsrv.11116)
--> USB 10 (okc-pps-usbsrv.11127)
--> USB 03 (okc-pps-usbsrv.11115)
--> USB 01 (okc-pps-usbsrv.11126)
--> USB 05 (okc-pps-usbsrv.11114)
--> USB 09 (okc-pps-usbsrv.11125)
--> USB 14 (okc-pps-usbsrv.11137)
--> USB 06 (okc-pps-usbsrv.11113)
--> USB 11 (okc-pps-usbsrv.11124)
--> USB 13 (okc-pps-usbsrv.11141)
--> USB 15 (okc-pps-usbsrv.11136)
--> USB 07 (okc-pps-usbsrv.11112)
--> USB 12 (okc-pps-usbsrv.11123)
--> USB 08 (okc-pps-usbsrv.11111)
--> Soft protection device: USB Protection Key v2.8. (okc-pps-usbsrv.11414) (In-use by:система (система) at 10.25.66.55)
--> Soft protection device: USB Protection Key v2.8. (okc-pps-usbsrv.11412) (In-use by:система (система) at 10.25.66.55)
--> 1C:UR_PROF 47 License (okc-pps-usbsrv.11415) (In-use by:система (система) at 10.25.66.55)
--> 1C Server x64 License (okc-pps-usbsrv.11442) (In-use by:система (система) at 10.25.66.47)
--> 1C Server x64 License (okc-pps-usbsrv.11441) (In-use by:система (система) at 10.25.66.48)
--> 1C Client License H4 Net5 (okc-pps-usbsrv.11437) (In-use by:система (система) at 10.25.66.47)

Auto-Find currently on
Auto-Use All currently off
Reverse Lookup currently off
Reverse SSL Lookup currently off
VirtualHere Client is running as a service

Submitted by mariaya on Tue, 2021/09/07 - 19:53

#13

USB in the In-use by status are virtualhereclient clients on windows.

Submitted by mariaya on Tue, 2021/09/07 - 19:56

#14

the problem occurs when connecting from a client on centos 7, when we try to use USB from the sequence: USB 01 (okc-pps-usbsrv.11126) - USB 15 (okc-pps-usbsrv.11136)

Submitted by mariaya on Tue, 2021/09/07 - 20:02

#15

if you connect USB on one client, everything is fine. But as soon as I connect the USB on the second client, an error occurs from the topic.

Submitted by Michael on Wed, 2021/09/08 - 08:49

#16

I checked all the virtualhere code and it seems ok and it also works fine on ubuntu so im not sure. If i can ssh to your client to have a look that would be helpful. If so email me at mail [at] virtualhere.com (mail[at]virtualhere[dot]com)