Server 'crashing' or disconnecting?

Submitted by daxliniere on #1

Hey Michael,

A couple days ago I updated a few things on my RPi and now VH has started dropping out. When it does so, all devices are obviously disconnected and the two devices that have auto-use enabled are shown as (In use by  (windowsPCname) at ::) and when I right-click on one, it says "In use elsewhere..." so it seems that it's getting 'locked up'.

Does the server or client store a log file so we can see what may have occurred to cause this drop-out?

I'm running RPi server v 4.6.7 and Windows client is 5.7.6.

 

All the best,
Dax.

Submitted by daxliniere on Fri, 2025/03/07 - 05:05

#2

Hey Michael,
Yes, I think you might be right. I had a session elsewhere last week which required me to bring my iLok with me (no reliable internet connection there, otherwise I would have used VH, of course).
My USB dongles usually reside inside the Pi's housing, and the iLok has a small inline USB power switcher which is controlled by a GPIO pin on the Pi so I can restart it when I need to switch it to another PC without having to reboot the whole Pi. (since the per-port power switching on my Pi 4b doesn't work for some reason.)
It's possible that the GPIO trigger cable wasn't fully seated. I've bypassed the power control PCB for now and will see if it continues to drop out.

Submitted by daxliniere on Thu, 2025/03/27 - 04:43

#3

Hey Michael,

I'm having unexpected complete disconnections, including the server completely disappearing and VH isn't displaying any kind of warning or error message about it.
Any ideas?

