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

Conference noted::dnu_osi

Title:DECnet/OSI for {ULTRIX,OSF/1}
Notice:Indicate version and platform when writing...see #2 for kits
Moderator:BULEAN::CARR
Created:Wed Sep 25 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2187
Total number of notes:10469

2125.0. "session control hangs on DECnet V3.2B" by BACHUS::ROELANDTS (Wa d'es ma da ve ne stuut) Fri Feb 07 1997 10:04

  Hello,

  We are experiencing some problems on one of our systems, it is an A2100
  with DU V3.2D-2. We were running with DECnet/OSI for Digital UNIX V3.2A but
  due to very regular hangs we upgraded two days ago to V3.2B, but we still
  have the same problem. The problem is that DECnet "does not work anymore",
  no dlogins, no dls no mails. Looking at it a bit closer, I see that we
  can't do anything anymore on the session control level, doing whatever
  command regarding the session control just hangs. Has anyone seen this ?
  Here follows a result of two things : ps -e | grep dn + an extract of the
  daemon.log file. In the daemon.log I see that errors are reported, what do
  they mean ? What and where is the dns clerk event file ? At the moment of
  the hangs a decnetshutdown fails, the only solution is to reboot the system.

  Thank you for any info

  Regards.

        Guy ROELANDTS


# ps -e | grep dn
 1100 ??       I        0:00.49 (dnsserver)
 1105 ??       I        0:00.15 (dnsserver)
 1108 ??       IW       0:00.02 (dnsserver)
 1286 ??       IW       0:00.07 /usr/sbin/dnalimd
 1289 ??       I        0:03.85 /usr/sbin/dnaevld
 1325 ??       U        0:34.22 /usr/sbin/dnascd
 1326 ??       IW       0:00.25 /usr/sbin/dnansd
 1327 ??       I        0:00.32 /usr/sbin/dnaksd
 1331 ??       I        0:03.17 /usr/sbin/dnsadv
 1371 ??       IW       0:00.12 /usr/sbin/dnanoded
 9746 ??       I        0:00.04 /usr/sbin/dnansd
32378 ??       S        0:00.65 /usr/sbin/dnsclerk -U root -u 0 -g 1 -m 5
 3138 ttypc    S  +     0:00.02 grep dn


Feb  7 07:56:54 ciney dnsclerk[9748]: Unable to open dns clerk event file. 
Error: No such file or directory
Feb  7 07:57:26 ciney dnsclerk[9748]: dn_connect: tower#0: DnaConnectAddress:
Connection timed out
Feb  7 07:57:50 ciney dnsclerk[9748]: dn_connect: tower#1: DnaConnectAddress:
Software caused connection abort
Feb  7 07:57:50 ciney dnsclerk[9748]: Clearinghouse DEC:.bro.bro7_ch
unreachable; DECdns error 1004 - Unable to communicate with any DECdns server;
detailed DECdns error 1004 - Unable to communicate with any DECdns server
Feb  7 07:57:50 ciney dnsclerk[9748]: Clearinghouse DEC:.bro.bro7_ch
unreachable; DECdns error 1004 - Unable to communicate with any DECdns server;
DECnet session control error 5053 - Software caused connection abort
Feb  7 07:57:51 ciney dnansd[9753]: write() failed, Broken pipe


T.RTitleUserPersonal
Name
DateLines
2125.1netrix.lkg.dec.com::thomasThe Code WarriorFri Feb 07 1997 11:233
If you disable the DNS clerk, do things start working again?

ncl disable dns clerk
2125.2will check it next weekBACHUS::ROELANDTSWa d'es ma da ve ne stuutFri Feb 07 1997 12:208
    
    I'll check that next time the system hangs, in the mean time I shut
    decnet re-ran the configuration and restarted decnet. We'll see what
    happens
    
    Thank you and regards,
    
    Guy
2125.3 disable dns clerk did not helpBACHUS::ROELANDTSWa d'es ma da ve ne stuutMon Feb 17 1997 08:1712
    
    in reply to .1 : no, I tried it out but am still having problems, still
    no DECnet connectivity anymore.
    
    I did install patches on V3.2B (the ones from netrix::patches/OSF/V3.2B)
    and will reboot the system at noon, we'll see how our system will
    behave after that.
    
    Rgds,
    
         Guy
    
2125.4dns clerk event fileJACEK::DANIELEWSKIFri Feb 21 1997 06:597
    If you want to get rid of "... dns clerk event file ..." events, try
    
    #touch /var/dss/dns/dnsclerk/dnsclerk.events
    
    It was suggested by Vince Wallace in note 2066.3 and worked for me.
    
    -Wlodek. 
2125.5uptime : 15 days ==> ok now apparentlyBACHUS::ROELANDTSWa d'es ma da ve ne stuutMon Mar 03 1997 13:2414
    
    
    Re .4 : Wlodek,
    
            Thank you for this, I did what you suggested
    
    Now regarding that system that was having problesm, the system is up
    since 15 days now and is happyly running, apparently no problems
    anymore since I installed those 5 new "images"
    
        Rgds,
    
             Guy