jobservers and users and groups

[wim.ve...@billinghouse.nl]

Hello,

I am improving on my schedulix jobs.Still not the final job layouts, but learning the system and implementing user requirements related jobs (monitoring, security etc).

So I had a working solution with a jobserver created with the following command line

setup_jobserver -n LOCALHOST_1 -w localhost_1 -w /opt/schedulix/workdirs/localhost_1 -c -h 45500 -u SYSTEM -p ****** -o PUBLIC

I used the standard sdmsadm user, and it worked.

One requirement is that we have tester, user acceptance testers and production operators. Each should see their jobs and the jobs of the groups before it (so production sees everything, testers only their stuff).

I adjusted my folders, jobs etc to have the correct groups and created both server users for the groups and web users so they can logon using the appropriate server user.

(In reality I fixed the scripts I use and then regenerated all jobs etc).

So I logged in as a tester and submitted a job. It failed with an error and the message : Couldn't execute command (13 / Permission denied) 

And now I am puzzled. It was my understanding I created the jobserver with owner PUBLIC so it would be public and everybody can see and access it. It turned out it was not visible (the GLOBAL.<nodename> level turned out to have group ADMIN. So I adjusted the group to PUBLIC.

Now the tester can see the resource, but I still get the same error.

I verified the tester user has the appropriate TESTER and PUBLIC groups assigned.

What is the system complaining about that it does not have permission for ?

[Ronald Jeninga]

Hi Wim,

this error message comes from the operating system.

The jobserver is started by some user, most likely not root (which is good), and all jobs will be executed with the privileges of that user.

The script or program you try to execute doesn't grant the user running the jobserver to execute it.

So you'll have to change the access mode of the program/script. "chmod 755" or so is a good starting point.

HTH

Regards,

Ronald

[wim.ve...@billinghouse.nl]

Hi,

I am improving my skills :)

On a hinch I decided to replace the run program line with '0', so it would only need the jobserver, and that worked.

So I investigated the os. It turned out that the execution bit on the shell script was no longer there. Fixed that and now it works.