Only one rhnsd process running. That bug report does seem to be of interest. I'll take this up with RH support. Thanks
Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: Brad Hinson [mailto:[email protected]] Sent: Monday, August 22, 2011 3:37 PM To: [email protected] Subject: Re: Rhnsd? The checkin at 21 minutes after the hour is definitely the regularly scheduled one. If you take these out, then you have a second pattern starting at 51 minutes past the our at roughly 6 hour intervals. Looks like rhnsd isn't doing the right thing. Is there only one rhnsd process running? If so, I'd recommend opening a RH support ticket. fyi, there's one open bug report against rhnsd that could be related: https://bugzilla.redhat.com/show_bug.cgi?id=730350 -- Brad Hinson <[email protected]> Worldwide System z Sales, Strategy, Marketing Red Hat, Inc. +1 (919) 360-0443 http://www.redhat.com/z On Aug 22, 2011, at 11:14 AM, Bauer, Bobby (NIH/CIT) [E] wrote: > Hi Brad, logrotate is installed. There doesn't seem to be a pattern. > > [Thu Aug 18 02:21:30 2011] up2date logging into up2date server > [Thu Aug 18 02:21:34 2011] up2date successfully retrieved authentication > token from up2date server > 90 minutes - 1'30'' > [Thu Aug 18 03:51:26 2011] up2date logging into up2date server > [Thu Aug 18 03:51:29 2011] up2date successfully retrieved authentication > token from up2date server > 210 minutes - 2'30'' > [Thu Aug 18 06:21:30 2011] up2date logging into up2date server > [Thu Aug 18 06:21:33 2011] up2date successfully retrieved authentication > token from up2date server > 210 minutes - 2'30'' > [Thu Aug 18 09:54:50 2011] up2date logging into up2date server > [Thu Aug 18 09:54:54 2011] up2date successfully retrieved authentication > token from up2date server > 270 minutes - 4'30'' > [Thu Aug 18 14:21:31 2011] up2date logging into up2date server > [Thu Aug 18 14:21:34 2011] up2date successfully retrieved authentication > token from up2date server > 90 minutes - 1'30'' > [Thu Aug 18 15:57:52 2011] up2date logging into up2date server > [Thu Aug 18 15:57:55 2011] up2date successfully retrieved authentication > token from up2date server > 150 minutes - 2'30'' > [Thu Aug 18 18:21:30 2011] up2date logging into up2date server > [Thu Aug 18 18:21:34 2011] up2date successfully retrieved authentication > token from up2date server > 100 minutes - 1'40'' > [Thu Aug 18 22:01:18 2011] up2date logging into up2date server > [Thu Aug 18 22:01:22 2011] up2date successfully retrieved authentication > token from up2date server > 150 minutes - 2'30'' > [Fri Aug 19 02:21:30 2011] up2date logging into up2date server > [Fri Aug 19 02:21:34 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 04:04:42 2011] up2date logging into up2date server > [Fri Aug 19 04:04:45 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 06:21:30 2011] up2date logging into up2date server > [Fri Aug 19 06:21:33 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 10:08:00 2011] up2date logging into up2date server > [Fri Aug 19 10:08:03 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 12:53:56 2011] up2date logging into up2date server > [Fri Aug 19 12:54:00 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 16:11:27 2011] up2date logging into up2date server > [Fri Aug 19 16:11:31 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 20:53:57 2011] up2date logging into up2date server > [Fri Aug 19 20:54:00 2011] up2date successfully retrieved authentication > token from up2date server > [Fri Aug 19 22:14:13 2011] up2date logging into up2date server > [Fri Aug 19 22:14:16 2011] up2date successfully retrieved authentication > token from up2date server > [Sat Aug 20 00:53:56 2011] up2date logging into up2date server > [Sat Aug 20 00:54:00 2011] up2date successfully retrieved authentication > token from up2date server > [Sat Aug 20 04:17:36 2011] up2date logging into up2date server > [Sat Aug 20 04:17:40 2011] up2date successfully retrieved authentication > token from up2date server > [Sat Aug 20 08:53:56 2011] up2date logging into up2date server > [Sat Aug 20 08:54:00 2011] up2date successfully retrieved authentication > token from up2date server > [Sat Aug 20 10:21:10 2011] up2date logging into up2date server > [Sat Aug 20 10:21:13 2011] up2date successfully retrieved authentication > token from up2date server > [Sat Aug 20 12:53:56 2011] up2date logging into up2date server > [Sat Aug 20 12:53:59 2011] up2date successfully retrieved authentication > token from up2date server > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -----Original Message----- > From: Brad Hinson [mailto:[email protected]] > Sent: Friday, August 19, 2011 5:58 PM > To: [email protected] > Subject: Re: Rhnsd? > > Hi Bobby, > > Can you check further back in the older logs (/var/log/update-<date> if you > have logrotate installed) to see if this is the 12th up2date checkin? What > may be happening is that rhnsd is designed to check in regularly 11 times, > then on the 12th time it applies some random jitter to the time (to avoid > lots of systems checking in at the same frequency all the time). After that > it resumes the 4 hour checkins. > > -- > Brad Hinson <[email protected]> > Worldwide System z Sales, Strategy, Marketing > Red Hat, Inc. > +1 (919) 360-0443 > http://www.redhat.com/z > > On Aug 18, 2011, at 11:50 AM, Bauer, Bobby (NIH/CIT) [E] wrote: > >> In our RHEL 6, there is an RHNSD task that the man page says queries 'Red >> Hat Network for updates and information'. It is suppose to check in every 4 >> hours, the default, this is also specified in /etc/sysconfig/rhn/rhnsd. >> According to /etc/init.d/rhnsd it uses /etc/sysconfig/rhn/up2date as its >> config file. In here specifies logging as /var/log/up2date >> >> Looking at /var/log/up2date it appears the 4 hour default is ignored. In >> fact, I'm not sure what interval it is using: >> >> [Thu Aug 18 02:21:30 2011] up2date logging into up2date server >> [Thu Aug 18 02:21:34 2011] up2date successfully retrieved authentication >> token from up2date server >> [Thu Aug 18 03:51:26 2011] up2date logging into up2date server >> [Thu Aug 18 03:51:29 2011] up2date successfully retrieved authentication >> token from up2date server >> [Thu Aug 18 06:21:30 2011] up2date logging into up2date server >> [Thu Aug 18 06:21:33 2011] up2date successfully retrieved authentication >> token from up2date server >> [Thu Aug 18 09:54:50 2011] up2date logging into up2date server >> [Thu Aug 18 09:54:54 2011] up2date successfully retrieved authentication >> token from up2date server >> >> The RHN web page indicates the server "Checked In: 8/18/11 10:21:34 AM EDT" >> >> >> Using the RHN web page, I specified 4 fixes to be pushed to this server and >> I expected it to happen when the server checked in. It didn't. >> >> So can anybody explain the time that time intervals we are seeing and when >> RHN will actually push fixes to a server? >> >> Thanks >> Bobby Bauer >> Center for Information Technology >> National Institutes of Health >> Bethesda, MD 20892-5628 >> 301-594-7474 >> >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> ---------------------------------------------------------------------- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
