topic SASGSUB LOGCONFIGLOC Error in Administration and Deployment

SASGSUB LOGCONFIGLOC Error

Key123 — Tue, 25 Feb 2025 04:09:57 GMT

in the new SASM8 environment we have been receiving the below error when user submits the job with SASGSUB and GridServer Logs complains the below error . when I submit the sample job with my id (not SAS installer) job is successful but user jobs are reporting 105 errors in the "bhist -l" output with below error in /Lev1/SASApp/GridServer/Logs.

I switched to the user and checked he is able to access all relevant config and log locations and have write permissions as well. Is there any other permissions I need to set on OS level OR any fix is available for this?

ERROR: Invalid option value /sas/foundation/config/Lev1/SASApp/GridServer/logconfig.batch.xml for SAS option LOGCONFIGLOC.
ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

Re: SASGSUB LOGCONFIGLOC Error

doug_sas — Tue, 25 Feb 2025 12:48:18 GMT

Does /sas/foundation/config/Lev1/SASApp/GridServer/logconfig.batch.xml exist? (I am assuming it does since it works for you)
Is /sas/foundation/config/Lev1/SASApp/GridServer/logconfig.batch.xml a valid Log configuration file? (I am assuming it does since it works for you)
Do users have access to the output log location (the grid shared directory)?

Re: SASGSUB LOGCONFIGLOC Error

Key123 — Tue, 25 Feb 2025 13:00:47 GMT

@doug_sas : Yes, file exists and valid. all users have access to grid shared work directory and folder is getting created under grid work with his user name and SASGSUB logfile/folders are storing.

BUT when the user is trying to re-route his SASGSUB log using the parameter -gridwork to other folder (where he has full access) it is failing with 105 error. Again ,I am able to run successfully using this -gridwork parameter as well.

Re: SASGSUB LOGCONFIGLOC Error

Tom — Tue, 25 Feb 2025 13:14:30 GMT

I would assume you are using a GRID of nodes to run the SAS jobs.

Are you sure the directory exists (and has the right permissions) on the host that was picked to run the jobs that are failing.

Remember to check each directory level along the path as you cannot get to /a/b/c if you cannot get to /a/b even if you have permission of c.

Re: SASGSUB LOGCONFIGLOC Error

doug_sas — Tue, 25 Feb 2025 13:20:13 GMT

OK, I do not have enough information.

What is the client platform?
What is the server platform?
Are you using a shared directory?

Re: SASGSUB LOGCONFIGLOC Error

Key123 — Tue, 25 Feb 2025 13:34:16 GMT

We are on SAS9.4 M8, RHEL8 and user jobs are starting from crontab with sasgsub command.

Yes, it is a shared directory for both gridwork and configuration.

Re: SASGSUB LOGCONFIGLOC Error

doug_sas — Tue, 25 Feb 2025 13:48:26 GMT

So '-gridwork' should point to the grid shared directory and be the same from the client machine as it is from the grid machine.

For example, SASGSUB has '-GRIDWORK /grid/shared/dir' means that SASGSUB will create a user directory & job directory at '/grid/shared/dir/<user>/<job>'.

In the grid, the GridServer directory should have a grid.cfg that has SASGRIDSHARDIR also set to `/grid/shared/dir``. Is that correct?

Have you logged onto a grid machine as the user and tried to run the command that LSF ran?