Clarity

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

Upgrade failed - 15.2 patch 8 to 15.6.1

  • 1.  Upgrade failed - 15.2 patch 8 to 15.6.1

    Posted May 13, 2020 01:53 PM
      |   view attached
    Hi All,

    While trying to upgrade  to 15.6.1 from 15.2 patch 8, the upgrade got failed in the 14th min. But couldn't understand what was the root cause of the failure.
     
    Am attaching install.log for the reference.


    OS: Linux 
    DB:Oracle 12.2

    Could anyone please help me here?

    Regards,
    Agin

    Attachment(s)

    txt
    install.txt   1.02 MB 1 version


  • 2.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Broadcom Employee
    Posted May 13, 2020 02:07 PM
    Hi Agin

    5/12/20 10:26 AM (Echo) service id = beacon
    5/12/20 10:26 AM (Echo) servicecmd = niku
    5/12/20 10:26 AM (ExecTask) /494fs01/clarity/bin/niku: line 1: syntax error near unexpected token `newline'
    5/12/20 10:26 AM (ExecTask) /494fs01/clarity/bin/niku: line 1: `<!doctype html>'
    5/12/20 10:26 AM (UnknownElement) Task "exec" finished with error.
    /494fs01/Installer_15.6.1/install.xml:1161: exec returned: 2


    Looks like there was an issue to deploy beacon service with command niku.

    I would recommend to rollback and start again. Before starting the upgrade, stop and remove all services.

    Hope this helps -Nika

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 3.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Broadcom Employee
    Posted May 13, 2020 02:09 PM
    You do not have to rollback the database as the database upgrade was not started yet. Just rollback the Clarity files to 15.2

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 4.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Posted May 13, 2020 02:23 PM
    Edited by Agin Vadath May 13, 2020 02:24 PM
      |   view attached
    Thanks, @Nika Hadzhikidi for quick help on this.

    We have stopped and removed the service before the upgrade starts. 

    "You do not have to rollback the database as the database upgrade was not started yet. Just rollback the Clarity files to 15.2" - Even we felt the same and re run the upgrade again after roll back clarity files, but this time it failed in 6 minutes.

    Am attaching the log file

    Regards,
    Agin

    Attachment(s)

    txt
    install.txt   3.07 MB 1 version
    Original Message


  • 5.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Broadcom Employee
    Posted May 13, 2020 02:55 PM
    Hi Agin

    This looks to be the same error.

    1. Can you delete the install files and extract the install.jar again from scratch?

    2. Also please rollback and remove all services not only beacon.

    3. Save the hosts.xml

    Retry and if you still have an issue share the hosts.xml as well as the install.log

    Hope this helps -Nika

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 6.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Posted May 14, 2020 08:28 AM
    Hi  @Nika Hadzhikidi​

    Still getting the same error even after the steps performed.

    Please find the hosts.xml & install.log.

    Regards,
    Agin

    Attachment(s)

    xml
    hosts.xml   387 B 1 version
    txt
    install.txt   3.86 MB 1 version
    Original Message


  • 7.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Broadcom Employee
    Posted May 14, 2020 08:45 AM
    see the error 

    Are you chaning files and adding new lines under clarity/bin/niku

    5/13/20 9:21 AM (ExecTask) /xxxfsxx/clarity/bin/niku: line 1: syntax error near unexpected token `newline'
    5/13/20 9:21 AM (ExecTask) /xxxfsxx/clarity/bin/niku: line 1: `<!doctype html>'

    ------------------------------
    Thanks & Regards
    Suman Pramanik
    Sr. Principal Support Engineer | Customer Success & Support, Enterprise Software Division
    Broadcom
    ------------------------------

    Original Message


  • 8.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Posted May 14, 2020 11:00 AM
    Thanks Nika & Suman for your prompt response.

    We got the issue. Our lower environment is on higher version (15.5), but we need to refresh it with prod. Hence we rolled out the old clarity backup after refresh (15.2.)
    So  the previous installer already installed 15.3 and 15.4 folders. hence when our 15.6 installer tries, it was failing.

    Regards,
    Agin
    Original Message


  • 9.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Broadcom Employee
    Posted May 14, 2020 11:19 AM
    Great to hear this Agin. Keep us updated on how it goes. -Nika

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 10.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1
    Best Answer

    Posted May 14, 2020 02:57 PM
    Hi @Nika Hadzhikidi,

    Upgrade  went well. Build successful and it took around 134 min.

    No issues reported in the post check install and able to start the services.

    But in install.log, i saw an error, could you please let me know what is the cause of this one?

    5/14/20 9:04 AM (ExecTask) Error: Exception encountered in updateTemplateFolders5/14/20 9:04 AM (ExecTask) com.niku.union.exceptions.DMSException: File is currently checked out by another user.5/14/20 9:04 AM (ExecTask) at com.niku.dms.service.DMSService.checkoutFileObject(DMSService.java:599)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.replaceTemplateFileContent(ConfigUpdateTemplateFolders.java:593)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.walkRecordTypes(ConfigUpdateTemplateFolders.java:541)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.walkActivity(ConfigUpdateTemplateFolders.java:378)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.walkActivityGroups(ConfigUpdateTemplateFolders.java:343)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.walkCatalog(ConfigUpdateTemplateFolders.java:292)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.walkCatalog(ConfigUpdateTemplateFolders.java:306)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.updateTemplateFolders(ConfigUpdateTemplateFolders.java:259)5/14/20 9:04 AM (ExecTask) at com.niku.xdm.ConfigUpdateTemplateFolders.main(ConfigUpdateTemplateFolders.java:161)5/14/20 9:04 AM (ExecTask) Error occurred: /xxxfsxx/clarity/.setup/scripts/xdm.xml:110: The following error occurred while executing this line:5/14/20 9:04 AM (ExecTask) /xxxfsxx/clarity/webroot/WEB-INF/xdm/xdmApplyConfig.xml:170: Java returned: 75/14/20 9:04 AM (ExecTask) Check admin.log or use -verbose for more information.5/14/20 9:04 AM (ExecTask) Ended in failure

    in Admin.log, i can see the error below. XDM is showing as 14.2.0.237 in CSA, Is it beause of this? Whatis the impact of XDM

    May 14, 2020, 10:45:21 AM Error executing command: xdm install/xxxfsxx/clarity/.setup/scripts/xdm.xml:110: The following error occurred while executing this line:/xxxfsxx/clarity/webroot/WEB-INF/xdm/xdmApplyConfig.xml:170: Java returned: 7 at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:568) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:443) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at com.niku.nsa.service.AntUtil.executeTargets(AntUtil.java:119) at com.niku.nsa.service.AntUtil.executeAntScript(AntUtil.java:81) at com.niku.nsa.service.AdminManager.invokeAction(AdminManager.java:610) at com.niku.nsa.service.AdminManager.execute(AdminManager.java:207) at com.niku.nsa.service.Admin.main(Admin.java:78) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581)
    Caused by: /xxxfsxx/clarity/webroot/WEB-INF/xdm/xdmApplyConfig.xml:170: Java returned: 7 at org.apache.tools.ant.taskdefs.Java.execute(Java.java:111) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441) ... 23 more

    Regards,
    Agin  ​
    Original Message


  • 11.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Broadcom Employee
    Posted May 14, 2020 04:46 PM

    Hi Agin,

    Correct, looks like XDM did not upgrade due to this. For root cause, check out this thread:

    https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=730235 

    You might have to rollback, fix the lock and upgrade again if you want it fixed right now. 



    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 12.  RE: Upgrade failed - 15.2 patch 8 to 15.6.1

    Posted May 15, 2020 12:32 AM
    Hi @Nika Hadzhikidi,

    That helps. I can see for few templates documents are not checked in. Hence unlocked it and upgraded the XDM. and it got successfully upgraded.

    Thanks,
    Agin​
    Original Message