Manual Log Rotation

Hello,
I am trying to figure out how to go about doing log rotation in my production
environment. The requirements are that I send a daily logfile over to a centralized
server each night around midnight. There are three options that I would think
possible:
1) Shutdown the instance and manually rotate the logs with a script.
2) Setup by TIME log rotation
3) Figure out which mbean is responsible for log rotation and access it directly.
Ok, #1 is out of the question. #2 doesn't work because it's relative to the boot
time of the instance. #3 is what I really would like to do, has anyone done this?
Or doesn't anyone have any ideas of how I could do it?
Thanks!
Brett Bajcsi

Did you use the logrot script or the web gui?
The scheduler is activated?

Similar Messages

Agent log rotation

Agent - Sunone Agent 2.1
Webserver - IIS
Policy Server - IS 6.0 SP1.
How do you get the agent log to rotate on size/time? Is there a parameter?
Currently we have to manually delete it.

Log rotation feature available in 2.2 web agents. You need to find other ways to do it.
-Subba

IPlanet 4.1 Web Server - ns-cron process hangs for log rotation

Does anybody know if there is a known issue with iPlanet 4.1 Web Server where the ns-cron log rotation process hangs up?
Basically it won't rotate any logs, and using either the "Stop" or "Restart" buttons in the console won't shut it down, so you have to kill it manually, then start it again.
It seems like it will run for a couple days fine, then it will hang up.
Thanks.

Nope, I've not seen this before. But 4.1 version is really old and no longer supported, you should consider upgrading to a supported version.

LMS3.2 log rotation (syslog_info)

Hi,
What should I do to get my syslog_info file rotated whenver the file grows to 512 megabytes in size? I've set up the log rotation in Common Services->Server->Admin but it doesn't seem to work, the file grew to 1.9 gigabytes.
Is there any process that should be running that monitors the logrotation?
Greets,
Tomek

Restarting dmgtd is not an option and most probably it would not work for that case.
I would like to see if any overgrown log file will rotate. For example - I set max log file size to 512 megabytes. And I expect that LMS will somehow monitor the size of the file (for example with an entry in crontab, or by a specified daemon) and rotate it whenver the log file exceeds previously set size.
That doesn't work that way. The file grows and exceeds set size. Only manual triggering of rotation process works as expected.
Is that a bug?

Log Rotation

Hi,
We are monitoring our logs with several scripts, however we are finding inconsistency with the time of new logs created like access and error. We would like to have it created a new file everyday at 12:01 AM and should end at 11:59 PM.
Please let me know if someone knows how to do it with some DS Settings.
Thanks, John.

These are the links to the official docs for 5.x:
http://download.oracle.com/docs/cd/E19341-01/817-5221/logs.html
From this manual you see that the only way to rotate by hand the log files is:
1) Stop the Directory Server instance
2) rename current access/error/audit log files
3) Restart Directory Server instance
In that case the DS will create a new access/error/audit log file.
Moreover from:
http://download.oracle.com/docs/cd/E19341-01/817-5235/config.html#wp21217
We see that in 5.x version the attribute nsslapd-accesslog-logrotationtime has a different syntax (single integer value) compared to what it has in 6.x and later releases, that doesn't allow to specify you the exact time to rotate the log files. It will simply rotate after the amount of units expressed by the nsslapd-accesslog-logrotationtimeunit attribute.
Given that we could mix a bit of both, and set a rotation policy from the Administration Console of the Directory Server Instance->Configuration Tab->Logs:
- Check the box Unlimited size
- Create new log every: *1 Day(s)*
- Click Save
A pop-up box will inform you that:
You have set an unlimited size for the log files. Note that this can be dangerous as it can cause problems to your system if the size of the logs is very big. Do you want to continue?
You can acknowledge this message and click Yes
This should create a policy to rotate the access log file every 1 day ( = 23h59m59s after last log rotation) regardless of log size. The only advice I have with these settings is that you've to carefully monitor also the filesystem occupation, or set a proper deletion policy.
Last step is then to sync the log time rotation, you have to 'manually' perform a rotation at midnight
HTH,
marco

LDAP Log Rotation

Does anybody know how to change the time of the log rotation for access and error logs. Currently, the logs rotate at 12:50 in the afternoon. I would like to change that. I have looked at the admin console and documentation and there is nothing on changing the time. You can change the size and interval. I assume that it does it at 12:50 because that's when the database was created.

The time (12:50) is the time you started the server. Unfortunately, iDS will only rotate your logs on this time. One solution is to start your server on another time. Another solution is to manually rotate your logs using a script. But, you need to shutdown your server to manually rotate logfiles.

GC log rotation question

