new1234.jpg

Archive

Posts Tagged ‘Troubleshooting’

VMware: Perf Charts service experienced an internal error

December 16th, 2015 No comments

A few weeks ago a customer asked me to take a look at the following warning message in VMware vCenter when the Performance Tab in the vSphere client is being opened.

  

Perf Charts service experienced an internal error.

Message: Report application initialization is not completed successfully. Retry in 60 seconds

 
image


Troubleshooting time

Global checks:

  • The Windows Event logs are clean
  • VMware vSphere (web-) services are started with normal credentials
  • I was able to restart service accounts with domain based credentials (no locking)
  • Windows Firewall was enabled but no drops in the logging
  • No recent installed Windows Updates
  • No unplanned restarts or crashes
  • The installed certificate was not expired
  • The installed certificate was 2048 bit
  • No conflicting webserver ports at the vCenter server
    ..some more troubleshooting

I checked the wrapper.log and stas.log files located at the following location:

Path: C:\ProgramData\VMware\VMware VirtualCenter\Logs\

clip_image002

 

 

 

 

 

 

 

 

 

  

clip_image002[5]

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Hmm, he logging shows that there are problems with the installed vCenter SSL certificate:
 

Error constructing private key..

..Error decrypting password

After some troubleshooting I saw that every time I open the Performance tab a new webserver SSL private key decrypting error was written in the stats.log.

I already had checked the expire date of the installed SSL certificate, it was a normal 2048 bit wildcard certificate.. oh, eh, wildcard..?? Let’s see if it is supported:

“The use of wildcard certificates are not supported with vCenter Server and its related services. Each service must have its own unique certificate”

Nope, it is not! Maybe this is the root cause.

After checking the SSL requirements at the VMware KB  I found the SSL format which is needed to generate the certificate: OpenSSL Version 0.9.8 must be used. If you do not use this version, the SSL implementation fails. <– I couldn’t check this because there was no documentation of the SSL generation

 

Solution

The customer used a wildcard SSL certificate which is not supported

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Install VMware vCenter Support Assistant 6.0.0 appliance

November 20th, 2015 No comments

Install and configure VMware vCenter Support

1. Download the VMware vCenter Support Assistant

2: Deploy the OVF > Accept license agreement > login to the appliance’s IP via web browser (login/password –  root/vmware)

3: From withing the web UI of the appliance, connect and push the installation of vCenter web client plugin > Enter SSO user name and password > done

 

image

 

 

 

 

 

 

 

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Could not connect using the requested protocol [PowerCLI]

October 26th, 2015 1 comment

Connecting from workstation with PowerCLI to VMware vCenter 6.0 appliance fails with error:

Could not connect using the requested protocol

image

 

 

 

 

Solution

This issue occurs due to the proxy settings in the environment. To resolve this, check the proxy settings using the PowerCLI and set the proxy to “No Proxy”.

To set the proxy setting to No Proxy:

Run this command to find the current proxy settings:

Get-PowerCLIConfiguration

image

 

 

 

 

 

To change this setting, run this command:

Set-PowerCLIConfiguration -ProxyPolicy NoProxy -Confirm

image

 

 

 

 

 

Result

image

 

 

 

 

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Quick stats on [SERVERNAME] is not up-to-date

June 4th, 2015 No comments

Few weeks ago I upgraded for a customer vCenter Server 5.5. to 6.0, today I received a yellow warning in the Summary tab:

Quick stats on [SERVERNAME] is not up-to-date

image

 

Solution

This is a known issue in vCenter Server 5.5 and 6.0.

  • This issue is resolved in VMware vCenter Server 5.5.0b.
  • Currently there is no resolution for vCenter Server 6.0.

To work around this issue, add these quickStats parameters to the Advanced Settings of vCenter Server:

  • vpxd.quickStats.HostStatsCheck
  • vpxd.quickStats.ConfigIssues

Note: Adding these parameters to vCenter Server does not affect future upgrades.

