We’ll I’m not entirely sure that it “Hates” me. Perhaps that is too strong a word. Trolling around my VI today, I found a host that had it something spinning out of control:
[root@hyp1 root]# top
10:50:35 up 12 days, 1:08, 1 user, load average: 2.00, 1.98, 1.92
306 processes: 297 sleeping, 9 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 52.0% 0.0% 48.0% 0.0% 0.0% 0.0% 0.0%
Mem: 510720k av, 413604k used, 97116k free, 0k shrd, 69936k buff
359172k actv, 13356k in_d, 72k in_c
Swap: 1052216k av, 0k used, 1052216k free 90460k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
30367 root 25 0 6968 6968 2528 R 99.0 1.3 0:31 0 ftPerl
Shit, ftPerl, what is that?
[root@hyp1 /]# find / -name “ftPerl*” -type f
[root@hyp1 bin]# file ftPerl
ftPerl: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped
Looks like it belongs to the HA suite, and is some sort of executable. The initial workaround from the VMware communities, was to “Reconfigure for HA”. This worked, but only temporarily.
As with all good problems, this was resolved through the application of a larger bat. We eventually rebuilt the cluster.
Note: After a discussion with VMware support. There may be a fix for this forthcoming.