nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwtmplpreview.cgi loop

diago

Hello
zombie processes iwtmlprieview are still alive when IHM is killed by user
theses use large amount of CPU

how to identify the zombie from the real one ?
how to kill them properly ?

regards
eric grandjean

Find more posts tagged with

Comments

Migrateduser

Interwoven Support is currently tracking an issue that sounds similar to this on TS5.5.2.

If you have not already done so, please open a support case regarding this problem (please state when opening the case that you believe that it is related to bug 36327). If you are on solaris you may want to try running truss on the iwtmplpreview.cgi process that you think is zombied.

ps -ef|grep iwtmplpreview.cgi

and then

truss -f -p <pid from the ps output>

You can redirect this to a file and send the output to support (which may help in determining the cause of the problem).

diago

the command line truss -f -p on this process produces no output ...
The process has been alive for 66 hours.
It take 100 % of the CPU and does nothing ?

Migrateduser

What is the command line that you used? If I wanted to run truss on say iw-webd and I had the following from ps output:

root 14548 1 0 Dec 13 ? 0:01 /usr/iw-home/iw-webd/bin/iwwebd -DUNIX -d /usr/iw-home/iw-webd -DSSL

Then the truss command I would run would be:

truss -f -p 14548 > truss_out_12192002.txt 2>&1

The reason why I think there is something wrong is that if a process is taking up 100% of the cpu it has to at least have some output of some sort (even if it is just a loop).