To add the quickStats parameters to the Advanced Settings of vCenter Server 6.0:

  1. Connect to the vCenter Server using the vSphere Client and administrator credentials.
  2. Select Administration > vCenter Server Settings to display the vCenter Server Settings dialog box.
  3. In the settings list, select Advanced Settings.
  4. Add the following parameters:
  5. vpxd.quickStats.HostStatsCheck = False

    vpxd.quickStats.ConfigIssues = False

      
    image

  6. Restart the vCenter Server services. For more information, see:

    More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Troubleshooting Performance vSphere 4.1 guide

February 18th, 2011 1 comment

VMware VROOM released/updated a nice Performance Troubleshoot guide for vSphere 4.1

The hugely popular Performance Troubleshooting for VMware vSphere 4 guide is now updated for vSphere 4.1 . This document provides step-by-step approach for troubleshooting most common performance problems in vSphere-based virtual environments. The steps discussed in the document use performance data and charts readily available in the vSphere Client and esxtop to aid the troubleshooting flows. Each performance troubleshooting flow has two parts:

  1. How to identify the problem using specific performance counters.
  2. Possible causes of the problem and solutions to solve it.

New sections that were added to the document include troubleshooting performance problems in resource pools on standalone hosts and DRS clusters, additional troubleshooting steps for environments experiencing memory pressure (hosts with compressed and swapped memory), high CPU ready time in hosts that are not CPU saturated, environments sharing resources such as storage and network, and environments using snapshots.

This document by no means covers the entire breadth of performance-related problems. We request the readers of this document, including VMware performance community members and vSphere administrators, to help us enhance this document by letting us know about all the performance problems they encounter in their vSphere-based virtual environments, including those that require elaborate troubleshooting steps.  We hope that the community will actively contribute by engaging in live discussions, providing feedback, and asking questions. All this input will serve as the topics for future updates

[gview file=http://communities.vmware.com/servlet/JiveServlet/downloadBody/14905-102-1-17952/vsphere41-performance-troubleshooting.pdf]

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Console-setup, Configure or Troubleshoot the ESX Service Console

December 2nd, 2010 No comments

Oke.. I didn’t know this feature, last week a colleague consultant shows me a little menu to (re-)configure the ESX service console. With the command “console-setup” you can add or delete some vSwitches, create a new SC and view current configurations.

If you never worked with ESX CLI then will this a nice feature to setup/troubleshoot the SC.

image

The option “Console-setup” is available since ESX 4.0 update 2

Menu structure:

When you console-setup as root from the service console, you are presented with this menu:

1. Show Current Service Consoles

2. Show Network Adapters

3. Show vSwitch/vDS Information

4. Delete Service Console

4.1 Select the interface to delete, defaults to vswif0

5. Configure Service Console

5.1 vswif ID, default to vswif0

5.2 Name of service console port group: default to “Service Console”

5.3 vSwitch for service console, default to vSwitch0

5.4 IP Address:

5.5 Subnet mask:

5.6 Default gateway:

5.7 VLAN ID: default to 0

5.8 vmnic to use for the service console

5.9 Save Changes

5.10 Return to Menu

6. Exit

Use:

  • Options 1,2 and 3 for display current information
  • Option 4 to remove an existing service console interface (vswif). You may also do this, if you want to recreate it.
  • Option 5 to change the configuration of an existing vswif interface, or for creating a new one.

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: How to revert root user role from "Read-only" to "Administrator"

July 24th, 2010 15 comments

Today on the Dutch VMug forum somebody got some trouble to connect a ESX host after changing the “root” permissions from Administrator to Read-only. Nice problem to find a solution, I created the same situation in my test environment.

Situation:

User: Root – Role: Read-Only

image You can’t connect the host anymore with your VI Client..

Solution:

… but you can still login at the console or putty session.. so what to do:

Edit the authorization.xml file: nano /etc/vmware/hostd/authorization.xml

image

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn