Conference noted::sns

1016.0. "SNS-E-REJECT (again)" by PRSSOS::MENICACCI () Fri Mar 07 1997 10:45

		Hi,

OpenVMS V6.2
PSW V2.2

SENSE WATCHDOG ADD MESSAGE "essai" results in 

***Error*** Connection attempt to MEA002 failed: %SYSTEM-F-REJECT, connect to
network object rejected
%SNS-E-REJECT, The SNS$WATCHDOG process rejected your request


The only workaround at this time is :

	- stop SNS$WATCHDOG
	- @SYS$STARTUP:SNS$STARTUP, then the add message is ok.

SNS$WATCHDOG process :

$ SH PROC/ALL/IDE=202002C3

 7-MAR-1997 14:54:59.31   User: SYSTEM           Process ID:   202002C3
                          Node: MEA002           Process name: "SNS$WATCHDOG"

Terminal:
User Identifier:    [DECNET,SNS$WATCHDOG]
Base priority:      4
Default file spec:  Not available

Devices allocated:  NET71:
                    NET7959:
                    BG122:
                    BG7692:

Process Quotas: 
Account name: <start>
 CPU limit:                      Infinite  Direct I/O limit:       100
 Buffered I/O byte count quota:     95392  Buffered I/O limit:     100
 Timer queue entry quota:              14  Open file quota:        124
 Paging file quota:                 58720  Subprocess quota:        32
 Default page fault cluster:           64  AST quota:              198
 Enqueue quota:                       599  Shared file limit:        0
 Max detached processes:                0  Max active jobs:          0

Accounting information:
 Buffered I/O count:     25604  Peak working set size:       5696
 Direct I/O count:          59  Peak virtual size:          48864
 Page faults:            26166  Mounted volumes:                0
 Images activated:           0
 Elapsed CPU time:          0 00:01:38.93
 Connect time:              2 22:01:35.03

Authorized privileges:

Process privileges:

Process rights:
 NET$MANAGE

System rights:
 SYS$NODE_MEA002

Auto-unshelve: on

Image Dump: on

There is 1 process in this job:

  SNS$WATCHDOG (*)
                             

$ mc ncl sho SESSION CONTROL APPLICATION OSCINT$CL all

Node 0 Session Control Application OSCINT$CL
at 1997-03-07-15:26:20.623+01:00Iinf

Identifiers

    Name                              = OSCINT$CL

Status

    Process Identifiers               =
       {
       }
    UID                               = 84ABAD44-94AE-11D0-8008-AA000400A307
Characteristics

    Client                            = <Default value>
    Addresses                         =
       {
          name = OSCINT$CL
       }
    Outgoing Proxy                    = True
    Incoming Proxy                    = True
    Outgoing Alias                    = True
    Incoming Alias                    = True
    Node Synonym                      = True
    Image Name                        = SYS$SYSTEM:OSCINT$DECNET.COM
    User Name                         = "OSCINT$CL"
    Incoming OSI TSEL                 = <Default value>
    Network Priority                  = 0
    Counters

    Creation Time                     = 1997-03-04-16:44:06.481+01:00Iinf


The following messages are found in SNS$WATCHDOG_ERROR_MEA002.LOG;1 (but not
sure they appeared at the time of the error) :

$ TYP SNS$WATCHDOG_ERROR_MEA002.LOG;1
%ADA-F-EXCCOP, Exception was copied at a raise or accept statement
-ADA-F-EXCEPTION, Exception TCPIP_INIT_ERROR
-ADA-I-EXCRAIPRI, Exception raised prior to PC = 00073D0C
%ADA-I-TASTERUNH, Task with ID %TASK 18 of type AST has terminated due to
unhand
led exception
%ADA-I-RTLEVENT, Debugging event
-ADA-F-ASTDELTER, An AST was delivered, but the task is terminated
-ADA-I-TASTYPEIS, The task's type is AST
-ADA-I-TASIDIS, The task's id is %TASK 18

    Hi Maria,
    
    Does it happen often?
    
    This exception was raised when something went wrong in the TCP/IP
    initialization process:
    
        o Prepare to listen to the incoming Consolidator requests on the network
          . Assign LISTEN channel to INET device (UCX$DEVICE, default BG0:)
    	  . Get local host address.
    	  . Create a socket and bind it to the local host @  ($QIOW IO_SETMODE).
    
    	o Handle requests asynchronously using ASTs
          . Assign CLIENT channel to INET device (UCX$DEVICE, default BG0:)
          . Queue an AST, which requeues itself, to proceed incoming requests...
    
    I corrected the error handling, a bit in the ECO03, and some more advanced
    way in the ECO04 (I'm still working on it, as a matter of fact...)
    
    I'll provide you with the new kit as soon as recreated and QA'ed by
    Computer Associates...
    
    Best Regards,
    
    	-- Olivier.