What to do about NodeManager's .out log file?

Hi all,
in your production environments, how do you handle <server name>.out log file created by NodeManager?
Do you let it run in gigabytes size? Currently our applications are a bit verbatim on stdout which in our test
environment creates quite large .out files, since the server is not restarted for many weeks. How could
we handle this? Reduce stdout output? Do not start the managed server through NodeManager? Create a
separate process to delete the file every few days?
I've check in the documentation and it says that I can't limit the size of the file.
Thanks

You cannot rotate the stdout file unless you are starting weblogic as windows service.
Link : http://e-docs.bea.com/wls/docs81/adminguide/winservice.html#1188735
You can use third party log rotation utilities in unix platforms :-
http://linuxcommand.org/man_pages/logrotate8.html

Similar Messages

Mackeeper and daily.out log file

This is not a question, but a tutorial garnered bits and pieces from the communtiy.
If you have downloaded Mackeeper, you should check your daily.out file. It continues to try to run every 10 sec. even when you have trashed it (via their uninstall instructions) and will fill up that file over time. ( 10.4 gigs in my case on the daily.out log file....).
Disclaimer note: I am using OSX 10.6.7 but this should work for most OSX systems with this bug.
I recently found this recurring cycle.
Fri Mar 29 06:42:29 admin-admins-power-mac-g4-3 com.apple.launchd.peruser.502[103] (com.zeobit.MacKeeper.Helper) <Warning>: Throttling respawn: Will start in 10 seconds
Fri Mar 29 06:42:39 admin-admins-power-mac-g4-3 com.apple.launchd.peruser.502[103] (com.zeobit.MacKeeper.Helper[19883]) <Warning>: Exited with exit code: 1
Fri Mar 29 06:42:39 admin-admins-power-mac-g4-3 com.apple.launchd.peruser.502[103] (com.zeobit.MacKeeper.Helper) <Warning>: Throttling respawn: Will start in 10 seconds
Fri Mar 29 06:42:49 admin-admins-power-mac-g4-3 com.apple.launchd.peruser.502[103] (com.zeobit.MacKeeper.Helper[19884]) <Warning>: Exited with exit code:
....and could only see it happening by watching it log every 10 sec. in the Mac Console.app. (Was not registering in Activity Monitor.app). This apparently has been going on for over 2 years even though I thought I had uninstalled Mackeeper via their own instructions.
This has the unfortunate consequence of filling up your daily.out log over time (mine was at 10.3 gigabytes after a little over 2 years... imagine infinite pages upon pages of the same stupid recurring message).
If you have ever downloaded MacKeeper, I strongly suggest you view your daily.out log file via Console.app. You can see Mackeeper working simply by viewing “All Messeages” in Console if it’s still running... or trying to run (every 10 sec.), that is the problem, and follow carefully all the steps listed here: http://applehelpwriter.com/2011/09/21/how-to-uninstall-mackeeper-malware/ .Use the 2nd portion of the tutorial. Do not trust that by simply dragging and dropping the app. file into trash you have gotten rid of this beast (even though Mackeeper says you can).
Ironically, I found this anomaly using the freeware GrandPerspective (1.5.1) http://grandperspectiv.sourceforge.net/ and noticed a huge, very pretty, yet clear (not subdivided) block in the colored rectangles right away (the software was so intuitive, I simply clicked the block and then the “Reveal” button) and saw that my daily.out file (a file I didn’t even know I had) was at 10.3 gigs.
The highlighted large light yellow area is my daily.out log file.
(Note: you can give a donation to sourceforge.net if you think it helped you.) I find it ironic simply because I’m using freeware to free up hard disk space and speed up the computer, by getting rid of malware that claimed to do the same (Mackeeper) for a fee.
Onward... You then need to go into terminal (something I’ve never done before... just be careful and unintimidated) and follow these instructions to delete or empty your daily.out log file. (cannot be done with a simple drag and drop to trash). I found terminal instructions for deleting (not harmful and will reconstruct) or emptying the daily.out files here: http://forums.macrumors.com/showthread.php?t=1229894
After a try or two, this did not work for me somehow... (user error?) but this did...
Some files are locked. In order to delete locked files, go to Apps/Utilities/Terminal, use Terminal command line : sudo rm -rf ...add one space after “f” then drag the file “daily.out” that grandperspective “revealed” into the terminal, hit “return/enter” type admin. password. Hit “return” again.
The files should delete. You will see more HD space (in my case 10.3 gigs... small these days perhaps, but can throw an almost full HD off). The daily.out log file should reconstruct on your mac’s next scheduled daily. Obviously, you should read your daily.out log file via Console.app first before delete to determine the problem.
Hope this helps.
(Disclaimer: I don't work for sourceforge, I am a mere musician trying to get the job done.) Thanks to all the other posters.

Hmm. So your weekly and monthly clean-ups are running normally - I had thought there might be something wrong with them. It seems to be alot of kernel debugging entries that are making it grow so much. Did you deliberately do something to turn it on? You could try, in terminal,
sudo rm /var/log/daily.out
- it will ask for your admin password to confirm it. Then maybe do a system shutdown/restart to see if that kills the debugger logging. I don't know how to turn it off.

Error in Weekly.out log file

I was just about to clone my MacintoshHD to a new SSD drive for my boot volume, so did a search for any basic cleanup tools or scripts or anything else I could do before creating the clone
I came across the fact that there are the daily weekly and monthly scripts that run by default within OS X.
On checking the logs I cam across this and it has been happening every week since Sat Sep 12 12:51:09 BST 2009
Here it is:
Mon 14 Nov 2011 12:02:35 GMT
Rebuilding whatis database:
Running /etc/weekly.local:
-n Rotating psync log files:
/etc/weekly.local: line 17: syntax error near unexpected token `)'
/etc/weekly.local: line 17: `if [ -f /var/run/syslog.pid ]; then kill -HUP 0 101 80 79 102 103 81 98 106 104 0cat /var/run/syslog.pid | head -1); fi'
-- End of weekly output --
Is this an issue? obviously not a great one since I had not noticed it before..and as far as I know it has not created any issues to my use of the machine...just interested, that is all, and if I need to anything about it
Thanks

