Updating 3.1.7 to 3.1.10 Shell app terminates after 2 min

Get Help
1

Good Afternoon All,
We recently were forced to upgrade our instance of OOD from 3.1.7 to 3.1.10 and now our users are experiencing issues with the OOD shell app where it terminates the connection after 2 min. I think this is related to: 3.1.9 seems to break the Shell app due to CSRF token issue · Issue #3894 · OSC/ondemand · GitHub

That said, it is unclear how to fix this. We are running the following:
OS: Rocky Linux 9.5 (5.14.0-162.6.1.el9_1.x86_64)
Httpd: httpd-2.4.62-1.el9.x86_64
OOD: ondemand-3.1.10-1.el9.x86_64

Is this issue related to the above bug? Or am I just missing a new config somewhere?

Thanks for any direction.

2

Hi, sorry for the delay - Yes you are missing a new configuration. You can find more here.

https://osc.github.io/ood-documentation/latest/customizations.html#enable-and-configure-shell-ping-pong

3

Appreciated and no worries about he delay, I implemented the following:
/etc/ood/config/apps/shell/env

# /etc/ood/config/apps/shell/env

#needed for shell app to not log you out every 2 minutes
OOD_SHELL_INACTIVE_TIMEOUT_MS=1200000
OOD_SHELL_MAX_DURATION_MS=3600000
# OOD_SHELL_PING_PONG=false

However, it is not taking affect. I tried running the ‘update_ood_portal’ ‘systemctl restart httpd’ and ‘restart web server’ in OOD but no dice. I read through the docs as well and couldn’t see anything else to try. Thoughts?

4

This is the default - i.e., commented out means ping pong is not enabled.

# OOD_SHELL_PING_PONG=false

The docs say

Setting OOD_SHELL_PING_PONG to anything will enable ping pongs.
Removing it or commenting it out will disable ping pongs
(it's disabled by default).

So you should likely set it to true or similar, a value of false would work, but is likely confusing.
OOD_SHELL_PING_PONG=true

5

That makes sense now. Sorry Iw as confused about what that ENV var did. I set it to true and that fixed my issue. Thanks!