-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[Bug]: Broken pipe when listening over tcp for events from meshtasticd (solved: blanking screen crashes meshtasticd) #5764
Comments
If I knew the exception had happened, I could restart my connection or exit the script. But it keeps running as if nothing is wrong. |
Ok I've lost the exact log message, but I believe it was saying it would blank the screen, then crashed and restarted meshtasticd. I was still configured for a 2.8" waveshare screen. I think the blanking operation is dangerous with the configured and not present screen. Removing the screen from the config is avoiding the crash. I'm ok if you want to close or combine or whatever since the ticket has taken a turn. |
I'm seeing this crash even when the screen is present |
I'm seeing this error too. Here's my log error.
|
A potential answer for this is my host machine going to sleep while the script is running. Edit: update. It's not. Ran this on Ubuntu server as a docker container and still got a broken pipe error. |
Category
Other
Hardware
Linux Native
Firmware Version
2.5.15
Description
If I use the tcp listener from https://github.com/brad28b/meshtastic-cli-receive-text/blob/main/read_messages_tcp.py it gets stuck every once in a while, crashing in a background thread apparently. I can't rescue it and once it crashes, no events will be received.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: