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
How often does it reproduce? Is there a required condition?
Always for me.
What is the expected behaviour?
The option to enable/disable ping of the db host should be available in webapp, and saved correctly in config.xml.
What do you see instead?
Additional information
While not common in the kind of environments mythtv is going to be installed in, a host not responding to ping is (or was last time I looked) a perfectly valid condition.
The text was updated successfully, but these errors were encountered:
The ping option is no longer used. Since 2017 the code uses a port check rather than a ping, and always does the check, regardless of the setting. The ping check should really be removed from the mythfrontend setup and from the config.xml file. I don't know why the web app is always setting it true.
Platform:
Linux mythbackend 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
MythTV version:
Package version:
Component:
webapp
What steps will reproduce the bug?
<PingHost>
is now set to true.How often does it reproduce? Is there a required condition?
Always for me.
What is the expected behaviour?
The option to enable/disable ping of the db host should be available in webapp, and saved correctly in config.xml.
What do you see instead?
Additional information
While not common in the kind of environments mythtv is going to be installed in, a host not responding to ping is (or was last time I looked) a perfectly valid condition.
The text was updated successfully, but these errors were encountered: