Hi Devnetters -
This is my 2nd attempt trying the 6.0 > 6.1 upgrade on my Solaris dev machine. I'm trying to get 2 results from this upgrade: 1) to get the machine up to the current release and 2) to gain some experience in preparation for a production upgrade.
I've had the same result 2 times with this upgrade. After what seems like a problem-free upgrade and subsequent reboot, I get the following error in the iwserver.log file:
ERROR: Failed to start Interwoven Web Daemon.
197 of /interwoven/iw-home/iw-webd/conf/httpd.conf:
Cannot load /interwoven/iw-home/iw-webd/libexec/mod_fastcgi.so into server: ld.so.1: /interwoven/iw-home/iw-webd/bin/iwwebd: fatal: /interwoven/iw-home
/iw-webd/libexec/mod_fastcgi.so: open failed: No such file or directory
As the error says, mod_fastcgi.so does not exist in that (or any other) directory. The directory exists, but not the file.
At this point, I removed TeamSite from the machine altogether and reinstalled from scratch. This worked and I didn't have the problem. Being a glutton for punishment, I restored the machine to its previous 6.0 state, made absolutely sure that I followed all of the upgrade instructions correctly and came up with the same results. I'm now trying to find out if there is an issue with my machine & its configuration, or with the upgrade process.
If it's an issue with the upgrade process, I may have to modify my plans for the production upgrade.
Support article 50400 (
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=50400) describes the function of FastCTGI:
Content Services 2.0 uses FastCGI (mod_fastcgi) as an Apache plugin to route SOAP messages to the SOAP server library. Additional information about FastCGI can be found at:
http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html. CSSDK 2.0 uses the Systinet WASP-CPP libraries for the FastCGI integration with our libraries. The fcgiwaspc.exe (on Windows) and fcgiwaspc (on Solaris) is automatically spawned as a child of the iwwebd process when iwwebd is started. In order to see this directive, look at the <iw-home>/iw-webd/conf/httpd.conf file and search for the FastCgiServer keyword.
Here come my questions:
- have any of you experienced this problem?
- is anyone out there familiar enough with how FastCGI is installed with TeamSite to know how the mod_fastcgi.so service object is created during installation? I believe it's created on the fly and not copied in from the install media. (BTW, the directory in which it is supposed to reside is wide open, permission-wise). Is it possible to run that portion of the installation manually?
- in lieu of running the installation manually, would anyone care to share their copy of mod_fastcgi.so from a 6.1 installation that I could see if that's the only issue keeping 6.1 from running?
BTW, I'm also working with Support on this problem - but it never hurts to appeal to one's peers!
Thanks for any advice,
Wally Box
Nike, Inc.
