Bug 97057 - Website incorrectly reports "System not checking in with RHN"
Summary: Website incorrectly reports "System not checking in with RHN"
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-09 19:10 UTC by Need Real Name
Modified: 2007-04-18 16:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-18 12:29:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2003-06-09 19:10:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030516
Mozilla Firebird/0.6

Description of problem:
The website is showing "System not checking in with RHN", it shows "Checked In:
2003-06-08 15:34:28 (GMT)".

Yesterday, the RHN tray icon was showing a big blue circle with a tick.
Shortly after booting my computer today, it changed to a red circle with an
exclamation mark. It's found an update.

My computer must have checked in to look for updates.


Additional info:

This has happenned before. Previously, right-clicking and choosing "check for
updates" would fix the problem.

Comment 1 Chip Turner 2003-06-09 19:19:31 UTC
confirm that the account you are logging into the website with is the same that
is listed in /etc/sysconfig/rhn/systemid (search for 'username').  also confirm
that rhnsd is running:
/sbin/service rhnsd status

if it is not running, execute:
/sbin/service rhnsd start
/sbin/chkconfig rhnsd on


Comment 2 Need Real Name 2003-06-09 19:22:37 UTC
Confirmed.

The daemon is running, and my username matches.

Comment 3 Need Real Name 2003-07-01 19:46:05 UTC
It's working now..

Comment 4 Need Real Name 2003-11-19 22:29:47 UTC
It still works - BUT scheduled reboots don't.

Comment 5 Need Real Name 2004-03-16 12:16:48 UTC
I'm happy for this bug to be closed. Original problem fixed.


Note You need to log in before you can comment on or make changes to this bug.