BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.

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? 

1 ACCEPTED SOLUTION

Accepted Solutions
sewa_bal_gmail_com
Quartz | Level 8

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)

View solution in original post

19 REPLIES 19
alexal
SAS Employee

@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
sewa_bal_gmail_com
Quartz | Level 8

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

 

alexal
SAS Employee

@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
sewa_bal_gmail_com
Quartz | Level 8

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.

anja
SAS Employee

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

 

sewa_bal_gmail_com
Quartz | Level 8

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?

sewa_bal_gmail_com
Quartz | Level 8

Attached error screenshot


sas conf steps.JPGsas_error.JPG
alexal
SAS Employee

@sewa_bal_gmail_com,

 

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

sewa_bal_gmail_com
Quartz | Level 8

Can we reboot Linux server during sas configuration step?

 

 

 

alexal
SAS Employee

@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

sewa_bal_gmail_com
Quartz | Level 8

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?

 

[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

 

 

alexal
SAS Employee

@sewa_bal_gmail_com,

 

Sure, just do:

 

./sas.servers stop
sewa_bal_gmail_com
Quartz | Level 8

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

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 19 replies
  • 6169 views
  • 0 likes
  • 5 in conversation