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
Chase Eyster asked me to create this issue related to a recent conversation with the OOD Team during the SC24 conference.
I had a question about troubleshooting Open OnDemand problems reported by the users, which are caused by factors outside what we can control.
For example, we often get users reporting OOD connectivity issues, unresponsive app pages, logout, etc., and in many cases, the route cause is outside our control, like networking/firewall rules from an affiliate institution,
browser issues on the user’s end or even just user behavior.
As of right now, our best option is to check logs under /var/log/ondemand-nginx/$USER, but that is a tedious job,
and I was wondering if there is any plan from OOD to have a built-in tool reporting connectivity issues from the client side, maybe even something visible to the end user like a log of detected connect/disconnect times and errors.
Thank you,
Raffaele
The text was updated successfully, but these errors were encountered:
Chase Eyster asked me to create this issue related to a recent conversation with the OOD Team during the SC24 conference.
I had a question about troubleshooting Open OnDemand problems reported by the users, which are caused by factors outside what we can control.
For example, we often get users reporting OOD connectivity issues, unresponsive app pages, logout, etc., and in many cases, the route cause is outside our control, like networking/firewall rules from an affiliate institution,
browser issues on the user’s end or even just user behavior.
As of right now, our best option is to check logs under /var/log/ondemand-nginx/$USER, but that is a tedious job,
and I was wondering if there is any plan from OOD to have a built-in tool reporting connectivity issues from the client side, maybe even something visible to the end user like a log of detected connect/disconnect times and errors.
Thank you,
Raffaele
The text was updated successfully, but these errors were encountered: