Dear Folks,   We are using SAS 9.4M6 with having multiple tier architecture (3 meta, 6 compute and 2 web nodes - all in Linux). We are facing issues in turning on the web services, specifically SASServer1_1 which takes time more than usual. While trying to turn on the services, they are shown like below. However, I read somewhere that in 2 hours everything is up, SAS Studio works absolutely fine after a couple of hours. Cleaning of logs did not help.   I am looking for a reason of such a delay, and possible solution to fix it. A call has already been raised with SAS tech support and I am currently awaiting a response from them. /opt/sas/web/sasconfig/Lev1/sas.servers start Starting SAS servers Starting SAS JMS Broker Starting SAS Cache Locator Service: ins_41415 waiting 30 ... Starting SAS Web Server Starting SAS Web App Server: SASServer1_1 (this can take a while) waiting 30 ... waiting 30 ... waiting 30 ... waiting 30 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 60 ... waiting 120 ... waiting 120 ... waiting 120 ... waiting 120 ... waiting 120 ... waiting 120 ... SAS Web App Server SASServer1_1 is still in the process of starting up, proceeding with additional servers. Starting SAS Web App Server: SASServer2_1 (this can take a while) waiting 30 ... waiting 30 ... Starting SAS Environment Manager Starting SAS Environment Manager Agent   While checking the the logs, it shows below such messages in the catalina file [pool-7-thread-1] WARN com.sas.svcs.cluster.httpinvoker.AutoDiscoveredHttpService - Have received 20 failures while trying to access an auto-discoverable service to satisfy request for 'com.sas.svcs.config.client.ConfigurationServiceInterface'. Please ensure that the application and/or process surfacing this interface is still in the process of starting. ... View more

Hi Folks,   We are using SAS 9.4M6 with having multiple tier architecture (3 meta, 6 compute and 2 web nodes - all in Linux). We have been facing issues frequently with the Web Infrastructure services getting down again and again, as due to High Availability the system tries to start the services in other compute nodes than the existing (it may be due a network glitch that the server might not be providing the correct status of service's availability). Once it tries to start the WIP services in another compute node with a new PID, this locks/corrupts the WIP database as it does not match with the existing PID added in the postmaster.pid file. So, every time we have to run the pg_resetxlog to fix the problem.   Is there any suggestion how this issue can be fixed so that we do not need to reset the lock file every time to make the WIP services and hence the web services (SAS Studio) working? ... View more

Hi All, We are using 9.4 M6 with having multiple Application servers (workspace servers) configured in it. We have a problem recently we faced after installation of missing fonts (Arial, Times New Roma, Courier New etc) in our SAS environments through SAS Registry. We were able to successfully install the fonts starting in Development and then to the Validation environment.   However, during business acceptance test, it has been identified that it works fine into the Development environment but it does not work properly into the Validation environment. Although it shows the list of fonts installed properly, but when generating PDF reports/documents from business side it has issues. When a SAS program is run to generate a pdf report with desired newly installed fonts in one Application server (workspace server) named- SASAppUTF8, it works fine. However, it does not work in rest of the 6 Application Server (workspace servers) out of the total 7 application servers configured in the server.   Does anyone have any suggestions how to investigate the issue further and get rid of the situation?   The SAS program which is run to test the fonts:   “proc template;    define style styles.smaller;    parent = styles.printer;       class fonts from fonts /  /* Reduce all sizes by 2pt */             'TitleFont2' = ("Courier New",10pt,Bold Italic)             'TitleFont' = ("Courier New",11pt,Bold Italic)             'StrongFont' = ("Courier New",8pt,Bold)             'EmphasisFont' = ("Courier New",8pt,Italic)             'FixedEmphasisFont' = ("Courier New, Courier",7pt,Italic)             'FixedStrongFont' = ("Courier New, Courier",7pt,Bold)             'FixedHeadingFont' = ("Courier New, Courier",7pt,Bold)             'BatchFixedFont' = ("SAS Monospace, Courier New, Courier",5pt)             'FixedFont' = ("Courier New, Courier",7pt)             'headingEmphasisFont' = ("Courier New",9pt,Bold Italic)             'headingFont' = ("Courier New",9pt,Bold)             'docFont' = ("Courier New",8pt);       class Table from Output /             rules = ALL             cellpadding = 2pt     /* Reduced from 4pt to 2pt */             cellspacing = 0.25pt             borderwidth = 0.75pt;    end; run; ods pdf file="<file path>/test.pdf" style=styles.smaller;   proc print data=sashelp.class; run;” ... View more