Which log level to use?

My /etc/conf.d/crond                                                                                 
# Parameters to be passed to crond
CROND_ARGS="-S -l info"
From the crond man page:
-l loglevel
log events <= this level. The default is `notice' (level 5). Valid level names are as
described in logger(1) and syslog(3): alert, crit, debug, emerg, err, error (deprecated
synonym for err), info, notice, panic (deprecated synonym for emerg), warning, warn
(deprecated synonym for warning).
I looked at the logger and syslog man pages but didn't find a description of these levels.  Google didn't help much either.  Anyone?  I want to avoid seeing an entry in my /var/log/crond.log each time a script I asked to run actually runs.  For example, both of these runs once per minute on my machine making my log file huge:
Jun 13 16:02:01 reborn crond[2893]: FILE /etc/cron.d/monitorix USER root PID 26996 /usr/sbin/monitorix.pl update
Jun 13 16:02:01 reborn crond[2893]: FILE /var/spool/cron/root USER root PID 26997 /root/bin/autocheck_mount > /dev/null 2>&1
Jun 13 16:03:01 reborn crond[2893]: FILE /etc/cron.d/monitorix USER root PID 27020 /usr/sbin/monitorix.pl update
Jun 13 16:03:01 reborn crond[2893]: FILE /var/spool/cron/root USER root PID 27021 /root/bin/autocheck_mount > /dev/null 2>&1
Jun 13 16:04:01 reborn crond[2893]: FILE /etc/cron.d/monitorix USER root PID 27044 /usr/sbin/monitorix.pl update
Jun 13 16:04:01 reborn crond[2893]: FILE /var/spool/cron/root USER root PID 27045 /root/bin/autocheck_mount > /dev/null 2>&1
Jun 13 16:05:01 reborn crond[2893]: FILE /etc/cron.d/monitorix USER root PID 27068 /usr/sbin/monitorix.pl update
Jun 13 16:05:01 reborn crond[2893]: FILE /var/spool/cron/root USER root PID 27069 /root/bin/autocheck_mount > /dev/null 2>&1
Jun 13 16:06:01 reborn crond[2893]: FILE /etc/cron.d/monitorix USER root PID 27114 /usr/sbin/monitorix.pl update
Jun 13 16:06:01 reborn crond[2893]: FILE /var/spool/cron/root USER root PID 27115 /root/bin/autocheck_mount > /dev/null 2>&1
Last edited by graysky (2010-06-16 11:13:23)

Trial an error!
try -f with the following: alert, crit, debug, emerg, err, info, notice, warning
until desired result. (redundant ones removed for your convenience)
By looking at the names I would guess that warning, err, crit, and emerg would show less respectively. The rest spill more with debug showing everything possible.

Similar Messages

  • ODI Log Level

    Hi,
    I am looking for a description of ODI Log Levels.
    I know that the log level controls the details of the log output in ODI operator, but does exists some more detailed documentation about it?
    I would need information like what details are shown in which log level.
    Thanks in advance!
    Cheers,
    H.

    It is important to understand that the way odi works, it uses the "log" to drive all executuions. When you start a scenario, it copies eachof the steps of the scenarios into the execution log with the session ID, and wih a status of Waiting. As it executes each, it marks it as being executed, and when complete, marks it as completed (in or or successfully). When it has executed all the steps, it will go back to the log and selectively delete the entries there. When you execute the scenario, you execute it with a log-level of 0-5, and ODI will basically delete all entries in the log with a level > your chosen level. If you inspect the steps of a KM, Procedure etc, you will see that each has a log-level associated with it. This is what will decide if it is to be kept or not.
    If the session ends in failure, it will keep all the entries.

  • Ojdeploy + log level

    Hi,
    How can I specify logging thresholds for the ojdeploy tool ? I tried $JDEV_HOME/jdev/bin/jdev-logging.conf but didn't work. I'm using Jdev 11g.
    Thanks
    Suraj

    No issues I'm aware of. What is the general log level set to, and are any other categories set? Finest includes all levels below it, so Finer, Warning etc message levels will still get logged for the SQL category. If a category is not set, the general log level is used (try getSessionLog().getLevel() or getLevelString() to see the value). Which logger are you using?
    Best Regards,
    Chris

  • Apache log level (dontlog)

    Hello folks,
    I'm using Oracle application server 10.1.2 and am trying to cut down the logging in the Apache access_log files. I would like to not see lines for example like this :
    172.22.69.87 - - [25/Aug/2005:12:12:51 +0100] "GET /services/images/services_o.gif HTTP/1.1" 404 358
    I tried a bunch of regular expressions in httpd.conf but nothing seems to stop the logger.
    Example : SetEnvIf Request_URI "^(.*)\/services\/(.*)$" dontlog
    According to the Apache doc (see example below) something like this should work :
    # Mark requests for the robots.txt file
    SetEnvIf Request_URI "^/robots\.txt$" dontlog
    Any suggestions ? Any examples welcome !
    Mark.

    No issues I'm aware of. What is the general log level set to, and are any other categories set? Finest includes all levels below it, so Finer, Warning etc message levels will still get logged for the SQL category. If a category is not set, the general log level is used (try getSessionLog().getLevel() or getLevelString() to see the value). Which logger are you using?
    Best Regards,
    Chris

  • Setting log level of an appender

    I have 2 appenders in my logger.
    mergeLogger.addAppender( consoleAppender );
    mergeLogger.addAppender( fileAppender );
    to set the log level I use logger.setLevel( XX ) but this applies to all appenders
    Is it possible to set the logging level for each appender to different levels?

    Have you read the log4j documentation?

  • The problem about  the Log Level

    Hi everyone,
    The Log Level of Oracle Application Server includes NULL,Severe,Warning,Info,Config,fine,finer,finest.
    Which log level is the highest ?
    I want to get more message about My Esb instances,How to set the log level ?

    finest is the highest level logging and can either be turned on for all logs or just specific logs within the Enterprise manager.

  • I want to set-up a network with our current two laptops for a family of 4 w/unique 4 profiles. I'd like everyone to be agnostic about which computer to log into and use but still have private docs and apps (i.e.mail/facebook). How best can I do this?

    I want to set-up a network with our current two laptops for a family of 4 with unique 4 profiles.  I'd like everyone to be agnostic about which computer to log into and use but still have private docs and apps (i.e. mail/facebook).  How best can I do this?

    iCloud Photo Sharing FAQ - Apple Support
    http://www.fatcatsoftware.com/iplm/Help/accessing%20an%20iphoto%20library%20on%2 0another%20mac.html

  • Using log4j to create custom log level in standalone batch application

    Hi all,
    I would like to use Log4j to create a custom log level so that from my standalone java batch process application, whatever error messages I can log to a log file.
    Can any one give me any pointer on this.
    Appreciate any help.

    This doesn't seem to warrant a 'custom level'. Just use Log4J as is... create a Logger object and use its error() or warn() or whatever methods are appropriate for the logging you want to do. I don't understand the reason for the question.

  • How to log the exception using Log action in Oracle Service Bus

    Hi,
    Whenever an exception is raised how to log the exception using Log action in oracle service bus.After logging where I have to find the logged message.

    It would be in the log file for the managed server which ran the request. If you are logging the message at a lower level than your app server, however, you won't see it. You should be logging the exception at Error level.

  • Implement row-level security using Oracleu2019s Virtual Private Databases (VPD)

    Environment: Business Objects XI R2; Oracle 10g
    Functional Requirement:
    Implement row-level security using Oracleu2019s Virtual Private Databases (VPD) technology. The restriction is that the Business Objects Universe connection should use a generic/u201Capplicationu201D database user account. This will allow the organization to avoid the situation where the Business Objects password and the Oracle password need to be kept in synch.
    What do we need from the Business Objects support team?
    1.     Review the 2 attempted solutions that we have tried to implement
    2.     Propose solutions/answers to open questions for each of the attempted solutions
    3.     Propose any alternate solution that will help us implement the Function Requirement stated above
    Attempted Solution 1: Connection String uses Oracle Proxy User
    The connection string that is specified in the Universe is the following:
    app_user[end_user]/app_user_pwdarrobaDatabase.WORLD
    app_user = generic application user
    end_user = the oracle account of the end user which is set using arrobaVariable('BOUSER') app_user_pwd = password of the generic application user
    We have tried and implemented this in our test environment. However, we have some questions and concerns around how the connections are reused in a connection pool environment.
    Open Question for Solution 1:
    i. What happens when multiple proxy users try to connect on at the same time?  Business Objects shares the generic app_user connect string.  However, every user that logs on will have their own unique proxy user credentials.  Will there be any contention involved?  If so, what kind of errors can we expect?
    ii. If a user logs on using his credentials (proxy user), and business objects opens up a connection to the database using that user's credentials (as the proxy user but logging in through the generic app user). Then the user exits out --> based on our test today, it seems like the database connection remains open.  In that case, if another user logs on similarly with their credentials, will business objects simply assign the first users connection to that second user?  If so, then our security will not work.  Is there a way that Business Objects can somehow ensure that everytime we close a report, the connection is also terminated both at the BO and DB levels?
    iii. Our 3rd question is general high level -> How connection pooling works in general and how it is implemented in BO, i.e. how are new connections assigned, how are they recycled, how are they closed, etc.
    Attempted Solution 2: Using the ConnectInit parameter
    Reading through a couple of the Business Objects documents, it states that u201CUsing the ConnectInit parameter it is possible to send commands to the database when opening the session which can be used to set database specific parameters used for optimization.u201D
    Therefore, we tried to set the parameter in the Universe using several different options:
    ConnectInit = BEGIN SYSTEM.prc_logon('arrobaVARIABLE('BOUSER')'); COMMIT; END; ConnectInit = BEGIN DBMS_SESSION.SET_IDENTIFIER('arrobaVariable('BOUSER')'); COMMIT; END;
    Neither of the above iterations or any variation of that seemed to work. It seems that the variable is not being set or being u201Cexecutedu201D on the database.
    One of the Business Objects documents had stated that Patch ID 38, 977, 350 must be installed in our BO environments. We have verified that this patch has been applied on our system.
    Open Questions for Solution 2:
    How do we get the parameter ConnectInit to work? i.e. what is the proper syntax to enter and what other things do we need to check to get this to work.
    Note: Arroba word is being used instead of the symbol in order to avoid following error message:
    We are sorry but your message can not be posted since you have included an email address. Please remove the email address and re-post.

    the connectinit setting should look something like this:
    declare a date; begin vpd_setup('@VARIABLE('BOUSER')'); Commit; end;
    The vpd_setup procedure (in Oracle) should look like this:
    CREATE OR REPLACE procedure vpd_setup (p_user varchar)IS
    BEGIN
      DBMS_SESSION.set_vpd( 'SESSION_VALUES', 'USERID', p_user );
    END vpd_setup;
    Then you can retrieve the value of the context variable in your vpd functions
    and set the vpd.

  • Logging with whereabouts using open source and freeware

    You can find the html version of this at:
    http://www.acelet.com/whitepaper/loggingWithWhereabouts.html
    Logging with whereabouts using open source and freeware
    The purpose of logging is to find out what had happened when needed. When the
    time comes to read log messages, you want to know both the log message and its
    whereabouts (class name, method name, file name and line number). So you need
    to hard code whereabouts.
    But hard coded whereabouts are very difficult to maintain: when you modify your
    source code, line number changes; when you copy and paste a line, its class name
    and method name change. If whereabouts are wrong, you introduce bugs in your logging
    logic and the log messages are useless at the best.
    This article shows you an example of using freeware Redress tool to rectify whereabouts
    programmatically in your Makefile or Ant build file. So your whereabouts are always
    correct for both Java and JSP source file.
    Redress tool is part of SuperLogging at http://www.ACElet.com. SuperLogging also
    provides an open source wrapper Alog.java, which redirects log method calls to
    your favorite logging package. Redress tool can rectify whereabouts information
    on all Alog's method calls in your application. So, if you call Alog's log methods,
    these calls will be rectified by Redress.
    JDK 1.4 introduces a new utility package java.util.logging. The example in this
    article is based on JDK logging. Log4J is a cousin of JDK logging. Log4J users
    should have no difficulties to modify this example for Log4J. Both JDK logging
    and Log4J are excellent logging software for single JVM.
    Note: Redress tool rectifies method calls on Alog, not JDK logging. You need to
    call Alog instead of JDK logging in your application.
    Source code of Alog.java
    The following is the source code of Alog's JDK logging version. It serves as an
    library file and should be on your CLASSPATH:
    * Copyright Acelet Corp. 2000. All rights reserved
    * License agreement begins >>>>>>>>>> <br>
    * This program (com.acelet.opensource.logging.Alog) ("Software") is an
    * open source software. <p>
    * LICENSE GRANT. The Software is owned by Acelet Corporation ("Acelet").
    * The Software is licensed to you ("Licensee"). You are granted a
    * non-exclusive right to use, modify, distribute the Software for either
    * commercial or non-commercial use for free, as long as: <br>
    * 1. this copyright paragraph remains with this file. <br>
    * 2. this source code (this file) must be included with distributed
    * binary code.<br>
    * NO WARRANTY. This comes with absolutely no warranty. <p>
    * <<<<<<<<<< License agreement ends <p><p>
    * The purpose of releasing this open source program is to prevent vendor
    * lock in. <p>
    * You can code your program using this class to indirectly use Acelet
    * SuperLogging (com.acelet.logging). If later you want to swith to other
    * logging package, you do not need to modify your program. All you have
    * to do is: <p>
    * 1. modify this file to redirect to other logging packages. <br>
    * 2. replace existing com.acelet.opensource.Alog with your modified one. <br>
    * 3. you may have to reboot your EJB server to make the changes effect.<br>
    * <p>
    * This program is just a wrapper. For detail information about the methods
    * see documents of underline package, such as com.acelet.logging.Logging.
    * <p>
    * Visit http://www.ACElet.com for more information.
    * <p>
    * This file is a modified for using JDK logging as an EXAMPLE.
    * <br>
    * You can use Redress tool to keep your whereabouts information
    * always correct. See http://www.ACElet.com/freeware for detail.
    * <p>
    * Please see http://www/ACElet.com/opensource if you want to see the
    * original version.
    package com.acelet.opensource.logging;
    import java.util.logging.*;
    public final class Alog {
    * Log level value: something will prevent normal program execution.
    public static int SEVERE = 1000;
    * Log level value: something has potential problems.
    public static int WARNING = 900;
    * Log level value: for significant messages.
    public static int INFO = 800;
    * Log level value: for config information in debugging.
    public static int CONFIG = 700;
    * Log level value: for information such as recoverable failures.
    public static int FINE = 500;
    * Log level value: for information about entering or returning a
    * method, or throwing an exception.
    public static int FINER = 400;
    * Log level value: for detail tracing information.
    public static int FINEST = 300;
    static Logger logger;
    static {
    logger = Logger.getLogger("");
    public Alog() {
    public static void alert(String subject, String message) {
    public static void error(String text, int level, String fullClassName,
    String methodName, String baseFileName, int lineNumber) {
    String[] para = {lineNumber + "", baseFileName};
    logger.logp(getLevel(level), fullClassName, methodName, text, para);
    public static Level getLevel(int levelValue) {
    if (levelValue == SEVERE)
    return Level.SEVERE;
    else if (levelValue == WARNING)
    return Level.WARNING;
    else if (levelValue == INFO)
    return Level.INFO;
    else if (levelValue == CONFIG)
    return Level.CONFIG;
    else if (levelValue == FINE)
    return Level.FINE;
    else if (levelValue == FINER)
    return Level.FINER;
    else if (levelValue == FINEST)
    return Level.FINEST;
    else
    return Level.ALL;
    public static void log(String text, int level, String fullClassName,
    String methodName, String baseFileName, int lineNumber) {
    String[] para = {lineNumber + "", baseFileName};
    logger.logp(getLevel(level), fullClassName, methodName, text, para);
    public static void sendMail(String to, String from, String subject,
    String text) throws Exception {
    public static void sendMail(String to, String cc, String bcc, String from,
    String subject, String text) throws Exception {
    Test program
    The simple test program is Test.java:
    import com.acelet.opensource.logging.Alog;
    public class Test {
    public static void main(String argv[]){
    Alog.log("Holle world", Alog.SEVERE, "wrongClassName", "wrongMethod",
    "wrongFileName", -1);
    How to run the test program
    1. Compile Alog.java (JDK 1.4 or later, not before):
    javac Alog.java
    2. Download freeware Redress tool from http://ACElet.com/freeware.
    3. Run Redress tool:
    java -cp redress.jar Test.java
    4. Check Test.java. The Alog.log method call should be rectified.
    5. Run test program:
    java Test
    You should see log message with correct class name and method name.

    Hi;
      I found this code and would like to share it with you :
    JCoDestination destination = JCoDestinationManager
      .getDestination(DESTINATION_NAME2);
      JCoFunction function = destination.getRepository().getFunction(
      "RFC_FUNCTION_SEARCH");
      if (function == null)
      throw new RuntimeException("RFC_FUNCTION_SEARCH not found in SAP.");
      function.getImportParameterList().setValue("FUNCNAME", "*");
      function.getImportParameterList().setValue("GROUPNAME", "*");
      try {
      function.execute(destination);
      JCoTable funcDetailsTable = function.getTableParameterList()
      .getTable("FUNCTIONS");
      int totalNoFunc = funcDetailsTable.getNumRows();
      if (totalNoFunc > 0) {
      for (int i = 0; i < totalNoFunc; i++) {
      System.out.println("Function Name: "
      + funcDetailsTable.getValue(i));
      } catch (AbapException e) {
      System.out.println(e.toString());
      return;
      System.out.println("RFC_FUNCTION_SEARCH finished");
    It is working and retrieving FM.
    Regards
    Anis

  • Log Levels

    Hi,
    In my application I use a lot of info/debug printouts with the method log which writes to the appservers (sun appserver 8) log file (server.log). Log method called with a string (log("message")) seems to give Log Level INFO in server.log. Now I want to get rid of the info messages without actually removing them from the source code. Easy, I thought, just to change Log Level from INFO to WARNING for module Web Container in the appserver (with admin console) because the help page says "The default level is INFO, meaning that messages at that level or higher (WARNING, SEVERE) will appear in the log". The result was not what I expected, the log posts did not disappear, instead the log level changed from INFO to WARNING!!!
    In my next try, I used System.out.println for my info messages instead of method log. This also writes log posts, with log level INFO, to server.log with logger name javax.enterprise.system.stream.out. To turn off the logs the help page says "specify the logger name with the value OFF in the Additional Properties area". That is exactly what I did (yes, I also restarted the appserver) but the log posts are still written to server.log.
    No more ideas.
    Am I misunderstanding something, bugs in appserver or what?
    Regards
    Mats

    Maybe you need to implement Java Logging in your application. Check out the below URL for more details :
    http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/
    Once you have implemented Java logging, you need to edit either <jdk_home>/jre/lib/logging.properties and include something like this :
    com.util.level = INFO
    com.servlet.level = SEVERE
    (Assuming com.util and com.servlet and two packages in your application, all Java classes in com.util will log only INFO and above messages and all Java classes in com.servlet will log only SEVERE messages).
    Alternatively, you can also add the above properties in the Logger Settings tab from the admin GUI.
    Hope that helps
    Cheers,
    Vasanth

  • Scenario execution with log level Zero

    I am executing the scenarios with log level zero, but it purges the operator logs on successful execution. With log level Zero, is it possible to stop the automatic purge of the operator logs on successful execution?

    I just get "SnpSession does not exist" error on this, this error is generated if we don't have an entry for that scenario in SNP_Session table. However, ODI if is provided with log level 0 deletes corresponding entries from SNP_Session table on successful completion of a scenario. Which is also happening in my case and entries are being deleted from table for Scen B and Scen C, but since Scen fails it remains in the table. Again, Once I have gotten the log_level in a variable in Scen A i am just making use of that variable in the subsequent scenarios. Also, when executed with log level 1, 2, 3, 4, 5 it works jolly good.

  • Which tool do you use for load testing?

    Which tool do you use for load testing for J2EE application?

    hi,
    i use jmeter for without issues..
    first make sure that the system from where you are doing load testing is in the same lan(without firewall) to that of server. Here you are testing the capacity of server and not the network bandwith.
    So assuming very good network connection what is the servers performance level...
    If u have to decide which tool is decent enough to load testing,
    i would suggest go for jmeter. its reliable and i have used it without problems.
    Here is my quick tutorial for jemeter which i made for my teams reference.
    REFERENCE
         For Getting Started refer to any tutorial for Jmeter
         You can refer to introduction on
              http://jakarta.apache.org/jmeter/usermanual/
    RUNNING LOAD TEST
         Extract jakarta-jmeter-2.3RC4.zip in c:
         install jdk-1_5_0_12-windows-i586-p.exe
         Run C:\jakarta-jmeter-2.3RC4\bin\jmeter.bat
         In Test Plan add Thread Group
         Right Click Thread Group -> Add->Sampler->HTTP Request
         Select HTTP Request added fill details
              Serverip:www.xyz.com
              Port:80
              Path:/xyz-webapp/index.jsp
              Use KeepAlive: Checked
              Retrive All Embeded images from HTML: Checked(For geting images inside html)
         Right Click Thread Group -> Add->Listner->Graph Results
         Click on Thread Group Fill details
              No of Threads:3(This means no of simultaneous users)
              Ramp Up Period:1(3 Request will be made in 1 second period)
              Loop Count:5(Above process should be repeated how many times)
         Save TestPlan
         Run -> Clear All
         Run -> Start
              Click on Graph Results for Output
         Try adding different listener in Thread Group
              Thread Group -> Add->Listner->Summary Report
         Listeners coud be added at thread group level or HTTP Request Level
    RECORDING A TEST.
         Add a HTTP proxy server in workbench by right clicking on it and selecting Add->Non test Element->HTTP Proxy Server.
         In Test Plan Add Thread Group
         In HTTP proxy server select Target Controller as Test Plan > Thread Group.
         Go to Internet Explorer and go to internet settings and set proxy server as localhost and the port
              which is configured in Jmeter proxy server.Save Settings.
         In Jeter proxy server start by Clicking on Start button in the HTTP Proxy Server Flap.
         In browser navigate the application which you want to test.
         The nodes will be added in the Thread Group.
         Once Navigation is done stop the proxy server and save the test plan from file menu.
    LOGGING INTO APPLICATION.
         When we have to login into system and then navigate the system
              we need a cookie to be tracked after login. This could be achieved
              simply by Add -> Config Element -> HTTP Cooie Manager.
         After adding the HTTP Cooie Manager simply run the test.
    LOOPING COUNTER.
         When a request is made multiple parameter is sent to server.
         Parameters are sent from the HTTP Request node added in the Thread Group
              in "Send Parameter with the request" table.
         If we run the loop count 10 times the parameters will be sent same in every request.
         If you have to send parameters like user1,user2,user3,user4....
              then add -> Pre processor -> Counter.
         Put start as 1 and and Maximum as 10 or whatever required.
         Put Referene name as iCtr or whatever.
         In the "Send Parameter with the request" in value column put user${iCtr}

  • Suggestions for changing logging levels?

    I'm looking at using the JDK 1.4 Logging API in my web application. I want the ability to selectively change the logging level for my application component loggers (not the global logging level) without recompiling and redeploying my code. I can live with having to restart my web container.
    As I understand the documentation, the API provides 3 options for customizing logging properties:
    1) Modifying the default logging.properties file in the JRE lib folder, which is not workable for a application component for a number of reasons.
    2) Specifying an alternative properties file when the JVM is started, which is not workable because my web app doesn't start the container.
    3) Specifying a class that acts as the property file loader, again not workable because my web app is only one of many running in my container.
    Additionally, the API docs are not clear on the effect of calling the LogManager method readConfiguration(InputStream ins) with just my properties at some point in my application.
    Does anyone know a reasonable way of controlling logging levels in this fashion?

    Use log4j, and put the log4j.properties in the <webapp>/WEB-INF/classes directory.
    To use log4j, simply put log4j-x.x.x.jar into your <webapp/WEB-INF/lib directory. The java logging setup will automatically use it.

Maybe you are looking for