log files

Has anyone come up with any utilities or other mechanisms to aid TS customers in trimming all the IWOV log files (e.g., iwevents.log, iwserver.log, access.log, error.log, etc.)?

Find more posts tagged with

Comments

Adam Stoller

At this point it generally involves creating a script to periodically run [e.g. via cron] that:

stops the TeamSite processes
- this includes things like iwserver, iwwebd, reporting and GRC processes, etc.
rotates the logs (renames this with a date or number prefix or suffix)
restarts the TeamSite processes
- On Windows this means rebooting the server - I believe there is a reboot.exe in the NT 4.0 Options Pack (or something like that?)
- On Windows you can restart the processes using the standard /etc/init.d/... scripts

The contents of the script are pretty straight forward.
The writing of the script is pretty straight forward.
The testing of the script is very important though because sometimes the environment that this is running in is not that straight forward.

Hope that helps,

--fish
(Interwoven, Curriculum Development)

Migrateduser

This approach makes a lot of sense for single server installations, how would you suggest implementing it in a Windows 2000 Adv Server Cluster environment?

I could write a script that runs on both nodes on a periodic basis to archive the logs, but I can only successfuly accomplish this on the inactive node, since I can't just be stopping services (the cluster would failover).

Any thoughts?