About MadhuKiran1

MadhuKiran1 · ‎12-21-2017

Risk Dimension promotion is not a typical metadata code promotion, since everything you develop in RD is getting saved in the folder level on the OS. you would need to copy paste the entire folder to the new environment and compile all your user defined functions and variables, Along with the parameters changed in the configuration data set. this made us new environment up and running. Sad part if not much help from SAS Tech support as well :(. anyways, we found it after banging head adn able to get it through finally 🙂

MadhuKiran1 · ‎12-15-2017

Hello , We have SAS Risk Dimension code developed in the windows environment and it is ready for moving to PROD. 1. we tried to copy and paste the entire project repository folder (from windows level) to the new environment (in the matching location from the current server to new server). 2. current server RD code is running fine with no issues. 3. when migrated to new environment the new changes(other than SAS provided along with installation) which we have made has not reflecting in the new environment. (changes like Pricing Methods, Instrument types, variable definitions, Curve Registrations.. etc). as I understand SAS has not provided any tool to migrate this RD environments across servers, could you please guide us the right way of migrating things specific to Risk Dimensions. Thanks in Advance.

MadhuKiran1 · ‎10-30-2017

The easier way to do this is, login to SMC using admin credentials and recover the metadata object(removed flow) and unschedule it.

MadhuKiran1 · ‎10-30-2017

Hi, Did you unscheduled the flow before you remove it from SMC?. Removing from SMC without unschedule doesn't remove the scheduled instance from scheduler.in such case, it would keep on executing on scheduled time.

MadhuKiran1 · ‎12-06-2016

looks like you would need to increase the port banks on the object spawner configuration , this is to accept more connections simultaneously. These timeout settings are set in the cluster using SAS Environment Manager, by default it is set to >2% but you could modify these to a higher % and see if it solves your problem. Thanks !!

MadhuKiran1 · ‎10-27-2016

I had the same problem in my environment and it got solved after adding more roles and capabilities in metadata thrugh SMC. earlier I have only SAS Admin role assigned since I am an admin, then I added one of the business group to the user and it worked fine.

MadhuKiran1 · ‎10-24-2016

look slike some problem with server.xml file, Did you check the catalina.log and server.log files for any error messages?. And is this the firsttime you are starting the server??. or is it a resart?.

MadhuKiran1 · ‎02-09-2016

Thanks Timmy. Yes it looks like working properly. Yes I did validate workspace server(after Object spawner restart) through SMC and it is successful. In our current configuration, even we don't have any hard coded host names and its already configured with $HOSTNAME, also config directory is shared across all nodes for us too. Looks like we are good to go. The current problem I see (all jobs are going to grid-node1) may be because the grid-node1 machine is always free since it is a test environment and hence it is always accepting the connections.

MadhuKiran1 · ‎02-09-2016

Yes, all workspace servers are grid-launched. I checked the object spawner logs and it seems to be(not confirmed yet) actual processes are going to different nodes. and we do have the configuration to create separate log file for all grid nodes and all these node log files has below entry , this means the port we have added seems to be activated on all. 2016-02-09T14:14:36,807 INFO [00000031] :sas - Reserved IPv6 port 8599 for launched server connect back listen (connection 15). 2016-02-09T14:14:36,807 INFO [00000031] :sas - Activated listen on IPv6 port 8599 (connection 15).

MadhuKiran1 · ‎02-08-2016

Thanks Timmy, I do have one more doubt, since we are in grid, should we need to add $HOSTNAME.mydomain.com?. curretly we do have 4 compute nodes, if I add this parameter, it is resolving to the firstnode it self and I ran a job multiple times using EG after adding this parameter with 8599 port, every time job is running only on Grid node1. USERMODS=" -dnsmatch $HOSTNAME.mydomain.com -conversationport 8599 $JREOPTIONS" earlier we had only below entry to this file. USERMODS=$JREOPTIONS I am little confused now whether toa dd $HOSTANME parameter or not. can you please help me and give me some more details?.

MadhuKiran1 · ‎02-08-2016

Hi Sireesha, Did you get around this problem?. can you please post the solution it worked for you?. Thanks Madhu

MadhuKiran1 · ‎02-08-2016

Hi Timmy, we are using SAS9.4 Grid Ts1M2 and we started receiving bunch on below Error every day(customers are mainly using SAS EG). Objspawn was unable to launch the server SASApp - Workspace Server (A5UCJJ3G.AY00000C) due to the server launch exceeding the specified wait time And then I did try to validate the application server using non-unrestricted user and got the below error. [2/9/16 11:58 AM] INFO: Starting extended validation for Workspace server (level 1) - Making a connection [2/9/16 11:59 AM] SEVERE: The launch of server SASApp - Workspace Server for user failed. [2/9/16 11:59 AM] SEVERE: Failed to start the server. [2/9/16 11:59 AM] SEVERE: The application could not connect to any server in the cluster And I checked the available ports starting with 859* and below is the output I got(mostly all ports are established), can you please suggest me which Port I can use [sas@localhost ObjectSpawner]$ netstat -anp | grep 859 tcp 0 0 :::8591 :::* LISTEN 7296/objspawn tcp 0 0 :::8593 :::* LISTEN 7296/objspawn tcp 0 0 :::8594 :::* LISTEN 7296/objspawn tcp 0 0 :::8595 :::* LISTEN 7296/objspawn tcp 0 0 :::8596 :::* LISTEN 7296/objspawn tcp 0 0 ::ffff:10.1.6.34:8591 ::ffff:144.131.10.135:59241 TIME_WAIT - tcp 0 0 ::ffff:10.1.6.34:8596 ::ffff:144.131.24.62:34525 ESTABLISHED - tcp 0 0 ::ffff:10.1.6.34:8596 ::ffff:144.131.24.62:34657 ESTABLISHED - tcp 0 0 ::ffff:10.1.6.34:8596 ::ffff:144.131.24.75:55006 ESTABLISHED - tcp 0 0 ::ffff:10.1.6.34:8596 ::ffff:144.131.24.75:53706 ESTABLISHED - tcp 0 0 ::ffff:10.1.6.34:8596 ::ffff:10.47.26.27:54600 ESTABLISHED - Based on your note to avoid ths problem, adding below line to ObjectSpawner_usermods.sh, can you please suggest which port I can use from above utput instead of 8599?. USERMODS=" -dnsmatch $HOSTNAME.mydomain.com -conversationport 8599 $JREOPTIONS" Thanks Madhu

MadhuKiran1 · ‎01-18-2016

Hi, Its time for software renewal on sas9.4 grid environment with 3 meta nodes 4 compute nodes, 2 management nodes and midtiers when I renew license for LSF the follwoing tech note says I need to restart certain services.(jadmin , badmin , res ans lim) Tech note : http://support.sas.com/kb/18/638.html can some body confirm on which machine I need to restart these services? is it on metadata server or on management server?. S : $LSF_TOP (lsf instalaltion) directory is accessible from all machines

MadhuKiran1 · ‎12-01-2015

in RTM cluster master status shows "RES-Down" (outof service ??) , canyou pease help me what actions I need to take to bring that back to "Ok" status?. I tried to start this through "RES - startup" but it is asking for root password, which I dont have it. another one I tried to look for the status from cmd line as below every thing is running fine on OS /etc/init.d/lsfpollerd - status running Attaching the status of cluster & individual hosts.

MadhuKiran1 · ‎10-09-2015

Guys, Using SAS9.4 backup & recovery tool, is it required to keep Metadata server on non-clustured mode before I run "sas-backup" command?. I guess using sas-backup it is not just metadata gets backed up, all other components in the environment will be backup. Thanks!!

Online Status	Offline
Date Last Visited	‎12-21-2017 06:58 AM

Re: Risk Dimension Code promotion

Risk Dimension Code promotion

Re: Scheduling Manager - Flow that has been removed is still running

Re: Scheduling Manager - Flow that has been removed is still running

Re: SAS 9.4 Performance issue | Clustered architecture for High availa...

Re: Enterprise Guide 7.1 fails to submit grid job

Re: sas web server stated and stopped immediately

Re: SAS Grid Validation error

Re: SAS Grid Validation error

Re: SAS Grid Validation error

Re: SAS 9.4 Performance issue | Clustered architecture for High availa...

Re: odd things happened on a restart

Re: Scheduling Manager - Flow that has been removed is still running

Re: Enterprise Guide 7.1 fails to submit grid job

Re: sas web server stated and stopped immediately

Re: Risk Dimension Code promotion

Risk Dimension Code promotion

Re: Scheduling Manager - Flow that has been removed is still running

Re: Scheduling Manager - Flow that has been removed is still running

Re: SAS 9.4 Performance issue | Clustered architecture for High availa...

Re: Enterprise Guide 7.1 fails to submit grid job

Re: sas web server stated and stopped immediately

Re: SAS Grid Validation error

Re: SAS Grid Validation error

Re: SAS Grid Validation error

Re: SAS Grid Validation error

Re: SAS Grid Validation error

SAS 9.4 Grid : LSF license renewal

RTM Cluster master Status

SAS9.4 Backup and Recovery Tool