-
Notifications
You must be signed in to change notification settings - Fork 138
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
[Services] Websocket failure to update service status #2681
Comments
As a confirmation, setting |
For details, the exception we see in the logs when visiting the Services page is:
As we can see, the command itself does not fail, but returns a proper output with a rockstor-core/src/rockstor/system/osi.py Lines 243 to 251 in a2d7594
Here, we should thus set |
…r#2681 We currently throw an Exception when checking the status of a surpervisor-controlled service such as replication. This leads to an exception being thrown even when expected (service is off), which can itself interrupt other parts such as our get_services websocket. This commit adds a new arg to the superctl() function to allow for the possibility to not throw an exception. Note that run_command's default for throw is True, so respect this here.
…r#2681 We currently throw an Exception when checking the status of a surpervisor-controlled service such as replication. This leads to an exception being thrown even when expected (service is off), which can itself interrupt other parts such as our get_services websocket. This commit adds a new arg to the superctl() function to allow for the possibility to not throw an exception. Note that run_command's default for throw is True, so respect this here.
…date-service-status Don't throw exception when getting supervisord service status #2681
Closing as: |
In the "System" > "Services" page, we have websocket that fetches the status of each service and sends it to our front-end to update the toggle buttons. This unfortunately is currently failing, resulting in a toggled button remaining "misaligned" (see screenshot below) until a manual page refresh:
By using Firefox's dev tools, we can see that the websocket is correctly created and removed upon visiting/leaving the "Services" page, but it does not seem to send/return any data on the services' statuses, hence the failure to refresh the toggle button state.
It turns out this failure results from an Exception thrown when checking the status of the "replication" service. This exception is normal (when the replication service is OFF), but we shouldn't fail the checking of service status as a result.
The text was updated successfully, but these errors were encountered: