Bug 432522
Summary: | Satellite Sync timesout syncing channels | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Arlinton Bourne <abourne> |
Component: | Satellite Synchronization | Assignee: | Pradeep Kilambi <pkilambi> |
Status: | CLOSED WONTFIX | QA Contact: | Brandon Perkins <bperkins> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 400 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-10 18:59:29 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
Arlinton Bourne
2008-02-12 16:19:02 UTC
Closing. This is doing the right thing by throwing a timeout. This is typically because of something going wrong in RHN Hosted and not Satellite. However, if there is a slowness to the network, you can boost the timeout value by editing the value for: DEFAULT_TIMEOUT in: /usr/lib/python2.3/site-packages/rhn/SSL.py It defaults to 120, but you can raise that number to something significantly higher if you like. Otherwise, there may be a problem in RHN Hosted that requires an email to helpdesk. |