Opened 10 years ago

Last modified 7 years ago

#1085 new defect

IZ144: open_remote_spawn_process does not handle "Connection reseted by peer message"

Reported by: rhierlmeier Owned by:
Priority: high Milestone:
Component: testsuite Version: current
Severity: Keywords: Sun framework
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=144]

        Issue #:      144             Platform:     Sun           Reporter: rhierlmeier (rhierlmeier)
       Component:     testsuite          OS:        All
     Subcomponent:    framework       Version:      current          CC:    None defined
        Status:       RESOLVED        Priority:     P2
      Resolution:     FIXED          Issue type:    DEFECT
                                  Target milestone: milestone 1
      Assigned to:    rhierlmeier (rhierlmeier)
      QA Contact:     joga
          URL:
       * Summary:     open_remote_spawn_process does not handle "Connection reseted by peer message"
   Status whiteboard:
      Attachments:

     Issue 144 blocks:
   Votes for issue 144:     Vote for this issue


   Opened: Fri Aug 24 05:29:00 -0700 2007 
------------------------


We testsuite uses rlogin it can happend that (x)inetd limits the number of
parallel sessions. If this limit is reached it simply closes the incoming socket.
The client receives a "Connection reseted by peer message".

This message is not handled by the expect loop in open_remote_spawn_process.

You simple get the following error:

check       : connection_test
procedure   : open_remote_spawn_process (startup)
called from : connection_test_test
----------------------------------------------------------------
connection to host "foo.bar" as user "root"
startup timeout
----------------------------------------------------------------

   ------- Additional comments from rhierlmeier Fri Aug 24 05:29:30 -0700 2007 -------
Reassigned

   ------- Additional comments from rhierlmeier Fri Aug 24 05:29:44 -0700 2007 -------
Started

   ------- Additional comments from rhierlmeier Fri Aug 24 05:44:21 -0700 2007 -------
Fixed with check in RH-2007-08-24-0

Change History (0)

Note: See TracTickets for help on using tickets.