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.

Similar Messages

New log rotation problem

I have resolved some log rotation problem...I have set del log rtation by size...and now the first time the log rotate,but then the output continue to go on the lod with the extension .log001 and not on the configured file.
why?

no,it the server rotates the log only the first time but then it continues to write on the .log001.On the original file it continues to write some server exception.
the server launch line in the scritp is the follow
nohup "$JAVA_HOME/bin/java" ${JAVA_VM} ${JAVA_OPTIONS_NODE} ${JAVA_OPTIONS} \
Dweblogic.Name=${SERVER_NAME} \
Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} \
Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy" \
Dweblogic.Stdout=/u02/bea/weblogic81/mydomain/mydomain_LOG/myserver_Admin.log \
Dweblogic.Stderr=/u02/bea/weblogic81/mydomain/mydomain_LOG/myserver_Admin.log \
weblogic.Server > /dev/null &
and the config.xml part for the server configuration is the follow
<Server COMEnabled="true" CompleteMessageTimeout="0"
ConsoleInputEnabled="false" EnabledForDomainLog="true"
ExpectedToRun="false" JDBCLogFileName="./mydomain_LOG/jdbc.log"
JDBCLoggingEnabled="true" JavaCompiler="javac"
ListenAddress="10.2.1.16" ListenPort="10001"
MaxMessageSize="100000000" Name="myserver_Admin"
ServerVersion="8.1.3.0" SocketReaderTimeoutMaxMillis="10"
StagingMode="nostage" StdoutDebugEnabled="true"
StdoutEnabled="true" StdoutSeverityLevel="16" TransactionLogFilePrefix="../myserver_LOG/myserverAdminTransaction.log">
<SSL Enabled="false" IdentityAndTrustLocations="KeyStores"
ListenPort="10002" Name="myserver_Admin"/>
<Log FileCount="4" FileMinSize="30"
FileName="/u02/bea/weblogic81/mydomain/mydomain_LOG/myserver_Admin.log"
FileTimeSpan="1" Name="myserver_Admin"
NumberOfFilesLimited="true" RotationType="bySize"/>
<WebServer LogFileCount="2" LogFileLimitEnabled="true"
LogFileName="./mydomain_LOG/access.log"
LogRotationPeriodMins="360" LogRotationType="size"
MaxLogFileSizeKBytes="20000" Name="myserver_Admin"/>

Time-based log rotation in Access Manager

Hi,
We have configured Access Manager for size-based log rotation. So the log files undergo rotation whenever the log files reach the size limit specified.
But I would like to know if the Access Manager Logging module provides options for:
Time-based Log Rotation : so that log files get rotated on a periodic basis.
Log File Name Customization: At present the old log files get suffixed with -n (e.g. amPolicy.access-1), where 'n' denotes the number in the rotation sequence . Is it possible to configure Access Manager to generate a timestamp as a suffix for old log files.
e.g. amPolicy.access-05_29_2005.
Regards,
Chetan Desai

The AM admin guide (ftp://docs-pdf.sun.com/817-7647/817-7647.pdf) page 335 has listed all available Logging attribute. It doesn't have the time based parameter and time stamp suffix. If you wish to have those features, please contact Sun Identity sales for filing a RFE. Also checking Logging API and see whether you can program yourself to achieve those features. (see page 47 of 817-7650.pdf) Jerry

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.

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.

Secure.log and log rotation problems

I had originally posted this in the Tiger section, but now finding the Unix section which I think would be able to help me more. here is the link to the post: http://discussions.apple.com/thread.jspa?threadID=1913487&tstart=0
Also I am getting this in my system.log, I have googled it and cannot find anything that tells me what it is:
Feb 19 18:54:34 SamiMac kernel[0]: m378d97c0 0
some help on this would also be appreciated.
Message was edited by: a Mac user

The secure.log message is explained at the bottom of Spurious Permission errors in OS X 10.4.
For your ipfw logs, check that /etc/periodic/weekly/500.weekly contains the line
for i in ftp.log lookupd.log lpr.log mail.log netinfo.log hwmond.log ipfw.log ppp.log secure.log; do
(although I don't know why it wouldn't) and then check this is actually being run by looking at /var/log/weekly.out. Try
tail -10 /var/log/weekly.out
Let us know what you see.
I haven't seen that kernel message before

Access and Error Log Rotation

When turning on Archive for the logs. cron style. The log gets archived with the date etc, but the new files access and error do not get created. I have ns-cron on and the rotation occurs, but the files name only changes and it never create the new files and only keeps changing the file names with the new name.

You may be running into Problem 4684892 mentioned in the release notes:
http://docs.sun.com/source/817-5170-10/rn60sp7.html
The Administration Server and the cron daemon must be run as root for cron-based log rotation to function properly. You may have to modify your cron.conf user to run as root.
Thanks,
Manish

Change beasvc.exe default stdout log rotation parameters in WLS10.0

Weblogic Server 10.0:
I'm trying to change default log rotation parameters for weblogic server service as suggested here:
http://edocs.bea.com/wls/docs100/server_start/winservice.html#wp1193277
my installsvc.cmd contains:
set ROTATION_TYPE = TIME
set TIME_START_DATE = Jun 12 2008 15:07:00
set TIME_INTERVAL_MINS = 3
set STD_LOG=C:\logs\stdout.log
beasvc.exe -install.... -log:"%STD_LOG%"
This is the sniplet from the stdout.log:
[Thu Jun 12 15:45:09 2008] [initLog] initializing logger
[Thu Jun 12 15:45:09 2008] [E] [initLog] No 'ROTATION_TYPE' header found. 'TIME' based rotation will be used by default.
[Thu Jun 12 15:45:09 2008] [E] [initLog] No 'TIME_START_DATE' header found or value is invalid. Rotation will take place every 24 hours beginning today at 23:59:59
[Thu Jun 12 15:45:09 2008] [E] [initLog] No 'TIME_INTERVAL_MINS' header found. Using the default value of 24 hours.
[Thu Jun 12 15:45:09 2008] [I] [initLog] TIME based log rotation is ON
[Thu Jun 12 15:45:09 2008] [I] [trigger] First rotation due in 29690 secs
[Thu Jun 12 15:45:09 2008] [I] [ServiceStart] console allocation successful. THREAD_DUMP redirection enabled
[Thu Jun 12 15:45:09 2008] [I] [ServiceStart] About to execute CreateThread()
the service then starts ok and works with default settings, but that's not what I'm looking for...
any ideas are welcome ;)
thanks!