I reconnected the USB power-cycling device the other day and the device disconnections started again (but am not triggering it, of course), though the server completely disappearing is a new one. The power-cycling device worked perfectly for almost exactly 1 year since I installed it and nothing about that setup has changed in that time.
(This is the device, by the way: https://thepihut.com/products/usb-power-switch-module?variant=394524652…)

 

Currently running today's releases (server and client), but it happened a couple days ago using the previous versions. I'm happy to enable aggressive debugging if it helps.
Do you have any way to enable VH server to automatically send this data to you?

Submitted by daxliniere on Thu, 2025/03/27 - 04:48

#4

"If you run lsusb can you see the ilok on the pi?"

I can right now, but I will check again the next time I get an iLok disconnection.

Before disconnection:
xxxx@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 064f:03e9 WIBU-Systems AG CmStick (MSD, article no. 1001-xx-xxx) <-----WIBU licensing dongle, Auto-Use enabled
Bus 001 Device 004: ID 096e:0201 Feitian Technologies, Inc. <-----Davinci Resolve licensing dongle, Auto-Use enabled
Bus 001 Device 013: ID 088e:5036 iLok Portable secure storage for software licenses <-----Auto-Use not enabled on any client PC
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

Submitted by daxliniere on Thu, 2025/03/27 - 05:26

#5

Just noticed that it happened again. 

After disconnection:
xxxx@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 064f:03e9 WIBU-Systems AG CmStick (MSD, article no. 1001-xx-xxx)
Bus 001 Device 004: ID 096e:0201 Feitian Technologies, Inc.
Bus 001 Device 014: ID 088e:5036 iLok Portable secure storage for software licenses
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 

I tried journalctl as you suggested. Does this help?

Mar 26 19:05:44 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:05:44 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:05:45 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:05:46 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:05:46 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:05:47 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:10:45 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:10:45 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:10:46 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:10:46 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:10:47 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:10:47 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 13 using xhci_hcd
Mar 26 19:15:47 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] UNBOUND from connection 48
Mar 26 19:15:47 raspberrypi kernel: usbhid 1-1.3:1.0: couldn't find an input interrupt endpoint
Mar 26 19:15:47 raspberrypi mtp-probe[4070]: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-
Mar 26 19:15:47 raspberrypi mtp-probe[4070]: bus: 1, device: 4 was not an MTP device
Mar 26 19:15:48 raspberrypi vhusbdarmpi4[20806]: Device 114 [064f:03e9] UNBOUND from connection 48
Mar 26 19:15:48 raspberrypi kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
Mar 26 19:15:48 raspberrypi kernel: scsi host0: usb-storage 1-1.4:1.0
Mar 26 19:15:48 raspberrypi mtp-probe[4080]: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-
Mar 26 19:15:48 raspberrypi mtp-probe[4080]: bus: 1, device: 5 was not an MTP device
Mar 26 19:15:48 raspberrypi kernel: usb 1-1.4: usbfs: process 20823 (op114) did not claim interface 0 before use
Mar 26 19:15:48 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:59773->[255.255.255.255]:161
Mar 26 19:15:49 raspberrypi kernel: scsi 0:0:0:0: Direct-Access     WIBU -   CodeMeter-Stick  v1.0 PQ: 0 ANSI: 2
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: [sda] 80384 512-byte logical blocks: (41.2 MB/39.3 MiB)
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: [sda] Write Protect is off
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: [sda] No Caching mode page found
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: USB disconnect, device number 13
Mar 26 19:15:49 raspberrypi kernel:  sda: sda1
Mar 26 19:15:49 raspberrypi kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: new full-speed USB device number 14 using xhci_hcd
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: New USB device found, idVendor=088e, idProduct=5036, bcdDevice= 0.30
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: Product: iLok
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: Manufacturer: iLok
Mar 26 19:15:49 raspberrypi kernel: usb 1-1.1: SerialNumber: 3ACBA729_131A1E44
Mar 26 19:15:49 raspberrypi mtp-probe[4086]: checking bus 1, device 14: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 19:15:49 raspberrypi mtp-probe[4086]: bus: 1, device: 14 was not an MTP device
Mar 26 19:15:49 raspberrypi mtp-probe[4088]: checking bus 1, device 14: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 19:15:49 raspberrypi mtp-probe[4088]: bus: 1, device: 14 was not an MTP device
Mar 26 19:15:49 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:59773->[255.255.255.255]:161
Mar 26 19:15:53 raspberrypi vhusbdarmpi4[20806]: Device 111 [088e:5036] UNBOUND from connection 48
Mar 26 19:15:53 raspberrypi mtp-probe[4104]: checking bus 1, device 14: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 19:15:53 raspberrypi mtp-probe[4104]: bus: 1, device: 14 was not an MTP device
Mar 26 19:15:54 raspberrypi vhusbdarmpi4[20806]: Connection 48 successfully removed (reason:timeout)
Mar 26 19:15:54 raspberrypi vhusbdarmpi4[20806]: Unmanaging device 111 [088e:5036]
Mar 26 19:15:54 raspberrypi vhusbdarmpi4[20806]: Found Full speed device [088e:5036] "iLok, iLok" at address 111
Mar 26 19:16:31 raspberrypi vhusbdarmpi4[20806]: 100.76.205.121 connected as connection 52 (Standard TCP)
Mar 26 19:16:31 raspberrypi kernel: usb 1-1.3: reset low-speed USB device number 4 using xhci_hcd
Mar 26 19:16:32 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] BOUND to connection 52
Mar 26 19:16:32 raspberrypi kernel: usb 1-1.4: reset full-speed USB device number 5 using xhci_hcd
Mar 26 19:16:32 raspberrypi vhusbdarmpi4[20806]: Device 114 [064f:03e9] BOUND to connection 52
Mar 26 19:16:32 raspberrypi kernel: usb 1-1.3: reset low-speed USB device number 4 using xhci_hcd
Mar 26 19:16:33 raspberrypi kernel: usb 1-1.4: reset full-speed USB device number 5 using xhci_hcd
Mar 26 19:16:33 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:53508->[255.255.255.255]:161
Mar 26 19:16:34 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:53508->[255.255.255.255]:161
Mar 26 19:17:01 raspberrypi CRON[4228]: pam_unix(cron:session): session opened for user root by (uid=0)
Mar 26 19:17:01 raspberrypi CRON[4229]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 26 19:17:01 raspberrypi CRON[4228]: pam_unix(cron:session): session closed for user root

Submitted by daxliniere on Thu, 2025/03/27 - 05:43

#7