OK, thnaks for that.
I guess just deleting it is the answer, but if I do, will the in built scripts still run, just wondering where that script is called from when it runs, and did maybe the app that installed it, delete the entry that runs the in built scripts?
He is the offending script and it loooks liek it came from a backup app called PsyncX
echo ""
echo -n "Rotating psync log files:"
cd /var/log
for i in psync.log; do
    if [ -f "" ]; then
        echo -n " "
        if [ -x /usr/bin/gzip ]; then gzext=".gz"; else gzext=""; fi
        if [ -f ".3" ]; then mv -f ".3" ".4"; fi
        if [ -f ".2" ]; then mv -f ".2" ".3"; fi
        if [ -f ".1" ]; then mv -f ".1" ".2"; fi
        if [ -f ".0" ]; then mv -f ".0" ".1"; fi
        if [ -f "" ]; then mv -f "" ".0" && if [ -x /usr/bin/gzip ]; then gzip -9 ".0"; fi; fi
        touch "" && chmod 640 "" && chown root:admin ""
    fi
done
if [ -f /var/run/syslog.pid ]; then kill -HUP 0 101 80 79 102 103 81 98 106 104 0cat /var/run/syslog.pid | head -1); fi
In my /private/etc/periodic/weekly folder there are two files
320.whatis
999.local

Want to delete out.log files

Log files having a file name of {servername}-out
n.log (where
n is a numeric identifying separate log files) accumulate in
great numbers in the folder, \JRun4\logs\. Some log files appear to
expand beyond their typical 200kb size into the hundreds of
megabyte range. We're looking for a solution that will
automatically delete these log files before they accumulate beyond
control.
What might be available to handle this, such as a solution
that will delete old log files after a certain limit is reached?
We are running CF MX 7.02 on Window 2003 OS.

videveloper wrote:
> Log files having a file name of {servername}-out
n.log (where
n is
> a numeric identifying separate log files) accumulate in
great numbers in the
> folder, \JRun4\logs\. Some log files appear to expand
beyond their typical
> 200kb size into the hundreds of megabyte range. We're
looking for a solution
> that will automatically delete these log files before
they accumulate beyond
> control.
>
> What might be available to handle this, such as a
solution that will delete
> old log files after a certain limit is reached?
Did you try the JRun update:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=8698aeb8
Jochem
Jochem van Dieten
Adobe Community Expert for ColdFusion

What is the purpose of standby redo log files

Hi,
What is the purpose of the standby redo log files in DR?
what if the standby redo log files are created? or else not created?
Please explain
Thanks

3.1.3 Configure a Standby Redo LogA standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.>
Reference http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
HTH
Anand

What to do about error msg: Warning: SUID file "System/Library/Core/Services/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDA gent"has been modified and will not be repaired" on MacBook Air.

What to do about error msg in Disk Utility on MacBook Air:
Warning: SUID file “System/Library/Core/Services/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDA gent"has been modified and will not be repaired.”

As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 onwards:
http://support.apple.com/kb/TS1448
Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard onwards changed the location of a number of system components.
Poster rccharles has provided this description of what it all means:
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
| | |
| | all other users not in first two types
| |
| group
|
owner

