Yum update there was an error communicating with rhn

Tony Vetter. The "--username" and "--password" arguments don't appear to be working for register. LV Newbie 7 points. Louis Vannatta. In Diagnostic Steps, clean options must be incompatible with proxy, local only? AK Active Contributor points. Alexander Kohr. Pro points. Daniel Beckman. Here are the packages I had to manually update: rpm -ivh nspr SP Newbie 12 points. Sam Pappachan.

Guru points. RJ Hinton Community Leader. Kindly request updating or validating this for RHEL 8 as well, thanks. Regards, RJ.

GS Active Contributor points. Glen Sinclair. Here are the common uses of Markdown. Learn more Close. Are you sure you want to update a translation? It seems an existing Japanese Translation exists already. However, the english version is more up to date.

We appreciate your interest in having Red Hat content localized to your language. Please note that excessive use of this feature could cause delays in getting specific content you are interested in translated. We are generating a machine translation for this content. Depending on the length of the content, this process could take a while. Which means that "yum" cannot download the necessary files, and it cannot rebuild Apache. I raised a ticket about this and the response seems to be that they don't know how long it will take to fix the repository problem.

In the meantime, all my sites are down because Apache is broken. Or can anyone suggest something I could do to get back online?! I am starting to shrug my shoulders at this stage :- Thanks in advance. I am using this opportunity to backup my databases and make sure I've got offline backups of everything.

There was an error communicating with RHN. RHN support will be disabled. This is partly because we distribute them through a Content Delivery Service by Akamai. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

New installation of RHEL 6. Firstboot registration fails. Firefox and curl also cannot access the network, even though it is possible to run nslookup successfully showing that the network is connected AND the DNS servers are available.

The Firefox message is "Cannot reach network" or similar. It would appear that there is undocumented internal security on RHEL? Thanks David. I was aware of this material before. I have more info after playing some more - for example when curl is pointed at a URL it DOES resolve the address but then reports "unable to connect to xxx. I can plug in my laptop on the same connection, set it to the server's IP address, and connect to whatever I please so is NOT the hardware firewall that is blocking the connection.

It "looks" like RHEL has installed and is running an internal software firewall with the wrong rules but so far I haven't been able to find it. I'll try the other forum suggested. Thanks again. Is it possible to have your IP subnet that could be assigned to content-xmlrpc. Our firewall only understands IP's.

I had given up on this! The server works properly in production but so far as I can see, no Red Hat support features work. Maybe they aren't in our subscription, I don't know. I tried to run "yum check-update" and get no response - it just runs for a few seconds and ends. Please run subscription-manager for more information. So, I'm in a loop!