On Wed, Dec 16, 2009 at 9:33 AM, Stainforth, Matthew (SD/DS) < [email protected]> wrote:
> > Do the machines in question happen to be Red Hat Enterprise Linux 5 > > boxes with rhn-virtualization-host installed and > > /etc/cron.d/rhn-virtualization.cron enabled? If so, you may be running > > into: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=546676 > > > > Otherwise, you are correct, 60 minutes is NOT abusive as defined by the > > server-side configuration. So if its not the bug above, and your > > configuration is 60 minutes, then there is something else that must be > > reaching out to RHN Hosted on a frequent basis that needs to be found. > > Hi Brandon, thanks for the link. Since we don't run any virtualization on > Red Hat and there are no calls to rhn_check in any crontab I can find on > these servers I'm at a loss. > > The only thing I can think of is yum-updatesd and rhnsd are both running. > But out of 23 servers, most of which have been checking in happily for > months, RHN has locked out only 4 of them. They all seem to get locked out > at random times; the first one being at 9:14am on Nov 21 and the latest one > at 1am on Dec 16. > > I've already got the ticket open and escalated to highest priority so we'll > see where they get with it. I really appreciate the confirmation that I'm > not crazy in thinking that 240 minutes as the minimum acceptable check-in > time is crazy. > > Matt > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list > For what it's worth, I've been seeing this issue with some of my servers as well. This week I've had two out of 50 servers punted from RHN. I've seen this issue on and off for a while now, but I just assumed that since no-one else had reported it, it must be something in my setup. -- Jesse Weisner [email protected]
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
