Bug 53674
Summary: | up2date gets Authorization Required, terminates | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | GeoffLeach <geoffleach.gl> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | limbo | CC: | aleksey, gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-07-20 16:49:37 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
GeoffLeach
2001-09-14 17:47:25 UTC
That sounds like a message from an authenticated proxy where the appropriate credentials are not getting presented. Are you attempting to connect through a proxy? There is no proxy involved on my end. Connection is through PPP on a slow (26KB) line. A comment on the Roswell list suggested that that might be a factor. Package retrieval is done via some authentication tokens which expire after one hour. If up2date does not finish its job in one hour, it needs to reauthenticate. The up2date client had a bug which is fixed now. Could you please report what version of up2date you're using? Thanks. Version in use is up2date-2.7.0-7.x.1 This bug appears to be back in Limbo (up2date-2.9.13-7.x.9, up2date-gnome-2.9.13-7.x.9, rhnlib-0.8-7, python-2.2.1-10) - up2date failes to re-authenticate after timeout, it just reports the error to the user and aborts... same behaviour, different bug. I'd rather track it with a different bug id. If someone hasnt opened another bug report yet, I'll open one. opened as a new bug #69518 |