Log rotation in Teamsite 7.2.1

Guys,

Can anyone please guide me in stopping the TS log rotation.

When I am trying the same from Admin Console it is giving an error.

Which log should be monitored in this case, I checked server.log, iwserver.log, iwtrace.log etc but could not find anything significant.

OR

Is there a way we can control this through any command or file.

I found a log config file under /conf but that did not seem to contain log rotation factor.

Any advice here is much appreciated!!

Cheers

Find more posts tagged with

Comments

Adam Stoller

Why would you want to *stop* log rotation?

If you're having problems doing it through the Admin UI - you might need to restart jboss (I've seen the Admin UI get messed up in a number of ways that tend to get fixed by restarting jboss)

Garth McMillan

I agree with ghoti, stopping log rotation is probably not a great idea.

If you want to alter the logging details alter the various log4j.xml files. They may be located in the ApplicationContainer folder depending on what log files you want to alter.

Generally you probably want to copy any files to the relevant location within the customer_src or livesite_customer_src folders and use make_toolkit.ipl or build.bat to overwrite the default versions in the ApplicationContainer folder.

Kallu

Basically my requirement is to do a monthly archival of the TS logs viz iwevents.log,iwtrace.log etc.

Any advice, as how can I achieve this?

Adam Stoller

Basically my requirement is to do a monthly archival of the TS logs viz iwevents.log,iwtrace.log etc.

Any advice, as how can I achieve this?

Some of the log files can be controlled via the "internal" (log4j) rotation scheme - which you can control via the Admin UI - and it does allow you to set it to rotate at the end of the month as opposed to on a size basis.

Other log are, to the best of my knowledge, still tied to processes that keep them open (e.g.: iwserver) - and cannot be rotated without actually stopping and re-starting the processes. For these, generally one creates a script that stops the services, performs whatever desired log rotation you want, and then restarts the processes.

Unfortunately, at least in the Windows environment, sometimes this doesn't work that well - and you end up having to go through the Services panel to stop the services rather than being able to do it via a script front-end (this might be due to a 64-bit OS vs. 32-bit version of Perl -- not sure)

Kallu

Thank you for your reply.

Since my primary requirement is to stop the rotation scheme for iwevents.log, could you please guide me as how can I do this?

Regards,

Adam Stoller

Thank you for your reply.

Since my primary requirement is to stop the rotation scheme for iwevents.log, could you please guide me as how can I do this?

Regards,

Admin UI: Logs: Select "iwevents.log", click on Logging Rotation which brings up a dialog box in which you adjust (or cancel) the logging rotation schedule.

Kallu

Yes, I am aware of that option but whenever i choose Do not rotate logs, it throws an error saying "Rotation policy could not be saved for iwevents.log"

There is one cfg file which contains some info about the iwevents.log (/conf/log4CPlus_iwserver.cfg)

but I am not sure what attribute I can change in this to fix the logging as "Do not rotate"

Adam Stoller

Yes, I am aware of that option but whenever i choose Do not rotate logs, it throws an error saying "Rotation policy could not be saved for iwevents.log"

There is one cfg file which contains some info about the iwevents.log (/conf/log4CPlus_iwserver.cfg)

but I am not sure what attribute I can change in this to fix the logging as "Do not rotate"

Have you restarted jboss like I suggested initially?
Usually problems with the Admin UI are fixed by doing so.
Also - check for any log files (within IWHOME and ApplicationContainer directory trees) that get updated when you receive that error in the UI - because there's often a chance that a more informative message might have made it into a log file.
Lastly - if the error message is justified (i.e.: not a problem with jboss) - it sounds like it could be a permissions issue on one of the various log4j.xml files - which I believe is what is used for managing the log files

Kallu

Hi Ghoti,

I did try to restart the JBoss but still had no luck to resolved this.

I finally consulted Autonomy Support and as per their record this is filed as a defect in 7.2.1.

Thanks Smiley Happy