topic Re: SAS Configuration Error in Administration and Deployment

SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 13:31:19 GMT

Hi All,

We are upgrading from SAS9.4M3 to M4. We are getting some error during sas web app server configuration: -

Java.lang.llegalstateException: Port (6161) isn't available

Config script:

/opt/sas/software/sasdeploymentmanager/9/4/products/cfgwizard__94480__prt__xx_sp0__1/Utilities/Appserver/source/Ant/appserver+config.xml

Please advise?

Re: SAS Configuration Error

alexal — Fri, 07 Jul 2017 13:38:50 GMT

@sewa_bal_gmail_com,

Are you sure you brought all SAS services down?

ps -ef | grep -i sas

Who is holding that port? Run the following command as root user:

lsof -i tcp:6161

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 13:45:37 GMT

Thanks for reply.

Yes, we have stopped all the services before starting the upgrade.

No one is using the 61616 port. Nothing comes out when I type

lsof -i tcp:6161

Re: SAS Configuration Error

alexal — Fri, 07 Jul 2017 14:14:30 GMT

@sewa_bal_gmail_com,

Are you talking about port 6161 or 61616? We do not use port 6161 in SAS, but 61616 is in use by SAS JMS Broker. Are you sure that brought down the JMS Broker? Please send an output from the following commands:

/<SASConfig>/Lev<X>/sas.servers status
netstat -an | grep 61616

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 14:29:38 GMT

Thanks for reply.

Port is 61616 used for JMS.

[root@sasprod01 Lev1]# ./sas.servers status
SAS servers status:
SAS Web Infrastructure Data Server is UP
SAS Metadata Server 1 is UP
SAS Object Spawner 1 is NOT up
SAS DIP Job Runner 1 is NOT up
SAS Information Retrieval Studio Server is NOT up
SAS JMS Broker is NOT up
SAS Cache Locator Service ins_41415 is NOT up
SAS Web Server is NOT up
SAS Web App Server SASServer1_1 is NOT up
SAS Web App Server SASServer12_1 is NOT up
SAS Web App Server SASServer2_1 is NOT up
SAS Environment Manager is NOT up
SAS Environment Manager Agent is NOT up

[root@sasprod01 Lev1]# netstat -an | grep 61616
[root@sasprod01 Lev1]#

We are upgrading the sas environment and currently, we are on configuration part for sas web app server cong.

Please advise.

Re: SAS Configuration Error

anja — Fri, 07 Jul 2017 16:01:21 GMT

Hi,

could you provide some more details, such as: where exactly are you at in the config process/

what step are you trying to do when this error occurs?

When looking at the list of your servers, the ones that are not up, can you start those or

does this result in this error? Can you stop all services or are some still showing as up even tho

you stopped them? Can you kill the process?

A netstat -a | findstr 6161 might provide some info?

Thanks

Anja

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 16:29:04 GMT

Thanks Anja,

We are upgrading the sas servers from 9.4 M3 to 9.4 M4 and this error occurred during step 20th of sas configuration that is "sas web application server configuration".

for more info please please find attached screenshot of error and sas config step.

[root@sasprod01 bin]# netstat -a | findstr 61616
bash: findstr: command not found
[root@sasprod01 bin]# netstat -a | grep 61616

[root@sasprod01 bin]#

Please advise?

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 16:33:06 GMT

Attached error screenshot

Re: SAS Configuration Error

alexal — Fri, 07 Jul 2017 16:41:18 GMT

@sewa_bal_gmail_com,

Restart Linux and try once again. Someone is holding that port.

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 16:45:54 GMT

Can we reboot Linux server during sas configuration step?

Re: SAS Configuration Error

alexal — Fri, 07 Jul 2017 16:55:51 GMT

@sewa_bal_gmail_com,

You can close SAS Deployment Wizard, restart Linux and restart the configuration step. Make sure that you do not have sas.servers script in /etc/init.d

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 17:09:25 GMT

Thanks Alexal,

There are no sas.servers file under /etc/init.d dir

Currently, below services are running. Do we want to stop running services first before linux reboot server?

Re: SAS Configuration Error

alexal — Fri, 07 Jul 2017 17:10:27 GMT

@sewa_bal_gmail_com,

Sure, just do:

./sas.servers stop

Re: SAS Configuration Error

sewa_bal_gmail_com — Fri, 07 Jul 2017 17:18:41 GMT

Thanks for quick reply.

Do I need to restart the below services to resume the config steps after server reboot?

SAS Web Infrastructure Data Server is UP
SAS Metadata Server 1 is UP

Re: SAS Configuration Error

alexal — Fri, 07 Jul 2017 17:19:47 GMT

@sewa_bal_gmail_com,

Yes.

Re: SAS Configuration Error

sewa_bal_gmail_com — Sat, 08 Jul 2017 08:48:22 GMT

Hi Alexal,

We have reboot the server and started the below services:-

SAS Web Infrastructure Data Server is UP

SAS Metadata Server 1 is UP

But when we started the sas deployment wizard to upgrade the sas, it's not started at the same point where we getting an error. Please find attached screenshot for the same.

When I select "configure sas software" from the options list then its start from asking the same option when we required to configure sas at a very first time after passing deployment xml file.

