Checked the logs.
Customer implemented the patch asgProps-installer-1.0.bsx at Jan24 15:32:58 with success,
<134>Jan 24 15:32:58 CDOM-1ST -bash: +09:00 2017 924 1 com.avaya.vsp | 0 HISTORY: PPID=29792 PID=29793 UID=0 md5sum asgProps-installer-1.0.bsx
<134>Jan 24 15:33:16 CDOM-1ST -bash: +09:00 2017 723 1 com.avaya.vsp | 0 HISTORY: PPID=29792 PID=29793 UID=0 sh ./asgProps-installer-1.0.bsx
the exit code of asgProps_install.log showns as below:
2017-01-24 15:33:16 INFO: Begin install of asgProps rpms
2017-01-24 15:33:17 INFO: Completed asgProps install return code 0
And the tomcat’s logs showed the service restart was successful.
2017-01-24 15:33:23,140|Jan 24, 2017 3:33:23 PM org.apache.catalina.startup.HostConfig deployD. escriptor
2017-01-24 15:33:23,140|INFO: Deploying configuration descriptor webconsole.xml
2017-01-24 15:33:26,272|log4j: reset attribute= "false".
Then he did the second patch webconsole-asg-fix-1.0.bsx
<134>Jan 24 15:34:11 CDOM-1ST -bash: +09:00 2017 474 1 com.avaya.vsp | 0 HISTORY: PPID=29792 PID=29793 UID=0 md5sum webconsole-asg-fix-1.0.bsx
<134>Jan 24 15:34:22 CDOM-1ST -bash: +09:00 2017 541 1 com.avaya.vsp | 0 HISTORY: PPID=29792 PID=29793 UID=0 sh ./webconsole-asg-fix-1.0.bsx
And the tomcat’s logs showed the service restart was failed.
2017-01-24 15:34:30,783|Jan 24, 2017 3:34:30 PM org.apache.catalina.startup.HostConfig deployDescriptor
2017-01-24 15:34:30,783|SEVERE: Error deploying configuration descriptor webconsole.xml
2017-01-24 15:34:30,783|java.lang.UnsupportedClassVersionError: com/avaya/vsp/webconsole/system/WebContextListener : Unsupported major.minor version 52.0 (unable to load class com.avaya.vsp.webconsole.system.WebContextListener)
In this case, the issue might be caused by the secondary patch. And the kay jar file is named webconsole.jar