Bug 1193374

Summary:	It is not possible to login to system after upgrading snoopy
Product:	[Fedora] Fedora EPEL	Reporter:	Maurizio Schena <mschena>
Component:	snoopy	Assignee:	Mosaab Alzoubi <moceap>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	moceap
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 15:04:41 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:

Description Maurizio Schena 2015-02-17 09:37:06 UTC

Description of problem:

After system upgrade from 6.5 to 6.6, the system was not reachable via as it was giving the error: sshd[13514]: error: setsockopt SO_KEEPALIVE: Bad file descriptor. After a few test the customer side, the error seemed to be linked to the "snoopy" package

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

snoopy-1.7.10-1.el6.x86_64


Steps to Reproduce:

Install rhel 6.6
install snoopy-1.7.10-1.el6.x86_64
edit /etc/ld.so.preload adding /lib64/snoopy.so
Since then nether "su - user" or "ssh user@server"

Actual results:
Cannot login, having error message "error: setsockopt SO_KEEPALIVE: Bad file descriptor" on /var/log/secure

Expected results:
Log in normally

Comment 1 Mosaab Alzoubi 2015-03-22 13:39:52 UTC

You can merge with f20 repo.

Comment 2 Steve Traylen 2015-03-23 12:29:33 UTC

We don't see this error ever.

Upgrading from the current 1.7.10 to 2.2.6 seems quite a jump.

Comment 3 Mosaab Alzoubi 2015-03-23 20:44:33 UTC

(In reply to Steve Traylen from comment #2)
> We don't see this error ever.
> 
> Upgrading from the current 1.7.10 to 2.2.6 seems quite a jump.

If this problem not confirmed you can close the bug.

1.7.10 VERY OLD, and 2.2.6 is the current, I worked on the SPEC as it written from ZERO. Don't wory :) and try to KEEP it updated all the time.

Regards.

Comment 4 Ben Cotton 2020-11-05 16:48:54 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 5 Ben Cotton 2020-11-30 15:04:41 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.