You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven’t had time to fix it, but I wanted to document this bug here as it’s been causing the container to restart continuously because of a failed health check.
In your rtl_airband.conf file you can define multiple outputs per device, and then temporarily or permanently enable/disable them by doing one of these 3 things
delete the output from the config file (really permanent)
Set disable=true in the output block
Comment out the output block with # in front of each line
The health check unfortunately doesn’t ignore any output blocks that are disabled with methods 2 or 3.
3 is an easy fix by updating the grep formula here.
2 is harder to fix and would require a more structural way of parsing the config file.
The text was updated successfully, but these errors were encountered:
Work around for now… in the custom rtl_airband.conf, in addition to deploying method 2 or 3, also temporarily add an extra letter in server and port in the inactive output block.
I haven’t had time to fix it, but I wanted to document this bug here as it’s been causing the container to restart continuously because of a failed health check.
In your rtl_airband.conf file you can define multiple outputs per device, and then temporarily or permanently enable/disable them by doing one of these 3 things
disable=true
in theoutput
blockThe health check unfortunately doesn’t ignore any output blocks that are disabled with methods 2 or 3.
3 is an easy fix by updating the
grep
formula here.2 is harder to fix and would require a more structural way of parsing the config file.
The text was updated successfully, but these errors were encountered: