[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

596.0. "7.1 log file growth" by ALLOUT::STEWART (Bob Stewart) Wed May 14 1997 17:02

    Under VMS 6.2, my operator.log file size was a few blocks per week.
    UNder VMS 7.1, the file size is about 100 blocks per day. Most of the
    space is full of messages like 
    
    %%%%%%%%%%%  OPCOM  10-MAY-1997 05:21:18.31  %%%%%%%%%%%
    Message from user SYSTEM on ALLOUT
    Event: Too Few Servers Detected from: Node LOCAL:.ALLOUT DTSS,
            at: 1997-05-10-05:21:18.312-04:00Iinf
            Number Detected=0,
            Number Required=1
            eventUid   3B6A856C-C8F5-11D0-B217-414C4C4F5554
            entityUid  BCD5EA2F-C610-11D0-8004-AA0004000274
            streamUid  AFEC8F5D-C610-11D0-8003-AA0004000274
                                                                   
    These messages get dumped inot the log file every 10 minutes, forever. 
    
    How do I get rid of the messages?
    
T.RTitleUserPersonal
Name
DateLines
596.1Your time server is missingNETCAD::ROLKEThe FDDI Genome ProjectWed May 14 1997 17:4213
    Event: Too Few Servers Detected from: Node LOCAL:.ALLOUT DTSS,
            Number Detected=0,
            Number Required=1
    
Your system is looking for a DTSS (Distributed Time mumble) server
and can't find one.

    How do I get rid of the messages?
    
You can 1) stop DTSS and it will stop logging its complaint or 2) try
to find out what happened to your server.

Chuck
596.2EEMELI::MOSEROrienteers do it in the bush...Thu May 15 1997 02:2210
    you could also rename SYS$MANAGER:NET$LOGICALS.TEMPLATE to .COM
    (if not already doen), and then uncomment the logical
    NET$IGNORE_EVD to be true, so the event logger will not startup
    and you will not see those error messages.
    
    Of course this doesn't fix the fact that you don't have a DTSS
    server on your net, but at least it doesn't fill up your operator
    logfile.
    
    /cmos
596.3BLOCK EVENT ...HAN::HALLEVolker Halle MCS @HAO DTN 863-5216Thu May 15 1997 03:0911
    
    ... or you could selectively block this event from being reported:
    
    $ MC NCL BLOCK EVENT DISPATCHER OUTBOUND STREAM local_stream -
    	GLOBAL FILTER ((NODE,DTSS), Too Few Servers Detected)
    
    Volker.
    
    	local_stream = your local outbound stream name. Check with
    		       $ MC NCL SHO EVENT DISPA OUTBOUND STREAM * NAME
    
596.4Obviously...XDELTA::HOFFMANSteve, OpenVMS EngineeringThu May 15 1997 09:473
   ... or you could work with your network folks to configure a local
   timeserver...
596.5sys$manager:net$event_local.template VELI::KORKKOVeli K�rkk� @FNO, 879-5512Sun May 25 1997 14:059
        And there is sys$manager:net$event_local.template which you can
        copy to sys$manager:net$event_local.ncl. It contains few other
        useful things.
        
        Also,
        
        	$mc ncl show dtss local server * all
        
        woulc reveal whether your system sees any local DTSS servers.
596.6how to kill dtss?ALLOUT::STEWARTBob StewartTue May 27 1997 12:1311
    There are no timeservers here, and no plans to have any. My system
    worked just fine under 6.2 without any, so I suppose it ought to work
    under 7.1 without any. Right?
    
    My system worked fine before with no DTSS, I suppose that it ought to
    continue working fine under 7.1 without DTSS. Right? So how do I kill
    off DTSS? There is no HELP DTSS, there is no command DTSS HELP , there
    is no MC DTSS HELP. I suppose I could mess with
    SYS$COMMON:[SYSMGR]NET$DTSS_CLERK_STARTUP.NCL;1 , but the next upgrade
    would probably undo it. What is the official way?
    
596.7Disabling DECdtssXDELTA::HOFFMANSteve, OpenVMS EngineeringTue May 27 1997 12:3211
   Donno if the following works over a reboot, but here's one set
   of commands -- you'd be better off over in HELP::DECNET-OSI_FOR_VMS.

$ run sys$system:ncl
ncl> disable dtss
ncl> delete dtss
ncl> !To make sure it's gone, type the following commands:
ncl> show dtss all
ncl> exit
$ show logical dtss$_service_active