Hey, is it possible that it's the WIBU key that is causing this problem?? (Strangely, it acts as a USB drive. Don't ask me why...) I basically don't use it anymore, anyway, so I will disable the Auto-Use for now.
If issue still persist, I will unplug it and continue testing.

Submitted by daxliniere on Thu, 2025/03/27 - 06:16

#8

Just got a warning from a plugin (that uses iLok) that there had been another disconnection, about 9 minutes after the last entry here:

I'll unplug the WIBU now to see if it makes any difference.


Mar 26 19:32:38 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:32:38 raspberrypi vhusbdarmpi4[20806]: Device 111 [088e:5036] BOUND to connection 52
Mar 26 19:32:38 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:32:40 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:32:41 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:32:41 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:32:42 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:35:47 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:35:48 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:35:49 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:35:49 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:35:49 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:35:50 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 19:43:45 raspberrypi kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
Mar 26 19:43:45 raspberrypi kernel: scsi host0: usb-storage 1-1.4:1.0
Mar 26 19:43:45 raspberrypi vhusbdarmpi4[20806]: Device 114 [064f:03e9] UNBOUND from connection 52
Mar 26 19:43:46 raspberrypi mtp-probe[8149]: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-
Mar 26 19:43:46 raspberrypi mtp-probe[8149]: bus: 1, device: 5 was not an MTP device
Mar 26 19:43:47 raspberrypi kernel: scsi 0:0:0:0: Direct-Access     WIBU -   CodeMeter-Stick  v1.0 PQ: 0 ANSI: 2
Mar 26 19:43:47 raspberrypi kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0
Mar 26 19:43:47 raspberrypi kernel: sd 0:0:0:0: [sda] 80384 512-byte logical blocks: (41.2 MB/39.3 MiB)
Mar 26 19:43:47 raspberrypi kernel: sd 0:0:0:0: [sda] Write Protect is off
Mar 26 19:43:47 raspberrypi kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
Mar 26 19:43:47 raspberrypi kernel: sd 0:0:0:0: [sda] No Caching mode page found
Mar 26 19:43:47 raspberrypi kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Mar 26 19:43:47 raspberrypi kernel:  sda: sda1
Mar 26 19:43:47 raspberrypi kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Mar 26 19:43:47 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:33502->[255.255.255.255]:161
Mar 26 19:43:48 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:33502->[255.255.255.255]:161
Mar 26 20:01:02 raspberrypi rngd[367]: stats: bits received from HRNG source: 500064
Mar 26 20:01:02 raspberrypi rngd[367]: stats: bits sent to kernel pool: 453824
Mar 26 20:01:02 raspberrypi rngd[367]: stats: entropy added to kernel pool: 453824
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2 successes: 25
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2 failures: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2(2001-10-10) Poker: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2(2001-10-10) Runs: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2(2001-10-10) Long run: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: HRNG source speed: (min=295.901; avg=505.255; max=556.256)Kibits/s
Mar 26 20:01:02 raspberrypi rngd[367]: stats: FIPS tests speed: (min=10.544; avg=13.575; max=31.268)Mibits/s
Mar 26 20:01:02 raspberrypi rngd[367]: stats: Lowest ready-buffers level: 2
Mar 26 20:01:02 raspberrypi rngd[367]: stats: Entropy starvations: 0
Mar 26 20:01:02 raspberrypi rngd[367]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Mar 26 20:04:36 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 20:04:36 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 20:04:37 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 20:04:37 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 20:04:38 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 20:04:38 raspberrypi kernel: usb 1-1.1: reset full-speed USB device number 14 using xhci_hcd
Mar 26 20:05:17 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] UNBOUND from connection 52
Mar 26 20:05:18 raspberrypi kernel: usbhid 1-1.3:1.0: couldn't find an input interrupt endpoint
Mar 26 20:05:18 raspberrypi mtp-probe[10587]: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 20:05:18 raspberrypi mtp-probe[10587]: bus: 1, device: 4 was not an MTP device
Mar 26 20:05:19 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:58621->[255.255.255.255]:161
Mar 26 20:05:20 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:58621->[255.255.255.255]:161
Mar 26 20:05:23 raspberrypi vhusbdarmpi4[20806]: Device 111 [088e:5036] UNBOUND from connection 52
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: USB disconnect, device number 14
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: new full-speed USB device number 15 using xhci_hcd
Mar 26 20:05:23 raspberrypi vhusbdarmpi4[20806]: Connection 52 successfully removed (reason:timeout)
Mar 26 20:05:23 raspberrypi vhusbdarmpi4[20806]: Unmanaging device 111 [088e:5036]
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: New USB device found, idVendor=088e, idProduct=5036, bcdDevice= 0.30
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: Product: iLok
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: Manufacturer: iLok
Mar 26 20:05:23 raspberrypi kernel: usb 1-1.1: SerialNumber: 3ACBA729_131A1E44
Mar 26 20:05:23 raspberrypi vhusbdarmpi4[20806]: Found Full speed device [088e:5036] "iLok, iLok" at address 111
Mar 26 20:05:23 raspberrypi mtp-probe[10606]: checking bus 1, device 15: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/
Mar 26 20:05:23 raspberrypi mtp-probe[10606]: bus: 1, device: 15 was not an MTP device
Mar 26 20:05:23 raspberrypi mtp-probe[10607]: checking bus 1, device 15: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/
Mar 26 20:05:23 raspberrypi mtp-probe[10607]: bus: 1, device: 15 was not an MTP device
Mar 26 20:05:34 raspberrypi vhusbdarmpi4[20806]: 100.76.205.121 connected as connection 56 (Standard TCP)
Mar 26 20:05:35 raspberrypi kernel: usb 1-1.3: reset low-speed USB device number 4 using xhci_hcd
Mar 26 20:05:35 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] BOUND to connection 56
Mar 26 20:05:35 raspberrypi kernel: usb 1-1.3: reset low-speed USB device number 4 using xhci_hcd
 

