06-09-2017 09:56 AM
I have a new Linux admin that just started this week (and let me note that I too am new to SAS). We loaded the SAS tools on his computer yesterday and I have been showing him our system. I have LASR load jobs that need to be run anytime the server is taken offline. I can run these jobs without any issues. I have a backup who can run these jobs with any issues. And, we also have another Linux admin who can run these jobs without any issues. However, my new Linus admin is getting the following error (in the log file) when he attempts to run the LASR load jobs via Schedule Manager:
ERROR: Invalid option value /data/sasconfig/Lev1/SASApp/BatchServer/logconfig.apm.xml for SAS option LOGCONFIGLOC.
ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.
I should also not that this error ONLY occurs when he attmpts to run the jobs via Scheudle Manager. If he goes into DI Studio, he can run the jobs successfully, without any issues.
What am I missing?
06-23-2017 07:35 AM
I just wanted to follow-up on this ticket. This ended up being a Linux permissions issue. We got the new admin added to the appropriate Linux group and the problem was solved. Thanks for everyone's help and suggestions.
06-09-2017 10:07 AM
My first avenue of debugging would be to log on to the server with his/her credentials (or do su - username from the root account), navigate to /data/sasconfig/Lev1/SASApp/BatchServer/, and try to read logconfig.apm.xml. If somewhere on the way you get a "permission denied", you've come a lot nearer to the solution.
06-09-2017 11:14 AM
Make sure that he has read/write access to folder /<SASConfig>/Lev<X>/SASApp/BatchServer/PerfLogs
But that would make the error message from the OP seriously misleading.
06-09-2017 11:12 AM
06-09-2017 11:22 AM
06-09-2017 11:42 AM - edited 06-09-2017 11:43 AM
What do you mean when you say "start Base SAS"? I am new to SAS, so I am still learning. :-)
06-09-2017 11:46 AM
@rgreen33 I suppose that SAS has been installed on Linux? If so run the following command:
06-09-2017 11:52 AM
06-09-2017 02:22 PM
06-09-2017 02:30 PM
06-09-2017 09:18 PM
This problem is usually caused either by:
Also, if the logconfigloc option is pointing to NAS using CIFS, you may have a file locking issues.
06-11-2017 11:58 PM
Need further help from the community? Please ask a new question.