About snlbse

snlbse · ‎09-11-2019

Hi sergie89, I have seen this issue before. It seems that in SAS 9.4M6 the SAS Theme Designer has gotten a new name and Metadata entry on the plugins tab -> Application Management -> SAS Application Infrastructure -> Theme Designer. Please verify that this entry has the correct connection information listed. So communication protocol, hostname and port number. Do the same for the Help Viewer for Midtier App. Bram Seldenthuis

snlbse · ‎04-07-2014

Hello Andreas, Thanks for the answer, but I did actually install TKGrid_2.5 prior to migrating the environment to VA 6.4. The one thing that I didn't do here, was update the Hadoop installation. If anyone can verify that an updated Hadoop is necessary for the migration or that not doing so can cause the issue I mentioned, I would love to know. Kind regards, Bram Seldenthuis

snlbse · ‎04-07-2014

Hello, I’ve been trying to get a customer’s 6-blade environment upgraded from VA 6.2 to VA 6.4 and failing. I was hoping some of you could take a look at this, and give me your thoughts on it. I installed a clean 6.4 environment, using an SMU package to transfer all metadata. Customer uses an SSL reverse proxy, so I updated: All connection properties in SMC Server.xml files for the 3 webapp servers Copied the cacerts file with the SSL certificate from the old 6.2 deployment After installing, I logged on to the VA Hub and everything appeared to be running smoothly, however, as soon as I went to the VA Admin page and ‘Manage Servers’ (or any of the other options there), it failed to load or display anything and just gave this pop-up: Going through the log files, I see this one popping up quite a few times: [VIEWER ] ERROR [tomcat-http--36] 2014-04-01 11:19:15,801 [ST-32-7uZmnfxNm1P0qKoWtPnN-cas:<username>] mobiledesigner.data.query.LasrQueryRunner - Error of type ServerNotFound.Connection refused Exception caught in LASRClient (lasr=null, host=<hostname>, port=10010) java.net.ConnectException: Connection refused action=ServerVersionInfo Exception caught in LASRClient (lasr=null, host=<hostname>, port=10010) java.net.ConnectException: Connection refused action=ServerInfo [VIEWER ] ERROR [tomcat-http--36] 2014-04-01 11:19:15,822 [ST-32-7uZmnfxNm1P0qKoWtPnN-cas:<username>] sas.bidata.error.DataErrorHandler - ServerNotFound java.net.ConnectException: Connection refused At first glance I figured there was either something wrong with the LASR license, or with the password used for the sassrv account. Re-applying the license and using the SDM to update the sassrv password didn’t solve anything though. In the end I reverted the environment back to 6.2 so that the customer could at least go on with their normal production. VA 6.2 is running normally, so the problem must be somewhere in 6.4. Anyway, that’s the situation. I am very interested in hearing your suggestions or pointers for troubleshooting this issue. Maybe you’ve seen something like this before. To make your life easier, this is a list of what I have already checked: LASR license appears to be correct. I applied it manually using the applylasrlic tool and also by simply running the sassetup tool to update the entire environment. The password for the sassrv account was updated and verified to be correct. Used the SDM for this. File permissions were set correctly. The entire config and sashome directories are owned by the SAS Installer account, except for the files that need root ownership. Metadata permissions are set correctly, for as far as I could check. System settings were functioning correctly for VA 6.2, so I assumed this should work in VA 6.4 as well. However, comparing the system settings to the prerequisites mentioned for 6.4, these are the differences: /etc/security/limits.conf uses the old requirements of 65536 and 350000 instead of 100000 and 350000. Also, no limits are set for stack. /etc/security/limits.d/90-nproc.conf has a value of 65536 instead of 100000. /etc/ssh/sshd_config has MaxSessions of 1000, but MaxStartups is not set. Works fine in 6.2 though. IPTables is running, but was configured to allow traffic over all the necessary ports. Unless new ports are added, that shouldn’t be the problem. SELinux is set to permissive. Running gridmon.sh showed all 6 nodes; no problems there. Password-less SSH has been correctly set up for the sasinst, lasradm and hadoop accounts. Submitting SAS code manually to start a LASR also resulted in an error, saying that a connection to LASR could not be made. And these are my questions: I haven’t updated Hadoop, as I figured it should run just as well on the version shipped with 6.2. Also, the customer hardly uses Hadoop anyway, but instead loads everything directly into memory (I know, I know …). Is there some hard dependency between TKGrid/SAS and Hadoop? I haven’t disabled the IPTables service, as it was configured to not be a problem. Besides, I expect other error messages if this is the problem. Am I right in assuming this? I think the changes in system settings between 6.2 and 6.4 are not the cause of the problem. Can anyone verify that? I’ve not changed the setenv.sh files for the 3 webapp servers, apart from increasing the memory settings in the JVM_OPTS. Should I have made changes there to reflect the SSL proxied address? Documentation doesn’t say so and I was able to log on just fine. After seeing a track about this, I have added the sasinst and lasradm accounts to the SAS General Servers group in SMC. Do you see any relation between this and the error? I would really appreciate some help and/or your thoughts on this. Kind regards and thanks in advance. Bram Seldenthuis Technical Administration Consultant, SAS Application Management SAS Netherlands

