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
The qmsk-dmx process exits if sending ArtNet discovery packets fails:
qmsk-dmx
INFO qmsk.web: POST presets/test: &heads.APIPresetParams{preset:(*heads.Preset)(0xc82001f880), Intensity:(*heads.Intensity)(0xc82026ea20)} WARNING artnet:controller<[::]:6454> discovery timeout: 192.168.2.100:6454 INFO artnet.Discovery: 192.168.2.100:6454: INFO Name: NodeMCU-ARTNET INFO Output 0: 0:0.1 WARNING artnet:controller<[::]:6454> discovery timeout: 192.168.2.100:6454 INFO artnet.Discovery: 192.168.2.100:6454: INFO Name: NodeMCU-ARTNET INFO Output 0: 0:0.1 WARNING artnet:controller<[::]:6454> discovery timeout: 192.168.2.100:6454 INFO artnet.Discovery: 192.168.2.100:6454: INFO Name: NodeMCU-ARTNET INFO Output 0: 0:0.1 WARNING artnet:controller<[::]:6454> discovery timeout: 192.168.2.100:6454 INFO artnet.Discovery: 192.168.2.100:6454: INFO Name: NodeMCU-ARTNET INFO Output 0: 0:0.1 WARNING artnet:controller<[::]:6454> discovery timeout: 192.168.2.100:6454 WARNING artnet:universe<0:0.1> SendDMX: SendDMX broadcast 0:0.1: write udp [::]:6454->192.168.2.100:6454: sendto: network is unreachable ERROR artnet:controller<[::]:6454> discovery: sendPoll: write udp [::]:6454->192.168.2.100:6454: sendto: network is unreachable FATAL artnet discovery ended
This happens if the interface associated with the artnet discovery addresse goes link-down. The controller should keep running instead.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
qmsk-dmx
process exits if sending ArtNet discovery packets fails:This happens if the interface associated with the artnet discovery addresse goes link-down. The controller should keep running instead.
The text was updated successfully, but these errors were encountered: