kumarnirmal
asked on
Killing a defunct vpx-agent process in VMware ESX Server 3.5.0 build-64607
I am trying to reinstall VirtualCenter Agent in this ESX Host. When I try to start the vmware-vpxa service in the host, I get the error which I have updated below
Log for VMware VirtualCenter Agent, pid=32255, version=2.5.0, build=build-119598, option=Release, section=2
[2009-04-05 12:15:50.865 'App' 3076450208 info] Current working directory: /var/log/vmware/vpx
[2009-04-05 12:15:50.865 'Libs' 3076450208 info] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1.
[2009-04-05 12:15:50.865 'Libs' 3076450208 info] HOSTINFO: numPhysCPUs is 0, bumping to 1.
[2009-04-05 12:15:50.865 'Libs' 3076450208 info] HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 1 logical CPUs.
[2009-04-05 12:15:50.865 'ThreadPool' 3076450208 verbose] Thread info: Min Io, Max Io, Min Task, Max Task, Max Thread, Keepalive, thread kill, max fds: 2, 200, 2, 10, 25, 8, 600, -1
[2009-04-05 12:15:50.866 'App' 3076450208 info] Log path: /var/log/vmware/vpx
[2009-04-05 12:15:50.866 'App' 3076450208 info] Initializing SSL
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] Using system libcrypto, version 90701F
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve FIPS_mode_set: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: FIPS_mode_set
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve FIPS_mode: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: FIPS_mode
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve SHA256: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: SHA256
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve SHA512: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: SHA512
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha224: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: EVP_sha224
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha256: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: EVP_sha256
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha384: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: EVP_sha384
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha512: /opt/vmware/vpxa/vpx/vpxa: undefined symbol: EVP_sha512
[2009-04-05 12:15:50.869 'App' 3076450208 info] Vmacore::InitSSL: doVersionCheck = false, handshakeTimeoutUs = 120000000
[2009-04-05 12:15:50.870 'App' 3076450208 info] Initializing SSL Contexts
[2009-04-05 12:15:50.871 'Libs' 3076450208 warning] Another process is already running for this config file : pid=12781
[2009-04-05 12:15:50.872 'App' 3076450208 error] Failed to initialize authd module functionality. Is vpxa already running?
[2009-04-05 12:15:50.872 'App' 3076450208 error] Failed to do early initialization
The ps -aef commands shows this
root 12781 1 0 2008 ? 02:06:45 [vpxa <defunct>]
root 32542 30611 0 12:25 pts/3 00:00:00 grep vpx
The ESX Host is running Virtual Machines that are very critical.
Please provide a method to restart the vmware-vpxa service without restarting the Host.
Log for VMware VirtualCenter Agent, pid=32255, version=2.5.0, build=build-119598, option=Release, section=2
[2009-04-05 12:15:50.865 'App' 3076450208 info] Current working directory: /var/log/vmware/vpx
[2009-04-05 12:15:50.865 'Libs' 3076450208 info] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1.
[2009-04-05 12:15:50.865 'Libs' 3076450208 info] HOSTINFO: numPhysCPUs is 0, bumping to 1.
[2009-04-05 12:15:50.865 'Libs' 3076450208 info] HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 1 logical CPUs.
[2009-04-05 12:15:50.865 'ThreadPool' 3076450208 verbose] Thread info: Min Io, Max Io, Min Task, Max Task, Max Thread, Keepalive, thread kill, max fds: 2, 200, 2, 10, 25, 8, 600, -1
[2009-04-05 12:15:50.866 'App' 3076450208 info] Log path: /var/log/vmware/vpx
[2009-04-05 12:15:50.866 'App' 3076450208 info] Initializing SSL
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] Using system libcrypto, version 90701F
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve FIPS_mode_set: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve FIPS_mode: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve SHA256: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve SHA512: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha224: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha256: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha384: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.867 'Libs' 3076450208 info] DLSYM: Failed to resolve EVP_sha512: /opt/vmware/vpxa/vpx/vpxa:
[2009-04-05 12:15:50.869 'App' 3076450208 info] Vmacore::InitSSL: doVersionCheck = false, handshakeTimeoutUs = 120000000
[2009-04-05 12:15:50.870 'App' 3076450208 info] Initializing SSL Contexts
[2009-04-05 12:15:50.871 'Libs' 3076450208 warning] Another process is already running for this config file : pid=12781
[2009-04-05 12:15:50.872 'App' 3076450208 error] Failed to initialize authd module functionality. Is vpxa already running?
[2009-04-05 12:15:50.872 'App' 3076450208 error] Failed to do early initialization
The ps -aef commands shows this
root 12781 1 0 2008 ? 02:06:45 [vpxa <defunct>]
root 32542 30611 0 12:25 pts/3 00:00:00 grep vpx
The ESX Host is running Virtual Machines that are very critical.
Please provide a method to restart the vmware-vpxa service without restarting the Host.
Use the PID returned from your ps command to then run this command
kill -9 PID
where -9 mean kill with extreme prejudice (don't know I feel about that though ;-) )
kill -9 PID
where -9 mean kill with extreme prejudice (don't know I feel about that though ;-) )
ASKER
za_mkh,
I have already tried it, it does not kill the process.
I have already tried it, it does not kill the process.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will try to schedule a downtime for the same and will update you accordingly.
ASKER
Unfortunately, the Host cannot be restarted since the VMs are mission critical.
ASKER