Bug 331001
Summary: | osad stops working if rhn_check blocks forever | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Sven Trenkel <sven> |
Component: | yum-rhn-plugin | Assignee: | John Matthews <jmatthew> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | duffy, rhn-bugs |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHBA-2008-0360 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-21 14:27:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sven Trenkel
2007-10-13 21:45:05 UTC
Hi there, The sanuty check of osad to make sure that not more than one rhn_check is running at any time is sane and correct thing to do. If rhn_check is hanging, we need to investigate and determine the cause of rhn_check hanging. I am moving this from the Satellite product and onto the RHEL product and propose to investigate further for the rhn_check command (which is shipped with RHEL). This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. User jslagle's account has been closed This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Fixed in rev 134967. We decided that instead of allowing multiple instances of rhn_check to be run at the same time, we simply put a timeout on the socket. If the socket operation does not perform within a certain time, the rhn_check process will exit. I simulated your situation by using VMWare and "disconnecting" the network interface while a package download was occurring. In my tests, after the fix is used, rhn-check exits and then after the network connection is restored, osad re-connects to the satellite server after a few minutes, and the action is then picked up correctly (since the previous rhn_check has exited). Be aware that it can take several minutes (sometimes up to 10) for osad to re-connect. Also note, that this fix was actually in yum-rhn-plugin as that is actually what rhn_check uses to download the package, and so this fix is only for RHEL 5 (Which is what it was reported against). I setup and action to install eclipse (big package) and then waited until client check in again. Then yanked the network. rhn_check timed out with the error: Could not submit to <RetryServer for xmlrpc.rhn.redhat.com/XMLRPC>. Possible networking problem? No blocking here. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0360.html |