There is this bug: https://bugzilla.redhat.com/show_bug.cgi?id=546676
that is closed with the resolution being to apply this erratum: http://rhn.redhat.com/errata/RHBA-2010-0031.html > -----Original Message----- > From: [email protected] [mailto:rhelv5-list- > [email protected]] On Behalf Of Chris Adams > Sent: Tuesday, March 30, 2010 11:28 AM > To: [email protected] > Subject: [rhelv5-list] Systems getting dropped from RHN again > > Once again, my RHEL 5 Xen server (with a whopping 2 virtual hosts) has > been booted from RHN. I logged in this morning to find several dozen > emails (about every 2 minutes) from it telling me: > > Traceback (most recent call last): > File "/usr/share/rhn/virtualization/poller.py", line 281, in ? > _send_notifications(cached_state) > File "/usr/share/rhn/virtualization/poller.py", line 238, in > _send_notifications > plan.execute() > File "/usr/share/rhn/virtualization/notification.py", line 76, in > execute > server.registration.virt_notify(systemid, self.__items) > File "/usr/share/rhn/up2date_client/rhnserver.py", line 52, in > __call__ > raise self.__exception_from_fault(f) > up2date_client.up2dateErrors.AbuseError: > Error Message: > Abuse of Service detected for server xen.service.hiwaay.net > (1015605337) > 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. > > > Since I haven't changed any defaults, it is highly irritating to get an > error message that blames me for the problem. > > I got this last August and opened a support ticket that went nowhere > (the "solution" was to delete my server in RHN and re-register it), > with > RH support insisting I must have changed something to cause it. A > little while later, RH released an update to fix the problem (thanks > for > looking!), but now it is back again. > > Anybody else seeing this? > > -- > Chris Adams <[email protected]> > Systems and Network Administrator - HiWAAY Internet Services > I don't speak for anybody but myself - that's enough trouble. > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