Submitted by Michael on Thu, 2025/03/27 - 07:25

#9

Can do do this, in the VirtualHere client, right click on an ilok and select Custom Event Handler and paste in this line:

onUnbind.$VENDOR_ID$=

then press OK. See if that helps

 

 

Submitted by daxliniere on Thu, 2025/03/27 - 07:39

#10

Done. Thanks Michael. I will keep you posted!

BTW, I did not unplug the WIBU yet (and have continued to have multiple iLok disconnects).

Submitted by daxliniere on Thu, 2025/03/27 - 08:01

#11

Unfortunately not.

Unplugging WIBU now.


Mar 26 21:45:51 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] UNBOUND from connection 62
Mar 26 21:45:51 raspberrypi kernel: usbhid 1-1.3:1.0: couldn't find an input interrupt endpoint
Mar 26 21:45:51 raspberrypi mtp-probe[26001]: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 21:45:51 raspberrypi mtp-probe[26001]: bus: 1, device: 4 was not an MTP device
Mar 26 21:45:53 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:51202->[255.255.255.255]:161
Mar 26 21:45:54 raspberrypi vhusbdarmpi4[20806]: Connection 62 remotely disconnected gracefully (rx msg size)
Mar 26 21:45:54 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:51202->[255.255.255.255]:161
Mar 26 21:45:56 raspberrypi vhusbdarmpi4[20806]: Device 111 [088e:5036] UNBOUND from connection 62
Mar 26 21:45:56 raspberrypi kernel: usb 1-1.1: can't set config #1, error -32
Mar 26 21:45:56 raspberrypi mtp-probe[26017]: checking bus 1, device 17: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/
Mar 26 21:45:56 raspberrypi mtp-probe[26017]: bus: 1, device: 17 was not an MTP device
Mar 26 21:45:56 raspberrypi kernel: usb 1-1.1: USB disconnect, device number 17
Mar 26 21:45:56 raspberrypi vhusbdarmpi4[20806]: Connection 62 successfully removed (reason:timeout)
Mar 26 21:45:56 raspberrypi vhusbdarmpi4[20806]: Unmanaging device 111 [088e:5036]
Mar 26 21:45:56 raspberrypi kernel: usb 1-1.1: new full-speed USB device number 18 using xhci_hcd
Mar 26 21:45:57 raspberrypi kernel: usb 1-1.1: New USB device found, idVendor=088e, idProduct=5036, bcdDevice= 0.30
Mar 26 21:45:57 raspberrypi kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 26 21:45:57 raspberrypi kernel: usb 1-1.1: Product: iLok
Mar 26 21:45:57 raspberrypi kernel: usb 1-1.1: Manufacturer: iLok
Mar 26 21:45:57 raspberrypi kernel: usb 1-1.1: SerialNumber: 3ACBA729_131A1E44
Mar 26 21:45:57 raspberrypi vhusbdarmpi4[20806]: Found Full speed device [088e:5036] "iLok, iLok" at address 111
Mar 26 21:45:57 raspberrypi mtp-probe[26021]: checking bus 1, device 18: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/
Mar 26 21:45:57 raspberrypi mtp-probe[26021]: bus: 1, device: 18 was not an MTP device
Mar 26 21:45:57 raspberrypi mtp-probe[26022]: checking bus 1, device 18: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/
Mar 26 21:45:57 raspberrypi mtp-probe[26022]: bus: 1, device: 18 was not an MTP device
Mar 26 21:46:11 raspberrypi vhusbdarmpi4[20806]: 100.76.205.121 connected as connection 65 (Standard TCP)
Mar 26 21:46:12 raspberrypi kernel: usb 1-1.3: reset low-speed USB device number 4 using xhci_hcd
Mar 26 21:46:12 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] BOUND to connection 65
Mar 26 21:46:13 raspberrypi kernel: usb 1-1.3: reset low-speed USB device number 4 using xhci_hcd
 

