Logging Console

EP6 sp2
We have a 3 server (6 nodes) production environment and we are trying to figure out why some nodes have much higher CPU usage than others. We looked at the logger.xml on each node and noticed that, on the nodes with high CPU utilization, that the logger.xml is set to do a LOT more logging (ALL, WARNING, SEVERE, etc) than the other servers. This probably happened during troubleshooting problems over the past year.
I read an article on help.sap.com that states we should do a find/replace through the logger.xml and replace "isActive" with "False" to turn off all logging to tune performance.
I dont know if we want to turn off all logging. Does anyone know of an article or reference as to what are SAP best practices for all of these log settings? I'd like to change it, then move the logger.xml file to all nodes to make sure each portal is set up exactly the same.
Thanks, and points for anything halfway helpful

Hi Brent,
Lowering the priority I would say seems to be far more reasonable than switching the logging off. At least SEVERE should be logged.
As long as you don't feel the need to be informed about "regular" things (INFO/WARNING), set the level to SEVERE. If the code uses the levels correctly, SEVERE loggings messages definitely should be something to worry about...
Hope it helps
Detlev

Similar Messages

Runtime error in Logging Console

Hi,
after upgrading to Portal 6.0 SP2 from Patch 3 to Patch 4 i get an Portal Runtime Error via System Administration -> Monitoring -> Portal -> Logging Console. (com.sap.portal.runtime.admin.logadmin.default)
I cannot start this component via the PortalAnywhere.Go either.
This has happened with three different installations already. The issue does not occur with the EP SP 2 Patch 4 from scratch installation.
Any ideas?
rgds Marcel

Guys,
thanks for the help. The behaviour of the hotfix installation (7) is unexpected. It's probably due to J2EE caching or my misunderstanding of the deployment architecture but here's what happened:
I installed hotfix 7 with SAPinst on portal A. After the J2EE restart this logadmin iview still did not work.
I then uploaded the component manually via de Cluster Administration Console Component and voila: it worked.
Then I went to another portal system (B) where I installed hotfix 7 also (with logadmin still not working either). This time I verified the version that was deployed and installed against the working one from A -> they were identical! I pressed the update button and voila the iview worked, but the version number remained the same!!
I now just redeployed all the par files by renaming them back from .bak to .par and hopefully all the fixes have been applied.
Can someone understand why this happened?

Logging console NW04s

Hi all,
I can't find the logging console in the NW04s portal.
I know it used to be in EP6 under: Sys. admin.-> Monitoring -> Logging console.
Where is it now ?
Thanks,
Elad.

Hello,
I still have this option under System Admin -> Monitoring in EP7. This gives me portal and KM logs.
If you need more system logs, you can check the NWA, /nwa
It contains the logs, however I believe you need to have the j2ee_admin priviliges.
regards,
Jørgen

Could not find Activity Tracing & Logging Console in EP

Hi All,
I have portal Admin rights and when I go to
<b>System Admnistrator>Monitoring>Portal</b>, I could not find
Logged on users, Activity Tracing, Logging Console in the Detailed Navigation. (but I could see and access Request Smmary, Request Overview, Component Overview, Thread Overview)
EP 6.0 SP11 is in use. Linux is the OS.
Does anyone know why I am unable to see all the iviews here.
Thanks for the help.
regards
suresh.

Hi Suresh,
In EP 6.0 SP2 these (logged on users, Activity tracing and logging console) options are available. But not available after that version. Only Request summary, Request overview, component overview, Thread overview are available.
Regards
Arun

How to use log console

how to use log console?

kilty66 wrote:
disk1s3: media is not present.
Video capture fps 13.056067 , requested 15
(com.conduit.loader.Agent[866]) Exited with code: 1
The first means something is missing, most likely on an external HD.
If the other two were sent at the same time, they're probably all related to a video capture problem.
Many of the messages you'll see in your logs don't indicate a real problem -- they'll be status messages, info for developers, etc., so don't try to figure out every message you see.
If you see the same message repeated over and over (as the MacKeeper ones probably did), that's clearly a problem, of course.
If you're having specific problems, but not getting messages on your screen, check for log messages that seem related (ie, sent at the same time, and/or from a process you recognize as being related). See the blue box in OSX Log Files for help deciphering the messages. If you're not sure about what a particular process does, many of the names of Apple processes are listed here: http://triviaware.com/macprocess/all with a brief explanation.
For other processes, or other references, Google will often turn up some info.
If none of that helps, post a new thread for each such problem, with as much detail as you can about what you were doing and what kind of difficulty you were having, and, of course, the message(s) that seem related.
Try to post them in the appropriate forum; if you're having a problem with a specific Apple app, there may be a forum for that app, where folks who know it well hang out.

