06-04-2018
daithi1990
Obsidian | Level 7
Member since
01-23-2018
- 17 Posts
- 1 Likes Given
- 3 Solutions
- 5 Likes Received
-
Latest posts by daithi1990
Subject Views Posted 3935 04-18-2018 07:29 AM 4435 04-11-2018 12:26 AM 3963 04-10-2018 10:29 PM 7107 03-26-2018 06:22 AM 6822 03-25-2018 09:28 PM 2480 03-08-2018 06:41 PM 4089 03-08-2018 05:11 PM 4259 02-20-2018 10:53 PM 5016 02-18-2018 06:39 PM 4095 02-16-2018 07:46 AM -
Activity Feed for daithi1990
- Got a Like for Re: SAS VIYA Certificate issues. 08-30-2018 10:22 PM
- Got a Like for Re: SAS VIYA Certificate issues. 07-19-2018 08:58 AM
- Posted Re: SAS report on Viya perform very slow after migrate from SAS Visual Analytics 7.1 to 8.2 on SAS Viya. 04-18-2018 07:29 AM
- Posted Re: SAS VIYA Certificate issues on SAS Viya. 04-11-2018 12:26 AM
- Posted Re: SAS report on Viya perform very slow after migrate from SAS Visual Analytics 7.1 to 8.2 on SAS Viya. 04-10-2018 10:29 PM
- Posted Re: Enabling XCMD Option on Viya on Developers. 03-26-2018 06:22 AM
- Posted Enabling XCMD Option on Viya on Developers. 03-25-2018 09:28 PM
- Posted Re: How CAS tables load into memory on SAS Viya. 03-08-2018 06:41 PM
- Posted Re: VBA run-time error 3706 on SAS Programming. 03-08-2018 05:11 PM
- Liked Re: ansible-playbook -i inventory-name-filesystem-assessment.yml is giving error for alexal. 02-21-2018 10:47 PM
- Posted Re: SAS Viya Transfer CLI: HTTP Connection Error on Import Command (HTTPS connection defined) on Administration and Deployment. 02-20-2018 10:53 PM
- Got a Like for SAS Viya Transfer CLI: HTTP Connection Error on Import Command (HTTPS connection defined). 02-19-2018 04:42 AM
- Got a Like for Re: SAS Viya Transfer CLI: HTTP Connection Error on Import Command (HTTPS connection defined). 02-19-2018 04:42 AM
- Posted Re: VIYA ODBC Driver installation not functioning on SAS Viya. 02-18-2018 06:39 PM
- Posted Re: SAS Viya Transfer CLI: HTTP Connection Error on Import Command (HTTPS connection defined) on Administration and Deployment. 02-16-2018 07:46 AM
- Got a Like for Re: how to upgrade sas viya 3.2 to the upcoming release of sas viya 3.3. 02-16-2018 03:22 AM
- Posted Re: SAS Viya: Connect to DB using ODBC - OS = Linux Redhat 7.4 on Administration and Deployment. 02-16-2018 12:51 AM
- Posted Re: SAS Viya Transfer CLI: HTTP Connection Error on Import Command (HTTPS connection defined) on Administration and Deployment. 02-16-2018 12:36 AM
- Posted Re: SAS Viya Transfer CLI: HTTP Connection Error on Import Command (HTTPS connection defined) on Administration and Deployment. 02-16-2018 12:12 AM
- Posted Re: how to upgrade sas viya 3.2 to the upcoming release of sas viya 3.3 on Administration and Deployment. 02-15-2018 11:24 PM
-
Posts I Liked
Subject Likes Author Latest Post 2 -
My Liked Posts
Subject Likes Posted 2 04-11-2018 12:26 AM 1 02-15-2018 11:07 PM 1 02-16-2018 12:36 AM 1 02-15-2018 11:24 PM
04-18-2018
07:29 AM
they are generally located on the server i.e. var/logs/sas/viya/.... microservice
... View more
04-11-2018
12:26 AM
2 Likes
I would add that it is extremely important to keep in mind, that the hostname on the certificate must match that which is provided using the hostname -f command.
... View more
04-10-2018
10:29 PM
Have you checked httpd to see if there are any requests which are flooding any microservices? Also check the consul log, SAS Visual Analytics Logs, and other SAS logs, to see if anything shows up there?
... View more
03-26-2018
06:22 AM
I actually got it on Viya 3.3, if you go to vi /opt/sas/spre/config/etc/spawner/default/spawner_usermods.sh & vi /opt/sas/viya/config/etc/spawner/default/spawner_usermods.sh Then add the following statement USERMODS="$JREOPTIONS -allowxcmd" Then restart the sas-viya-spawner-default service, you should be able to run system commands in procedures in Viya
... View more
03-25-2018
09:28 PM
Hi, I am currently creating a process which will be scheduled on our Viya 3.3 environment which will effectively loop through a folder and read filenames of a certain pattern. So obviously to start I need a list of files. This would be completed using something similar to the below filename myfiles pipe "ls /data/files/*.ext"; And stored in a table using a subsequent data step. I first got errors then surrounding XCMD issues, so obviously this option is disabled by default. Similar messages occur using the %SYSEXEC Macros. ERROR: Shell Escape is Not Valid in this Session I've tried adding the OPTIONS XCMD; to the start of the script which appears to not have worked, and I do have access to autoexec_usermods.sas and have added the same still no luck. Finally I've tried implementing the Enabling -XCMD for the SAS Connect Spawner and still no luck. I get the security implications for disabling this initially, however it surely isn't that hard to enable system commands in SAS? If anybody can point me in the right direction, it would be greatly appreciated.
... View more
03-08-2018
06:41 PM
It would be best to view impact on memory on the Linux boxes itself. Using a command like top. In relation to the NFS, as long as the drive is mounted or if the drive is shared on the network you should be able to see it within the filesystem. This is a replication of what lies on the Linux box.
... View more
02-20-2018
10:53 PM
Okay so a few points to note: 1. As we are running our Viya instance on AWS we have defaulted all external traffic through our load balancer to Port 443. The request then internally is converted into a port 80 request when it hits the server. We temporarily had to open our Load Balancer to Port 80 to accept HTTP traffic for this to work. 2. When this occurred we received a report of the reports we were ingesting however it contained errors on the CLI import log. /var/log/sas/viya/importvaspk/default/<logfiles> We checked in the log, and saw that a missing PNG Shared object in the renderer folder was stopping the ingest of report files. (Apparently we had installed the Golden Build too, good old SAS ;)) Status: Report import failed. 1) error converting unknown page/section: unexpected java.lang.UnsatisfiedLinkError thrown. Message = "/opt/sas/viya/home/lib64/renderer/libCommonsJava.so.2.0.0: libpng12.so.0: cannot open shared object file: No such file or directory" We then used YUM to install the 64 bit renderer yum install libpng12 And copied this file cp /usr/lib64/libpng12.so.0 /opt/sas/viya/home/lib64/renderer/ Then we reran the process and reports uploaded successfully.
... View more
02-18-2018
06:39 PM
I had a similar issue with unixODBC MySQL drivers. The solution was to either A add encoding option to the CASLIB statement: caslib odbccaslib datasource=(srctype="odbc" odbc_dsn="MySQL" dm_unicode="utf-16" ); Or B add this option as part of the ODBC setup on the Linux server. Now I appreciate you're dealing with MSSQL, so this maybe different for you, however it would appear that there are issues with unixODBC. Also please ensure you have CAS Connector for ODBC installed prior to looking into the above.
... View more
02-16-2018
07:46 AM
Thanks alexal, Just breaking your comment down there a little. 1. I was able to OAuth and upload .spks to the Viya instance, so that could in my own mind rules out the firewall/wrong address issue. i.e. I can connect and interface with the site. 2. I noticed some Strange behaviour with the exe is despite the fact I've entered https:// it reverts to http:// on the import stage. I have an inkling that this is what's causing the problem, as our viya instance is setup only to accept https:// not http:// requests.
... View more
02-16-2018
12:51 AM
There was an encoding issue with the openODBC drivers and as such the encoding had to be added into the CASLIB statement. caslib odbccaslib datasource=(srctype="odbc" odbc_dsn="MySQL" dm_unicode="utf-16" );
... View more
02-16-2018
12:36 AM
1 Like
Hi Angian, This is the documentation i'm working with. http://documentation.sas.com/?cdcId=calcdc&cdcVersion=3.2&docsetId=calpromotion&docsetTarget=n0ihk3dsgoiqvtn15oce7kguif1s.htm&locale=en At the moment the target env is Viya 3.2 (soon to be upgraded though) You effectively install the .exe from viya into the location you wish to transfer from (in this case windows) So have updated the env variable and am getting a slightly different message. C:\Users\Folder>sas-transfer import -packageId d2dfe0c1-3b03-4de1-b962-4d91f2cd84b6 -mapping mapping.yml running .....failed The following errors have occurred: Get http://url/SASHome/: dial tcp <insertiphere>:80: connectex: No connection could be made because the target machine actively refused it. Http Status: 0
... View more
02-16-2018
12:12 AM
Hey Angian, Will give it a try 🙂
... View more
02-15-2018
11:24 PM
1 Like
A little pointer to people before running this: We've found it useful to upgrade ansible before running the playbook. pip install ansible --upgrade Can save hours, ansible 2.2.1 seems to cause trouble.
... View more
02-15-2018
11:07 PM
1 Like
Hi, I've tried importing an SPK from a 9.4 VA Environment to a SAS Viya VA Environment. This is using the transfer CLI on windows. We have our Viya instance setup via AWS and for obvious security reasons have disabled access over http://, i.e. we are only accepting traffic over a https:// request. (and no reopening http is not an option) I've taken the following steps to get to the sticking point. I was wondering if anybody else had the same issue and if so what steps have they taken to resolve? It all looked to be going pretty good until push came to shove. Step 1: Create the Profile C:\Users\Folder>sas-transfer profile init Enter configuration options: Service Endpoint> https://site:7980 Output type (text|json|fulljson)> text Saved 'Default' profile to C:\Users\Folder\.sas\config.json. Step 2: Get an OAuth Token for profile C:\Users\Folder> sas-transfer authenticate login -u sasadmin -p password Login succeeded. Token saved. Step 3: Upload SPK with Mapping File C:\Users\Folder> sas-transfer upload --spk package.spk --mapping mapping.yml Id 3e253eb5-cfd5-47fd-b949-ba4d86f1082a Name package.spk INFO: Mapping file mapping.yml created. Step 4: Import updated file and mapping (the puzzling bit) C:\Users\Folder>sas-transfer import -packageId 3e253eb5-cfd5-47fd-b949-ba4d86f1082a --mapping mapping.yml running ....failed The following errors have occurred: Get http://site/SASHome/: dial tcp 10.10.10.10:80 : connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Http Status: 0 Why would the cli default back to http:// especially when I've specified the request/site to be https://? Kind Regards, David
... View more