-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: expected START_HEADER0 0xfe, got nothing #22
Comments
same. this line in SocketServerCollector is reading 0 bytes, which I believe means the socket is closed: Line 2558 in fa488f9
|
in 7 hours, it spewed 155GB in logs until it filled up my disk 🤪
|
interesting. mine goes bad because a port scanner on my network (an ovrc hub) hits the listening socket and sends garbage. I dunno what would cause an issue like that with client mode.
after that, it loops forever with (these logs from |
I ended up forcing a restart on error as a temp solution but am curious in why it's happening. I see you have a pending commit and will try the change. |
adding the PR stated by mroch seems to have fixed the problem so I am closing this issue. |
Having issues with btmon in client mode hanging up and giving
expected START_HEADER0 0xfe, got nothing
restarting the btmon.py seems to fix it for awhile but eventually comes back after a few days.
The text was updated successfully, but these errors were encountered: