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; } } }

iw_cgi_wrapper error

Icebreaker

Hi There,

All my workflows are working fine until this morning.

Now when I try start of my workflow I am hit with the following error:

TeamSite: Wrapper
Error: Installation problem: "iw_cgi_wrapper.cgi" needs to be run as root.

We did not perform any installation on our server. We ar running on TS 6.5 SP3

Any help is highly appreciated.

Regards,

Find more posts tagged with

Comments

ISCBorisB

ls -al /iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi

What does it show?

Icebreaker

Here is the result..

bash-2.03# ls -al /app/iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi
-rwxrwxrwx 1 root daemon 3690180 Feb 11 2007 /app/iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi
bash-2.03#

nipper

It should have the setuid flag on it.

Did this ever work ?

I have seen companies that have a process that removed the setuid root flag from files. It usually runs automatically and they never tell anyone. If it did work & then stopped, talk to one of your admins.

Andy

ISCBorisB

Here is the result..

bash-2.03# ls -al /app/iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi
-rwxrwxrwx 1 root daemon 3690180 Feb 11 2007 /app/iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi
bash-2.03#

Must be -rwsrwxr-x !

Log as root ( I do not think sudo will work ) and
chmod 5775 /app/iw-home/httpd/iw-bin/iw_cgi_wrapper.cgi

Icebreaker

The CGI Wrapper is working fine until this morning with the setuid flag.

I am not sure if this is a mandatory change. I will check with my admin on this. Thanks anyway for your help.

Regards,

ISCBorisB

The CGI Wrapper is working fine until this morning with the setuid flag.

I am not sure if this is a mandatory change. I will check with my admin on this. Thanks anyway for your help.

Regards,

Mandatory or not, iw_cgi_wrapper won't work without setuid root flag. And if it ever did work - the flag was there all right.

aby_sam

We had almost similar issue in the past and setting sticky bit to iw_cgi_wrapper.cgi, iwwft_instantiator.cgi made it work.
Also some of the workflow jobs were found to be failing if sticky bit is not set on iwjobc. (try chmod u+s /opt/interwoven/iw-home/bin/iwjobc)

Icebreaker

Thanks Guys,

After applying the sticky bit for the root on wrapper cgi, the Wfs are working properly.

Thanks again.

nipper

It would be a very good idea to find out WHY it was removed. Because it may happen again. Also there are multiple files that are setuid, you should get a list form support and see if they were all modified or only cgi_wrapper.