EFForg
Device Crashes / Reboots When Walking By Particular Location
A particular location that I normally pass by has, twice, caused the device to crash/reboot. Upon looking at the rayhunter console after it comes back up there doesn't appear to be anything recorded for this timeframe.
This is on an RCL400L with a not-activated Verizon SIM installed; device purchased new directly from an eBay seller.
What's the best way to gather more information so this can be troubleshot?
that's incredibly odd! before you restart the rayhunter daemon, there should be logs from the crash in /data/rayhunter/rayhunter.log. if rayhunter's starting up automatically and wiping the old log away, you might change line 9 of /etc/init.d/rayhunter_daemon to:
--startas /bin/bash -- -c "RUST_LOG=info exec /data/rayhunter/rayhunter-daemon /data/rayhunter/config.toml >> /data/rayhunter/rayhunter.log 2>&1"
It was actually the whole device that is rebooting. Like, I'd see it doing the powering on message and all... Then rayhunter starts right up.
And thanks, I'll give that a go and see if I can repro it again the next time I'm in that location. (Likely early next week.) Maybe having adb log running would be interesting as well...
ohh i misread the issue, that's even odder. when you say nothing's recorded for that timeframe, do you mean the QMDL is 0 bytes long?
I'll just dump a bunch of info here; hopefully that's okay.
First, the device didn't seem to set its time right.
This morning I started up the device and went somewhere. As I was walking into the building I noticed the device seemed off, so I turned it on. (It had been on in the car.) During the time I was in the building it seemed just fine. Then I walked out to my car and just before getting to the car I noticed it was going through it's power on sequence.
(EDIT: So I twice passed the entrance to this facility, and it wouldn't surprise me if there's some manner of network experimentation happening here.)
Attached are the current and previous QMDLs and PCAPs in crash.zip.
rayhunter.log is showing just this, which I believe is since it last started up:
R A Y H U N T E R 🐳 [2025-03-19T17:36:02Z INFO rayhunter::diag_device] retrieving diag logging capabilities... [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 329 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 1 [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 298 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 4 [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 140 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 5 [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 168 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 7 [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 122 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 10 [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 73 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 11 [2025-03-19T17:36:02Z WARN rayhunter::diag] warning: 72 leftover bytes when parsing Message [2025-03-19T17:36:02Z INFO rayhunter::diag_device] enabled logging for log type 13 [2025-03-19T17:36:02Z INFO rayhunter_daemon] Starting Diag Thread [2025-03-19T17:36:02Z INFO rayhunter_daemon] Starting UI [2025-03-19T17:36:02Z INFO rayhunter_daemon] create shutdown thread [2025-03-19T17:36:02Z INFO rayhunter_daemon] spinning up server [2025-03-19T17:36:22Z WARN rayhunter::diag_device] warning: 20296 leftover bytes when parsing MessagesContainer [2025-03-19T17:36:22Z WARN rayhunter::diag_device] warning: 509 leftover bytes when parsing MessagesContainer [2025-03-19T17:36:22Z WARN rayhunter::diag_device] warning: 1222 leftover bytes when parsing MessagesContainer [2025-03-19T17:36:22Z WARN rayhunter::diag_device] warning: 512 leftover bytes when parsing MessagesContainer [2025-03-19T17:36:22Z WARN rayhunter::diag_device] warning: 8224 leftover bytes when parsing MessagesContainer [2025-03-19T17:36:22Z INFO rayhunter_daemon] The orca is hunting for stingrays...
Here's what the web UI shows currently:
adb logcat is giving me a logcat read failure unfortunately, so nothing there. And /var/log/dmesg seems to be just since boot.
Hmm...
I also had frequent crashes in a certain area. I will go back there some time and see if it happens again, and try to get some logs if so.
@c0nsumer adb logcat won't work because logcat doesn't exist on this system because its not actually an android system. If either of you can start rayhunter like so:
export RUST_BACKTRACE=1; ./rayhunter-daemon config.toml > crash.log and paste the output of crash.log here when it crashes also upload the qmdl file of the session where it crashes please. Thanks!
@c0nsumer
adb logcatwon't work because logcat doesn't exist on this system because its not actually an android system. If either of you can start rayhunter like so:export RUST_BACKTRACE=1; ./rayhunter-daemon config.toml > crash.logand paste the output of crash.log here when it crashes also upload the qmdl file of the session where it crashes please. Thanks!
Sure thing. Let me see what I can do. Might take me a few days to get back to the location again.
closing this as stale, reopen if you are able to repro and produce logs though!
Understood. Sorry I don't have anything more for now, just haven't made it back to this location with sufficient time. I'll see what I can do...