I have a freshly bought and licensed Virtualhere setup. Server on a Raspberrypi 4, client on Windows 10. Works fine, except that the W10 client keeps losing the license information at least one a day. Keeps coming up as trial. The license is seemingly lost at random, can’t figure out a pattern. Of course, the license can be reinstalled, and it works, but it is a nuisance. How can the license be installed persistently?
.
Actually the license is stored persistently in the config.ini file which is usually in the same directory as the server binary.
That file must be being deleted, or on a temporary path.
When the virtualhere server starts in Linux it will write the path to the config.ini file it is using in syslog.
In the shell can you:
grep vhusbd /var/log/syslogWhat path does it say?
Hi.
Hi.
It is the Windows CLIENT that complains occasionally about a missing license.
Server-side, the license WAS stored into the config.ini file in/usr/sbin/config.ini, and the stored license agrees with my license.
The log says:
root@pi4:~# grep vhusbd /var/log/syslog
Dec 20 18:14:52 pi4 vhusbdarm[670]: Device 113 [1df7:3030] UNBOUND from connection 5
Dec 20 18:14:53 pi4 vhusbdarm[670]: Connection 5 successfully removed (reason:server shutdown)
Dec 20 18:14:53 pi4 vhusbdarm[670]: Connection 5 successfully removed (reason:timeout)
Dec 20 18:14:55 pi4 vhusbdarm[670]: Unmanaging device 113 [1df7:3030]
Dec 20 18:14:56 pi4 vhusbdarm[670]: >>> Shutdown <<<
Dec 20 18:15:42 pi4 systemd[5826]: virtualhere.service: Failed at step EXEC spawning /usr/sbin/vhusbdarmpt4: No such file or directory
Dec 20 18:16:07 pi4 vhusbdarmpi4[5975]: >>> Starting VirtualHere USB Server v4.2.0 (Built: Jul 27 2020, 11:37:47)<<<
Dec 20 18:16:07 pi4 vhusbdarmpi4[5975]: Using configuration /usr/sbin/config.ini
Dec 20 18:16:07 pi4 vhusbdarmpi4[5976]: Server licensed to=100000004915b9d6 max_devices=unlimited
Dec 20 18:16:07 pi4 vhusbdarmpi4[5976]: Using large URB's
Dec 20 18:16:07 pi4 vhusbdarmpi4[5976]: Listening on all network interfaces at TCP port 7575
Dec 20 18:16:07 pi4 vhusbdarmpi4[5976]: Warning, could not open device product file /sys/bus/usb/devices/1-1.3/product, error 2 (No such file or directory)
Dec 20 18:16:07 pi4 vhusbdarmpi4[5976]: Found High speed device [1df7:3030] "0x1df7, 0x3030" at address 113
Dec 20 18:16:12 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 1
Dec 20 18:16:12 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 1
Dec 20 18:17:06 pi4 vhusbdarmpi4[6274]: >>> Starting VirtualHere USB Server v4.2.0 (Built: Jul 27 2020, 11:37:47)<<<
Dec 20 18:17:06 pi4 vhusbdarmpi4[6274]: Using configuration /usr/sbin/config.ini
Dec 20 18:17:07 pi4 vhusbdarmpi4[6274]: Server licensed to=100000004915b9d6 max_devices=unlimited
Dec 20 18:17:07 pi4 vhusbdarmpi4[6274]: Using large URB's
Dec 20 18:17:07 pi4 vhusbdarmpi4[6274]: Error starting server
Dec 20 18:17:08 pi4 vhusbdarmpi4[6274]: >>> Shutdown <<<
Dec 20 18:17:12 pi4 vhusbdarmpi4[6304]: >>> Starting VirtualHere USB Server v4.2.0 (Built: Jul 27 2020, 11:37:47)<<<
Dec 20 18:17:12 pi4 vhusbdarmpi4[6304]: >>> Shutdown <<<
Dec 20 18:17:46 pi4 vhusbdarmpi4[6462]: >>> Starting VirtualHere USB Server v4.2.0 (Built: Jul 27 2020, 11:37:47)<<<
Dec 20 18:17:46 pi4 vhusbdarmpi4[6462]: >>> Shutdown <<<
Dec 20 18:26:57 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 1
Dec 20 18:27:04 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 1
Dec 20 18:28:06 pi4 vhusbdarmpi4[5976]: Connection 1 remotely disconnected abruptly (rx msg size)
Dec 20 18:28:14 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 1
Dec 20 18:28:15 pi4 vhusbdarmpi4[5976]: Connection 1 successfully removed (reason:timeout)
Dec 20 18:29:50 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 4
Dec 20 18:29:50 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 4
Dec 20 18:34:50 pi4 vhusbdarmpi4[5976]: Error 22 discarding urb 0x7c0710 for device /sys/bus/usb/devices/1-1.3, Invalid argument (abort endpoint)
Dec 20 18:36:25 pi4 vhusbdarmpi4[5976]: Connection 4 remotely disconnected abruptly (rx msg size)
Dec 20 18:36:25 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 4
Dec 20 18:36:26 pi4 vhusbdarmpi4[5976]: Connection 4 successfully removed (reason:timeout)
Dec 20 18:36:26 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 6
Dec 20 18:36:27 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 6
Dec 20 19:11:37 pi4 vhusbdarmpi4[5976]: Error 22 discarding urb 0x7bd990 for device /sys/bus/usb/devices/1-1.3, Invalid argument (abort endpoint)
Dec 20 19:11:37 pi4 vhusbdarmpi4[5976]: Error 22 discarding urb 0x7bd320 for device /sys/bus/usb/devices/1-1.3, Invalid argument (abort endpoint)
Dec 20 20:21:57 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 6
Dec 20 20:21:58 pi4 vhusbdarmpi4[5976]: Connection 6 successfully removed (reason:timeout)
Dec 20 20:22:08 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 8
Dec 20 20:22:08 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 8
Dec 20 20:33:06 pi4 vhusbdarmpi4[5976]: Connection 8 remotely disconnected abruptly (rx msg size)
Dec 20 20:33:06 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 8
Dec 20 20:33:06 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 10
Dec 20 20:33:07 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 10
Dec 20 20:33:07 pi4 vhusbdarmpi4[5976]: Connection 8 successfully removed (reason:timeout)
Dec 20 22:03:16 pi4 vhusbdarmpi4[5976]: Error 22 discarding urb 0x7c0610 for device /sys/bus/usb/devices/1-1.3, Invalid argument (abort endpoint)
Dec 20 22:04:55 pi4 vhusbdarmpi4[5976]: Connection 10 remotely disconnected abruptly (rx msg size)
Dec 20 22:04:55 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 10
Dec 20 22:04:56 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 12
Dec 20 22:04:56 pi4 vhusbdarmpi4[5976]: Connection 10 successfully removed (reason:timeout)
Dec 20 22:04:56 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 12
Dec 20 22:13:58 pi4 vhusbdarmpi4[5976]: Error 22 discarding urb 0x7bcd10 for device /sys/bus/usb/devices/1-1.3, Invalid argument (abort endpoint)
Dec 20 22:15:31 pi4 vhusbdarmpi4[5976]: Connection 12 remotely disconnected abruptly (rx msg size)
Dec 20 22:15:31 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] UNBOUND from connection 12
Dec 20 22:15:32 pi4 vhusbdarmpi4[5976]: Connection 12 successfully removed (reason:timeout)
Dec 20 22:15:32 pi4 vhusbdarmpi4[5976]: 192.168.100.178 connected as connection 14
Dec 20 22:15:32 pi4 vhusbdarmpi4[5976]: Device 113 [1df7:3030] BOUND to connection 14
I have upgraded the RaspberryPi server to vhusbdarmpi4. If I'm having more problems, I'll be back.
General comment: The documentation needs a serious overhaul. I have 40+ years of PC experience, and I needed to dig alot for the proper docs to install the Linux driver, and I had to patch install_server to install vhusbdarmpi4. To avoid confusions, you want to name your config file something like vhusb.conf, and store it into /etc, it doesn't belong into sbin. You want to put all options into that config file as commented-out lines, showing the proper format for each option.
Ok, it has done it again.
Ok, it has done it again.
After some digging, it turned out that the setting did not survive a reboot of the RaspberryPi 4 server.
After some more digging the culprit was found in a filesystem that was set to overlay. Of course, all changes to the file system were gone after a reboot. Overlay turned off, all good.
While we are at it: The “Always on top” option in the Windows client GUI does not work. The window gets hidden under other windows. You want to show the window when the icon in the taskbar is right-clicked and when “Virtualhere USB Sharing” is selected.
.
No everything in virtualhere works as it should including paths etc..everything is as it is for a reason