Bug 27682 - up2date-2.1.7 broke rhnsd --rhn_check (run by rhnsd) returns 255 missing 'id'
up2date-2.1.7 broke rhnsd --rhn_check (run by rhnsd) returns 255 missing 'id'
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-14 18:35 EST by Johnray Fuller
Modified: 2015-01-07 18:43 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-20 15:47:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Johnray Fuller 2001-02-14 18:35:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.16-22 i686)


Recieved a ticket in CRM (#168896 )

Here is the text form the ticket.
up2date-2.1.7 broke rhnsd

after upgrading to up2date-2.1.7 my system status is not
being updated on the RHN web site.  This seems to be because
rhn_check (run by rhnsd) returns 255.  When I run 
"rhn_check -v -v -v" I see these three lines of output

"check_action({})".
"Got invalid response - missing 'id'".
"{}".

what I see in /var/log/messages is

Feb 14 10:03:10 wot rhnsd: running program /usr/sbin/rhn_check
Feb 14 10:03:12 wot rhnsd: command returned: 
Feb 14 12:03:12 wot rhnsd: running program /usr/sbin/rhn_check
Feb 14 12:03:15 wot rhnsd: command returned: 
Feb 14 14:03:15 wot rhnsd: running program /usr/sbin/rhn_check
Feb 14 14:03:17 wot rhnsd: command returned: 

Have sent several emails on this issue and have gotten no reply, so I'm
posting it to bugzilla.

Johnray

Reproducible: Didn't try
Comment 1 Cristian Gafton 2001-02-19 20:33:03 EST
Assigned QA to jturner
Comment 2 Preston Brown 2001-02-20 13:15:08 EST
adrian, cristian: ideas?
Comment 3 Adrian Likins 2001-02-20 14:04:47 EST
i'd verify that their /etc/sysconfig/rhn/systemid is valid (attache
it if need be...)

Also need some additional info about the user in question, and I'll
check the db and see if they have any weird actions queued that
could be causing problems.



Comment 4 Cristian Gafton 2001-02-20 15:47:54 EST
This is a server side problem - a change which is making the older up2date
clients to whine about this. This is harmless - I will change the live servers
back.
Comment 5 Jay Turner 2001-03-07 11:57:10 EST
This is indeed resolved.  Closing out the bug.

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