SAS Web application redeploy failed

[sathya66]

Hi all,

Rebuilt was successful  and trying to redploy the web apps. It is failed at "Starting SAS Web Application Server Configuration".and it is failed due to  SASDeploymentBackup and SASBackupManager startup. Please can you advice .

logs:

log4j:WARN No appenders could be found for logger (org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASDeploymentBackup]).
log4j:WARN Please initialize the log4j system properly.
12:00:25,380 | ERROR | [StandardContext] | One or more listeners failed to start. Full details will be found in the appropriate container log file
12:00:25,380 | ERROR | [StandardContext] | Context [/SASDeploymentBackup] startup failed due to previous errors

log4j:WARN No appenders could be found for logger (org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASBackupManager]).
log4j:WARN Please initialize the log4j system properly.
12:00:28,997 | ERROR | [StandardContext] | One or more listeners failed to start. Full details will be found in the appropriate container log file
12:00:28,998 | ERROR | [StandardContext] | Context [/SASBackupManager] startup failed due to previous errors

[JuanS_OCS]

Hello @sathya66 ,

we would need to give a further look at the logs, perhaps even on debug/trace mode.

For now, I would assume that perhaps the deployment files or the log4j config files for those 2 applications (SASDeploymentBackup and SASBackup) might have been modified/customized/removed from your current environment (by a person in the past, not this upgrade in place) and, if so, that might be causing issues with the UIP, which is assuming you had those in place, close to default.

In any case,

a) while very important applications, I don't think they are critical and if the other webapps could be rebuilt and redeploy, you could skip this error/warning and validate your environment. Unless, of course, that your employer is an organization that does not accept easily warnings or errors, such as some financial institutions or life-sciences/pharma. In that case you would need to choose a path with 0 errors in your logs, or to explain the situation extremely well. 

b) it is always an option to remove the configuration for those 2 web applications and re-install/re-configure them again. If you go for this option, I would advise you to do it in alliance with SAS Tech Support, who can guide you through some intricate steps and ensure the quality of your upgrade.

Does it help?

Best regards,

Juan

[sathya66]

Thanks Juan,

I can't ignore it because it will ignore the 3rd stage "SAS Web Application
Server Configuration". I need to go with option b) below or need to solve this issue.

[JuanS_OCS]

Are you sure? You could try to start the web applications (by the usual means) by yourself and see if (and what) works.

Before you started this upgrade, did you have the chance to run the SAS Content Assessment tool?

[sathya66]

Thanks Jaun,

yes,I started manually, all looks working except SASDeploymentBackup and SASBackupManager through web.

https://test.com:8343/SASEnvironmentMgrMidTier/

login is failed to SAS Environment manager as it holds backup manager (I think it is because of  3 rd stage (web app configuration) )

is this possible to configure /can we fix SASDeploymentBackup and SASBackupManager  manually now ?

see the error below

no , I look into this SAS Content Assessment tool

[JuanS_OCS]

Hi @sathya66 ,

I am sure that it can be resolved, the question is "how".

A manual investigation and resolution is probably possible, but with all the technical details it is hard to help you through this media. You need someone to look at your environment together with you.

Probably the most suitable option will be to move ahead with the configuration steps, and one you are done, to remove the failing applications and then re-configure them and re-deploy them. If you do this by yourself, though, and you are not fully confident, you would be assuming a certain risk. You know better than anyone what you can or can't do.

This being said, the best path would be to contact SAS Tech Support right away, and let them guide you through the best steps for your environment, possibly with a webex/skype session.

[AnandVyas]

Does the log4j config files exist or they have been removed? Do you have any similar environment? You can look for these files available there and give it a shot!

[sathya66]

Thanks Anand,
I found only for deployment backup(SASDeploymentBackup-log4j.xml). There is no file for backup manager.
I compared above file with our other ENV and it is same(there is no difference ).
is there any other way I can solve this.

[AnandVyas]