We have selected server and middle tier to configure first from the options list and it's throwing some warning pop-up. Please see the attached screenshot of this warning.

Please advise.

Re: SAS Configuration Error

sewa_bal_gmail_com — Sun, 09 Jul 2017 17:03:55 GMT

Hi All,

After server reboot still, I am getting the same error. Please see below sas config logs. "java.lang.IllegalStateException\: Port (61616) isn't available\!"

2017-07-09 19:16:30,902 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - url=file:////opt/sas/config/Lev1/Web/Common/LogConfig
2017-07-09 19:16:30,903 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - IPJavaOptions=-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=false
2017-07-09 19:16:30,903 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - multicastAddress=239.143.82.132
2017-07-09 19:16:30,903 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - multicastPort=8561
2017-07-09 19:16:30,903 [main] INFO com.sas.appserver.utils.AppServerHelper - getServerID >>>
2017-07-09 19:16:30,904 [main] INFO com.sas.appserver.utils.AppServerHelper - getServerID <<<
2017-07-09 19:16:30,904 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - wipServerId=server1
2017-07-09 19:16:30,905 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - webServerIsConfigured == true
2017-07-09 19:16:30,905 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - wsScheme = https
2017-07-09 19:16:30,906 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - sas.cache.locators=server.name[41415]
2017-07-09 19:16:30,906 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - gemfire.conserve-sockets=false
2017-07-09 19:16:30,906 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - cacheLocator spring.profile.active=locators
2017-07-09 19:16:30,906 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - ttfontsvert.install.dir="/opt/sas/software/ReportFontsforClients/9.4"
2017-07-09 19:16:30,906 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - bivaprint.install.dir="/opt/sas/software/SASVisualAnalyticsPrintingSupport/7.4"
2017-07-09 19:16:30,906 [main] INFO com.sas.appserver.utils.JvmOptionBuilder - buildSDMWhitelistOption serverId = server1
2017-07-09 19:16:31,306 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable(server.name,8080) >>>
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - Connection refused
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - isAvailable=true
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable() <<<
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable(server.name,8080) >>>
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - Connection refused
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - isAvailable=true
2017-07-09 19:16:31,312 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable() <<<
.
.
.
.
2017-07-09 19:16:34,857 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable(server.name,8080) >>>
2017-07-09 19:16:34,857 [main] INFO com.sas.appserver.utils.PortUtils - Connection refused
2017-07-09 19:16:34,857 [main] INFO com.sas.appserver.utils.PortUtils - isAvailable=true
2017-07-09 19:16:34,857 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable() <<<
2017-07-09 19:16:34,857 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable(server.name,8080) >>>
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.PortUtils - Connection refused
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.PortUtils - isAvailable=true
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable() <<<
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Environment Variables:
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - CONTAINER_TYPE=vfabrictcsvr
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - SCRIPTING_DIR=/opt/sas/config/Lev1/Web/Scripts/AppServer
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Working Directory: /opt/sas/config/Lev1/Web/Scripts/AppServer
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Executable: /opt/sas/config/Lev1/Web/Scripts/AppServer/appsrvconfig.sh
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Arguments:
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - undeploy
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - application
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - all
2017-07-09 19:16:34,858 [main] INFO com.sas.appserver.utils.AntProcessInvoker - server
2017-07-09 19:16:34,859 [main] INFO com.sas.appserver.utils.AntProcessInvoker - SASServer1
[exec] log4j:ERROR setFile(null,true) call failed.
.
.
.
2017-07-09 19:16:35,081 [main] INFO com.sas.appserver.utils.AntProcessInvoker - ReturnCode=1
2017-07-09 19:16:35,081 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Output=
java.lang.IllegalStateException: Port (61616) isn't available!

...
...
#Sun Jul 09 19:16:37 EEST 2017
error.deploydir=
error.inifile=
error.docpart=
error.serviceName=
error.msg=java.lang.IllegalStateException\: Port (61616) isn't available\!
error.logfile=/opt/sas/config/Lev1/Logs/Configure/vfabrictcsvr_checkForErrors_2017-07-09-19.16.35.log
error.srcdir=
error.task=com.sas.sdw.SDWExceptionHandler
error.commandline=
error.command=
error.whatFailed=checkForErrors
error.user=

Re: SAS Configuration Error

SASKiwi — Sun, 09 Jul 2017 20:04:37 GMT

In my experience you would get faster progress by using SAS Tech Support directly.

Re: SAS Configuration Error

AnandVyas — Mon, 10 Jul 2017 04:18:41 GMT

Hi @sewa_bal_gmail_com

This error during config is basically due to config wizard unable to fetch the port 61616, can you check if you are JMS broker was started properly before the Web App servers started to launch?

you can go to directly the JMS logs and validate this.

Thanks,
AV

Re: SAS Configuration Error

sewa_bal_gmail_com — Mon, 10 Jul 2017 10:39:53 GMT

Issues have been fixed after granting the permission to these files.

java.io.FileNotFoundException: /opt/sas/config/Lev1/Web/Scripts/AppServer/logs/config.log (Permission denied)

and

java.io.FileNotFoundException: /opt/sas/config/Lev1/Web/Scripts/AppServer/logs/bootstrap.log (Permission denied)