Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Failed to load OpenSSL libraries" rhttpproxy service crashes continuously during in-place windows vcenter server upgrade from 6.0 U3i to 6.0 U3j (76272)

Last Updated: 4/14/2020Categories: TroubleshootingTotal Views: 5241Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While updating the Windows vCenter from 6.0U3i to 6.0U3j the rhttpproxy service fails to start, however it tries to start continuously in an infinite loop, every time it fails to start it creates a dump file as the service was crashing.

You will see similar entries in rhttpproxy.log as mentioned below,

rhttpproxy.log:

2019-11-01T11:13:14.563+01:00 Section for VMware VirtualCenter, pid=7044, version=6.0.0, build=14510545, option=Release
2019-11-01T11:13:14.563+01:00 verbose rhttpproxy[08932] [Originator@6876 sub=Default] Dumping early logs:

------ Early init logs start --------
2019-11-01T11:13:14.345+01:00 info -[08932] [Originator@6876 sub=Default] Initialized SystemFactory

------ Early init logs end  --------
2019-11-01T11:13:14.563+01:00 warning rhttpproxy[08932] [Originator@6876 sub=Default] Unrecognized log/level '' using 'info'
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] Logging uses fast path: true
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] The bora/lib logs WILL be handled by VmaCore
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] Initialized channel manager
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] Current working directory: C:\Windows\system32
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] ThreadPool windowsStackImmediateCommit = true
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08328] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-01T11:13:14.563+01:00 info rhttpproxy[12756] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-01T11:13:14.563+01:00 info rhttpproxy[09208] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=ThreadPool] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 44, 2, 18, 2147483647
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-01T11:13:14.563+01:00 info rhttpproxy[11588] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] Listening on HTTP port 80.
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] Listening on HTTPS port 443.
2019-11-01T11:13:14.563+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] Vmacore::InitSSL: path configuredLibDir = C:\\Program Files\\VMware\\vCenter Server\openSSL\
2019-11-01T11:13:14.797+01:00 info rhttpproxy[08932] [Originator@6876 sub=Default] CoreDump: Writing minidump
2019-11-01T11:13:14.953+01:00 panic rhttpproxy[08932] [Originator@6876 sub=Default]

--> Panic: SSLLoadSharedLibraries: Failed to load OpenSSL libraries. libdir is C:\\Program Files\\VMware\\vCenter Server\openSSL\
-->
--> Backtrace:
-->
--> [backtrace begin] product: VMware VirtualCenter, version: 6.0.0, build: build-14510545, tag: rhttpproxy
--> backtrace[00] vmacore.dll[0x001C9C0A]
--> backtrace[01] vmacore.dll[0x0005E15F]
--> backtrace[02] vmacore.dll[0x0005EA7E]
--> backtrace[03] vmacore.dll[0x001DF985]
--> backtrace[04] vmacore.dll[0x001DFA7D]
--> backtrace[05] vmacore.dll[0x00027B53]
--> backtrace[06] vmacore.dll[0x001FCE38]
--> backtrace[07] vmacore.dll[0x00206E9E]
--> backtrace[08] vmacore.dll[0x00118A7F]
--> backtrace[09] rhttpproxy.exe[0x0000401A]
--> backtrace[10] rhttpproxy.exe[0x000017B3]
--> backtrace[11] sechost.dll[0x0000A82D]
--> backtrace[12] kernel32.dll[0x0001556D]
--> backtrace[13] ntdll.dll[0x0005385D]
--> [backtrace end]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article is to identify and resolve the rhttpproxy service crashing issue while upgrading to 6.0U3j.

Cause

Rhttpproxy failed to load openssl libraries while starting rhttpproxy services as the OpenSSL libraries were used by third party applications.

Resolution

To resolve this issue make sure there are no third party applications which uses the same openssl libraries as vCenter Server and uninstall the applications.

Re-try the windows in-place vCenter Upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VUM 扫描失败：VMware vSphere Update Manager 存在未知错误。请查看事件和日志文件 (76357)

KB
•
在 vCenter 6.5 和 6.7 的 HTML5 客户端中，无法将精简磁盘增加到超过 "最大大小" (78594)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant