Huge logfile on VxVm for W2K - Veritas Volume Manager

This is a discussion on Huge logfile on VxVm for W2K - Veritas Volume Manager ; Hi Has anyone alse than me seen problems with a big log file on W2K servers running Veritas Volume Manager 3.0? The logfile is called vxisis.log, and i can see in the documentation that you should be able to controle ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Huge logfile on VxVm for W2K

  1. Huge logfile on VxVm for W2K

    Hi

    Has anyone alse than me seen problems with a big log file on W2K servers
    running Veritas Volume Manager 3.0? The logfile is called vxisis.log, and i
    can see in the documentation that you should be able to controle the logging
    lever by

    HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentV ersion\Tracing\vxisis



    but it's allready set to 6, this should be the lowest level. The logfil
    keeps telling me:



    cluster(3456) - Going to invoke service request. OBJ:
    {d9e33bf8-1248-431e-940e-83adc208b8c4}, INTF:
    {375ec58d-475e-4658-3bcd-61c7483a4fc6}, MJ: 0, MN 5
    cluster(3456) - service request returned. ERR: 0x0. OBJ:
    {d9e33bf8-1248-431e-940e-83adc208b8c4}, INTF:
    {375ec58d-475e-4658-3bcd-61c7483a4fc6}, MJ: 0, MN 5





  2. Re: Huge logfile on VxVm for W2K

    How big is the file? Unfortunately max size is not configurable. 6 is the
    lowest setting and is the default. The messages you are seeing are
    informational, they are not cause for concern. Is there a very large amount
    on activity on the server?

    The file will be overwritten if the VEA service is restarted, which can be
    done without interrupting access to volumes, either via Control Panel or by
    typing "net stop vxob" and "net start vxob" from a command line.


    KM


    "RRE" wrote in message news:3e632d7c@hronntp01....
    > Hi
    >
    > Has anyone alse than me seen problems with a big log file on W2K servers
    > running Veritas Volume Manager 3.0? The logfile is called vxisis.log, and

    i
    > can see in the documentation that you should be able to controle the

    logging
    > lever by
    >
    > HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentV ersion\Tracing\vxisis
    >
    >
    >
    > but it's allready set to 6, this should be the lowest level. The logfil
    > keeps telling me:
    >
    >
    >
    > cluster(3456) - Going to invoke service request. OBJ:
    > {d9e33bf8-1248-431e-940e-83adc208b8c4}, INTF:
    > {375ec58d-475e-4658-3bcd-61c7483a4fc6}, MJ: 0, MN 5
    > cluster(3456) - service request returned. ERR: 0x0. OBJ:
    > {d9e33bf8-1248-431e-940e-83adc208b8c4}, INTF:
    > {375ec58d-475e-4658-3bcd-61c7483a4fc6}, MJ: 0, MN 5
    >
    >
    >
    >




  3. Re: Huge logfile on VxVm for W2K

    The file is growing with a rate of 70 mb a day, this can cause some
    problems!!

    RRE

    KM wrote:
    > How big is the file? Unfortunately max size is not configurable. 6 is the
    > lowest setting and is the default. The messages you are seeing are
    > informational, they are not cause for concern. Is there a very large amount
    > on activity on the server?
    >
    > The file will be overwritten if the VEA service is restarted, which can be
    > done without interrupting access to volumes, either via Control Panel or by
    > typing "net stop vxob" and "net start vxob" from a command line.
    >
    >
    > KM
    >
    >
    > "RRE" wrote in message news:3e632d7c@hronntp01....
    >
    >>Hi
    >>
    >>Has anyone alse than me seen problems with a big log file on W2K servers
    >>running Veritas Volume Manager 3.0? The logfile is called vxisis.log, and

    >
    > i
    >
    >>can see in the documentation that you should be able to controle the

    >
    > logging
    >
    >>lever by
    >>
    >>HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentV ersion\Tracing\vxisis
    >>
    >>
    >>
    >>but it's allready set to 6, this should be the lowest level. The logfil
    >>keeps telling me:
    >>
    >>
    >>
    >>cluster(3456) - Going to invoke service request. OBJ:
    >>{d9e33bf8-1248-431e-940e-83adc208b8c4}, INTF:
    >>{375ec58d-475e-4658-3bcd-61c7483a4fc6}, MJ: 0, MN 5
    >>cluster(3456) - service request returned. ERR: 0x0. OBJ:
    >>{d9e33bf8-1248-431e-940e-83adc208b8c4}, INTF:
    >>{375ec58d-475e-4658-3bcd-61c7483a4fc6}, MJ: 0, MN 5
    >>
    >>
    >>
    >>

    >
    >
    >



+ Reply to Thread