Operating System Scheduling: unable to login

[MariaD]

Hi Folks,

We tried to login in Operation System Services through SAS MC but we can't login. We are on Linux server and the crontab is working fine. We are using an account with administration privilege.

Any idea? Regards,

[VDD]

Did you confirm the server is available via you personal access account???????????????

[MariaD]

Thanks, how could I verify? If you mean that my server user (on Linux) could add events on crontab and execute it, yes my user can jobs on it and it’a working.

Regards,

[AnandVyas]

Hi @MariaD ,

UNIX scheduling uses the at command to execute jobs. However, this command might not be enabled for use by the scheduling server's user ID. To determine whether the command is enabled, run a test of the at command. Here is an example test:

echo touch /tmp/attest | at now
sleep 5
ls /tmp/attest

What is at?

Unlike cron, which let us run a task on a regular basis, at gives us the ability to execute a command or a script at a specified date and hour, or after a given interval of time. Minutes, hours, days or weeks can be used as units. It's even possible to use certain "keywords" as midnight or teatime (which corresponds to 4pm). 

Thanks!

[MariaD]

Thanks @AnandVyas . In fact, I verified and we don't have "at" command enable on our Linux server. I'll install it and make again the test. Let's you know the results. 

[MariaD]

Hi @AnandVyas ,

We installed "at" command and it's working. Our linux user for SAS (we use a SAS Token) can execute at command without any error. 

But still, we can't not login on Operating System Services to schedule throw SAS MC. We tried with "sasadm" user, with Linux user (used for SAS Token), nothing works. Any idea why?

[SASKiwi]

The sasadm@passwd account is only defined in SAS metadata. It is not an OS account. You need to use an OS account to log onto OS scheduling. You can use a personal user OS account to test scheduling as long as the account has scheduling permissions setup in SMC.

[AnandVyas]

What's the error you get when you use a normal user, not SAS internal user (sasadm@saspw) ?

[MariaD]

Hi @AnandVyas ,

We test using another user (not sasadm@saspw) and the situation is the same. Please see images below. We have all our users defined with internal account and we use a SAS Token to connect to SAS Workspace Server. Off course the user has Job Scheduling permission.

We also made a test using a host server user to login on Operating System Scheduling when login windows appears (image 1) and the results is the same.

[VDD]

@MariaD maybe you should call in and get assistance from SAS technical advisors.  If you pay for SAS and need assistance that help should be part of the purchase.  

Like I noted at the beginning of this Q, test access using a real person access.  Can they make connection without using the tokens being passed?

You are the server admin?  Then call in a ticket.

[SASKiwi]

@MariaD - By adding @saspw on the end of the user account you are calling the metadata identity of the account not the OS version. Try removing this.