Rotate Logs

Hi,
We know that opmn.log can be rotated on time basis or size basis in <log-path> tag.
How can we rotate the logs for OC4J instances?
Oracle Application Server 10.1.3.1.0
Windows prof 2000
Thanks in advance :)
(Adding version info)
Message was edited by:
Aalap Sharma

Thanks for the Doc Id, it surely is informative.
Apart from this, there are other logs which are recorded in
$ORACLE_HOME/opmn/logs
We also want to rotate these logs, any idea where can we set this parameter ?
Example:
The log file for Default Home OC4J component named "default_group~home~default_group~1.log" has grown to 55 MB.
Thanks in advance :)

Similar Messages

Java.io.IOException: Failed to rename log file on attempt to rotate logs

Hello.
I'm currently using Weblogic 5.1 SP6 on WinNT Server 4.0 SP6.
I set the weblogic.properties file like this so that the "access.log" will
be rotated every day at midnight.
-- weblogic.properties --
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=D:/WLSlog/access.log
weblogic.httpd.logFileFlushSecs=60
weblogic.httpd.logRotationType=date
weblogic.httpd.logRotationPeriodMins=1440
weblogic.httpd.logRotationBeginTime=11-01-2000-00:00:00
-- weblogic.properties <end>--
The rotation has been working well, but one day when I checked my
weblogic.log, I was getting some errors.
I found out that my "access.log" wasn't being rotated (nor being written,
flushed) after this error came out.
After rebooting WebLogic, this problem went away.
Has anyone clues about why WebLogic failed to "rename log file?"
-- weblogic.log --
? 2 04 00:00:00 JST 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Failed to rename log file on attempt to rotate logs
at weblogic.t3.srvr.httplog.LogManagerHttp.rotateLog(LogManagerHttp.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.io.IOException.<init>(IOException.java, Compiled Code)
at weblogic.t3.srvr.httplog.LogManagerHttp.rotateLog(LogManagerHttp.java,
Compiled Code)
at
weblogic.t3.srvr.httplog.LogManagerHttp.access$2(LogManagerHttp.java:271)
at
weblogic.t3.srvr.httplog.LogManagerHttp$RotateLogTrigger.trigger(LogManagerH
ttp.java:539)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java, Compiled Code)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
, Compiled Code)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
? 2 04 00:00:25 JST 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Bad file descriptor
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java, Compiled Code)
at
weblogic.utils.io.DoubleBufferedOutputStream.flushBuffer(DoubleBufferedOutpu
tStream.java, Compiled Code)
at
weblogic.utils.io.DoubleBufferedOutputStream.flush(DoubleBufferedOutputStrea
m.java, Compiled Code)
at
weblogic.t3.srvr.httplog.LogManagerHttp$FlushLogStreamTrigger.trigger(LogMan
agerHttp.java, Compiled Code)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java, Compiled Code)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
, Compiled Code)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
-- weblogic.log <end> --
note:
? 2 04 00:00:25 JST 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Bad file descriptor
keeps coming out every minute after on.
I suppose this is because I have set the HTTP log to be flushed every one
minute.
Thanks in advance.
Ryotaro

I'm also getting this error on Weblogic 6.1.1.
It only occurs if you set the format to "extended".
Is there any fix or workaround for this?

903 management of app / out / err logs to rotating log files??

I'm deploying BC4J apps under OC4J.
One of my complaints about the production environment is that the noisy logging from
BC4J is directed to a static file name by the shell startup script. This not enterprise nor
manageable in a 24x7 environment since the log file grows boundlessly.
It was mentioned that 903 OC4J would fix log mangement. I've not seen anymention in doc's.
Might someone offer how -out and -err logs can be better managed in 903?
Thanks curt