Can you place the file you found in the LogConfig location and restart server and see if you still see the error?

[sathya66]

Thanks ,
No luck, same error after placing that file in <config>/Web/Common/LogConfig/SASDeploymentBackup-log4j.xml.

[AnandVyas]

Ok, may be then you can search for this file in SASHome on mid-tier server and try with that one?

cd <SAS-Home>
grep -iR SASDeploymentBackup-log4j.xml *

It should be available with .orig which you will have to rename after copying to LogConfig location. Even after this if it fails then its best you reach out to TS.

[JuanS_OCS]

@sathya66 , @AnandVyas , I am not fully sure the issue is on the log4j files, it could also be on the deployment files.

Web\WebAppServer\SASServer1_1\conf\Catalina\localhost

It is often than people take some xml out to disable some minor applications to load/work (for whatever reason).

@sathya66 , in any case, you need to read carefully your server.log of SASServer1_1 to identify the issue a little bit more scientifically. The log should tell you where the issue lies, exactly, in the startup lines before "(WrapperSimpleAppMain) [org.apache.catalina.startup.Catalina] Server startup in XXXXXXX ms".

[sathya66]

see the errors in SASSERVER1_1/logs.

2020-09-03 09:52:35,613 INFO (localhost-startStop-3) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASAdmin]] Initializing Spring FrameworkServlet 'rest'
2020-09-03 09:52:35,725 ERROR (localhost-startStop-7) [org.apache.catalina.core.StandardContext] One or more listeners failed to start. Full details will be found in the appropriate container log file
2020-09-03 09:52:35,726 ERROR (localhost-startStop-7) [org.apache.catalina.core.StandardContext] Context [/SASDeploymentBackup] startup failed due to previous errors
2020-09-03 09:52:35,758 INFO (localhost-startStop-7) [org.apache.catalina.startup.HostConfig] Deployment of configuration descriptor [/opt/sas/config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASDeploymentBackup.xml] has finished in [3,974] ms
2020-09-03 09:52:35,758 INFO (localhost-startStop-7) [org.apache.catalina.startup.HostConfig] Deploying configuration descriptor [/opt/sas/config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASBIWS.xml]
2020-09-03 09:52:36,617 INFO (localhost-startStop-1) [org.apache.catalina.startup.HostConfig] Deployment of configuration descriptor [/opt/sas/config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASFlexThemes.xml] has finished in [3,908] ms
2020-09-03 09:52:36,617 INFO (localhost-startStop-1) [org.apache.catalina.startup.HostConfig] Deploying configuration descriptor [/opt/sas/config/Lev1/Web/WebAppServer/SASServer1_1/conf/Catalina/localhost/SASWIPClientAccess.xml]
2020-09-03 09:52:36,957 ERROR (localhost-startStop-5) [org.apache.catalina.core.StandardContext] One or more listeners failed to start. Full details will be found in the appropriate container log file
2020-09-03 09:52:36,957 ERROR (localhost-startStop-5) [org.apache.catalina.core.StandardContext] Context [/SASBackupManager] startup failed due to previous errors

[JuanS_OCS]

Thank you @sathya66 . Good, this gives more information, and we will need a bit more. 

The issue for both webapps is "One or more listeners failed to start. Full details will be found in the appropriate container log file".

Is there anything in the localhost.XXXXXX.log  logs? If there is nothing, check this:

I would suggest to apply the increased debug options described here

https://stackoverflow.com/questions/48639816/tomcat-one-or-more-listeners-failed-to-start

[AnandVyas]

@JuanS_OCS Just wanted to be sure if it's just because of the log file then a copy is available and can be used.

@sathya66 Full server.log would be a good place to see what's failing starting from SASServer1_1. As mentioned by @JuanS_OCS earlier, sometimes it could be known defect as well. I have seen a case where there were two extra dots (..) in one of the web application and it was only resolved after TS confirmed it.