Skip to main content

Posts

Showing posts from December, 2019

(resolved) - Panic: Memory exceeds hard limit

Panic: Memory exceeds hard limit Error:   2019-10-29T03:35:29.797Z panic hostd[309C2B70] [Originator@6876 sub=Default] --> --> Panic: Memory exceeds hard limit. Panic --> Backtrace: --> [backtrace begin] product: VMware ESX, version: 6.5.0, build: build-6765664, tag: hostd, cpu: x86, os: esx, buildType: release ---> Fix : NOTE : Put the host in Maintenance mode.  To be on a safe side, Copy the /productLocker/vmtools/ folder and its contents from a working host running the same ESXi version/build and replace them on the affected host. 1. take SSH on one working host and the affected host, let us take esxi0A is working and esxi0B is affected. 2. Login as "root" user 3. scp the /productLocker/vmtools/   folder and contents from the "good" host to the "problem" host $ [esxi0A:~]$ scp -rf /productLocker/vmtools/ esxi0B:/productLocker/ COAUTION: This will overwrite the vmtools  folder on the problem host, hence you could back

(resolved) - Long boot time for ESXi hosts even after marking RDM LUNs as perennially-reserved

Long boot time for ESXi hosts even after marking RDM LUNs as perennially-reserved    Error : 2019-09-17T19:47:44.846Z cpu39:65984)WARNING: celerity16fc: Task management abort failed, status:fffffffd 2019-09-17T19:47:44.849Z cpu21:66065)ScsiDeviceIO: 7916: Could not detect setting of QErr for device naa.600507680c8080dca80000000000058a. Error Timeout. 2019-09-17T19:48:02.959Z cpu28:66342)WARNING: ScsiCore: 1806: Invalid sense buffer: error=0x0, valid=0x0 Reason for the issue: This is due to a known issue with storage stack. Some commands at boot time sense fail with reservation conflicts, timeouts and aborts.   Resolution: At the moment, please try to use vmdk instead of RDM disks and the VMware engineering team looks like they are working on the fix.           

(solved) - Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path

Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path   The reason behind the issue:  The vcdb.properties file does not get automatically updated, when we change from Windows Authentication to SQL authentication. Since migration assistant uses that vcdb.properties file to obtain the database configuration, it fails to connect because it is expecting integrated authentication instead of SQL authentication.    Resolution:   To resolve this issue modify vcdb.properties file. This file can be located in Windows vCenter Server at C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vcdb.properties  and in VCSA at   /etc/vmware-vpx/vcdb.properties .  Now modify the vcdb.properties files as mentioned below from: driver = com.microsoft.sqlserver.jdbc.SQLServerDriver dbtype = mssql url = jdbc:sqlserver://;serverName= Server_Name ;DatabaseName= Database_Name ;instanceName= Instance_Name ;integratedSecurity=True to driver = com.microsoft.sqlser

(resolved) - SLES 12 SP3 & SP4 Menu bar issue

The reason behind the issue : This issue occurs when the GNOME shell is not checking the current resolution that was set during the login screen. The login shows the resolution correctly as does the report from xrandr.   Resolution : To resolve this issue, use one of this options: Open a terminal window, and enter: nohup gnome-shell > /dev/null & This restarts the gnome session and restore the menu bar.   Force the window to resize

Step by step - configure timeout value for span customization deployment

There is a default timeout value, which is 100 seconds, for the customization deployment process. we can configure a larger timeout value in tools.conf to extend the timeout limit of the process. Please notice that this timeout value is the up limit of time cost of the customization deployment process, the actual time cost of that will not be impacted by this value if it does not reach this up limit. Save and exit :)  

Buzz words around VMware

In VMworld’19, Pat has mentioned that Kubernetes is becoming the front and center of the company’s product strategy. Sanjay poonan has declared that using containers in digital transformation is a   “birthright” of VMware. wait wait.! what are these Buzz words? Why are they overused? Because they sound cool? or exciting?  Lets break this down and understand this in detail. Containers :   It’s a method to bundle packages of application and can be isolated with its Network, file system and its processes.   One of the famous container technology is “Docker” Kubernetes : When I have huge number of containers I need someone to manage and orchestrate it, that is achieved thru a technology called “Kubernetes” -> Google’s product which was made opensource. Related to VMware: Project pacific : VMware is Embedding Kubernetes right into the core of vSphere. This will enable developers and IT operators to build and manage apps comprised of containers and/or virt