Log console information to a log file

I am using the latest plug-in from sun (1.4) and I set the plugin.trace and plugin.logging options in the Java run time parameters of the console using the Control Panel as follows.
-Djavaplugin.trace=true -Djavaplugin.trace.option=5 -Djavaplugin.trace.filename=test.trace -Djavaplugin.logging=true -Djavaplugin.log.filename=test.log -Djavaplugin.outputfiles.overwrite=false
I do not see the message getting logged or the log file being created.
Any suggestions would help
Thanks
ah

akpattuka, having tried your run time parameters with plugin 1.4.2, i can tell you that they do not work here either. I have even tried setting -Djavaplugin.trace.option=ext as suggested by online help (not with numbers). Nothing. What does work for me is the following. While running your applet open the console window. Hit 'o' to enable logging, hit '5' to set the trace level. Hit the refresh button inside your browser. This will create a trace file and a log file.
HTH, Markus

Filtering system.log & console.loog

I have a few problems which I have been trying to find in console.log & system.log
I have a couple of applications which write a lot of entries here, which makes it very difficult to read.
Is it possible to filter events in console.log - saying for example that any entries from a certain application do not get shown - or is there a better application available for viewing these logs.
Thanks for any help...

The Console app has a filter box at the right of the toolbar.
If you don't see it, click the little lozenge button at the extreme upper right.
You might also want to click +Show Log List+ at the left of the toolbar, and navigate in the sidebar that produces -- there are a whole bunch of logs on your Mac.

Does Adobe Air have an Error logging console?

I have an issue with a specific AIR program that was working but now it's not. I went ahead and reinstalled my version of Air and when I launched the program it is just freezing, works for about 2 seconds. This AIR application uses login info to pass over an API and I'm wondering if it's possible that the data is corrupted causing the AIR program to freeze. Uninstalling and reinstalling has no effect and I've been looking to see if the AIR application uses a seperate folder to store the configuration. Could someone provide to me the filepath of the AIR profiles, or if it's possible to enable an error console for AIR, I'm not seeing anything in the event logs of any worth.
Your help is much appreciated.
Thanks,
Lucas

@RocknRollTim
Not in the manner of Maemo or MeeGo although not sure whether SmartInstaller for applications saves log upon this S60 5th Ed.device as in later devices, which is found in either c:\data\ovismartinstallerlog.txt or c:\ovismartinstallerlog.txt
Happy to have helped forum with a Support Ratio = 42.5

Mac OS 10.4.11 console.log.1 = 256 GB HDF filling up

My HD Is rapidly filling up. The only file that seems unusually large is
file:///Library/Logs/Console/501/console.log.1 = 256GB
This problem started within the last few weeks.
Any Ideas?

Just a guess but you could try and turn off or trash WeatherBug, or at least unload it as a login item, to see if that is the problem.

Console Log files taking up 7gb of space.

I am trying to clear up some space on an old eMac. I have come accross two log files one called console.log.0 which is taking up 1 gb, and console.log.3 which is taking up 5.8gb. Both of these files are located in Macintosh HD/Libary/Logs/Console/emac (emac is the username). What are these files for, and is there anyway I can take back this space?
Thanks, James.

go ahead and trash them. or open the Console app, and clear the log files.

Disable EEM console logging?

I currently have EEM running some applets, and they're working, but I cannot figure out how to suppress the messages popping up in the console. I send the output from a cli command to syslog using a watchdog timer.
I can do a "no logging console informational", but that shows up in the config as "no logging console"
event manager applet syslog
event timer watchdog time 180
action 1.0 cli command "show ip interface brief"
action 2.0 syslog priority informational msg "$_cli_result"
Is there a way to hide only the eem syslog traffic from the console?

