Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: kettle logging in the BI Server

  1. #1

    Default kettle logging in the BI Server

    Hi all,

    I am trying to trace down a problem I have with logging.

    The problem is that on the BI Server I am logging out to the PENTAHOFILE and CONSOLE appenders (I have not changed the config from the sourceforge download). I find after a certain amount of time the pentaho.log file no longer contains entries but catalina.log continues happily and contains warnings like

    log4j:ERROR Attempted to append to closed appender named [PENTAHOFILE].

    Restarting the tomcat fixes it, but it re-occurs regularly. After some trial and error I believe it is being caused by running any report which uses kettle as a data source (since I had reports of this nature scheduled through kettle transforms the logging would break regularly).

    I can get around this, by using scheduled kettle jobs to import data to a common location and then change the report to use SQL over that location rather than the kettle source over multiple data sources but it would be nice to understand the problem.

    Reading around the subject I understand that kettle has its own log4j file in the jar and logging classes which build on log4j (new levels etc) and override some of the behavior defined in the log4j file including forcing a console appender if one cannot be found.

    I don't know how to go about proving whether this is right or wrong but my best guess is that for some reason the LogWriter is deciding an appropriate appender cannot be found, creates a new console appender (hence the output to Catalina.out continues happily) and the PENTAHOFILE appender is lost somewhere.

    Can anyone with more experience of this suggest anything?

    Thanks,
    James

  2. #2
    Join Date
    Mar 2012
    Posts
    28

    Default Similar Issue

    I am facing similar issue with our pentaho BI Server. The logging stops in pentaho.log however it continues in catalina.out with the error
    log4j:ERROR Attempted to append to closed appender named [PENTAHOFILE].

    In addition to this, the pentaho BI server occupied memory( checked using TOP command) is shooting up very seriously and the application needs to be restarted to ensure proper functioning of BI Server. The version of pentaho BI Server is 4.1.0.

    Can someone please help??

    Thanks




    Quote Originally Posted by jswinnerton View Post
    Hi all,

    I am trying to trace down a problem I have with logging.

    The problem is that on the BI Server I am logging out to the PENTAHOFILE and CONSOLE appenders (I have not changed the config from the sourceforge download). I find after a certain amount of time the pentaho.log file no longer contains entries but catalina.log continues happily and contains warnings like

    log4j:ERROR Attempted to append to closed appender named [PENTAHOFILE].

    Restarting the tomcat fixes it, but it re-occurs regularly. After some trial and error I believe it is being caused by running any report which uses kettle as a data source (since I had reports of this nature scheduled through kettle transforms the logging would break regularly).

    I can get around this, by using scheduled kettle jobs to import data to a common location and then change the report to use SQL over that location rather than the kettle source over multiple data sources but it would be nice to understand the problem.

    Reading around the subject I understand that kettle has its own log4j file in the jar and logging classes which build on log4j (new levels etc) and override some of the behavior defined in the log4j file including forcing a console appender if one cannot be found.

    I don't know how to go about proving whether this is right or wrong but my best guess is that for some reason the LogWriter is deciding an appropriate appender cannot be found, creates a new console appender (hence the output to Catalina.out continues happily) and the PENTAHOFILE appender is lost somewhere.

    Can anyone with more experience of this suggest anything?

    Thanks,
    James

  3. #3
    Join Date
    Sep 2007
    Posts
    834

    Default

    Hi,
    three years later...
    similar issue here! We don't have a Pentaho BI server running, but an own Tomcat application that runs PDI jobs. The behavior is similar.
    Anyone familiar with this who could help us? thank you
    (PDI: 4.4, PRD: 3.9)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.