topic Re: SAS Environment Manager Framework activiation in Administration and Deployment

SAS Environment Manager Framework activiation

cesargf80 — Mon, 03 May 2021 20:09:03 GMT

After initializing ./apm_init.sh , all sasv9_usermods.cfg file under SASAPP(BatchServer, ConnectServer, StoredProcessServer, WorkspaceServer, PooledWorkspaceServer) are getting updated with below line.

/* EMI_BEGIN */

/* Added by configureAPM at time and date stamp , DO NOT EDIT THESE LINES OR EMI TAGS */

-logconfigloc

/data/sasconfig/Lev1/SASApp/BatchServer/logconfig.apm.xml

/* EMI_END */

This change is effecting SAS batch jobs running using SAS scheduler. Below is the error message:-

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.

can you please provide your sugessions to fix this problem.

Re: SAS Environment Manager Framework activiation

gwootton — Mon, 03 May 2021 20:27:33 GMT

The BatchServer's logconfig.apm.xml adds a log in BatchServer/PerfLogs to capture data for the framework. Does that path exist and are users able to write to it?

Re: SAS Environment Manager Framework activiation

SASKiwi — Mon, 03 May 2021 20:35:28 GMT

Try making sure this option is all on the same line and that the XML file exists.

-logconfigloc /data/sasconfig/Lev1/SASApp/BatchServer/logconfig.apm.xml

If that doesn't help then back out the change.

Re: SAS Environment Manager Framework activiation

cesargf80 — Wed, 05 May 2021 15:36:14 GMT

@gwootton Thanks for your reply.

1. BatchServer/PerfLogs path is avialable.

2. User is having access to write logs into this path.

But still getting error message.

Pipe command =" SASHOME directory/9.4/sasexe/sas -autoexec /sasprogram directory/xxxxx.sas"

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.

Re: SAS Environment Manager Framework activiation

cesargf80 — Wed, 05 May 2021 15:41:51 GMT

@SASKiwi Thank you for your reply.

logconfig.apm.xml is avialable.

-logconfigloc /data/sasconfig/Lev1/SASApp/BatchServer/logconfig.apm.xml

I tried to back out the change , but SAS Environment Manager Frame work processes (ACM and APM ETL processes ) are adding the line automatically for every 30 mins , even after removing it.

Re: SAS Environment Manager Framework activiation

gwootton — Wed, 05 May 2021 15:41:56 GMT

is that path correct? (/data/sasconfig/Lev1/SASApp/BatchServer/logconfig.apm.xml)
is the file readable by the users? does it have content?

Re: SAS Environment Manager Framework activiation

SASKiwi — Wed, 05 May 2021 20:09:44 GMT

@cesargf80 - I suggest you track this to Tech Support.

Re: SAS Environment Manager Framework activiation

cesargf80 — Wed, 05 May 2021 22:03:34 GMT

@gwootton yes, path is correct. it is having content also.

Re: SAS Environment Manager Framework activiation

gwootton — Thu, 06 May 2021 12:47:33 GMT

I agree with @SASKiwi, you should open a track with technical support so we can take a look at the file and see what is wrong with it.

Re: SAS Environment Manager Framework activiation

Sajid01 — Tue, 11 May 2021 23:56:57 GMT

Create a new copy of the file (logconfig.apm.xml )and make the new copy immutable (Not the original one)
Assign this to logconfigloc. Thus you will have-logconfigloc.

Thus if logconfig_imm.apm.xml is the immutable copy, then you will have.

/data/sasconfig/Lev1/SASApp/BatchServer/logconfig_imm.apm.xml.
This way the SAS Environment Manager Frame work processes can read it but not change.

Re: SAS Environment Manager Framework activiation

gwootton — Wed, 12 May 2021 13:58:28 GMT

It is not the logconfig.apm.xml file that is being modified.

The log discovery process (Lev1/Web/SASEnvironmentManager/emi-client/bin/log_discovery.sh) is run every 4 hours by the Environment Manager Agent, and will automatically check for the /* EMI BEGIN */ and /* EMI END */ lines in every application server it discovers on the host. If they aren't present it will add them again, with the new log configuration inside it (pointing to logconfig.apm.xml). This is to ensure the log files needed by the APM reports are generated. If you comment out the -logconfigloc line rather than removing it, the log discovery process will not re-add it.