To be 24/7 an appserver needs to at least support managing the System.out traffic
that apps, frameworks (BC4J) spew.
It was suggested that 903 OC4J will support rotating log files?
Is this true and any help or doc pointers would be great.
BTW, I'm moving to 903 enterprise with OEM.
Thanks, curt Curt - there is no way in 903 to rotate log files for a specific OC4J instance.
There is a feature request in place for this functionality but I am not sure which version it will be delivered with.
-steve-

Is it possible to rotate log of iplanet server once a month ?

Instead of changing log file each day or each week, I would like to know if is possible to rotate log of iplanet server once a month.

Yes, you may use the internal daemon log rotation (available in iPlanet Web Server 4.x and 6).
Using this new feature introduced in iWS 4, you may set up the rotation start time and the interval for the next rotation to happen (in minutes).
For every hour the interval is 60, every day 1440.
To config internal daemon to perform log rotation every 30 days the interval would be 43200 minutes.

Rotating logs and rdate don't work together

Hi people,
Recently I've noticed a problem with rotating logs and rdate. Since the server runs as a cronjob a 'rdate' command, web server logs are not rotated correctly.
Archived log files only keep messages from the last hour (23-24), when they should keep the messages of the whole day.
Servers without the 'rdate' cronjob keep archived messages properly.
The magnus.conf line that configures the archives logs is:
Init fn="flex-rotate-init" rotate-start="0000" rotate-interval="1440"
and the crontab that runs rdate:
10 20 * * * rdate mytimeserver
What is the problem with archiving logs and running rdate??
Thanks in advance,
Juan Fuentes.

This is a major screw-up on Apple’s part. Interesting that I just realized courtesy of MacIntouch that TM was NOT backing up my FileVaulted home folder. I use my MacBook Pro probably like most people. When I’m at home I’m behind a firewall. I leave the computer connected to my home network and I leave it open and on. I don’t log out ever! For security I do use the FileVault feature and I don’t use distant connections to my home network.
There should be an option for TM to back up the open file vault directory just as if, frankly, someone would have access to it if they picked up my open computer and walked off with it. The owner has to have physical control of the computer. FileVault works if the computer is asleep and the wake log-on is enabled or if the computer is restarted. However, if my filevault is open and being used by me it should be available for a TM back-up.
Interesting that Retrospect, with all its faults and promises of vaporware to come, WILL back up my MacBook FileVault.
Apple should provide some type of option for this situation. On the fly decoding of the open FileVault directory so as to avoid a repeated total backup of the whole thing is the answer. It is the owner’s responsibility to keep the TM volume secure.

Has 903 oc4j fixed / added rotating log files; -out and -err ?

To be 24/7 an appserver needs to at least support managing the System.out traffic
that apps, frameworks (BC4J) spew.
It was suggested that 903 OC4J will support rotating log files?
Is this true and any help or doc pointers would be great.
BTW, I'm moving to 903 enterprise with OEM.
Thanks, curt

To be 24/7 an appserver needs to at least support managing the System.out traffic
that apps, frameworks (BC4J) spew.
It was suggested that 903 OC4J will support rotating log files?
Is this true and any help or doc pointers would be great.
BTW, I'm moving to 903 enterprise with OEM.
Thanks, curt Curt - there is no way in 903 to rotate log files for a specific OC4J instance.
There is a feature request in place for this functionality but I am not sure which version it will be delivered with.
-steve-

Rotating logs in OC4J SO?

Is there a way to configure OC4J stand alone version so that I can have access logs automatically rotated when the logs reach a certain size or when a period of time has elapsed? Ideally I would like to be able to pipe the web site access logs (and others) to a tool such as cronolog that handles log file rotation. I've tried to modify the http-web-site.xml file entry for the path to the access log so that it pipes to cronolog, but oc4j barfs. Anybody out there have any ideas?

You can rotate logs in OC4J 9.0.4 using ODL. Please look at the OC4J Standalone userguide at http://download-west.oracle.com/docs/cd/B12314_01/web.904/b10323/advanced.htm#1015201
regards
Debu

How to set the FileHandler to daily rotate logs?

