Bug 20441 - RH7.0 rexec fails
Summary: RH7.0 rexec fails
Status: CLOSED DUPLICATE of bug 18886
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rsh   
(Show other bugs)
Version: 7.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
: 20592 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-11-06 22:18 UTC by dnd
Modified: 2007-04-18 16:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-11-20 22:18:00 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description dnd 2000-11-06 22:18:48 UTC
Command executed on system "dndsd4" RH7.0 to remote system "dndsd3" RH6.2:

# rexec dndsd4 date

<Hostname>: Connection refused
rexec: Error in rexec system call
rexec: The following system error may itself be in error
rexec: Connection refused.

I tried the same command on a RH6.2 and it works just fine. I moved 
the /usr/bin/rexec executable to the RH7.0 system and that works fine on 
the RH6.2 system but fails on the RH7.0 system. I used strace to trace 
both situations:

1) rexec from RH7.0 to RH6.2 => Good trace

2) rexec from RH6.2 to RH7.0 => Bad trace

rexec command trace analysis

strace shows initiation of a connection on a socket fails because of a bad 
destination socket number parameter for connect() function for rexec 

From rexec good trace (rexec RH6.2 to RH7.0)

dndsd3                                   dndsd4
[RH6.2] <---- rexec dndsd3 date ------> [RH7.0]

I'm showing only two lines of trace produced from:
"strace -v rexec dndsd3 date"

... trace clipped...

connect(3, {sin_family=AF_INET, sin_port=htons(512), sin_addr=inet_addr
("")}}, 16) = 0

where input parameters for connect() function are: 

1) file descriptor to a socket = 3

2) socket address data structure for destination address =
 	{sin_family=AF_INET, sin_port=htons(512), sin_addr=inet_addr

3) address length = 16

From rexec bad trace (rexec RH7.0 to RH6.2)

dndsd4                                   dndsd3
[RH7.0] <---- rexec dndsd3 date ------> [RH6.2]

I'm showing only two lines of trace produced from:
"strace -v rexec dndsd4 date"

.... trace clipped...

connect(3, {sin_family=AF_INET, sin_port=htons(2), sin_addr=inet_addr
("")}}, 16) = -1 ECONNREFUSED (Connection refused)

Return value for connect() shows: ECONNREFUSED (No one listening on remote 

The above shows that the problem lies with NOT getting a good end-point 
with a good destination socket number on RH7.0.

Is this a problem with RH7.0 rexec or is it a problem with the network 
stack on RH7.0 since I've moved the RH7.0 /usr/bin/rexec executable onto a 
RH6.2 system and it works just fine in RH6.2 environment.

Comment 1 Pekka Savola 2000-11-20 22:17:58 UTC
*** Bug 20592 has been marked as a duplicate of this bug. ***

Comment 2 Nalin Dahyabhai 2000-11-20 23:35:39 UTC

*** This bug has been marked as a duplicate of 18886 ***

Note You need to log in before you can comment on or make changes to this bug.