BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
MG18
Lapis Lazuli | Level 10

Hi all ,

 

I am running sas flow from LSF first time and job are hanging from last 2 days .

Licesnse are renewed and we are able to connect to LSF.

Please  suggest some thing. 

1 ACCEPTED SOLUTION

Accepted Solutions
MG18
Lapis Lazuli | Level 10

HI all,

 

 

I have one entry in lsf.conf file which  in LSF_TOP/conf as LSF_AM_OPTIONS=AMNEVER then restart the services , now it is running fine.

 

Thanks every buddy for contribution and guidence.

View solution in original post

10 REPLIES 10
Kurt_Bremser
Super User

Make sure that the batch jobs write logs to an accessible location. Use logparms="write=immediate", so that all steps are written to the log without delay, and inspect the logs of your hanging jobs.

MG18
Lapis Lazuli | Level 10

Please tell in which file i Should make changes and log folder is accessible .

Many thanks in adavnce

Kurt_Bremser
Super User

On the SAS commandline, -log controls where a log file is written, and -logparm controls how the log is written.

So you need to look in the LSF job definition for the SAS commandline call.

MG18
Lapis Lazuli | Level 10

 

Can Please tell how to  change -logparm in details as i am new to Technology Do I need to make changes while deploying job or in server i need to changes.

 

In addition i have tried,I took the command from DI and ran it on server it is able to run and generate log file also.

Kurt_Bremser
Super User

From what I see in the documentation for LSF with DI Studio, LSF uses a SAS Data Step Batch Server for execution. So you can get the configuration from the server definition in SAS metadata (Management Console).

 

anja
SAS Employee

Hi,

 

the following gives examples of how to use/set the logparm:

 

http://support.sas.com/documentation/cdl/en/lesysoptsref/69799/HTML/default/viewer.htm#p0fmptfnyvi1n...

http://support.sas.com/kb/10/110.html

 

What SAS version are you running, on whish OS?

Do you know if this ever worked before, or is it a new install?

 

Thanks

Anja

MG18
Lapis Lazuli | Level 10

HI,

 

We are using SAS 9.3 on linux OS and recently we have installed the LSF in our Envinorment and after installation it didnt worked.

Will Changing parameter is enough to resolve this problem ?

 

Please help me to resolve this.

Kurt_Bremser
Super User

@MG18 wrote:

HI,

 

We are using SAS 9.3 on linux OS and recently we have installed the LSF in our Envinorment and after installation it didnt worked.

Will Changing parameter is enough to resolve this problem ?

 

 


No. Setting the logparm causes the log to be written immediately, so a job that runs into an infinite loop or similar will at least have written the code causing it to the log.

Right now we are at a stage where we try to enable you to look for the cause of your problem.

 

Additionally, you should monitor your server where the jobs are supposed to run to see if the jobs are actually started by LSF (new SAS or SAS-related process appears in the process list). Once you have confirmed that processes have started, you can monitor them for resource consumption, mainly CPU cyles/ticks, to see if they are actually doing something.

 

You are no longer in a world where popping in a disc and hitting "Start" is sufficient. You need to get a grasp what the systems you are using are doing in detail, how they run, how they need to be configured, and so on. There is a reason why people like me (and hopefully you, at least one day) get paid the big bucks.

anja
SAS Employee

Hi MG18,

 

maybe the best way to proceed here is contacting Tech Support:

http://support.sas.com/en/technical-support.html#contact-technical-support or call +1-800-727-0025

 

They'll help you troubleshoot the problem and point you into the right direction.

 

Thanks

Anja

 

MG18
Lapis Lazuli | Level 10

HI all,

 

 

I have one entry in lsf.conf file which  in LSF_TOP/conf as LSF_AM_OPTIONS=AMNEVER then restart the services , now it is running fine.

 

Thanks every buddy for contribution and guidence.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 10 replies
  • 1289 views
  • 0 likes
  • 3 in conversation