Is it possible to make the JDK Logging API rotate logs daily, instead of rotating when it reaches a size limit? And append the date to the log file?

The really easy way is to make a new FileHandler for
every log call. However, this is slow(er), so there
are better ways for performance. For example, keep
track of the date or filename currently in use. For
each log call (or every 10, or every call that
happens at least one hour after the last one, or
whatever) make a new date and check it against the
old one. If it's different, remove the handler and
attach a new one. Voila, now it logs to a different
file.With Log4J instead of java's built-in logging, this can be done way easier than that, by simply configuring Log4J to use its built-in DailyRollingFileAppender (or whatever it's called) which automatically creates a new log file each day. I don't know why java's built-in logging would be so much more difficult - one would think it could map better like Log4J does it. Are you sure there's no built-in "appender" (whatever java logging calls an appender) to do this? Doesn't java logging use some kind of config file - does everything in java logging have to be done programatically rather than thru config files?

OPMN rotation log issue?

Hi all,
I already configured my opmn.xml , so that my application log could be rotate based on rotation-size and hour property.
The rotation done successfully and created new log file well. BUT MY BIG CONFUSING is why the log still write on the previous log that has been rotated???, and my new log file is ignored by application???
my server is UNIX, is it needs to additional configuration, like set the permission file or other??
Thanks in advance.
Regards,
Kahlil

Sorry to sound little rude but the truth is you have got it all wrong. You are very confused about the terminology and at the same time do not provide clear and complete information. We can continue going back and forth but will not be able to reach to any resolution.
I will try one more but last time:
No, I wanna rotate My_APP_NAME.log that generated on .../opmn/logs after I deployed my apps, so based on this reason on previous post I little bit confuse how to state kind of this log, application log or opmn log.First, can I rephrase it to say that when you deploy an application (named "MY_APP_NAME"), it creates a file named "MY_APP_NAME.log" in $ORACLE_HOME/opmn/logs directory?
If yes, this should be called your "application log file". Just because it gets created in $ORACLE_HOME/opmn/logs directory, it does not become OPMN log file.
If not, again tell us the "exact" name of the log file.
Second, by default, no application log files get created in $ORACLE_HOME/opmn/logs directory. If your application is doing it, there has to be something specific to your application.
I already use the second config :<log path="$ORACLE_HOME/opmn/logs/My_APP_NAME.log" comp="internal;ons;pm" rotation-size="1500000" rotation-hour="15"/>
What you have done above is changed the default opmn log file name from being "opmn.log" to "My_APP_NAME.log". By using this name, it will not automatically become "your application's log file". It will still remain OPMN's log file. No application log messages will be written to this file. Only OPMN log messages will be written to this file, irrespective of the file name.
and unfortunately failed to re-write on new file after rotating...Are you saying your application log messages are written to this file until it rotates? And once it gets rotated, your application log messages stop getting written to this file? Again, by just changing the name from "opmn.log" to "My_APP_NAME.log" will not make it "your application log". It will still be OPMN's log file and only OPMN log messages will be written to this file.
Again, I would love to help but with little, incomplete and wrong information, I can't. I would recommend you to call Oracle Support and have it discussed with them on the phone.
Thanks
Shail

Rotate Log Files - stdout.log & stderr.log

Hi Folks,
Whats the best way to rotate stdout.log & stderr.log.
I am assuming that rolling of these files can not be configured using felix (please correct me if I am mistaken)
Please advice!
Thanks,
Adnan

