Log / Trace - Files ?

server administration Web Intelligence 6.x Servers
1

Hi

We use InfoView 6.1B.
In which path are the LOG/Trace File (e.g. wiqt.log, wiqt.err, bomanger.log, …) are stored ?

Thanks for your help.

omuth

omuth :de: (BOB member since 2003-04-28)

2

In 6.1.b, it can be found under

D:\Program Files\Business Objects\BusinessObjects Enterprise 6\nodes<servername>\mycluster\logs

assuming you installed it on the D: drive on windows. However, you need to enable logs. To enable logs, copy the “BO_trace.ini” from D:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts\preconf file folder to under D:\Program Files\Business Objects\BusinessObjects Enterprise 6\nodes<servername>\mycluster\logs. Hope this helps

JSanthanam :india: (BOB member since 2003-12-17)

3

if you place the bo_trace.ini in this directory

E:\Program Files\Business Objects\BusinessObjects Enterprise 6\nodes<server_name><cluster_name>\logs

the log files will generate in here also.

csievert :denmark: (BOB member since 2002-06-17)

4

Hi,

Is there a way to clean up these log files - other than manually deleting them. Or do you think writing a script to delete or moving to another folder would help.

****************** I am adding something related to this post.

I am facing this problem. The BO Server is installed on the C Drive which has 10 GB space of which 80% is used. There is hardly 2 .5 GB left now without turning the Trace File ON.

My Logs folder is growing day by day, I had to get rid of old logs and I turned OFF the BO_trace.

BELOW IS the TRACE FILE

// this is really a TraceLog _trace.ini file although it looks like -- C++ --
// ============================================================================
// File: BO_Typical_trace.ini
// Directory: $(TOSCADIR)/astools/validation/resources/ConfigDir
// Language: _trace.ini
// Time-stamp: <02/11/07 15:34:15 tbravier>
// Created: 02/09/30 17:01:24 tbravier
// Author: Thierry Bravier
// Company: Business Objects
// ============================================================================
// This is a demonstration file of _trace.ini syntax.
// see BO_Guru_trace.ini for details
// ============================================================================

// ============================================================================
// trace.ini IO (including parse errors) redirecting:
// ____________________________________________________________________________
error_file = getenv (“BO_TRACE_LOGDIR”) + “/TraceLog.err”;
output_file = (getenv (“BO_TRACE_LOGDIR”) + “/TraceLog”
// + "" + name + “_” + pid

  • “.out”);

// ============================================================================
// Sensible default values for trouble-shooting:
// ____________________________________________________________________________
active = false; // trace all processes - make it true
importance = (debug ? xs : m); // trace more detailed for a debug build
size = debug ? 100000 : 10000; // longer _trace.log file in debug
keep = debug; // keep in debug only

// ============================================================================
// Typical usage:
// ____________________________________________________________________________
if (debug && (name == “wiqt” || name == “WISessionManager”)) {
active = true;
size = 100 * 1000;
keep = true;
importance = xs;
}

// ============================================================================
// useful final _trace.ini debugging messages with echo:
// ____________________________________________________________________________
if (true) {
echo("// ================================================================");
echo ("// TraceLog config of " + name + “#” + pid

  • " on " + oskind + “-” + compile_option
  • " (" + getenv (“LOGNAME”) + “)”);
    echo ("active = " + active + “;”);
    echo (“importance = '” + importance + “’;”);
    echo (“size = " + size + “;”);
    echo (“keep = " + keep + “;”);
    echo (”// ================================================================”);
    }

// ============================================================================

I have couple of questions before I could do anything-

Right now I am Turning ON the Trace File - and on a daily basis i should be cleaning up the Logs.

Quote:

Is there anyway i can write a script which would take care of this instead of cleaning up everyday?

DO i not recreate the Cluster if i have to Re-install it on a different drive?

  1. Do you have any other applications running on the server?
    A> We don’t have any other applications running on the server except for Microsoft Office/Outlook/E Trust Anti-virus.

  2. Are you creating multipe log files or audit files which are not regularly purged.
    A> The Log files generated are WIClustermanager,WIAde,WILoginServer,WIAPiBroker,WIStorageManager,WIDispatcher,WIOGenerator,WISiteLog,WIReportServer,WIProcessManager,wiqt, BOMgr.

I would be monitoring these how much space that would take, and would clean up on a daily basis.

Could you give me more details of how I can turn off the primary node and just move the storage.

Consider moving the storage to the D: drive, stop the primary (and all secondary nodes within the cluster) alter the storage location in the ORB parmaters in configuration tool. .

  • Please advise me on this.

BOBUSER :india: (BOB member since 2005-05-23)