About five

five

I had a request to find the last login for all users on my 3.5 Viya environment going back to August 2021. Using the Audit CLI plugin, I was able to pull in the last seven days, so that wasn't super useful for this scenario. I then got the last modified timestamp of the ~/sasuser.viya folder for every user. In some cases, that appears to be close enough. But in at least one case, for one of my regular SAS Studio users, they haven't modified that folder going back 3 years, even though they are on the system every day. Some of my users do not even have that folder. I don't know if that means they have never logged in. Or if only certain tools create that folder. I am curious if anyone has any suggestions or tricks for gathering this info for things that have aged out of the logs at this point. The main use cases in my environment are VA, CAS, and SAS StudioV. We are using LDAP to log in, if that makes a difference, and the login shell is set to /sbin/nologin; they only access the system via the GUI. I do have a ticket open with support about this as well.

five · ‎12-07-2021

Yea I did run that bash script afterward. If it gives any feedback, when it does something then it must not have done anything. sudo /opt/sas/spre/home/SASFoundation/utilities/bin/cleanwork /saswork Running as user root on hostname web01.server.edu I have run it a few times and it either displays sessions still running or returns nothing like above. And there have been times where ps aux will show sessions still running and there will be nothing listed in /saswork as well.

five · ‎12-06-2021

No, I've only been made aware one time. The user said it had happened before. And the initial email from the professor said multiple students were having the same issue, but I only had an exchange with one student and hers was the only process that was 4 days old. At the moment I have a few users with sessions greater than 4 hours. I am just going to keep an eye on it and see how it transpires through the week. I could always increase the number to 24 hours or something like that.

five · ‎12-06-2021

Yea, I am no expert. Why I was asking the community if anyone had an idea of a good way to remedy this. I have come up with this code, that I am thinking about running once an hour: ps -eo pid,etimes,comm,group | awk '{if ($3 ~ /compsrv/ && $4 ~ /aduser/ && $2>14400) print $1}' Returns the process id of our adusers that have compsrv running for more than 4 hours. I don't know if there is a better way to do it. But it's an idea I have at the moment, just to pipe those to kill.

five · ‎12-06-2021

Yesterday we had a user reach out that was able to login to our Viya environment ok, but could not submit code. She would click run and then nothing would hang. I logged in and verified services a status check and then healthcheck and everything seemed good. I wasn't really sure what to do, if it was simply a problem with her code or something else. I then responded and asked her to run PROC SETINIT; RUN; She said that would run the first time she logged into a new session, but if she ran it a second time it would do the same thing. Her mentioning sessions made me wonder how many were open. I did a ps -aux and grepped for her user id and sure enough there was an old session from December 2 still open. I killed the two pid's from back then. Had her run her sas code again and everything was working again. Anyone have any automated or better fixes for that type of scenario?

five · ‎11-30-2021

We were dealing with a situation where our /opt/sas was filling up and it ended up being the WORK location, that was the problem. We have since changed that to elsewhere on the machine. Hopefully that will keep the system from going down if the disk fills up again. If we decide to implement disk quotas as well, is there a way to notify the user when they hit that limitation? "Maximum file size is 100GB, please contact the system administrator if you need more space" We want the users to understand what is happening and encourage them to come to us, if they need more resources, rather than assuming it's just not possible. Kind of along the same mindset, while researching this, I found this old OpenVMS SAS 8 article and am curious if it still sound theory? We can have users use their own home directory instead of WORK for temp files?

five · ‎11-30-2021

I was comparing proxy.conf against the healthcheck and there are a handful of Infrastructure Applications that were not in the proxy list: cachelocator-listener-v1 (there is also cachelocator and cacheserver, so they might be redundant?) cas-shared-default (cas-shared-default-http was in proxy.conf, but not this one) SAS Infrastructure Data Server SAS Message Broker (I believe this is sasrabbitmq, so it seems like this one would be super critical to monitor.) Any ideas for monitoring these? Everything else was in both places.

five · ‎11-29-2021

