Raspberry Pi B+ server crashes

4 posts / 0 new
Last post
johng
Raspberry Pi B+ server crashes

I thought I'd try out virtualhere on a rpi b+, and have encountered crashes. Here is the log data :

Jul 22 09:38:05 raspberrypi vhusbdarmhf: >>> Starting v2.3.9 (Built: Jul 13 2015, 06:07:23)<<<
Jul 22 09:38:05 raspberrypi vhusbdarmhf: Using configuration /home/pi/config.ini
Jul 22 09:38:05 raspberrypi vhusbdarmhf: Server licensed to=unlicensed max_devices=1
Jul 22 09:38:05 raspberrypi vhusbdarmhf: Using large URB's
Jul 22 09:38:05 raspberrypi vhusbdarmhf: TCPServer starting...
Jul 22 09:38:05 raspberrypi vhusbdarmhf: Listening on all network interfaces at port 7575
Jul 22 09:38:05 raspberrypi vhusbdarmhf: Found Full speed device [045e:0745] "Microsoft, Microsoft® 2.4GHz Transceiver v8.0" at address 114
Jul 22 09:38:05 raspberrypi vhusbdarmhf: TCPServer (7575) started
Jul 22 09:38:05 raspberrypi vhusbdarmhf: Found Full speed device [0403:6001] "FTDI, FT232R USB UART" at address 115
Jul 22 09:38:06 raspberrypi vhusbdarmhf: Callback: #027VirtualHere USB Sharing#006_vhusb#004_tcp#005local Name Registered
Jul 22 09:38:21 raspberrypi vhusbdarmhf: 10.2.7.21 connected
Jul 22 09:38:21 raspberrypi vhusbdarmhf: Device 115 BOUND to connection 1
Jul 22 09:38:57 raspberrypi vhusbdarmhf: Device 115 UNBOUND from connection 1
Jul 22 09:39:05 raspberrypi vhusbdarmhf: Device 115 BOUND to connection 1
Jul 22 09:39:38 raspberrypi vhusbdarmhf: Device 115 UNBOUND from connection 1
Jul 22 09:39:42 raspberrypi vhusbdarmhf: Device 115 BOUND to connection 1
Jul 22 09:39:56 raspberrypi vhusbdarmhf: VirtualHere caught signal 11 (Segmentation fault) and must exit. Sorry for the inconvenience, please contact mail@virtualhere for help

RPi is running the current Raspbian release.

Also, when the server crashes, I get a BSOD on the Windows 7 Client. Not sure if the server crashes & causes the client problem, or the other way round.

Any suggestions ?

John

Michael
I notice its unbind/rebinding

I notice its unbind/rebinding to the device mutiple times, what was the reason for that? If you dont unbind the device does it keep running ok?

redyeti
I am seeing something very

I am seeing something very similar. My Rpi service will shutdown (but the process is still running), leaving the client in the dust.

Here's some logs of what I'm seeing.

SERVER

pi@server ~ $ps aux | grep usb
root 2176 0.4 0.6 5248 3068 ? Ssl Jul20 19:30 /usr/sbin/vhusbdarmhf -b -c /root/config.ini

pi@server ~ $ cat /var/log/syslog | grep usb
Jul 23 18:31:25 server vhusbdarmhf: Removing connection 5 (timeout)...
Jul 23 18:31:25 server vhusbdarmhf: Device 1121 UNBOUND from connection 5
Jul 23 18:31:25 server vhusbdarmhf: Device 1125 UNBOUND from connection 5
Jul 23 18:31:25 server vhusbdarmhf: Device 11271 UNBOUND from connection 5
Jul 23 18:31:25 server vhusbdarmhf: Device 1126 UNBOUND from connection 5
Jul 23 18:31:25 server vhusbdarmhf: Device 11272 UNBOUND from connection 5
Jul 23 18:31:25 server vhusbdarmhf: Connection 5 successfully removed
Jul 23 18:31:31 server vhusbdarmhf: 10.2.72.189 connected
Jul 23 23:49:17 server vhusbdarmhf: >>> Starting v2.3.8 (Built: Jul 9 2015, 14:19:45)<<<
Jul 23 23:49:17 server vhusbdarmhf: >>> Shutdown <<<

