We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
stampzilla-mbus[2334]: time="2023-04-01T22:14:04.113409363+02:00" level=error msg="error fetching mbus data from device 3: write tcp 192.168.13.2:38246->192.168.13.42:10001: write: broken pipe" func="main.(*Worker).start" file="/home/jonaz/git/stampzilla-go/nodes/stampzilla-mbus/worker.go:100"
perhaps check with errors.Is(err, syscall.EPIPE) or just reconnect on all errors?
The text was updated successfully, but these errors were encountered:
happend again. time="2023-09-06T11:21:58.749557326+02:00" level=error msg="error fetching mbus data from device 2: write tcp 192.168.13.2:46166->192.168.13.42:10001: write: broken pipe" func="main.(*Worker).start" file="/home/jonaz/git/stampzilla-go/nodes/stampzilla-mbus/worker.go:100"
Sorry, something went wrong.
Reconnect on broken pipe
a153ed6
Solves: #429
No branches or pull requests
stampzilla-mbus[2334]: time="2023-04-01T22:14:04.113409363+02:00" level=error msg="error fetching mbus data from device 3: write tcp 192.168.13.2:38246->192.168.13.42:10001: write: broken pipe" func="main.(*Worker).start" file="/home/jonaz/git/stampzilla-go/nodes/stampzilla-mbus/worker.go:100"
perhaps check with errors.Is(err, syscall.EPIPE) or just reconnect on all errors?
The text was updated successfully, but these errors were encountered: