topic Re: sas LSF LIM ERROR in Administration and Deployment https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574907#M16761 <P>Lots of things could cause this problem.</P> <OL> <LI>DNS changes such that the dpds1335a cannot resolve dpds1336a</LI> <LI>Firewall changes on dpds1335a that prevents dpds1336a from connecting</LI> <LI>Network equipment breakdown.</LI> <LI>LIM is hung on dpds1335a</LI> <LI>License has expired.</LI> </OL> <P>So you can do the following:</P> <UL> <LI>Make sure LIM is running and responding on dpds1335a. Run 'lsid' on dpds1335a</LI> <LI>Make sure you can ping dpds1335a from dpds1336a.</LI> <LI>You could also try to telnet from dpds1336a to dpds1335a on the LIM port.</LI> </UL> Fri, 19 Jul 2019 11:18:46 GMT doug_sas 2019-07-19T11:18:46Z sas LSF LIM ERROR https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574643#M16757 <P>Hi All , can some one assit me with below error ? we have 2 node lsf/grid, only 2 app servers, they are not able to communicate between them, below is the error I see, any idea ?</P><P>&nbsp;</P><P>&nbsp;</P><P>/sasgrid/BCUS_SASGRID/lsf/log&gt;tail -f lim.log.dpds1335a</P><P>Jun 17 18:05:35 2019 18744562 3 3.4.0 probeMasterTcp: Last master is&nbsp; UNKNOWN</P><P>Jun 17 18:05:35 2019 18744562 3 3.4.0 isHighestCandidate: Attempting to probe master candidate dpds1336a timeout is 2</P><P>Jun 17 18:05:50 2019 18744562 3 3.4.0 probeMasterTcp: Last master is&nbsp; UNKNOWN</P><P>Jun 17 18:05:50 2019 18744562 3 3.4.0 isHighestCandidate: Attempting to probe master candidate dpds1336a timeout is 2</P><P>Jun 17 18:05:50 2019 18744562 3 3.4.0 probeMasterTcp: Last master is&nbsp; UNKNOWN</P><P>Jun 17 18:05:50 2019 18744562 3 3.4.0 isHighestCandidate: Attempting to probe master candidate dpds1336a timeout is 2</P><P>Jun 17 18:06:05 2019 18744562 3 3.4.0 probeMasterTcp: Last master is&nbsp; UNKNOWN</P><P>Jun 17 18:06:05 2019 18744562 3 3.4.0 isHighestCandidate: Attempting to probe master candidate dpds1336a timeout is 2</P><P>Jun 17 18:06:05 2019 18744562 3 3.4.0 probeMasterTcp: Last master is&nbsp; UNKNOWN</P><P>Jun 17 18:06:05 2019 18744562 3 3.4.0 isHighestCandidate: Attempting to probe master candidate dpds1336a timeout is 2</P><P>Jun 17 18:06:20 2019 18744562 3 3.4.0 probeMasterTcp: Last master is&nbsp; UNKNOWN</P><P>Jun 17 18:06:20 2019 18744562 3 3.4.0 isHighestCandidate: Attempting to probe master candidate dpds1336a timeout is 2</P> Thu, 18 Jul 2019 15:40:55 GMT https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574643#M16757 Go 2019-07-18T15:40:55Z Re: sas LSF LIM ERROR https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574790#M16760 <P>Have you checked that all SAS services on both app servers are up and running? You could also try rebooting all of your SAS servers in the correct sequence.</P> <P>&nbsp;</P> <P>Also raise a track with SAS Tech Support as they can get you going faster.</P> Thu, 18 Jul 2019 20:51:07 GMT https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574790#M16760 SASKiwi 2019-07-18T20:51:07Z Re: sas LSF LIM ERROR https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574907#M16761 <P>Lots of things could cause this problem.</P> <OL> <LI>DNS changes such that the dpds1335a cannot resolve dpds1336a</LI> <LI>Firewall changes on dpds1335a that prevents dpds1336a from connecting</LI> <LI>Network equipment breakdown.</LI> <LI>LIM is hung on dpds1335a</LI> <LI>License has expired.</LI> </OL> <P>So you can do the following:</P> <UL> <LI>Make sure LIM is running and responding on dpds1335a. Run 'lsid' on dpds1335a</LI> <LI>Make sure you can ping dpds1335a from dpds1336a.</LI> <LI>You could also try to telnet from dpds1336a to dpds1335a on the LIM port.</LI> </UL> Fri, 19 Jul 2019 11:18:46 GMT https://communities.sas.com/t5/Administration-and-Deployment/sas-LSF-LIM-ERROR/m-p/574907#M16761 doug_sas 2019-07-19T11:18:46Z