Hi Adnan,
There is currently no way to rotate stdout.log and stderr.log. Therefore, if you want to preserve the stdout.log and stderr.log so that they do not get truncated after restart, add the following commands before any other command in the start script.
# Move stdout.log and stderr.log
mv ../logs/stdout.log ../logs/stdout_$(date +%Y-%m-%d-%H%M).log
mv ../logs/stderr.log ../logs/stderr_$(date +%Y-%m-%d-%H%M).log
Another possible way is to disable the stdout.log and stderr.log entirely and instead output the information to the startup.log. Then you can rotate the startup.log instead.
a) To disable the stderr.log and stdout.log, i guess you can add these lines to your crx-quickstart/server/start script:
QUICKSTART_OPTS='-verbose -nobrowser'
export QUICKSTART_OPTS
b) To configure the path of the startup.log, you can add this to the start script as well (replace /path/to/startup.log with the path you would like the log to be written to instead):
CQ_LOG=/path/to/startup.log
export CQ_LOG
c) Then after doing this, there is a side effect that crx output will go to the startup.log as well. to fix this, do the following:
1) Go to crx-quickstart/server/runtime/0/_crx/log4j.xml
2) Comment out this element <appender-ref ref="console" /> from log4j.xml
<root>
<level value="info" />

<appender-ref ref="error" />
</root>
d) Also, now you would like to rotate the startup.log file:
"The file startup.log logs messages while the Servlet Engine starts. It is usually small, and you cannot configure it."
The startup log cannot be rotated with CQSE facilities. Please note that logs under /server is rotated at operating system level,
for more info see http://httpd.apache.org/docs/2.0/programs/rotatelogs.html
Unix workaround :
in serverctl script, replace the line :
exec $jvmExe >> "$CQ_LOG" 2>&1
by :
exec $jvmExe | /usr/sbin/rotatelogs "$CQ_LOG.%Y%m%d" 86400 >> /dev/null 2>&1
If this doesn't seem to work, then try
exec $jvmExe 2>&1 | /usr/sbin/rotatelogs "$CQ_LOG.%Y%m%d" 86400
Unfortunately, I did not found any workaround for windows system.
Hope this helps.
Thanks,
Varun

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

What determines when logs get rotated?

I need to write a script to parse /private/var/log/secure.log and create a report consisting of the time and userid of each login. But secure.log gets archived periodically, and then the archives get deleted, so I need to time the execution of this script to whatever it is that triggers this archiving so I can record the logins before the log gets rotated.
Looking at the logs and archives, it's a little hard to tell what's going on.
% ls -l /private/var/log/secure.*
-rw-r----- 1 root admin 8153 Jul 24 21:37 /private/var/log/secure.log
-rw-r----- 1 root admin 2232 Jul 21 23:16 /private/var/log/secure.log.0.gz
-rw-r----- 1 root admin 2196 Jul 7 08:21 /private/var/log/secure.log.1.gz
-rw------- 1 root admin 6275 Jun 29 22:29 /private/var/log/secure.log.2.gz
The time intervals are not the same, and neither are the file sizes, so the logs don't appear to get rotated on a regular schedule or when they reach a certain size. It does seem to happen between logins, I think.
/private/etc/periodic/daily/100.clean-logs looks like it deletes old logs, but it isn't involved in archiving or deleting archived logs. /private/etc/periodic/daily/500.daily has a routine for archiving logs, but I don't understand it well enough to see what triggers it.