No, you cannot do this other than lowering the logging level on the console. For example:
logging console 4

Can I delete my Console Log and be safe ?

Here's the file path
" Macintosh HD/Library/Logs/Console/501/console.log.2 "
for some reason this file "console.log.2 " is 31.33 GB in size
Would it be safe to delete it ?
Thanks
Greg
Mac Pro Mac OS X (10.4.10)

Hi Greg, that is huge! Yes, you can delete the log files. I'd leave the 501 Folder and console.log but delete the other contents. (Also be sure all that is in there are log files.)
-mj
[email protected]

Empty console.log

We have a 10.6.7 server, originally installed somewhere in 2009. After doing some diagnostics research today I noticed several things:
/Library/Logs/Console/$user/console.log hasn't been updated since 2009.
There's no asl.db in /private/var/log , however it does live in /private/var.
Syslog was also broken, though I got it working with the default syslog.conf and restarting the daemon.
I understand the logging services changed a lot since 10.4, so what's the current correct information:
Is console.log supposed to work, and what kind of logs is it supposed to contain?
Is my asl.db where it's supposed to be? Is it indicative of a problem?

Are you sure the support rep realizes you're on Mac OS X?
It's not uncommon for different OS versions to store logs in different places, so he might have thought you were on some Linux or other UNIX environment. As far as I recall there's never been a per-user console log.
The closest thing I can think of is the system log (/var/log/system.log on Mac OS X but could be different on other OSes).
The alternative is that this isn't a system-level log, but it's application-specific, in which case I wouldn't know about it unless I had the same app installed.
The last option I can think of is that if this is a per-user log (as your path name implies) it would generally be stored in the user's own Log directory at ~/Library/Logs/ but even then I don't see a console.log OMM.
At this point I think your only option is to go back to the support guy to ask for more detail.
As for where you learn/find this stuff, experience counts, as well as a willingness to explore.
There is a lot of commonality across various UNIX/Linux flavors, so many online resources can provide a hint, just be aware that each OS is a little different so don't be surprised/annoyed when someone says a log file should be in one place but Apple put it somewhere else.
Apple provide a lot of hints about their specific impementation in their developer programs, but don't publicise as much for mere mortals. Just to compound the issue, things change between OS versions (usually with no peon-level documentation or explanation) as is the case with the ASL logging moving from text-based to binary.
My advice: poke around and see. There's no danger or risk to just looking.

50 GB of console logs! Can I delete it?

Hi, I was just wondering why I head about 50 GB less harddrivespace and checked the folders and my root library folder was suddenly about 51 GB big!! I checked the folders and found that library/logs/console is 50 GB big. Inside the console folder are two folders - one folder named 501 with console.log files in it and an other named 502 which is protected. The 501 folder is the problem - and there specific on conole log named console.log.0
What is it for and can I delete it?
Best regards - Christoph

Thanks for the feedback. I suggest keeping an eye on the console.log to ensure whatever was growing the previously large, rotated log isn't still happening. <edited by host - see [url=http://discussions.apple.com/help.jspa#terms]Terms of Use, section 4.2.2[/url]>

Locked console logs, how to delete?

Having discovered that my CanoScan scanner is writing one line of meaningless information to the console log every second, I have resolved to delete the logs. However I'm now faced with a whole bank of log files numbered from 0, then 501 to 512. I can access and read 502 (and delete it? safely? it doesn't matter?) but the others are all locked, I don't even know how big they are.
How do I delete the locked console log files? Please note - I am in the top level Library, not my user Home Library where there are no Console logs.

Hi, this is the response from Terminal...
-rw------- 1 xxxxx admin 11404 Jan 29 10:14 /Library/Logs/Console/501/console.log
(Ignore the xxxxx). Does this mean anything to you? Does it tell me that the 501 log is 11404 bytes big? What about the other files which it didn't list?
Happily though, with no warning the problem seems to have disappeared for no reason I can find. The scanner continues to work ok, but there is nothing in Login Items (I didn't remove anything), and the message in Console log has stopped.
The only thing now is to delete all those other console logs, (500, and 503 - 512). And to find out how big they are, as the Terminal command only seemed to work for 501.

Logging Console

Similar Messages

Maybe you are looking for