Red Hat Bugzilla – Bug 30467
Up2date -p hangs then aborts due to no response
Last modified: 2015-01-07 18:44:22 EST
When I run up2date with the -p parameter, it checks my system for install
packages (presumably due to the disk thrashing) and then connects to the
After an initial burst of communication across the internet connection the
system then does nothing. Eventually the program exits with a message
stating it received no response back from the server.
This happens every single time I try to do this. I have upgraded a number
of packages that the RHN update agent said I needed and am now trying to
update my system profile.
This has now made it impossible to use the update manager as the RHN does
not know about my newly upgraded packages.
My profiled registered on RHN is PepRedHat, I hope that you can get all the
information you need regarding my hardware/software from that profile.
That's what it's therefore isn't it?
server side or network connection issue.
Why was this closed? I sent a email directly to P Brown asking for progress on
this bug but got no response from him at all.
This bug is still happening! What further response do you require?
What version of up2date are you running?
The latest verison that I downloaded via up2date when I installed the system.
I'm not on the box right now but will send the version number when I get home
tonight which is about 5 hours away.
I am using version 2.1.7
This is still happening and I have not been able to update my profile since I
have upgraded all of my software via up2date.
I cannot setup a new profile either to try and get around the problem.
Is there any news on this problem yet?
What is happening with this? I am still waiting for a response and I still
can't do the upgrade with up2date.
There is a newer version of the client available (up2date-2.5.4). Is
this still a problem with that version?
Are you using a http proxy? Or any other strange networking
setup (restrictive firewall, etc) that might be causing any issues.
I havent seen any other reports of this, so my suspicion is that it
may be something particular to your networking setup. So, if you
know of anything that might be causing an issue we could replicate, it
would be helpful in tracking the problem down.
Closing this out due to lack of activity. Assumming that the new client made