RHN abuse of service?

[Mark Howell]

I'm having problems with up2date. A few days ago I started getting abuse of
service error messages when running up2date. I'd had some problems getting
up2date and rpm to complete as I fetched updates to get my Severn box caught
up on the Severn updates channel, so I ran up2date many times trying to get
all that sorted out. 

I e'd RH support last week and got a reply asking if I was running up2date
too frequently, but since I don't know what too frequently is, that's hard
to answer. In practice, I run it if I know there's a patch I need to fetch
(e.g. openssh this week) or if I notice the applet says it's time.

Anyway, I just left the box alone for a few days and tried up2date again and
was 3/4 of the way through retrieving some updates (a big chunk, about
240MB) when up2date quit with the abuse of service message again:

Error Message:
	Abuse of Service detected for server mjolnir (1003629530) Error
Class Code: 49

Etc.

Now up2date returns that message and exits when I start it.

I can understand throttling off 1GB/day bandwidth hogs or folks who are
pounding on RHN by running up2date every minute, but I'm neither. Is it
possible there's something wrong with my Severn box's config?

Here is the output of 'rpm -qa | grep up2date':

up2date-3.9.28-2
ip2date-gnome-3.9.28-2

And 'rpm -qa | grep rhn':

rhn-applet-2.0.10-6
rhnlib-1.4-1

I have observed one other bit of up2date weirdness on this box. It keeps
offering to update aspell-0.50.3-15 to aspell-0.50.3-15 (i.e., same
version). rpm --rebuilddb has not solved that.

Cheers,

Mark