We've got a puppet setup that has machines map to RHN, part of a puppet checkin includes a series of yum lists like: /usr/bin/yum -d 0 -e 0 list available logrotate This causes the following error: =================================================== Error Message: Abuse of Service detected for server app2.fedora.phx.redhat.com (1007544728) 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. ======================================================
I suspect it's caused by the virtualization poller. At least this seems to be the case for my systems.
I've disabled all the virtualization stuff (and some of these weren't virtualized) and we're still seeing the issue. I don't think we were having these sorts of issues a few weeks back. One of our servers hasn't been able to update for over 4 days now. I can remove the host and add it again for now.
(In reply to comment #2) > I've disabled all the virtualization stuff (and some of these weren't > virtualized) and we're still seeing the issue. I don't think we were having > these sorts of issues a few weeks back. One of our servers hasn't been able to > update for over 4 days now. I can remove the host and add it again for now. Yeah, I hijacked this one. I've opened a different but about the virt stuff (#245594).
Anyone have any more words on this? My machines can't install / update software and my logs are filling up with messages about it.
Isn't this a taskomatic bug? I seem to remember code that would lock your system if you had too much activity that was independent of anything virt-related.
(In reply to comment #5) > Isn't this a taskomatic bug? I seem to remember code that would lock your > system if you had too much activity that was independent of anything virt-related. Yeah, this one isn't virt-related. But no, taskomatic involved :) This particular bug is for anything that can be done client side (auth caching or whatnot). Also related are: 245794 - Create a better 'abuse' metric 201286 - Provide a means to re-enable 'abuse' systems within RHN Support Tools
As a suggested fix, how about pickling loginInfo in up2dateAuth.py in between runs?
I'd have to check with some of the puppet guys how to do that. I literally just have: package { httpd: ensure => present } In my configs. puppet does the rest for me.
(In reply to comment #8) > I'd have to check with some of the puppet guys how to do that. I literally just I meant to be implemented for the yum plugin :)
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Implemented client side cache of the loginInfo in up2dateAuth.py Checked in svn rev: 135236.
I no longer get the abuse error.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0360.html
I'm still experiencing this problem, exactly the same way mmcgrath describes. Putting an RHN proxy in between does not help, and apparently with a Puppet run interval of 30 minutes RHN still is contacted over a hundred times a day.
Also, how can this bug be closed while it is dependent on a bug in status NEW? I cannot examine the other bug 'cause of permission errors.