suexec Issue After Upgrading Server to RHEL 9

[brad.traver]

We recently upgraded our WebMO server to RHEL 9. I have reconfigured Apache and installed the necessary dependent packages. When I go to run a test job, the job reports as stuck in the "running" state but there is no actual job in the Slurm queue. When I look at /home/webmo/webmo/errors, I see the following:

Code: Select all

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

If I remember correctly, when I was troubleshooting install issues before, we had to set something in the /etc/sudoers file to get suexec to work for the webmo account. I can't for the life of me remember what that is. Does anyone know what needs to be set to resolve this issue? Thanks!

[schmidt]

Check out the following docs:

https://www.webmo.net/link/help/Externa ... ation.html

Step #7 is probably the one you want!

[schmidt]

Note also that 'suexec' != 'sudo' (although both are useful!)

Suexec just lets Apache scripts installed under ~user run under UID 'user'. This is useful for a vanilla WebMO install and keeps your jobs running as a normal user (vs. user 'apache', for example).

Sudo is used by WebMO Entprise with SLURM (or another batch queue) so that WebMO can exeute jobs under the UID of *many different* users, e.g. so your cluser users each have their own jobs queued/executed under their own unique UIDs.

[brad.traver]

That did it! Thank you so much!