I've written the script for doing user accounting on the Panther machines, but I'm still having trouble understanding what's going on on my own machine. I'm not positive, but I think there might be some serious problems with launchd and how it manages logs. Something is definitely not right.
According to the documentation Mark referred me to,
Beginning in Mac OS X v10.4, the preferred way to add a timed job is to use a launchd(8) timed job. A launchd timed job is similar to a cron(8) job, with two key differences:
* Each launchd job is described by a separate file. This means that you can add launchd timed jobs by simply adding or removing a file.
* If the computer is asleep at the designated time, a launchd job executes as soon as the computer wakes. This is similar to the behavior of anacron and other cron replacements).
From what I'm seeing, this simply isn't happening. Look at the listing I posted above:
% ls -l /private/var/log/secure.*
-rw-r----- 1 root admin 8153 Jul 24 21:37 /private/var/log/secure.log
-rw-r----- 1 root admin 2232 Jul 21 23:16 /private/var/log/secure.log.0.gz
-rw-r----- 1 root admin 2196 Jul 7 08:21 /private/var/log/secure.log.1.gz
-rw------- 1 root admin 6275 Jun 29 22:29 /private/var/log/secure.log.2.gz
This log is rotated by the script /private/etc/periodic/weekly/500.weekly, but it clearly isn't being rotated weekly. The dates the three archives were created fall on a Friday and two Saturdays, and there is a two week gap between 0 and 1. I am positive that my laptop was not asleep for a week or more. I use it every day. I noticed that the permissions on secure.log.2.gz are wrong, but I don't think that's the cause of the problem. It's just another sign of the hinkiness that abounds here.
The situation looks even stranger when you look at the dates of the first and last entries in each file:
secure.log.2: Jun 19 22:34:51 - Jun 29 22:29:19
secure.log.1: Jun 30 20:15:36 - Jul 7 08:20:33
secure.log.0: Jul 7 11:33:01 - Jul 21 23:16:07
secure.log: Jul 22 15:35:03 - Jul 27 22:43:46 (and counting)
So it looks secure.log.0 and secure.log.2 were truncated and archived around midnight--different days of the week, but at least they avoided getting entries from the same date in two different files. But look at secure.log.1. 8:21 in the morning??? Why???? It's not like it was asleep or anything. I had been using it until around 12:30, and started in again at around 6:30 Saturday morning. Why does it decide it's time to rotate the log at 8:21? And this is after it has already waited two weeks!
So if you're doing user accounting on a weekly basis, this just isn't helpful, and it sure isn't helpful if you're trying to do it monthly. You basically need to re-concatenate the files and split them out by grepping the dates. In other words, before you can do what you need to do, you have to undo what the periodic maintenance routines have done.
And you have to hope they haven't destroyed the records you need.
Among all the other mysteries I'm trying to sort out, I'm trying to understand why the /private/etc/periodic/monthly/500.monthly script didn't run at the end of June. One thing I can't do is go back and look at the system.log, because they rotate them daily (or they intend to, but this doesn't work correctly either) and only keep the last seven. Here's what the log rotation script looks like:
for i in system.log; do
if \[ -f "${i}" \]; then
printf %s " ${i}"
if \[ -x /usr/bin/gzip \]; then gzext=".gz"; else gzext=""; fi
if \[ -f "${i}.6${gzext}" \]; then mv -f "${i}.6${gzext}" "${i}.7${gzext}"; fi
if \[ -f "${i}.5${gzext}" \]; then mv -f "${i}.5${gzext}" "${i}.6${gzext}"; fi
if \[ -f "${i}.4${gzext}" \]; then mv -f "${i}.4${gzext}" "${i}.5${gzext}"; fi
if \[ -f "${i}.3${gzext}" \]; then mv -f "${i}.3${gzext}" "${i}.4${gzext}"; fi
if \[ -f "${i}.2${gzext}" \]; then mv -f "${i}.2${gzext}" "${i}.3${gzext}"; fi
if \[ -f "${i}.1${gzext}" \]; then mv -f "${i}.1${gzext}" "${i}.2${gzext}"; fi
if \[ -f "${i}.0${gzext}" \]; then mv -f "${i}.0${gzext}" "${i}.1${gzext}"; fi
if \[ -f "${i}" \]; then
touch "${i}.$$" && chmod 640 "${i}.$$" && chown root:admin "${i}.$$"
mv -f "${i}" "${i}.0" && mv "${i}.$$" "${i}" && if \[ -x /usr/bin/gzip \]; then
gzip -9 "${i}.0"; fi
fi
fi
done
That last part is just plain weird. They get done rotating all the gzipped archives, and then they need to test to see if there is a new log file, and if not, create one, then archive it. Archive an empty log??? What for? Don't you want to see if there's a current log, and that it has at least one line of data in it, before you start the whole process? Why bother rotating logs if there's no new information? And then, after they archive it, they don't create a new log? All of the other log rotation scripts archive the current log then create a new one. Why should this one be different? This just looks like a mistake.
Also, I'm not the most experienced shell scripter, but isn't this just plain crude and ugly? Instead of using a loop to do a repetetive task, with a variable you can change to set a limit on the number of iterations, they've hard-coded each step. And this is in the script that we're not supposed to change, and it can't be overridden. Nice.
So if we want to change how frequently our log files get trashed, we need to write a daily.local script that takes the truncated, archived files and decompresses them, concatenates them, and puts them somewhere out of harms way? Is that how we're supposed to proceed? Follow them around and undo what they do then try to do it right? Heaping more ugliness upon ugliness?
And keep in mind that the timing mechanism that controls it all is broken, and if you want to do your monthly reports at the end of the month, or your weekly reports at the end of the week, you either have to wait around until this byzantine Rube Goldberg machine spits out the logs you need or go to the terminal and call periodic to run whatever process you want it to run manually after all.
I am starting to wish I'd never looked at this.

Cron-based log rotation problem

In setting up Sun Web Server 6.1 2005Q4 SP5, I successfully restarted schedulerd after setting up cron-based log rotation for 12 AM for each Web instance. But still no rotated logs. I notice these messages in /app/sunone/https-admserv/logs/scheduler.error:
Tue Mar 14 00:00:00 2006: Warning: cron has no information about finished child process 11303
Tue Mar 14 23:00:03 2006: Warning: Process 11303 didn't finish in time, had to terminate it
Any ideas?
Thanks!

This bug is addressed in SunSolve:
Document ID:     4953147
Title:     cron based log rotation fails when admin user is root and instance is non-root
The workaround is to update this line in WS_ROOT/https-admserv/config/scheduler.conf:
    User <non-root user ID such as "nobody">to:
    User rootThen I restarted cron from the Server Manager to make sure the change was picked up.

WebLogic 9.2 : Log files are not rotating properly

Hello,
In Weblogic 9.2, i have mentioned the log archive directory to rotate log files on the basis of size (2 MB) and also checked the flag to rotate the file on startup of server so there are only two possibilities of rotation that is
1. Either reach file size upto 2 MB
2. On startup of server
Lets take an example step by step
1. I started server, a file e.g. running.out00142 is created.
2. Now running.out size is reached again upto 2 MB then a new file named running.out00143 should be created.
3. yes the file is created into the archive folder but every time when next file is created the first file running.out00142 is getting increase and exists till server restarts
4. Total file contains is 15 but the first file is getting increased and exists till server restart.
Can anyone help me
Thanks in advance
[email protected]

Hi,
That's a weird behaviour...
I had a problem with a non rotating log once and I found out that the domain and the server log were pointing to the same file and then they were locking each other.
Non-rotating logs are usually caused by weblogic being unable to rename the old file, either because of locking or file/directory rights.
Hope that helps.
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question. If you think this is helpful, please consider giving points

Msg log rotation

Hello,
I have several log rotation related questions:
1. http_sso - will simply rotating this to http_sso.old and zeroing out http_sso do the job?
2. uwc.log - this file is owneb by web server uid. will I have to restart web server(Sun web server) after rotating this file? ( apache needs kill -USR1 )?
3. Any advice on Access manager log file rotation?
Many thanks,
D.

Hello,
I have several log rotation related questions:
1. http_sso - will simply rotating this to
http_sso.old and zeroing out http_sso do the job?Huh? What are you trying to achive?
2. uwc.log - this file is owneb by web server uid.
will I have to restart web server(Sun web server)
after rotating this file? ( apache needs kill -USR1
)?I doubt it. Doesn't the web server rotate log files? I bet it does, automatically.
3. Any advice on Access manager log file rotation?Sorry, I have no idea. Messaging Server, I know well. AM, nope.
Many thanks,
D.

Rotate Logs

Similar Messages

Maybe you are looking for