Hi,
So after JDK 1.6.0_34 (as far as I know), java introduced GC log rotation JVM args (see below)
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1M
Prior to these JVM arg additions, on any java application start, your GC log would get wiped. In my case a tomcat server running java code.
So now I would assume when these JVM arg's are present, the GC log continues to rotate and not get wiped on application start up. However the above behavior still persists ever after JDK 1.6.0_34 with the new JVM args present.
I should mention while the java application is running, the GC log DOES rotate (i.e., gc_log.txt.0, becomes gc_log.txt.1), but when application is restarted the LAST GC log is erased completely.
This behavior isn't really "log rotation/backup", I've had to introduce my own shell/bat scripts to rotate the latest GC logs manually outside of these JVMargs. I'm not sure if I'm misunderstanding how to use the new JVM args or if oracle doesn't consider this a bug and this is normal behavior.
I did file a bug on this, 9005051. However there is no guarantee your bug request ever makes it to the public bug database and oracle doesn't provide reasoning back to the submitter when the bug is rejected or not looked at, so I don't really know what happened with my bug request.
If anyone has any insight into this, I would really appreciate it.
Thank you!

> Or better yet, where I can find someone to actually answer my question?
Me! Me! I know the answer to that question...
Oracle is more than happy for you to pay them for a support\service contract of which part of that will be that you can ask them questions and they will answer them. Real Oracle engineers and perhaps the very people who created the code in the first place. Or at least the ones in charge of it now.
> yet there is no guarantee my bug is even a bug or will even get posted to the bug database
Yes that is true.
But I suspect, strongly, that if you have a big enough contract that every bug you post to the database, and that you tell oracle about, will appear promptly and be addressed promptly.
And if you have a smaller (but not really small) Oracle contract I am rather certain that you can obtain a custom fix.
Alternatively you can download the source, figure out the problem, and fix it yourself. Then apply it to your running services.

Apache log rotation

From the documentation here: http://help.adobe.com/en_US/adobemediaserver/configadmin/WS5b3ccc516d4fbf351e63e3d119f2926 0bd-7ffa.2.3.html is is stated that " Adobe Media Server handles log rotation for the Apache logs." However, it appears not to be the case.
My logs in /opt/adobe/ams/Apache/logs are not rotating.
Can you help with this? Does AMS handle this or will I need to manually logrotate?
Regards,
A

So this isn't working?:
1. "One option is to rotate log files, moving or deleting the oldest files."
I usually rename the old log files whenever/before the server needs to be restarted and that forces the server to generate new log files.
2. "Use the rotation element in the Logger.xml file to specify a rotation schedule for log files. Two types of rotation schedules can be established. The first option is to set a daily rotation at a certain time. For example, setting daily at 00:00 rotates files every 24 hours at midnight. Alternatively, set a rotation that occurs when the log exceeds a specified length. Name, maximum file size in kilobytes, and maximum number of log files to keep can also be customized using the
rotation element. For an example, see the Logger.xml file installed in the /conf directory."
Did you modify the Logger.xml file to change the log rotation time? Save a copy of the original file before you modify it.
3. You can also try to use a third party module (this might/might not work for you depending on your system specs): http://www.sitebuddy.com/mod_log_rotate
mod_log_rotate.so seems pretty simple to set-up and implement.

Is there a way to identify manual log switches?

Hi!
A while ago I upgraded a 10g database to 11.2.0.2 64 Bit Windows.
During the Upgrade we realized that redo logs were configured really small (~10MB) what resulted in a lot of log switches (a few hundred per day). So we adjusted redo log size to 100MB and set archive_lag_target to 1800.
The amount of log switches went down a little but less far than we expected it. After further analysing the situation we recognized that Oracle is switching logs far before reaching the 100MB log size (and also far before reaching 1800s). All the archived logs have a size of about 15MB. I know that 11g invented something like "preemptive log switching" that switches logs round about 20% before reaching the maximum value (if I remember it correctly..). But switching already at 15% of the maximum size seems strange to me...
I couldn't find any helpful stuff on Google or Metalink about that topic but today I had a different idea: what if it's the application software that's doing manual log switches?
(I have no idea why it should do that but I can remember that the application user does require the sysdba privilege - don't ask me why, I didn't write it, I won't defend it...)
So I checked the alert log but unfortunately I had to realize that there is no difference between an automatic switch and a manual one (only alter system archive log... does get an extra line).
So my questions are:
1) Does anybody know a way of distinguishing between an automatic log switch and a manual one? Is there a table or another logfile where this information is recorded?
2) Has anybody experienced a similar situation where Oracle is switching the logs way before reaching the maximum size?
Best regards,
Marcus

