MS3FGX
Occassional "bluelog: Received error from BlueZ!" errors
I noticed (from the status LED on the back of the Air Cable Host XR3 that I'm using) that from time to time, bluelog has experienced an error, and I'm no longer logging devices. Please let me know if there is some way to enable additional debug output, etc. if you require additional detail. Information about the setup I'm using: Raspberry Pi running Kali Linux 1.0.6 (updated to current), with an Aircable host XR3, and of course bluelog 1.1.2.
Unfortunately, I've heard from multiple people that the USB controller in the Raspberry Pi occasionally glitches a bit when running for long stretches of time. A few fixes have been attempted like slowing down scanning or trying to reset the BT interface when it locks up, but none of them have worked.
I know it sounds pretty lame, but the only way anyone seems to have gotten around this particular problem is to watch for these error messages and restart BlueZ by way of something like a cron job.
How long are you running before you see the errors?
Sometimes a little less than an hour, sometimes a couple of hours. Now that I know they're reported in syslog, I will keep a closer eye on them and try to correlate those times against the begin scan timestamp in the log.
Really? That's pretty bad then. The last time somebody was having problems like this on a Pi, it didn't come up until they were scanning for a couple days continuously.
Let me see if I can figure something out in the way of diagnostics.
Come to think of it, I don't think it's purely the USB bus. I've got a 2.4GHz and a 5 GHz wardriving rig (each with 4 Alfa cards) that seem to run for at least a day at a time without issue. I wonder if BlueZ or something else is just polling too aggressively.
I'm going to fire up bluelog on Kali on my Samsung Ultrabook and let it run overnight to see if all is still well in the morning.
Did you ever get a chance to run it on the Samsung to see if it crashes? One thing you might try, which works on some embedded devices with janky USB controllers, is to connect the Host XR to a USB hub, and then to the Pi.
For whatever reason, using a hub in between the BT adapter and the device has cleared up errors I've gotten in the past on things like OpenWRT routers.
I ran the AirCable with the Ultrabook overnight without any errors. I will give the hub idea a try and report back. Thanks for following up.