Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    4
  • Answers answer
    1
  • Subscribers subscribers
    177
  • Views views
    264
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Jetty server is not able to start on the DR end

Haniyya Rehan

Hi,

Description:

DB: Database
DR: Disaster Recovery
PR: Production environment

uCMDB version: 11.2018



We have shifted the DB to the DR side from PR but uCMDB is not starting on the DR side.

The DB on both sides are in sync mode, data is same on both DBs.

uCMDB is connected to the DB on DR but jetty server is not able to start there.

Please help us to resolve this issue.

Thank you.

  • Suggested Answer

    0  

    Hello Haniyya,

    first of all CMS 2018.11 is out of Support for some time.

    Also, in CMS 2020.08 we updated the JDBC drivers and I suspect that this is relevant.

    What are the errors during startup for startup.log and wrapper.log on server side?

    Is the DB version supported?

    Either way, most probably you will have to do an upgrade of CMS.

    \Bogdan

  • 0 in reply to   

    Hi John,

    The startup.log is stating that Jetty server is not starting.

    Is there any to way to fix this?

  • 0   in reply to 

    This is to generic to provide a fix for it.

    What about wrapper.log?

    Usually the Jetty won't start if the DB is not available.

  • 0  

    Hello,

    You can try the following steps:

              a. clean content of folder "\runtime\jetty-cache" then restart service

              b. make sure there are backed up or other war files in deploy/ folder  (like ucmdb-browser.war.bk)

                              i. backup folders /deploy/rest-api, /deploy/discovery-log, /deploy/ucmdb-browser. Then delete these folder and restart service

    Check error, startup & dal logs for errors.

    Hope it helps.

    Best Regards,

    Gabi Medan

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.