Bug 813099 - up2date_client.up2dateErrors.AbuseError on RHEL6.x
Summary: up2date_client.up2dateErrors.AbuseError on RHEL6.x
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-rhn-plugin
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-16 21:32 UTC by Sonny DeLara
Modified: 2016-02-08 14:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-04 11:45:49 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Sonny DeLara 2012-04-16 21:32:02 UTC
Description of problem:

After enabling yum updates, the following errors kept appearing on our RHEL6.x host.  

Error Type: up2date_client.up2dateErrors.AbuseError
Error Value: 
Version-Release number of selected component (if applicable):
Linux perf-ibm-x3650 2.6.32-220.7.1.el6.x86_64 #1 SMP Fri Feb 10 15:22:22 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

The error message occurs randomly on our IBM x3650 server where RHEl 6.0 was first installed, followed by 'yum update'.

Steps to Reproduce:
1. Simply enable 'yum update' on RHEL6.0
  
Actual results:


Expected results:


Additional info:

Comment 2 James Antill 2012-04-23 18:28:17 UTC
I assume this is a message from rhnplugin, or it's stack.

Comment 3 Miroslav Suchý 2012-04-24 07:54:35 UTC
It is weird that the value is empty. There should be:

     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.

     The Red Hat Network services for this system will remain disabled
     until you will reduce the RHN network traffic from your system to
     acceptable limits.

     Please log into RHN and visit https://%(hostname)s/help/contact.pxt
     to contact technical support if you think you have received this
     message in error.

Anyway, in fact this is just abuse reject from RHN. Most probably caused by too often run of rhn_check.
Is it possible that you have it in crontab with low interval (few minutes)?
Are you registred to rhn.redhat.com or to RHN Satellite?

Comment 4 RHEL Program Management 2012-05-03 05:19:52 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Clifford Perry 2014-11-04 11:45:49 UTC
Needinfo for 2 1/2 years. Closing out as insufficient information. 

Please reopen if required. 

Cliff


Note You need to log in before you can comment on or make changes to this bug.