About dpage

dpage · ‎07-20-2017

It depends on where / when (how did you get back from the Enterprise Miner failure to Web Application Server configuration). You might be better off to open a Tech Support track to reach a faster resolution.,

dpage · ‎07-20-2017

That log shows a failure trying to write to the /etc/opt/vmware/vfabric directory (since it failed, things that depend on it, also fail)From the log: Here are the manual steps: Logon as root user Create the directory /etc/opt/vmware/vfabric/ chown -R "Current SAS install user name" /etc/opt/vmware/vfabric/ chgrp -R "Group name of current SAS install user" /etc/opt/vmware/vfabric/

dpage · ‎07-19-2017

Do you have a vfabrictcsvr_configure*.log in your Lev1/Logs/Confgure path (sorry about the plan file, I missed that comment). What version of Enterprise Miner are you installing (I see SAS 9.4, but not a specific Enterprise Miner release)

dpage · ‎07-19-2017

Do you recall if you saw 'SAS Web Application Server' as an item being configured in the Deployment Wizard?

dpage · ‎06-22-2017

Anything incriminating in the Metadata Server logs? I'd be suspect of an expired license.

dpage · ‎05-26-2017

You'll find the system requirements in the Viya 3.2 deployment guide http://support.sas.com/documentation/onlinedoc/viya/index.html That's not a complete answer, it will depend on data size, product combination, number of users, do you want to continue running VA 7.3 side by side, etc. It will at least give you an idea of the minimum requirements / Operating System baselines.

dpage · ‎05-16-2017

I believe that should be http://<hostname>:7080 not /7080.

dpage · ‎04-05-2017

It's loaded by the configuring application at deploy time, some use a guid, some use the same identifier you'll find in the Lev1/ConfigData/status.xml.

dpage · ‎03-21-2017

if you're reffering to " WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable" That's an expected message unless you've setup the native libraries. https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/NativeLibraries.html Hadoop should still be functional.

dpage · ‎03-20-2017

You're seeing javac.exe in the 9.4\jre\bin directory? or 9.4\bin?

dpage · ‎03-20-2017

SASPrivateJavaRuntimeEnvironment\9.4\jre\bin is where you'll find java, javac is the compiler and not part of the jre (and why it's a level higher)

dpage · ‎03-07-2017

It's the way postgres works, every open connection gets a separate process. There was a slightly different question, but with the same root cause a little while ago. https://communities.sas.com/t5/Administration-and-Deployment/PostgreSQLserver-connections-left-open/m-p/334427

dpage · ‎02-24-2017

It needs to be done once per SID, if your metadata server has a different SID than your compute, you'll need to run it twice. Not new, it's been in place since at least 9.2, but depending on the combination of software you have it might not have been neccesarry until now. http://support.sas.com/documentation/installcenter/en/ikunixplannedri/66610/PDF/default/setinit_planned.pdf Covers the process, including "After you apply renewal SID files on all hosts in your environment, restart all SAS Servers and SAS Spawners in your environment in the appropriate order, beginning with the SAS Metadata server if it is used. The new expiration dates and licenses for any newly added products will take effect."

dpage · ‎02-20-2017

Can you confirm the other endpoint of the connection? The database may be on the compute tier, but the initiant may be on another machine (so you'd see no corresponding local process for it besides the postgres process) The Web Application server keeps a pool of connections open at all times, user activity or not. I think if you shut the web application server down as an experiment you'd see them go away, but if that's what you're seeing, it's expected.

dpage · ‎02-20-2017

The Web Application Servers have a connection pool they allocate and re-use connections from, is it possible that's what you're seeing? They should clean up when you shut down the web application server though. The way the postgres server works, you'll see a separate process created for each incoming connection, so they may appear orphaned on the database server side, but the java process that's using them is still running.

Online Status	Offline
Date Last Visited	‎07-14-2021 02:23 PM

Re: External Account Password Change

Re: SAS WebApp | Horizontal Cluster -- 404 after start the second mid ...

Re: Cannot execute systemEvalutation application - invalid config-dir ...

Re: Deployment error on task 'Create token for staticcerts'

Re: SAS Support policies

Re: %FSLOGIN error

Re: %FSLOGIN error

Re: %FSLOGIN error

Re: Hostname Update Error

Re: Hostname Update Error

Re: Cannot execute systemEvalutation application - invalid config-dir ...

Re: Deployment error on task 'Create token for staticcerts'

Re: SAS Support policies

Re: %FSLOGIN error

Re: %FSLOGIN error

Re: HP-UX | Install SAS Enterprise Miner

Re: HP-UX | Install SAS Enterprise Miner

Re: HP-UX | Install SAS Enterprise Miner

Re: HP-UX | Install SAS Enterprise Miner

Re: SAS Metadata Services SAS 9.4

Re: Hardware Requirement of SAS Viya vs SAS9 VA7.3 Distributed

Re: SAS Environment Manager - Page not found Http 404

Re: SoftwareComponent Source? from metadata_getnobj"omsobj:SoftwareCom...

Re: SAS-Hadoop Installation Error

Re: The Java child process terminated unexpectedly. Failed to attach J...

Re: The Java child process terminated unexpectedly. Failed to attach J...

Re: Postgress.exe processes

Re: SAS 9.4 - Updating SID file in metadata

Re: PostgreSQLserver connections left open

Re: PostgreSQLserver connections left open

SAS Global Forum 2019