That worked a treat. Thank you.

five · ‎11-29-2021

I get a 401 unauthorized when using curl, even if I use the one in proxy.conf. How do you get around having to login, in order to pull the 200 status? I am already doing temporary logging to determine what is filling up the drive, I don't know why I didn't think about having it send me an email as well. So that is a short time fix. But I'd like to get the rest setup properly as well.

five · ‎11-29-2021

Our NOC uses various ITSM tools, including Solarwinds and OpenDuty to send alerts out. I asked support if there was a best practice way to monitor any of the SAS services and applications that we run and the reply was "we have no recommendations regarding 3rd party tools." Currently, we are monitoring at the OS level. But we are currently fighting some problems with our disk filling up very rapidly. It has happened 3 times so far. The first time, generic curl commands would probably have worked, because apache did not load at all and was returning a 404 error. But the other time the ansible status command has mainly been up for the services and instead returns a 500 internal server error. Now that I know about healthcheck, I will run it the next time this happens. I would really like to get alerted if that happens again. Is there a way for my NOC department to use solarwinds to monitor specific Viya applications? I have read about the sas-admin healthcheck and have thought about using it to create some breadcrumb-type files that NOC could poll. Is there a more direct or better way to do this type of monitoring? I have attached a healthcheck that I ran a few minutes ago that includes the various services and applications that we have in our environment. If it's helpful to know, we have a 4 server environment: web (web, rabbitmq, ansible) app (cas) worker1 (cas worker) worker2 (cas worker)

five · ‎02-17-2020

Thanks for your help, I learned a few things - so it wasn't a pointless exercise. Where would that last action log be on the drive itself, instead of going through the GUI?

five · ‎02-17-2020

For others running TKGridMon for the first time, if you get java command not found error, you can edit the gridmon.sh to point to the java location like this: /opt/sasinside/sashome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java -jar /opt/sasinside/sasva/TKGrid/bin/GridMon.jar Gridhost=$HOSTNAME GridInstall=/opt/sasinside/sasva/TKGrid /opt/sasinside/sasva/TKGrid/bin/tkgridmon That's what I did at least and it worked. I don't know if that is best practice or not.

five · ‎02-17-2020

Mine is a gui and it was behind my ssh window. I ran the code again and I see all three workers now, so I don't know what happened earlier.

five · ‎02-17-2020

Well I got TKGridMon started and it says it's ready on 44346, but I don't know what to do next. EDIT: Nevermind it was behind my ssh window, I see all three worker nodes. So I am not sure why the report is only showing one of the workers.

five · ‎02-17-2020

I have not used tkgrid before or setup java before. Give me a few minutes and I'll try to get it working.

Online Status	Offline
Date Last Visited	Monday

Historic Last Login for All Users

Re: Kill Hung Sessions Automatically

Re: Kill Hung Sessions Automatically

Re: Kill Hung Sessions Automatically

Kill Hung Sessions Automatically

Notify User of Disk Quota

Re: 3rd Party Monitoring

Re: 3rd Party Monitoring

Re: 3rd Party Monitoring

3rd Party Monitoring

Re: 3rd Party Monitoring

Make sasauth trigger PAM session handling to allow auto-creation of ho...

Re: Kill Hung Sessions Automatically

Tutorial: Setting Up Oracle Access in Red Hat Environment

Historic Last Login for All Users

Re: Kill Hung Sessions Automatically

Re: Kill Hung Sessions Automatically

Re: Kill Hung Sessions Automatically

Kill Hung Sessions Automatically

Notify User of Disk Quota

Re: 3rd Party Monitoring

Re: 3rd Party Monitoring

Re: 3rd Party Monitoring

3rd Party Monitoring

Re: Multi-Tier VA Only Seeing One Worker

Re: Multi-Tier VA Only Seeing One Worker

Re: Multi-Tier VA Only Seeing One Worker

Re: Multi-Tier VA Only Seeing One Worker

Re: Multi-Tier VA Only Seeing One Worker