Abuse of Service detected for server webqa-ci1.qa.scl3.mozilla.com

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: davehunt, Assigned: ryanc)

Tracking

Details

(Reporter)

Description

3 years ago
+++ This bug was initially created as a clone of Bug #1216067 +++

I'm hitting an 'Abuse of Service' error when attempting to update jenkins on webqa-ci1.qa.scl3.mozilla.com:

$ sudo yum-wrapper update jenkins
Pinned packages detected, excluding the following from yum update jenkins:

bacula-enterprise-client 8.2.8-1.el6
facter 2.0.2-1.el6
puppet 3.2.4-1.el6

Command string: yum -x bacula-enterprise-client -x facter -x puppet update jenkins 
Loaded plugins: rhnplugin, security



Error Message:
    Abuse of Service detected for server webqa-ci1.qa.scl3.mozilla.com (1040137351)
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.

     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://rhn.redhat.com/help/contact.pxt
     to contact technical support if you think you have received this
     message in error.

This also happened recently in bug 1216067 for our staging environment. I'm not aware of any abuse of service, but it sounds like these boxes may be making frequent requests to RHN?
(Assignee)

Comment 1

3 years ago
Dave,

This is an issue we're working on in bug 1187175. In the meantime I have reactivated this server and ran all security updates. Let me know if there are any others that need intervention.

As soon as we get this deployed, we won't have these issues.

Sorry for the inconvenience.
Assignee: nobody → rchilds
Status: NEW → ASSIGNED
(Reporter)

Comment 2

3 years ago
Thanks Ryan, did you also run the Jenkins update? Or was that you Stephen? Either way we're on the latest LTS version now, and this can be closed.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 3

3 years ago
This is happening again. :(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 4

3 years ago
Ryan: Could you perform your magic once more for us? Thanks!
Flags: needinfo?(rchilds)
(Assignee)

Comment 5

3 years ago
Hello,

yum-wrapper runs fine.
Flags: needinfo?(rchilds)
(Reporter)

Comment 6

3 years ago
Not for me. :(

[dhunt@webqa-ci1.qa.scl3 ~]$ sudo yum-wrapper update jenkins
Pinned packages detected, excluding the following from yum update jenkins:

bacula-enterprise-client 8.2.8-1.el6
facter 2.0.2-1.el6
puppet 3.2.4-1.el6

Command string: yum -x bacula-enterprise-client -x facter -x puppet update jenkins 
Loaded plugins: rhnplugin, security



Error Message:
    Abuse of Service detected for server webqa-ci1.qa.scl3.mozilla.com (1040281023)
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.

     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://rhn.redhat.com/help/contact.pxt
     to contact technical support if you think you have received this
     message in error.
Flags: needinfo?(rchilds)
(Assignee)

Comment 7

3 years ago
Give it another shot.
Flags: needinfo?(rchilds)
(Reporter)

Comment 8

3 years ago
Thanks, it worked!
(Reporter)

Updated

3 years ago
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.