While all of this information is true, I am with Kurt: I think you need to understand the process owner and the permissions set up, on top of your LDAP vs local groups configuration. This is an OS question more than SAS. Permissions in UNIX based systems are tricky and meant to be more restrictive than permissive. If you are interested in being more in control of your Linux permissions I would suggest to apply a granular configuration with ACLs, then you gen something similar to Windows. ... View more

Agreed with the last comment of Sajid: specially on Windows you do not put your user profiles on a share, but local. That’s why there is a Roaming area in the Windows profiles! ... View more

Adding to Patrick’s comment, running the IoTest tool is always a good idea for performance. However! 1. This will not test creating thousands of files, but a few very large files 2. As you want to test the performance for 50-70 users, you would need to run it with at least 50 sessions… I doubt even that server has enough RAM or enough storage. In any case, please do read well the instructions of that tool. ... View more

You are not crazy and I think we can confirm that indeed. This being said a Terminal Server for 50-70 concurrent users, regardless of this issue, is killing a fly with a cannon, aside incredibly expensive! Do you know the saying divide and conquer? Coming back to the issue, SMB is not the way to go for this design, I think we stablished that. Leaving to you if you would go back to the drawing board and design (I would), here is a piece of extra knowledge: In SAS EG it’s possible to change configurations under the file SEGuide.exe.config and tell it to place the temporary files in a different location like this: <configuration> <configSections> <section name="Environment" type="SAS.EG.Configuration.EnvironmentSection, SAS.EG.Utilities"/> </configSections> <Environment> <Variables> <add name="TEMP" value="D:\MyTempFiles"/> </Variables> </Environment> </configuration> However, is up to you how you will do that for each user, since placing it for All users is just a formula for disaster. ... View more

Hello @Amitkum2,   I am quite surprised by this kind of message as early in the installation process.   Are you running Installation & Configuration together, or are you running first Installation only?  If you are running Installation only, not Configuration, you should share this with SAS Technical Support as soon as possible. If you are running Installation & Configuration together, I would like to discourage you to do so. Many reasons behind, the most important being:   1. Not really recommended for GRID environments. Plus if you have shared storage for your nodes, you will want to determine better how to deploy local vs shared, per node. 2. It will allow you to check and download for all the latest SAS hotfixes (yes, depot ones are not enough) and security patches before you run the configuration. 3. It is a best deployment practice, for the reasons above mentioned and many more.   This is still not ensuring the solution, but I think we need to separate concerns. ... View more

