Re: Abuse of service detected for server error (1013937626)
Clifford Perry <[email protected]>
| Newsgroups | gmane.linux.redhat.rhn.user |
|---|---|
| Organization | Red Hat, Inc. |
| Message-ID | <[email protected]> |
inode0 wrote: > On Fri, Nov 7, 2008 at 3:00 AM, Chandan M C <[email protected]> wrote: > >> I had gone through the link you sent before. But could get the clear >> idea on "connecting to RHn more frequently than once every 120 ses". >> >> Does that mean that, from once connection to another connection there >> should be atleast 120 min Interval. >> >> just for testing purpose, I tired login to RHN from my 2 different >> machines with the same redhat sid file, I am able to login. From the >> above statement this should not happen right. >> Every time you login from up2date or yum to RHN you increment you check-in counter by one for the systemid in question (unless our IT team blocked maybe a specific IP due to some really bad script/traffic). I do not remember the exact number, but you need to have connected many many many times to hit this issue, either over a long period of time with frequent connections, or with a short burst where you did 1000's of connections to trip this. Typically a script of some sort is miss configured or running too frequently. Suggestion, login to RHN, delete system. Re-run rhn_register to register system in question back to RHN. OR try opening a support ticket before doing anything. Cliff > > I don't recall the exact details of this but you really can't trip > this by doing anything "by hand." The abuse has to be sustained over a > fairly substantial period of time before it kicks in. But having > something like puppet check with RHN every minute can certainly do it. > > John > > _______________________________________________ > rhn-users mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhn-users > -- Clifford Perry Team Lead, Satellite Engineering Red Hat, Inc. http://www.redhat.com/ +1 919 754 4403 RHCA / RHCE# 805007680128201