Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1151704

Summary: scp failed whith error "SCP client said 'lost connection'"
Product: Red Hat Enterprise Linux 7 Reporter: Yang Xue <yaxue>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.1CC: cheliu, coli, fyang, jfilak, juzhang, michen, scui, shuang, xiagao, xuhan, xutian, yaxue, ypu
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-13 12:25:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
scplogs
none
scp logs none

Description Yang Xue 2014-10-11 05:07:32 UTC
Created attachment 945906 [details]
scplogs

Description of problem:
scp file from client to server failed with error "SCP client said 'lost connection'" ,but scp file from server to client successfully.

But the scp works well between rhel host and fedora.and works well  between the old openssh version.


Version-Release number of selected component (if applicable):

Client host(A):(the version of openssh is upgraded from 6.4 to 6.6.1)
openssh-server-6.6.1p1-3.el7.x86_64
openssh-6.6.1p1-3.el7.x86_64
libssh2-1.4.3-8.el7.x86_64
openssh-clients-6.6.1p1-3.el7.x86_64

Server host(B):(install openssh while install the os)
openssh-server-6.6.1p1-3.el7.x86_64
openssh-6.6.1p1-3.el7.x86_64
openssh-clients-6.6.1p1-3.el7.x86_64
libssh2-1.4.3-8.el7.x86_64

Third host(C):(install openssh while install the os with the old profile)
openssh-server-6.4p1-8.el7.x86_64
openssh-clients-6.4p1-8.el7.x86_64
libssh2-1.4.3-8.el7.x86_64
openssh-6.4p1-8.el7.x86_64

How reproducible:
Always

Steps to Reproduce:

1.Transfer the file from client host(A) to server host(B),"lost connection"
2.Transfer the file from server(B) to client(A),successfully.
3.Transfer the file from host A to host C and C to A ,successfully.
4.Transfer the file from C to B ,"lost connection".
  from B to C,successfully.

Actual results:
Transfer the file from client host to server SCP client(6.6.1) said 'lost connection'
Transfer the file from client to serever(6.4 or 6.6.1 upgrade from 6.4) successfully.
 
Expected results:
Transfer the file from each other host successfully.

Additional info:

Comment 1 Yang Xue 2014-10-11 05:13:11 UTC
Created attachment 945907 [details]
scp logs

Comment 5 Yang Xue 2014-10-11 06:28:26 UTC
summary:
scp server version

6.4 <-->6.4 works well
6.6.1 <--> 6.6.1 don't work
6.4 -> 6.6.1 don't work
6.6.1->6.4 works well

so set keywords:Regression

Comment 7 Petr Lautrbach 2014-10-13 09:08:12 UTC
I'm not able to reproduce your issue, it works for me as expected. Please provide a better reproducer and your configuration. Do you have anything special in ssh_config, sshd_config?

Comment 9 Petr Lautrbach 2014-10-13 12:15:04 UTC


The problem is in /etc/profile.d/abrt-console-notification.sh:

[root@ibm-x3650m3-07 ~]# scp file localhost:file-2
root@localhost's password: 
lost connection
[root@ibm-x3650m3-07 ~]# mv /etc/profile.d/abrt-console-notification.sh .
[root@ibm-x3650m3-07 ~]# scp file localhost:file-2
root@localhost's password: 
file                                                                                                                100%   30     0.0KB/s   00:00    


[root@ibm-x3650m3-07 ~]# cat abrt-console-notification.sh
# If shell is not connect to a terminal, exit immediately, because this script
# should print out ABRT's status and it is senseless to continue without
# terminal.
tty -s || exit 0
...

scp is run via shell on a remote side: /bin/bash -c "scp -v -t ."
and when a session is not interactive, bash is run without connected tty. call 'exit 0' is probably not the right solution in this case

Comment 10 Jakub Filak 2014-10-13 12:25:14 UTC
Thank you for the analysis and sorry for any inconvenience I caused you.

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