Like what you see? Have a play with our trial version.

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Log Name

Directory Path

Description

YellowfinInstallLog-XXXX.log

(where XXXX is the date of installation)

Directly in Yellowfin application folder

This is the installation log file, and contains all the chosen installation options, along with any errors encountered during installing.

YellowfinPatchLog–XXXX.log

(where XXXX is the date the update was run)

 

This is the update installation log file, it contains update information (such as updating the database) and will capture any errors encountered.  You will have a log file for each update that you have run.

Yellowfin.log

appserver>logs

This is the Yellowfin application log, and will log processes/tasks that are run in Yellowfin, such as startup, running reports, exporting items, etc. It will also capture most application errors.

By default this file will cycle once it reaches 1024KB , and will create up to 9 files. E.g. Yellowfin.log.1, Yellowfin.log.2, and so on.

Also note, additional information can be logged by enabling debug logging.

JDBC.log

appserver>logs

This is the Yellowfin configuration database log file. It will show the repository database startup and any connection errors.

source.XXXX.log

(Where XXXXX is the ID of the data source).

appserver>logs

These files contain connection information specific to the data source. Each data source has it’s its own ID , so for each data source, a respective log file will exist. When a data source is deleted, the log file doesn't get deleted, but has to be manually removed.

catalina.XXXX.log

(where XXXX is the date Tomcat was started)

appserver>logs

This is the Tomcat startup log, and will log any errors encountered while starting the service.

stdout_XXXX.log

(where XXXX is the date Yellowfin was started)

appserver>logs

Note: This file is ONLY present if you have installed Yellowfin as a Windows service.

This will contain information that is usually visible in the console log (the black window that opens when you start Yellowfin).

jakarta_service_XXXX.log

(where XXXX is the date Yellowfin was started)

appserver>logs

Note: This file is ONLY present if you have installed Yellowfin as a Windows service.

This will contain information relating to the actual Windows service start.

Catalina.out

appserver>logs

Note: This file is ONLY present if you have installed Yellowfin on a Mac (OS X)/Linux box. However, this will NOT be available on a Mac/Linux box if you are running it via the ‘Startup (Terminal)’ option, as all info will be logged in the console (as you would see on a Windows box).

This will contain all information relating to the Yellowfin application process; it captures all errors and processors.

stderr_XXXX.log

(where XXXX is the date Yellowfin was started)

appserver>logs

Note: This file is ONLY present if you have installed Yellowfin as a Windows service .

This should capture the same errors from the stdout file, however it should not contain any other processes.


...