lebigmac wrote:
1) Does anybody know a way of distinguishing between an automatic log switch and a manual one? Is there a table or another logfile where this information is recorded?
Off the top of my head - I think the only way to do a manual log switch is to issue "alter system switch log file", and I think that any "alter system" command is written to the alter log in you version of Oracle. (I really ought to check both statements before posting this, but I've been up since 2:30 am).
2) Has anybody experienced a similar situation where Oracle is switching the logs way before reaching the maximum size?
It's very common with recent versions of Oracle when private redo threads come into play; but your example seems a little exaggerated. The log file switch has to start when there is enough space left in the log file for all the public and all (or maybe it's the previously used - i'll have to check my book) private redo threads. You could check x$kcrfstrand to see what this sizes look like: http://jonathanlewis.wordpress.com/?s=private+thread
Regards
Jonathan Lewis

Regarding internal daemon log rotation...

I found a problem with internal daemon log rotation in iplanet webserver.it is not happening properly..........how to troble shoot this issue?

Web Server 6.0 is EOSLed. Please move to the newer Web Servers 6.1 or 7.0. Check [http://www.sun.com/download/index.jsp?cat=Web%20%26%20Proxy%20Servers&tab=3&subcat=Web%20Servers|http://www.sun.com/download/index.jsp?cat=Web%20%26%20Proxy%20Servers&tab=3&subcat=Web%20Servers]. If you still have problems in these(6.1 or 7.0) versions of Web Server let us know.

LMS3.2 Log rotation problem

Hi,
we use LMS3.2 (windows single-server) for ~4500 devices and have a problem with log rotation.
That's our configured log roation:
Name with location
Size (kb)
Format
No.of Backups
1.
D:\CSCOpx\log\dcrclient.log
102400
gz
3
2.
D:\CSCOpx\log\ICServer.log
102400
gz
3
3.
D:\CSCOpx\log\syslog.log
1024000
gz
5
The backup directory is the same as the usual log directory. The size of the 3 files is already bigger than the configured size in log roation, see:
dcrclient.log     2,1 GB
ICServer.log     1,1 GB
syslog.log        9,7 GB
After the log roation configuration we restarted the daemon manager, but it's not working. There are no backup files created and the 3 files are still growing.
Regards
Hendrik

After you configure the log rotation you need and restart the daemons, you need to schedule the job. The schedule buttong is available under
Common Services -> Server -> Admin -> Log Rotation.

Extended format of access.log and log rotation

I am using WebLogic Server 6.1sp1. I want to use extended format of web
server access log. I also want to use log rotation based on date. But it
seems not to work together. After my investigation I can say:
- access.log in common format can be rotated based on date an on size,
- access.log in extended format (either in its default form or
completely redefined) cannot be rotated neither based on date nor size.
In the second case at first time WebLogic tries to rotate logfile
IOException is thrown with a message like "java.io.IOException: Failed
to rename log file on attempt to rotate logs". Than it throws
IOException with a message "Exception flushing HTTP log file. (Bad file
descriptor)." when it tries to flush content of logfile to the disk.
After that WebLogic server stops to write to access.log.
Is it possible to rotate access.log in extended format?
Thanks,
Andrzej Derlacki
Infovide, Poland
[email protected]
[email protected]

i am pasting the entries below which i see in the log( access_log ) . I don't see DEBUG in them.
<AGENT_IP_ADDRESS> - - [29/Jun/2007:09:48:23 -0400] "GET /em/upload?ACTION=HEARTBEAT&EMD
_URL=https%3a%2f%2flph010%2egep%2ege%2ecom%3a3872%2femd%2fmain%2f&HEARTBEAT_TI
ME=2007-06-29+09%3a40%3a09&OUTSTANDING_SEVS=FALSE&EMD_UPTIME=2007-06-18+10%3a20%
3a23&OLDEST_COLL_TIME=2007-06-29+09%3a40%3a09&INSTALL_TYPE=agent&X-ORCL-EMOV=4%2
e0%2e0&X-ORCL-EMCV=10%2e2%2e0%2e1%2e0&X-ORCL-EMSV=10%2e2%2e0%2e1%2e0 HTTP/1.1" 2
00 5
<AGENT_IP_ADDRESS>- - [29/Jun/2007:09:48:23 -0400] "GET /em/upload?ACTION=HEARTBEAT&EM
D_URL=https%3a%2f%2fprdes%2eeur%2egep%2ege%2ecom%3a3872%2femd%2fmain%2f&HE
ARTBEAT_TIME=2007-06-29+15%3a48%3a23&OUTSTANDING_SEVS=FALSE&EMD_UPTIME=2007-06-1
8+18%3a27%3a33&OLDEST_COLL_TIME=2007-06-29+15%3a48%3a23&INSTALL_TYPE=agent&X-ORC
L-EMOV=4%2e0%2e0&X-ORCL-EMCV=10%2e2%2e0%2e1%2e0&X-ORCL-EMSV=10%2e2%2e0%2e1%2e0 H
TTP/1.1" 200 5
<AGENT_IP_ADDRESS> - - [29/Jun/2007:09:48:24 -0400] "GET /em/upload?ACTION=HEARTBEAT&E
MD_URL=https%3a%2f%2fug038%2egep%2ege%2ecom%3a3872%2femd%2fmain%2f&HEARTBEAT_
TIME=2007-06-29+22%3a19%3a35&OUTSTANDING_SEVS=FALSE&EMD_UPTIME=2007-06-18+18%3a3
7%3a03&OLDEST_COLL_TIME=2007-06-29+22%3a19%3a35&INSTALL_TYPE=agent&X-ORCL-EMOV=4
%2e0%2e0&X-ORCL-EMCV=10%2e2%2e0%2e1%2e0&X-ORCL-EMSV=10%2e2%2e0%2e1%2e0 HTTP/1.1"
200 5

