Our customer observed that the convertd server process (/opt/zimbra/java/bin/java com.zimbra.cs.convertd.TransformationServer)
is consuming a lot of CPU from this morning.
It consumes 90% of CPU so far.
We know restarting mailboxd is a workaround for this case, however our customer
want to minimize the impact to their service.
I believe we can triage by restarting the convertd process,
does anyone know how to restart it?
Zimbra Admin Guide describes that "zmconvertctl restart" can do this, on the other hand,
it seems zmconvertdmon script calls /opt/zimbra/libexec/zmconvertd instead.
If we can restart the convertd server, what is the expected impact to the service?
We think ZCS can't index the attachments and users can't view attahcments as html
while restarting. Am I right about that?
We've tried to kill the stuck kvoop processes, but those process become "defunct" and the convertd still consumes much CPU.
ZCS NE 5.0.16 multi-server installation with convertd v1
RHEL 5 64bit