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

vCenter 6.5.0 b（ビルド 5178943）以降で OVF を展開できない (53731)

Last Updated: 4/6/2018Categories: TroubleshootingTotal Views: 1Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

免責事項： これは英文の記事「Cannot deploy an OVF in vCenter 6.5.0b (build 5178943) and later (2150693)」の日本語訳です。記事はベストエフォートで翻訳を進めているため、ローカライズ化コンテンツは最新情報ではない可能性があります。最新情報は英語版の記事で参照してください。

注：この問題は、vCenter 6.5.0b（ビルド 5178943）以降にのみ影響します。

vCenter 6.5.0b 以降で OVF を展開しようとすると、次のエラーが表示される。
Unable to process template" or the wizard will hang during the validation process.

/var/log/vmware/content-library/cls.log ファイルに、コンテンツ ライブラリが try-instantiate 検証リクエストを呼び出したことが記録される。
2017-04-26T11:31:35.359Z | DEBUG | SelectResourcePageMediator-validate-16444858-ngc-51 | cls-simple-activity-7 | ImportSessionActivity | received event [RequestStateActivityEvent[source=TryInstantiateImportActivity(f612997b-acc8-47a8-b0dc-d3bba7278a98), resultName=3ec87a5d-e4a4-4b9e-bb70-8fcb778b2e6d, eventName=TryInstantiateImportSession] submitted on Wed Apr 26 11:31:35 GMT 2017]
2017-04-26T11:31:35.359Z | DEBUG | SelectResourcePageMediator-validate-16444858-ngc-51 | cls-simple-activity-7 | ImportSessionActivity | Try-instantiate of session 6d771f4b-4b09-4870-9f02-19e7cb25ce9f requesting...
2017-04-26T11:31:35.359Z | DEBUG | SelectResourcePageMediator-validate-16444858-ngc-51 | cls-simple-activity-7 | IntermediateResultListener | Activity ImportSessionActivity(6d771f4b-4b09-4870-9f02-19e7cb25ce9f) posted intermediate result: 3ec87a5d-e4a4-4b9e-bb70-8fcb778b2e6d
2017-04-26T11:31:35.359Z | DEBUG | SelectResourcePageMediator-validate-16444858-ngc-51 | cls-simple-activity-7 | ImportSessionActivity | Try-instantiate of session 6d771f4b-4b09-4870-9f02-19e7cb25ce9f requested

try-instantiate 検証は 2 分後に完了する。
2017-04-26T11:33:26.481Z | DEBUG | SelectResourcePageMediator-validate-16444858-ngc-51 | cls-simple-activity-3 | TryInstantiateImportActivity | tryInstantiate result: OvfValidationResult (com.vmware.vcenter.ovf.import_session.ovf_validation_result) => {
parameters = [NameAndProductParams (com.vmware.vcenter.ovf.name_and_product_params) =>

インポート セッションが 10 分後にタイムアウトになる。
2017-04-26T11:41:35.492Z | ERROR | SelectResourcePageMediator-validate-16443638-ngc-aa-51 | cls-simple-activity-5 | ImportSessionActivity | OVF import session 6d771f4b-4b09-4870-9f02-19e7cb25ce9f terminated abnormally.
(vim.fault.Timedout) {
faultCause = null,
faultMessage = null

Web Client の virgo ログ (/var/log/vmware/vsphere-client/logs) で、最初の try-instantiate の呼び出しの 1 分後に例外が表示される。
com.vmware.vise.vim.vapi.DefaultVapiConnectionControl Maximum number of attempts reached while trying to call com.vmware.vcenter.ovf.import_session.try_instantiate
...
[2017-04-26T11:32:35.701Z] [ERROR] http-bio-9090-exec-5117 70929481 118317 214508 c.v.vsphere.client.provisioning.ovf.impl.OvfDeployServiceImpl Unable to query OVF. java.lang.IllegalStateException: Connection pool shut down

Resolution

これは、vCenter Server 6.5.0b (Build 5178943) 以降の既知の問題です。

この問題が vCenter Server 6.5 Update 1 で解決されており、VMware Downloads から入手できます。

注：vCenter 6.5.0 b 以前ではタイムアウト値がなかったため、以前のビルドではこの問題は発生しません。

Workaround

この問題を回避するには、VAPI ソケットの読み取りタイムアウトをデフォルト値の 1 分から 10 分に増やします。

vCenter Server Appliance で VAPI ソケットの読み取りタイムアウトを増やすには：

SSH を使用して VCSA にログインします。

ディレクトリを usr ディレクトリに変更します。
cd /usr/lib/vmware-vsphere-client/server/repository/usr

新しい一時ディレクトリを作成します。
mkdir temp

新しい一時ディレクトリに変更します。
cd temp

vim-services.jar ファイルを上のディレクトリから一時ディレクトリに展開します。
unzip ../vim-services.jar

次のコマンドを使用して、vim テキスト エディタで vim-services.properties ファイルを開きます。
vim vim-services.properties

次の行を
vim.services.vapi.socket.timeout=60000
次のように変更します。
vim.services.vapi.socket.timeout=600000

次のコマンドを実行して変更を書き込み、ファイルを保存し、vim エディタを閉じます。
:wq!

次のコマンドを実行して、vim-services.jar ファイルを圧縮します。
zip -r vim-services.jar .

次のコマンドを使用して親ディレクトリに移動します。
cd ..

ファイルの名前を変更して元の vim-services.jar ファイルのバックアップを作成します。
mv vim-services.jar vim-services.jar.original

編集した vim-services.jar をコピーします。
cp temp/vim-services.jar .

手順 3 で作成した一時ディレクトリを削除します。
rm -rf temp

次のコマンドを使用して、vsphere-client サービスを停止してから再起動します。
service-control --stop vsphere-client
service-control --start vsphere-client

Related Information

简体中文：无法在 vCenter 6.5.0b（内部版本 5178943）和更高版本中部署 OVF

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.0.x

VMware vCenter Server Appliance 5.5.x

VMware vCenter Server Appliance 5.1.x

VMware vCenter Server Appliance 5.0.x

VMware vCenter Server Appliance 5.0

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

VMware vCenter Server 5.x - View

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.1 Extended Support

VMware vCenter Server 5.0.x

VMware vCenter Server 5.0 Beta

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

view all

Support Assistant