ftPerl and ftAgent

[tohmeiphun]

What the heck are the ftPerl process and ftAgent process? I've got two servers which have them consuming a fair amount of resources and another two server which don't.

thanks,

-tom

[ivoryt]

hi, I just finished troubleshooting ESX 3.01. The host went "disconnected" in VC and although the VM's kept running I could not connect. I could ssh into the box and ran top which showed ftperl chewing up 99% CPU. I killed it and everything returned to normal. Fperl and ftagent appear in top on all hosts but at a very low cpu. I cannot find any references to them and would like to know their purpose.purpose.

[Radler]

Hi, I had the same problem yesterday. One of the ESX-hosts in VC on state "Red / not responding". ftPerl was taking 50% of the ESX ServiceConsoles Memory. /var/log/messages showing several "out of memory" and "segmentation fault" entries. After a while looking for logs and trying to find a solution... I found this thread

So at last I killed the ftPerl process.

... then "disconnect" the ESX-host in VC (tooks 50 minutes). After that "connect" (tooks 35 minutes). The "configuring HA" task ran automatically after that. Now, everything looks fine, except the ftPerl process which wasn't restartet on the ESX-host.

Has anyone found more information about the LGTOaam processes especially the ftPerl? Do we really need it?

Regards, Martin

[DonalB]

have come across this on a couple of 3.01 hosts and it seems to happen quite a bit (every 3-4 weeks), restart mgmt-vmware and reconfiguring for HA usually sorts out the disconnect. Seems to be a memory leak in some HA agent components. Still haven't patched these boxes up to latest levels but expect that to fix it.

HTH

DB

[Grizzled_1]

I have FTAGENT consumming 99-100% via the console as well. Did anyone ever find out what the pupose is? I killed it too, but am wondering what I just killed.

[jdvcp]

Did patching your ESX 3.0.1 hosts resolve this? We are on 3.0.1 with patches only up to May 2007 (I know this is bad...) and have ftperl and/or ftagent swallowing up all of our SC mem, even if set to 800 MB. thx

[ekos]

For me reconfiguring HA on the affected host was the solution -

---

> http://communities.vmware.com/message/1196783

[depping]

ft = VMware HA.

Duncan

VMware Communities User Moderator

-

---

Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[cody_bunch]

I've found reconfiguring HA only holds this off a few days, and rather I have to rebuild the cluster: http://professionalvmware.com/2009/05/27/ftperl-hates-me/

-Cody Bunch

vExpert, VCP VI3

http://professionalvmware.com