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

Reason to NOT delete/rotate D:\Interwoven\OpenDeployNG\log?

SethHickel

So - My memory is not so good today ...

Simply speaking, my log rotation consists of using RoboCopy to /mov files to a compressed folder and delete the oldest of seven instances of my compressed log collections. The /mov command copies the files and then deletes them from the source.

If I do this daily are there issues with killing the

\Interwoven\OpenDeployNG\log log files? I don't think so since these are simply log files written when OD pushes files.

For some reason I did not include this in my original log file rotation and I am trying to remember if I had a reason or not: thus the post.

Thanks.

Find more posts tagged with

Comments

Adam Stoller

You might want to avoid replacing the odbase log file - as that may be held open by the OD server process. The individual src.* and rcv.* files (if older than 30 minutes [arbitrary number]) should be movable without any issues.
Note: OpenDeploy rotates its logs for you - and you can configure how big to let them grow and how many to keep - the only thing your script should be doing is managing *.log.[0-9]* files - as those have already been rotated, you should leave all files that end in .log (with no additional numerical extension) alone.

SethHickel

Actually - I stop all Autonomy and OD services before starting this process. So if that is the only issue - contention for the files - it sounds like I am OK - agree?

CustomSchedulerSchema.png

Satish_Jadhav

Actually - I stop all Autonomy and OD services before starting this process. So if that is the only issue - contention for the files - it sounds like I am OK - agree?

If you are stopping all services before starting should be fine. As quoted by Ghoti, the files might be open by service. So stopping the services will rule out the possibility.

Its recommended to stop service , before rotating any IW log files.

Regards,
SatishKumar T Jadhav

interDev

Actually - I stop all Autonomy and OD services before starting this process. So if that is the only issue - contention for the files - it sounds like I am OK - agree?

You can do it by stopping OD services only. Other services dont need to be stopped for rotating OD logs..

Adam Stoller

You can do it by stopping OD services only. Other services dont need to be stopped for rotating OD logs..

True - but again - OD handles log rotation by itself. You should only need to deal with archiving (if desired) and/or removal of old (already rotated) log files for OD.

SortCrosstabByDateInParameter.rptdesign

SethHickel

Do all versions of OD handle log rotation?

nipper

Do all versions of OD handle log rotation?

6.X plus. Though I do remember some bugs in the early 6.0/6.1 versions of log rotation.