Logging Rotation not working in Teamsite 7.1.0

Hi All,

When I set the rotation policy to ” beginning of each week” for access.log and error.log [color=#1f497d]and click on Save button I get a pop up message saying Saved successfully.[color=#1f497d]But this actually is not happening and the rotation policy is getting set to "None".[/color]

[/color]
[color=#1f497d][color=#1f497d][color=#1f497d][size=3]And also for some other logs like iwtrace.log, although the teamsite allows us to enter any value for Keep Most Recent rotated logs these values are getting reset to default values after the Save.
[/color][/color][/size][/color]

Find more posts tagged with

Comments

bagman

Did you get any resolution on this? I am having the same issue with the error.log and access.log and cannot change the value for iwserver.log.

Thanks,
Mark

MadhanKumar

This is a defect.

Adam Stoller

This is a defect.

Are you saying this is officially logged as a defect with Autonomy or that you consider this to be a defect personally?

If the former - do you have any more information about it - like defect number, expected fix delivery (patch, service pack, release), etc.?

bagman

KB Article #61411 describes a workaround for rotating the access and error logs:

Rotating the Web Daemon Access Log

This article describes a method to enable automatic rotation of the access log for the TeamSite web daemon.

The Apache web daemon that is integrated with TeamSite logs all calls to the UI in the access.log file, which can cause it to grow to a very large size. This may have some impact on UI performance over time as Apache tries to read the whole file into memory. The access log can be managed as part of the normal log rotation by stopping the web daemon, renaming the file, and then restarting the web daemon.

However, there is another way to rotate this log without the necessity of having to stop and restart the web daemon by using piped logging. Apache includes a small program within the /bin folder called rotatelogs that will do this automatically after a set amount of time.

See http://httpd.apache.org/docs/2.0/logs.html#accesslog for more information on this.

The procedure to make this change in the TeamSite web daemon is as follows:

For TeamSite 6.5 and earlier, locate the file iw-home/iw-webd/conf/httpd.conf.template. For TeamSite 6.7.x, the file is iw-home/iw-webd/conf/iwwebd.conf.template. Make a backup copy of this file for restore purposes.

Open the file and locate the line:

CustomLog "__IWWEBD_LOGS__/access__IWLOG_EXT__" common

Edit this line to read:

CustomLog "| path_to_iwhome/iw-webd/bin/rotatelogs __IWWEBD_LOGS__/access__IWLOG_EXT__ 86400" common

The first part is a pipe redirect to the fully qualified path to the rotatelogs utility, followed by the path to the default location for the access log. Leave the value that is already defined here. The last attribute is the amount of time in seconds that the log is active before being rotated. For example, 86400 equates to 24 hours. The edited string needs to be enclosed in quotes as above and there must be spaces between the values. You can specify a different log file name or append a date value to the file name for easier reference as in:

access__IWLOG_EXT__.%Y%m%d

After making the changes, run iwreset –ui to enable the new settings.

Special note for TeamSite 6.7.1 and above on Windows:

For TeamSite 6.7.1 and above, the path to rotatelogs must be a literal path starting from /iw-webd and the .exe extension must be added to rotatelogs. Therefore, the entry for a Windows server running TeamSite 6.7.1 is:

CustomLog "| bin/rotatelogs.exe __IWWEBD_LOGS__/access__IWLOG_EXT__ 86400" common

Do NOT put a leading ‘/’ in front of ‘bin’.

When I tried to do this, TeamSite hung because of a missing library I guess the "rotatelogs" process needed. I have not had time to go any further with it.

Mark