Submitted by daxliniere on Thu, 2025/03/27 - 08:59

#12

Another disconnect with the WIBU disconnected. Any new info in here?

Can you also add a warning popup to the client when a device-in-use disconnects?

Mar 26 22:55:50 raspberrypi vhusbdarmpi4[20806]: Device 113 [096e:0201] UNBOUND from connection 65
Mar 26 22:55:50 raspberrypi kernel: usbhid 1-1.3:1.0: couldn't find an input interrupt endpoint
Mar 26 22:55:50 raspberrypi mtp-probe[2100]: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-
Mar 26 22:55:50 raspberrypi mtp-probe[2100]: bus: 1, device: 4 was not an MTP device
Mar 26 22:55:51 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:50598->[255.255.255.255]:161
Mar 26 22:55:52 raspberrypi snmpd[645]: Connection from UDP: [192.168.2.221]:50598->[255.255.255.255]:161
Mar 26 22:55:55 raspberrypi vhusbdarmpi4[20806]: Device 111 [088e:5036] UNBOUND from connection 65
Mar 26 22:55:55 raspberrypi kernel: usb 1-1.1: USB disconnect, device number 18
Mar 26 22:55:55 raspberrypi kernel: usb 1-1.1: new full-speed USB device number 19 using xhci_hcd
Mar 26 22:55:56 raspberrypi kernel: usb 1-1.1: New USB device found, idVendor=088e, idProduct=5036, bcdDevice= 0.30
Mar 26 22:55:56 raspberrypi kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 26 22:55:56 raspberrypi kernel: usb 1-1.1: Product: iLok
Mar 26 22:55:56 raspberrypi kernel: usb 1-1.1: Manufacturer: iLok
Mar 26 22:55:56 raspberrypi kernel: usb 1-1.1: SerialNumber: 3ACBA729_131A1E44
Mar 26 22:55:56 raspberrypi mtp-probe[2117]: checking bus 1, device 19: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 22:55:56 raspberrypi mtp-probe[2117]: bus: 1, device: 19 was not an MTP device
Mar 26 22:55:56 raspberrypi mtp-probe[2118]: checking bus 1, device 19: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1
Mar 26 22:55:56 raspberrypi mtp-probe[2118]: bus: 1, device: 19 was not an MTP device
Mar 26 22:55:56 raspberrypi vhusbdarmpi4[20806]: Connection 65 successfully removed (reason:timeout)
Mar 26 22:55:56 raspberrypi vhusbdarmpi4[20806]: Unmanaging device 111 [088e:5036]
Mar 26 22:55:56 raspberrypi vhusbdarmpi4[20806]: Found Full speed device [088e:5036] "iLok, iLok" at address 111
 

