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

Problem with start Teamsite 6.5.1

squint

Hi,

We are having an issue with starting our Teamsite server...
ERROR: Failed to start Interwoven Web Daemon.
2006] [warn] module mod_fastcgi.c is already added, skipping
/u02/apps/Interwoven/Teamsite/iw-webd/bin/iw.webd start: iwwebd could not be started

This somehow started happening yesterday. We restart the server every night and this problem appeared after the restart. I dont think anything was changed in Teamsite so I am not sure how this happening. Could anyone shed any light on this issue? I tried to contact Interwoven support but it just goes to voicemail

Thanks

Find more posts tagged with

Comments

jkm

first thing why do you restart the TS server everyday like windows desktop Smiley Happy

which platform solaris/windows/patch level ?

This problem can happen because of various reasons ....like size of log files, permission of log files, port is occupied by some other service blah blah... best bet to resolve this try to run the iwreset -ui command, if doesnt work then stop all the TS processes and then restart the services one by one and
post the error messages from iwserver.log,iwtrace and servletd.log files so that people can give better pointers

Nicholas

Rebooting machine once could help.

Thanks Nicholas

Adam Stoller

first thing why do you restart the TS server everyday like windows desktop

One reason would be for backups - and that's certainly a valid reason.

which platform solaris/windows/patch level ?

Judging from the initial post:

...
/u02/apps/Interwoven/Teamsite/iw-webd/bin/iw.webd start: iwwebd could not be started

I think it's a safe bet that this is not Windows - it's most likely Solaris.

... post the error messages from iwserver.log,iwtrace and servletd.log files so that people can give better pointers

that and/or contact Interwoven Support (if you're having server problems, you really should contact Support)

jkm

One reason would be for backups - and that's certainly a valid reason.

Do we need to stop the TS for the back ups Adam...why cant we freeze the store and take the backup ?

Adam Stoller

Do we need to stop the TS for the back ups Adam...why cant we freeze the store and take the backup ?

You can do either - but some folks prefer to take it down completely. Among other things this allows you to do a thorough rotation of the log files - it will also let you know fairly quickly if your license expired ;-)

jkm

really not very safe stopping the TS server for content backups ...if someone stops the TS servers to take the backups then they are defeating the purpose of iwfreeze command Smiley Happy

There can be some particular scenarios depending upon the complex infrastructure set up but cant think much at the moment

Adam Stoller

really not very safe stopping the TS server for content backups ...if someone stops the TS servers to take the backups then they are defeating the purpose of iwfreeze command
There can be some particular scenarios depending upon the complex infrastructure set up but cant think much at the moment

This was true for Windows up to about 4.x, and was essentially fixed in 5.x
Unix has never (to my knowledge) had a problem with stopping the server and restarting it.

It's not a question of defeating the purpose of iwfreeze - iwfreeze exists as a means of freezing the backing store for a variety of reasons - including for doing backups - but iwfreeze doesn't remove the locks held on the log files - and until TS does a better job of log file rotation on its own, you either have to do something cruddy (copy and then overwrite the log file with nul [windows] or /dev/null [unix]) - or take the services down completely, rotate the logs and then either restart the services or, if absolutely necessary, reboot the server (last resort in general)

jkm

Unix has never (to my knowledge) had a problem with stopping the server and restarting it.

I really had bad experiences to do this exercise. In my previous projects TS 6.1 + solaris, we had bunch of issues where web daemon was not coming up because of few reasons i listed above...it crash sometime depending upon the load on the TS

If this is a production env of an enterprise scale application then you always require a huge explanation for stopping the prodcution server.

I am aware the other uses of iwfreeze but backing up the server is primary use of this command.

but iwfreeze doesn't remove the locks held on the log files

this is clean up of log files and not back up of TS....definitely there needs to be a better mechanism to rotate the log files in TS but still if we can redirect the log files on a different mount point then this can be avoided or I would say it will not be required so frequent.

I would again defer Ghoti on rebooting the machine...People defintely need long explanations why do you need to reboot the machine...what are the things TS can not handle without rebooting the machine ...a big question mark.....probably in our environment yes it defintely requires

cheers!
-rocky