About unable to initialize log file!

Hi,
I insatll the Sun Java communications suite 5 in one linux host.
When I restart web server, I got the following error, would you please give me a hand ?
Thank you in advance.
*# /var/opt/sun/webserver7/https-comms.swabplus.com/bin/stopserv*
server has been shutdown
*# /var/opt/sun/webserver7/https-comms.swabplus.com/bin/startserv*
Sun Java System Web Server 7.0 B12/04/2006 08:17
warning: CORE3283: stderr: Java HotSpot(TM) Server VM warning: Can't detect initial thread stack location - find_vma failed+_
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_09] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [com5.my.com] at [amserver]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [com5.my.com] at [ampassword]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [com5.my.com] at [amcommon]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [com5.my.com] at [amconsole]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [com5.my.com] at [da]
info: WEB0100: Loading web module in virtual server [com5.my.com] at [commcli]
info: url: jar:file:/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class
info: url: jar:file:/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class
info: LogFile is: //var/opt/sun/mfwk/logs/instrum.%g_
warning: Warning: unable to initialize log file!+_
warning: Couldn't get lock for //var/opt/sun/mfwk/logs/instrum.%g+_
info: group = 227.227.227.1, port = 54320
info: Set Time-to-live to 0
info: join Group /227.227.227.1
info: Starting listening thread
info: sends initial RESP message in SDK
info: HTTP3072: http-listener-1: http://com5.my.com:80 ready to accept requests
info: CORE3274: successful server startup

This happens when you install web server as "non-root" and start the instance as "root".
If you can avoid this, you can get around of
warning: CORE3283: stderr: Java HotSpot(TM) Server VM warning: Can't detect initial thread stack location - findvma failed_*
The cause for log file initialization problem appears to be some permission problem.
Can you get back once you take care of what suggested above.

What's the command to dump archived log file?

Could someone share if you remember? I forgot the syntax. Thanks alot.

Are you referring to extracting data from the archive log files? If so, you should refer to this Using LogMiner.

What to do about one greyed-out album?

Every other song on my iTunes is fine but this one album will not load onto my iPod.
I've deleted it and re-loaded it back into my iTunes several times but it still shows up grey.
Is there any way I can fix this so it is able to be loaded onto my iPod without deleting or refreshing my whole iTunes library?
I'm not using a mac.

You cannot rotate the stdout file unless you are starting weblogic as windows service.
Link : http://e-docs.bea.com/wls/docs81/adminguide/winservice.html#1188735
You can use third party log rotation utilities in unix platforms :-
http://linuxcommand.org/man_pages/logrotate8.html

Error in Tomcat catalina.out log file -

What do i need to do to recover from the error below:
INFO: Server startup in 83095 ms
17-12-10 11:04:40:432 - [/InfoViewAppActions].[jsp] Thread [http-443-Processor24]; Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
     at org.apache.jsp.jsp.InfoView_005fListing.infoviewListing_jsp._jspService(infoviewListing_jsp.java:253)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)

Please check if you have multiple versions of java/JRE installed on your BOBJ server. Which OS did you install the BOBJ server on?
Regards,
Stratos

How to rotate .out ( stdout) log file in weblogic 9.2 (solaris/linux).

Hi,
Is there a way we can rotate .out log file.
I have written a shell script which will backup the log file and dump .out file.
#!/bin/bash
FILE=/opt/bea10/user_projects/domains/wl102xdomain/servers/ManagedServer1/logs/ManagedServer1.log
if cp $FILE ${FILE}.`date +%m%d`; then
cp /dev/null $FILE
fi
and run this as cron job
Can we use this ? (cp /dev/null), this will dump the .out file with out restarting the server.
Thanks,
Krishna.

Yes John.. i am using startNodemanager.sh.
Is this the change OutFile=$ServerDir/logs/$ServerName.out you are talking about.
wlscontrol.sh file:
# Directory and file names
ServerDir=$DomainDir/servers/$ServerName
SaltFile=$DomainDir/security/SerializedSystemIni.dat
OldSaltFile=$DomainDir/SerializedSystemIni.dat
StateFile=$ServerDir/data/nodemanager/$ServerName.state
PropsFile=$ServerDir/data/nodemanager/startup.properties
PidFile=$ServerDir/data/nodemanager/$ServerName.pid
LockFile=$ServerDir/data/nodemanager/$ServerName.lck
BootFile=$ServerDir/security/boot.properties
RelBootFile=servers/$ServerName/security/boot.properties
NMBootFile=$ServerDir/data/nodemanager/boot.properties
RelNMBootFile=servers/$ServerName/data/nodemanager/boot.properties
OutFile=$ServerDir/logs/$ServerName.out
SetDomainEnvScript=$DomainDir/bin/setDomainEnv.sh
StartWebLogicScript=$DomainDir/bin/startWebLogic.sh
MigrationScriptDir=$DomainDir/bin/service_migration
Thanks,
Krish