yes, the parameters are set when service is being installed. Also, I can see in the log when changes are made to the parameters and service reinstalled.

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.

LMS - log rotation based on time period

Dear All
can we configure log rotation to be based on time period (ex:past one year)instead of log file size.
if it is feasable please advise who to do it?
Regards;
Antonio

I am not sure if I understand it correct, but you can do this easily by defining the expected file size of the log file to rotate;
logrot runs on a scheduled basis and checks if the log file has reached the defined file size - if not it will do nothing else the file will be backed up. The key point is the configured file size;
I use this for the syslog file to have a backup for each month:
schedule logrot to run every first of each month and set the file size to a low value guarantes that I ve got a file for every month;
from the online help of logrot:
http://:1741/help/cmf/index.html?sysad_adm_logrotate.html
4. Specify the number of archive revisions. If you do not want to keep any archives, enter 0 (the default) for this option.
5. Specify the maximum file size. The log will not be rotated until this size is reached. The unit is in kilobytes (KB). The default is 1024 KB or 1 MB.
why do you want to keep all log messages of a complete year in one file - what do you want to do?

[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.

Log Rotation on iPlanet 6.0 SP6

Hello,
I am running iPlanet 6.0 SP 6 on a Windows 2000 server and am having an issue with the access logs rotating. I have them set to rotate at 12:00 am using the Internal Daemon. The logs will rotate and begin to write to a new access file, however, there is no data in the log file. All that is showing up is the first line and the size of the log file is 1 KB. If anyone else has had this problem, please let me know. Thanks

I believe this may happen when a program, such as ntpdate, changes this system clock by more than a few seconds. The problem has been seen when the system clock is particularly slow and the clock is synchronized by a nightly cron job. Under such circumstances, the access log file may be rotated twice, the second rotation overwriting the first. Bug 6206179 has been filed to track this problem.
A work around is to modify the flex-rotate-init line in your magnus.conf configuration file so that it reads as follows:Init fn="flex-rotate-init"
     rotate-start="..."
     rotate-interval="..."
     rotate-suffix=".%Y%m%d%H%M.tmp"
     rotate-callback="/home/webservd/postrotate"Where /home/webservd/postrotate is an executable script that contains the following:#!/usr/bin/ksh
tmpfile=$1
logfile=${tmpfile%.tmp}          # removes .tmp part
if [[ -s $logfile ]];            # if logfile exists and not empty
then
    cat $tmpfile >>$logfile      # append the content of tmpfile to the logfile
    rm $tmpfile
else
    mv $tmpfile $logfile
fiThis will keep the server from overwriting access log entries if it tries to rotate the access log file twice.

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.

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

Cisco Security manager syslog.log file problem

Hello
I have this problem with the CSM, the next file Syslog.log (C:\Program Files\CSCOpx\log\Syslog.log ), this file grows very fast to fill the hard disk and saturates the server, I have tried the log rotation of the cisco works but it doesnt work, what else can i do?
the hard drive fills in 4 hours. tankyou

In CSM clinet under Tools > CSM Administration > Debugging you can changing the level to something higher than debugging.
I hope it helps.
PK

Cron-based log rotation problem

Similar Messages

Maybe you are looking for