Red Hat Bugzilla – Bug 70650
rhnsd gets "stuck"
Last modified: 2015-01-07 18:58:34 EST
just started digging into one of the dialup machines that doesn't do rhn checks
jmm@bp6:/var/log> rpm -qf $(which up2date)
jmm@bp6:/home/jmm> service rhnsd status
rhnsd (pid 670) is running...
jmm@bp6:/home/jmm> ps auxwww|grep -i rhn
root 1354 0.0 0.7 6692 1808 ? S Jun03 0:11 /usr/bin/python
root 670 0.0 0.2 1656 540 ? S Jun23 0:00 rhnsd --interval 120
root 22461 0.0 0.9 6088 2320 ? S Jun30 0:00 /usr/bin/python
jmm 19701 0.0 0.2 1744 600 pts/1 S 23:20 0:00 grep -i rhn
i'll attach all the up2date logs (cat /var/log/up2date* > up2date.logs). Not
sure if it was be running up2date while an rhn check was going on, or all the
comm problems causing something to screw up or what, but it's 1) not likely to
be easily reproducible and 2) not the first time this has happened.
up2date needs a dialup client test scenario - lots of things suck on dialup
Created attachment 68684 [details]
no idea what this might be at the moment, will investigate
have you seen this any more?
it happened again, but the machine in question is off any network at the moment
(he's doing duty as a mobile "tivo upgrades done fast" box as I help out some
friends :) so I'll have to see if this reproduces again once he's back
Haven't seen any other reports of this, and can't duplicate it
myself. I also suspect if anything it was related to some
rhnsd bugs that got fixed in the most recent 6.2-7.x errata.
So for now, I'm closing this WORKSFORME. If you see it