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 Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    8
  • Views views
    972
  • 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

Updating to Vibe 4.0.8.2 - success or fail?

Diethmar Rimser
 

I want to get some feedback if your updates were successful.

I have tried to update a test environment which failed. Well, not my update activity failed but my Vibe was not accessible. However this test environment has been used for many other software tests too. Maybe too often - I thought. 

Therefore I took an older snapshot and started Vibe 4.0.8.1 on this machine. Successful access. Now I repeated update again. Update successful but accessing Vibe failed. catalina.log showed this statement twice " Caused by: java.net.BindException: Address already in use". But neither ip address nor port are really in use.

So tell me your experiences! Thinking

Use "Verified Answers" if your problem/issue has been solved!

  • 0

    Yes, Diethmar, the update was successful, i must only reinstall the certifcate for ldap with keytool.

    I think that i don't keyin the certificate file name by installation!

  • 0   in reply to 

    Good to hear, Claude.

    So there is still some hope that my grumpily test environment annoys me ...

    Use "Verified Answers" if your problem/issue has been solved!

  • 0  

    Coming back with some details. My test environment is definitely guilty! Vibe 4.0.8.2 is okay.

    I did some simple tests. I started my server, started mysql and vibe. Vibe was accessible ... In my recent steps I updated to 4.0.8.2 and failed. This time I updated from 4.0.8.1 to 4.0.8.1 and failed too. So I knew that there must be another issue! Just now I do not know which of my packages causes this problem (it was one of some "novell" packages which does not sit on one ip address but occupies all addresses), but if I still the offending process, Vibe is accessible Innocent

    Use "Verified Answers" if your problem/issue has been solved!

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.