snlbse · ‎03-11-2014

On https://support.sas.com/planapp/ you can create a plan file, based on the customers Order Number. What you want to do to install the Enviroment Manager Agent on the other nodes, is define an extra machine in the planfile (so you end up with Server Tier, Client Tier, Metadata Node, Web Node and the added machine), on Linux for x64 (LAX) that you call EVManager or whatever and where you select ONLY the Environment Manager on the list of Machine Purposes. Next up, you will have to make the SAS Software Depot accessible on the other blades and start the Deployment Wizard on machine 2 (create a responsefile for this). You can point it to the newly created planfile and start the installation step for "EVManager" (or whatever you called it). Make sure that when you select the products to install, you deselect "Enviroment Manager" and "Environment Manager Plug-ins for Foundation Servers", so you end up like this: Then just run through the installation and do the same thing for machines 3 and 4. If you want, you can do a quiet installation on the other blades, based on the responsefile you created for machine 2. It erases the configured hostname from the responsefile, so that on blades 3 and 4 the SDW will simply use the 'hostname' command to get the actual hostname of the machine it installs to. To strip the hostname from a responsefile (I assume it's called "sdwresponse.properties"), use this command (on Linux): grep -v localhost /path-to-file/sdwresponse.properties > /path-to-file/sdwresponse_stripped.properties Next copy that file to the other 2 machines in the cluster and start the SDW in quiet mode, using that file (I assume you have SSH set up): ssh hostname_machine_3 /path-to-depot/setup.sh -quiet -responsefile /path-to-file/sdwresponse_stripped.properties & ssh hostname_machine_4 /path-to-depot/setup.sh -quiet -responsefile /path-to-file/sdwresponse_stripped.properties & You won’t see anything happening, but you can check to see if the installation is done by querying the sas.servers script on each machine. This will tell you if all SAS servers if they’re up or not. When you see “SAS Environment Manager Agent is UP”, you know it’s been successfully completed. Well, it turned out to be a bit more text than I first thought it would be, but I hope this is enough to answer your question. Kind regards, Bram Seldenthuis SAS NL

snlbse · ‎10-18-2013

First off: thanks for replying so quickly. I am a bit further now in my analysis of what's going wrong. I've found that Enterprise Guide isn't the culprit here. It's the whole environment. I've run a couple of SAS programs that are designed to stress the system a little and record things like I/O throughput and elapsed runtimes, while building very large data sets with between 10 million and 380 million records. The old environment is roughly twice as fast as the new one in both runtimes and throughput in MB/s. I'm going to run some additional checks to figure out exactly what is the bottleneck. Again, thanks for your help. Bram

snlbse · ‎10-17-2013

Hello everyone, I'm running into performance issues on a new 9.3 (yes, I know) environment of a customer of ours. Their migrated EG projects are running just fine and without any errors, but they take about 3 times longer than they used to. In both cases (old and new environment) the customer uses Enterprise Guide 5.1 to open a project and run it on the SASApp server. The data used is stored locally on the Compute tier that hosts the SASApp server. Workspace Server, Object Spawner and Metadata Server log files all report no problems. I'm looking for some useful tips to troubleshoot the performance issue. If anyone could help, I'd be much obliged. This is what I've determined so far, using a test project that exists on both environments: - In the new enviroment, the task status often reports "Waiting on server", while in the old environment it just says "Running..." all the time. - Between each step of the project in the new environment, you see "Connecting to server" flashing by. It's very fast but I haven't seen that message in the old environment. - In both environments the option to uses parallel execution on the same server is turned off. When turning it on, it does seem to improve performance, but the projects really aren't built in a way to properly use parallel processing. It somehow feels like it tries to reconnect to the server between every step in the project. Could this be the case and if so, where can I find more information on it? Anyway, like I said: any help would be much appreciated. Looking forward to hearing from you. Regards, Bram Seldenthuis SAS Application Maintenance