08-02-2017 04:00 PM
we have couple web applications running and we just restarted sas servers for web apps
SAS servers status:
SAS JMS Broker is NOT up
SAS Cache Locator Service ins_41415 is UP
SAS Web Server is UP
SAS Web App Server SASServer1_1 is UP
SAS Web App Server SASServer11_1 is UP
SAS Web App Server SASServer11_2 is UP
SAS Web App Server SASServer1_2 is UP
SAS Web App Server SASServer12_1 is UP
SAS Web App Server SASServer12_2 is UP
SAS Web App Server SASServer13_1 is UP
SAS Web App Server SASServer13_2 is UP
SAS Web App Server SASServer2_1 is UP
SAS Web App Server SASServer2_2 is UP
SAS Environment Manager is UP
SAS Environment Manager Agent is NOT up
we tried performing some work arround using below sas notes but still same situation - JMS Broker and EVM Agent not starting up
08-03-2017 06:04 AM
what nare the error messages in your logs? Have you tried to stop/starte them manually? Did you check the port numbers are not in use while the services are down? Some additional information will help us to understand what is going on, and the more, the best.
08-03-2017 09:51 AM - edited 08-03-2017 09:52 AM
your guess is right, we didn't check if services running before we restart services, but here are some logs.
date:time | ERROR | Failed to start Apache ActiveMQ (localhost, ID:....com-17792-1501701809286-0:1). Reason: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:xxxxx due to: java.net.BindException: Address already in use | org.apache.activemq.broker.BrokerService | main
java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:xxxxx due to: java.net.BindException: Address already in use
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
ERROR: java.lang.Exception: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
java.lang.Exception: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
08-03-2017 10:10 AM
It seems the previous process was not shut down properly and it is still locking the port.
netstat -nap |grep 61616
check the process ID and Kill it.
and then try to start again.
08-04-2017 11:32 AM - edited 08-04-2017 11:33 AM
we have multiple sas web app + processes running at the moment - if have issue with only one web applicstion and if we want to restart it, how we do it? for example if we have web app running under "SASServer11_1" - thank you-
08-08-2017 06:32 AM
justan addition to @vrkgali indications. There is an alternative of stoping and starting web applications or web application servers with the SAS Environment Manager GUI and an administrator account. The process is described here: https://platformadmin.com/blogs/paul/2015/09/restart-sas-web-apps-with-sas-environment-manager/
Anyway, whi would you need to do that? If you manage to kill the port as described by @vrkgali, you only need to ./sas.servers.mid stop and ./sas.servers.mid start. I just like simpler solutions when available.