Hello @Amitkum2 ,   thanks for providing the log. Not sure if those lines or this file is enough. When there is no more information anywhere else, I suggest to re-run the SDW with the paremeter loglevel=2, which runs SDW in debug/trace mode, to give more information.   This being said, there are more things that I wonder now: - How did you configure PAMD. (eg  https://sas.service-now.com/csm?id=kb_article_view&sysparm_article=KB0036255 ?) - How did you configure sasauth.conf ( eg change method to PW) - Did you create /etc/pam.d/sasauth as a copy of /etc/pam.d/system-auth, retaining  only those lines beginning with "auth" or "account"? ... View more

Hello there,   I see you are in good care by @sys-halt . In the meantime, I would wonder about the following points:   - what are the exact messages in the referred log. I think that would give a lot of additional information. - I assume you tested the accounts log in to the host? If not, please do so! Also, please provide the login information exactly as you would prompt it, meaning it is not the same to log in as "user", "user@domain", "user@host", etc. - Do you have enabled during the installation any antivirus, security software or storage backup running? When possible, I would disable them or create required exceptions (during the installation).   A side note, which for now I would only like to put on the back of your mind. No need to take this action at this point:   - I also believe to notice the installation is done over a mount on a NAS? As NFS? LUN? Depending on the laid out infrastructure and configuration, this might be a potential source of all sort of issues. Not necessarily, but could be. File locks being released later than expected, timeouts, micro-disconnections, performance ... resulting, for example in some installation processes ending later than expected, ending in pre-step validation failures. ... View more

Hi, It is definitely an interesting idea but to me it seems risky. In short, you would be assuming the compilation of dependencies. Not only that, every time your SAS images will get updates (more or less frequent depending on your chosen cadence), you would need to repeat this process and basically pray the OS on the images won’t change either. This is the risk of workarounds when talking about immutable images under CI/CD: you would assume any risk and risk mitigation is up to you too, not SAS anymore. This being said, if you have a test environment, go ahead and give it a shot and let us know 😉 ... View more

Have you found this support note? http://support.sas.com/kb/69/854.html On top of this, you can always run the SDW with loglevel=2 to get additional info in your logs, it will tell you all you need to know in the logs ... View more

Hi there,   I would look into the configuration done previously (response files, configuration files) and apply the same.   This being said, chances are high that this configuration is just the one that comes by default in the prompt 🙂   Edit: don't you have a Test environment or sandbox? Perhaps you can test this safely in that way. DTAP is always a good idea. ... View more

Potentially, and depending on the usage of SAS EG, yes, they could be some of the culprits.  Based on what you mention, chances are high that those are a big part of the issue. Please mind, it is very hard to say without knowing better your architecture, infrastructure and actual usage.    I would recommend some consulting hours from SAS Professional Services or a trusted SAS partner who can cover deeply the architecture details at the technical and functional level. ... View more

Hi there, excellent question!   Yes, the high performance I/O (thoughput) applies as well, and, in fact, specially, to the temporary files in SASWORK and UTILOC. What is important to mention is that SASWORK and UTILOC are not recommended to be mounted in a SMB mount/share!   Regardless of the excellent perfomance you have behind at your shared storage level, SMB is not a protocol you want to use for this kind of purpose.   It is simple: either keep it local storage/SSDs, with a (proper) LUN (as you mentioned) or a SAS supported & tested Distributed File System such as GPFS, Lustre, Veritas, NetApp, etc. If you can keep it local with Premium SSDs, the best.   I also notice you are using Windows. Please mind that, generally speaking, there is more support for this kind of configurations on Linux or AIX or windows, from a driver development point of view.  Of course the vendors will always try to do their best. In some cases the drivers work flawlessly, but in many cases i have seen and keep seeing, there are workarounds (such as installing a Linux substrate/Cywin) and that is rarely flawless.      ... View more

Silly answer but, besides the SAS tool or the policies you could still use the ECR CLI or webtool to delete images? aws ecr batch-delete-image --repository-name <repository_name> --image-ids imageTag=<tag> ... View more

Hi, I agree with the last reply. In short either data increased which increases processing time or there is a non visibly bottleneck which adds wait times. Or there is a configuration which could be fine tuned (and changed until now, but that’s another type of discussion) In my humble opinion and as you indicate resources are okay, I would start investigating the bottlenecks and wait times. It seems to me as SAS is not using your system fully. Fullstimer will give you real time vs system time, which should give you wait times. In the procedures where you have wait times, you will find culprits. For databases and such you have as well the sastrace option, which will tell you trace info about your data sources, a typical culprit for making SAS wait to receive information (eg bad join queries not optimized) That is within the SAS area. You can also monitor things from the system or system plus SAS point of view. From cron you could call SAS with the time command. This would add, at the process level, an output similar to fulltimer in SAS. You could also use SAS Enterprise Session Monitor, which is an amazing tool to monitor and understand what happens in SAS, and you can compare with previous executions. On one hand, you would need to know more about that/those jobs: are they connecting to a database, to a shared storage? Are the disks shared? How are the join queries be made? What type of operations are made? Stats or simple queries? Has data increased? Of course you would need to know about your infrastructure and SAS configuration…. I would wonder as well if there was any recent update in SAS or your OS which could have changed any custom configuration by overwrite. As you see, many areas of investigation. I’d start with finding out your wait times indeed. Once you find when and where wait happens, you will know what’s is the next step ... View more

Mhm. Security and licensing are certainly important considerations, for anyone working with COM or FFI. Leaving license aside, if anyone goes for this option you indicate, I’d strongly suggest to wrap it in a custom PHP extension and add security measures. Wondering how you tackle security concerns towards Penetration Tests and Audits? Feeling curious, Alan 🙂 ... View more