Dataguard- scheduling manual log switch to have minimal lag

Hi,
I need some suggestion..
Recentry I had configured a physical standby for my 10g production database in maximum performance mode.
Now , to reduce the lag between the primary and standby , I put one cron job which will do a manual log switch(alter system switch logfile) in every 30 minutes.
and it is doing the job..!
Does this have any impact on my databases...?
Looking forward for your invaluable responce...
Regards
Noushad
DBA

Maybe you should let Oracle do it's job, configure this parameter which signifies that no buffer will remain dirty (in the cache) for more than 1800 (or whatever you want) seconds:
LOG_CHECKPOINT_TIMEOUT = 1800:p

Log rotation problem

We are running WLS 8.1.4 and have had a recurring problem with log rotation for quite a long time. It has happened on every machine we've used, running both Windows 2000 and XP. What we want to do is have our logs roll nightly, but it seems that no matter what time we set in the WLS console, the log ends up rolled at an arbitrary time.
Our current configuration is the following:
Server File Name: ourServerName_%MM%-%dd%-%yyyy%.log
Rotation Type: By Time
Rotation Time: 04:00
File Time Span: 24 Hrs
We have tried many permutations on the Rotation Time field, including removing or adding leading zeros as well as seeing if the time difference is constant due to a time zone issue, but no discernible pattern has emerged.
For instance, the logs for the last few days have been rolled at exactly 2300, despite being set to roll at 0400. Other times it has been set to roll at 0204, and it will roll at 1104. One other thing to note: the minutes are always correct, but the hours are nearly always off.
Any ideas?

No, and I can verify that this problem has showed up at multiple sites configured by multiple people besides myself. As we are precisely following the specs laid out in the WLS 8.1 docs, I can only assume this is a bug.

[logging] Problems to configure logging rotation.

Hi,
I have an application .ear deployed in weblogic v10.3.1.0
This application use java.util.logging to write a log file.
      fh = new FileHandler(logFileName,0,1,true);
      fh.setFormatter(new XMLFormatter());
      logger.addHandler(fh);
FileHandler(String pattern, int limit, int count, boolean append)
pattern - the pattern for naming the output file
limit - the maximum number of bytes to write to any one file. If this is zero, then there is no limit. (Defaults to no limit).
count - the number of files to use
append - specifies append mode
http://www.javadocexamples.com/java/util/logging/java.util.logging.FileHandler.html
logFileName is dynamic with date formated like this yyyMMdd + ApplicationName + ".log"
This file is created but I have also yyyyMMddSEC.log.1, yyyyMMddSEC.log.2, yyyyMMddSEC.log.3,...
I DON'T WANT THESE FILES_, that's why I put limit to 0, count to 1 and append to true.
This code works without jdev/weblogic but has not effect in weblogic.
Q1. Why?
So I go to Weblogic console: Domain Structure-> DefaultDomain->Logging
Log file name: logs/DefaultDomain.log
Rotation type: None
NONE
Messages accumulate in a single file.
You must erase the contents of the file when the size is too large.
Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.
But it doesn't work, Weblogic continue to create log files like this *<filename>.log.<n>*
Q2. Why?
I have also created weblogic.xml in ViewControler/WEB-INF
thanks to this documentation:
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/webapp/weblogic_xml.html#wp1063199
but it doesn't work...again.
Q3. Why?
Q4. If I want applications manage themselves their log, how to deactivate the logging handler in weblogic (LogFileMBean?)
Thanks for your help.

You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.

Manual Log Rotation

Similar Messages

Maybe you are looking for