Limit Informational Scheduler entries in coldfusion-out.log

I recently upgraded to Coldfusion 9.
My {cfroot}/runtime/log/coldfusion-out.log files are being overrun by Informational messages.
01/04 00:57:00 Information [scheduler-6] - Starting HTTP request {URL='http://localhost:80/Reports/Prep/Production/Downtime/Files/Prep_Status.cfm', method='get'}
01/04 00:57:00 Information [scheduler-0] - Starting HTTP request {URL='http://localhost:80/Reports/Conf_Fin/Production/Status/Shop_Status_Grid1.cfm', method='get'}
01/04 00:57:00 Information [scheduler-7] - Starting HTTP request {URL='http://localhost:80/Reports/Prep/Production/Downtime/Files/Prep_Status.cfm', method='get'}
01/04 00:57:00 Information [scheduler-1] - Starting HTTP request {URL='http://localhost:80/Reports/Conf_Fin/Production/Status/Shop_Status_Grid1.cfm', method='get'}
01/04 00:57:00 Information [scheduler-0] - HTTP request completed {Status Code=200 ,Time taken=937 ms}
01/04 00:57:01 Information [scheduler-1] - HTTP request completed {Status Code=200 ,Time taken=1453 ms}
01/04 00:57:02 Information [scheduler-6] - HTTP request completed {Status Code=200 ,Time taken=2078 ms}
I have tdisabled scheduler logging in the ColdFusion Administrator and restarted the service. This only managed to stop logging to the {cfroot}/log/scheduler.log
I have managed to increase the size of the log file from 200k to a more manageable 2M using the
{cfroot}/bin/jrunsvc.exe -logfilesize 2000 "ColdFusion 9 Application Server"
What I am looking for is a way to suppress the Information [scheduler-#] Starting HTTP request and request completed messages.
I can see from my previous CF8 logs that it can be done.
I wish I could dig up my notes on how I did that.

I don't know the answer to your question. But I do know where I'd start looking for it - in the JRun 4 docs. For example, here's a link that discusses managing logging:
http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/logging4.htm
Dave Watts, CTO, Fig Leaf Software

Coldfusion-out.log

Does anyone know how to set up the CFAdmin to archive and
create a new coldfusion-out.log file after it reaches a certain
size? Our log file gets very large fairly quickly, and I believe is
causing the server to slow down.
In order to rename and create a new log file, we have to stop
the CF services, rename the file manually, and then restart the
services. This is a problem on a production server.

Oops - even better:
http://www.adobe.com/go/8698aeb8
Ken Ford
Adobe Community Expert
Fordwebs, LLC
http://www.fordwebs.com
"Ken Ford - *ACE*" <[email protected]> wrote in
message news:f1edev$ln2$[email protected]..
>
http://www.coldfusionmuse.com/index.cfm/2006/5/3/log.file.lock.fix
>
> Add a scheduled task to run the page with the code:
>
> <Cffile
> action="WRITE"
> file="*path*\logs\coldfusion-out.log"
> output="## Created by Bob, May 3, 2006"
> addnewline="yes"
> />
>
> --
> Ken Ford
> Adobe Community Expert
> Fordwebs, LLC
>
http://www.fordwebs.com
>
>
> "BD Hokie" <[email protected]> wrote in
message news:f1e4jf$c9o$[email protected]..
>> I'm having the same issue. I either need to be able
to control the log size or relocated the log file to a different
drive.
>> Thanks in advance for any help.
>

Need help to figure out default location of import log file

I imported the dmp file using the following command
$ imp <name>/<password> file=<pathname> FULL=Y
I got the following message after completion
"import terminatted sucessfully with warnings"
Can anyone help me where the log files would be put and what could be the probable name of log file.
Thanks in advance.
Regards,
Raj

Thanks a lot. I reimported the database with the log file location part of imp command

System.out logging

Hi,
I want to identify in which class of BI Beans does the logging of System.out is done. I want to customize the system.out logging, so that all such log entries move into my specified log file instead of server's system.out log file. Can any1 help?
Regards

2. The problem with the above solution is that myapp
has mulitple packages. This means that I have to
import the LogWriter to use it in any file that isnot
in the package where LogWriter resides.Why is that a problem?Maybe nuisance is a better word. It just seems like there should be a way to support a class which can be accessed (without using import) by all sub-packages of a given package.
Btw, Thanks for the other reference... I'm looking into it right now.
J

What to do about NodeManager's .out log file?

Similar Messages

Maybe you are looking for