pi@server ~ $ cat /var/log/syslog.1 | grep usb
Jul 22 19:05:28 server vhusbdarmhf: Removing connection 4 (timeout)...
Jul 22 19:05:28 server vhusbdarmhf: Device 1121 UNBOUND from connection 4
Jul 22 19:05:28 server vhusbdarmhf: Device 1125 UNBOUND from connection 4
Jul 22 19:05:29 server vhusbdarmhf: Device 11271 UNBOUND from connection 4
Jul 22 19:05:29 server vhusbdarmhf: Device 1126 UNBOUND from connection 4
Jul 22 19:05:29 server vhusbdarmhf: Device 1123 UNBOUND from connection 4
Jul 22 19:05:29 server vhusbdarmhf: Device 11272 UNBOUND from connection 4
Jul 22 19:05:29 server vhusbdarmhf: Connection 4 successfully removed
Jul 22 19:05:31 server vhusbdarmhf: 10.2.72.189 connected
Jul 22 19:05:31 server kernel: [171324.738928] usb 1-1.2.1: reset high-speed USB device number 6 using dwc_otg
Jul 22 19:05:31 server vhusbdarmhf: Device 1121 BOUND to connection 5
Jul 22 19:05:31 server kernel: [171324.918875] usb 1-1.2.5: reset high-speed USB device number 10 using dwc_otg
Jul 22 19:05:31 server vhusbdarmhf: Device 1125 BOUND to connection 5
Jul 22 19:05:31 server kernel: [171325.098865] usb 1-1.2.7.1: reset high-speed USB device number 79 using dwc_otg
Jul 22 19:05:31 server vhusbdarmhf: Device 11271 BOUND to connection 5
Jul 22 19:05:31 server kernel: [171325.278995] usb 1-1.2.6: reset high-speed USB device number 84 using dwc_otg
Jul 22 19:05:32 server vhusbdarmhf: Device 1126 BOUND to connection 5
Jul 22 19:05:32 server vhusbdarmhf: Error -1 resetting device 0x04e8/0x6860 for capture
Jul 22 19:05:32 server kernel: [171325.419943] usb 1-1.2.3: USB disconnect, device number 85
Jul 22 19:05:32 server vhusbdarmhf: Error -1 binding device 1123 to connection 5
Jul 22 19:05:32 server kernel: [171325.518917] usb 1-1.2.7.2: reset high-speed USB device number 86 using dwc_otg
Jul 22 19:05:32 server vhusbdarmhf: Device 11272 BOUND to connection 5
Jul 22 19:05:32 server vhusbdarmhf: Unmanaging device 1123
Jul 22 19:05:32 server kernel: [171325.698877] usb 1-1.2.3: new high-speed USB device number 87 using dwc_otg
Jul 22 19:05:32 server kernel: [171325.801307] usb 1-1.2.3: New USB device found, idVendor=04e8, idProduct=6860
Jul 22 19:05:32 server kernel: [171325.801350] usb 1-1.2.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jul 22 19:05:32 server kernel: [171325.801372] usb 1-1.2.3: Product: SAMSUNG_Android
Jul 22 19:05:32 server kernel: [171325.801395] usb 1-1.2.3: Manufacturer: SAMSUNG
Jul 22 19:05:32 server kernel: [171325.801416] usb 1-1.2.3: SerialNumber: 4d00071c99013125
Jul 22 19:05:33 server vhusbdarmhf: Found High speed device [04e8:6860] "SAMSUNG, SAMSUNG_Android" at address 1123

CLIENT

user@client ~ $ sudo vhclientx86_64 -t "LIST"
IPC client timeout waiting for server...

user@client ~ $ ps aux |grep vh
root 1089 0.0 0.4 12508 9588 ? Ssl 11:31 0:08 /usr/sbin/vhclientx86_64 -n -c /root/.vhui

redyeti
My issue seems to be related

My issue seems to be related to the client instead, I'll open a new thread for this.

Log in or register to post comments