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

Failing of deployment

Nitin_B

Hi,

We are working on Teamsite 6.5.The deployment fails once the deployment log size reached 5 MB.

Can anyone please let me know what should be the ideal behavior for this, like should this happen that the log file should empty itself once it reaches its limit (5MB in our case) and again start writing in the same file.

Or should it be that once the log file reaches its limit, it should be renamed and a new log file is made and logs are witten in that.

Regards

Find more posts tagged with

Comments

Adam Stoller

Hi,

We are working on Teamsite 6.5.The deployment fails once the deployment log size reached 5 MB.

Can anyone please let me know what should be the ideal behavior for this, like should this happen that the log file should empty itself once it reaches its limit (5MB in our case) and again start writing in the same file.

Or should it be that once the log file reaches its limit, it should be renamed and a new log file is made and logs are witten in that.

Regards

The version of OpenDeploy (not TeamSite) is what is important here - and the platform on which it is being run.

I believe this is probably a Windows installation - as I recall that was where this problem occurred - and I think it was in OD 6.0x (possibly 6.1.0) - in which case you should be looking on the support site for patches, service packs or upgrades (e.g.: 6.1.1) as I believe this bug was fixed.

Nitin_B

Thanks but what is the ideal behavior. Is it that teh logs are emptied or is it that these are renamed and the nnew logs are written in a new file.

Adam Stoller

Thanks but what is the ideal behavior. Is it that teh logs are emptied or is it that these are renamed and the nnew logs are written in a new file.

The logs are supposed to be rotated such that when the current log reaches its threshold, it gets renamed to log.001 and a new log file is created, when that fills up it becomes log.002, and so on - until you reach log.999 at which point it's supposed to start overwriting log.001, etc.