Submitted by Michael on Thu, 2025/03/27 - 10:53

#13

"kernel: usb 1-1.1: USB disconnect, device number 18" this means the usb device is disconnecting itself and virtualhere detects that and then it drops from the client. 

Its not virtualhere disconnecting the device. 

Do you have all your USB devices just plugged into a normal hub or do you have some PCB in between like you mentioned.

 Are you sure thats ok? Does that cut the data lines and the power lines to the device? How do you trigger that?

 Normally to power cycle devices you just use a per-port-power-switching hub which i sell or you can find on here https://github.com/mvp/uhubctl then its all automatic (or you can do it from the virtualhere client if you want)

 

Submitted by daxliniere on Thu, 2025/03/27 - 20:06

#14

>Its not virtualhere disconnecting the device. 

Any idea why the server just completely disappears sometimes? I thought it may have been related to the issue of a single device disconnecting, but perhaps unrelated.

 

>Do you have all your USB devices just plugged into a normal hub or do you have some PCB in between like you mentioned.

Directly into the RPi 4b with the exception of the iLok which is through the USB power switch PCB I linked above. (which has worked for 1 year without issue.)

 

 >Are you sure thats ok? Does that cut the data lines and the power lines to the device? How do you trigger that?

Just power cut and it does so through a MOSFET. It's triggered by a GPIO pin controlled by Node-RED so I can reset the iLok when switching between machines. (otherwise I get the 'no sharing' warning.)

 

 >Normally to power cycle devices you just use a per-port-power-switching hub which i sell or you can find on here https://github.com/mvp/uhubctl then its all automatic (or you can do it from the virtualhere client if you want)

Yes, we chatted ages ago about trying to get this working. PPPC seems to have problems on my RPi, but I can't think of any good reason for it.
I did notice on the uhubctl link that you mention firmware versions and USB permissions. Would it be as simple as that now?



BOOTLOADER: update available
  CURRENT: Tue 25 Jan 14:30:41 UTC 2022 (1643121041)
   LATEST: Wed 11 Jan 17:40:52 UTC 2023 (1673458852)
  RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
           Use raspi-config to change the release.

 VL805_FW: Dedicated VL805 EEPROM
    VL805: up to date
  CURRENT: 000138c0
   LATEST: 000138c0

Submitted by daxliniere on Thu, 2025/03/27 - 20:22

#15

Updated, still no PPPS.


BOOTLOADER: up to date
  CURRENT: Wed 11 Jan 17:40:52 UTC 2023 (1673458852)
   LATEST: Wed 11 Jan 17:40:52 UTC 2023 (1673458852)
  RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
           Use raspi-config to change the release.

 VL805_FW: Dedicated VL805 EEPROM
    VL805: up to date
  CURRENT: 000138c0
   LATEST: 000138c0

Submitted by daxliniere on Fri, 2025/03/28 - 00:20

#16

Probably too early to say, but I haven't noticed a single disconnection today and the iLok is not set to auto-use, so that means no drop-outs yet.
I'll check back in.

Submitted by Michael on Fri, 2025/03/28 - 07:04

#17

"Any idea why the server just completely disappears sometimes? I thought it may have been related to the issue of a single device disconnecting, but perhaps unrelated."

Mar 26 22:55:56 raspberrypi vhusbdarmpi4[20806]: Connection 65 successfully removed (reason:timeout)

It times out, the network connection is dropping 

 

Submitted by daxliniere on Sat, 2025/03/29 - 10:14

#18

Yeah, drop-outs still occurring (probably) due to the power cycler PCB. 🙄

 

"It times out, the network connection is dropping "

Cheers, Michael. I have no idea in the world why that would be happening since it's connected via a 1 metre ethernet cable direct to the network switch. Gah. Technology is driving me crazy lately.
Thanks again.

Submitted by Michael on Sun, 2025/03/30 - 07:38

#19

I really recommend buying one of my power switching hubs and giving that a try instead.