Bug 108821
| Summary: | distro upgrade triggers account suspension "for abuse" | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Network | Reporter: | Rik van Riel <riel> |
| Component: | RHN/Backend | Assignee: | Mihai Ibanescu <mihai.ibanescu> |
| Status: | CLOSED NOTABUG | QA Contact: | Fanny Augustin <fmoquete> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | RHN Stable | CC: | rhn-bugs |
| 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: | 2004-04-05 20:26:38 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: | |||
Was the machine freshly registered? Nope, the machine was registered over a month ago and has (I think) done some small updates via RHN before. Under normal circumstances this should not happen. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030423 Description of problem: Running one single up2date to upgrade from an older Fedora beta to newer packages (maybe 1600 packages) triggers the following message: up2date_client.up2dateErrors.AbuseError: Error Message: Abuse of Service detected for server mirkwood.surriel.com (1003617555) Error Class Code: 49 Error Class Info: You are getting this error because RHN has detected an abuse of service from this system and account. This error is triggered when your system makes too many connections to Red Hat Network. This error can not be triggered under a normal use of the Red Hat Network service as configured by default on Red Hat Linux. This is with ONE up2date program running. After this happens I need to wait for 2 hours before I can get more packages... Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. run up2date --nox --update 2. wait for error 3. Expected Results: up2date should just run to completion Additional info: