Joomla Drupal Update and Install from URL failures

Latest response

I need some help on a problem.

The problem I'm having is on RHEL 6.5 with the following versions (all php, mysql, and apache versions are current)
--Drupal 7.28
--Joomla 3.3.0

Errors when trying Updates

--Error on Drupal - Failed to get available update data for one project.

--Error On Joomla - 0 Couldn't resolve host 'update.joomla.org'

Example Error when trying Install from URL Errors

--On Drupal - HTTP error 0 occurred when trying to fetch http://ftp.drupal.org/files/projects/token-7.x-1.5.tar.gz
Unable to retrieve Drupal project from http://ftp.drupal.org/files/projects/token-7.x-1.5.tar.gz.

--On Joomla - 0 Couldn't resolve host 'www.elitewebdev.com'

I have found simmilar problems in my searches but no resolutions. Any help is appreciated.

Responses

Hi James,

I was able to manually download Joomla, and Drupal (see below) perhaps see if you can manually download the Joomla updates you want and the Drupal gz file you are citing.
(See some examples I posted further below in this and the next post).

Can you ping any of those domains?

ping ftp.drupal.org
ping www.elitewebdev.com
ping www.google.com

Is your resolv.conf configured properly? the /etc/resolv.conf file is used to resolve dns lookups like when your system attempts to go to those domains you cited.

Have you checked the Joomla and drupal websites to see if there's any info or other locations to get the files you need? Or if perhaps they were down temporarily?

Also see https://drupal.org/upgrade/, and not sure if this bit on Drupal Core update will help

You can download the latest Joomla and it's updates I suspect here, verify it is what you need.

At this link you will find the Joomla Pommunity Portal).

And it seems this is the link for community discussions for upgrades/install at Joomla's forum.

Kind Regards,
Remmele

I just tried this wget of the drupal tar.gz file you mentioned. See this code block (scroll box right & left as needed):

[notroot@mysystem mydownloads]$ wget http://ftp.drupal.org/files/projects/token-7.x-1.5.tar.gz
wget http://ftp.drupal.org/files/projects/token-7.x-1.5.tar.gz
--2014-05-23 22:31:21--  http://ftp.drupal.org/files/projects/token-7.x-1.5.tar.gz
Resolving ftp.drupal.org (ftp.drupal.org)... 140.211.166.134
Connecting to ftp.drupal.org (ftp.drupal.org)|140.211.166.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 44012 (43K) [application/x-gzip]
Saving to: ‘token-7.x-1.5.tar.gz’

100%[========================================================================================>] 44,012       227KB/s   in 0.2s

2014-05-23 22:31:21 (227 KB/s) - ‘token-7.x-1.5.tar.gz’ saved [44012/44012]

Are you using dhcp on the system you are facing the public internet with? If so, your /etc/resolv.conf is likely being generated automatically.

If needed, add another dhcp server such as google's public dns (see this link for the dns ip addresses) if your dns server you're behind can not resolve the domains you cited. If you are using dhcp, if you add a nameserver to your /etc/resolv.conf, it will not be persistent across network restarts or reboots.

Lastly, I was able to ping and do nslookups against these domains.


[notroot@mysystem mydownloads]$ nslookup www.elitewebdev.com -truncated output- Non-authoritative answer: www.elitewebdev.com canonical name = elitewebdev.com. Name: elitewebdev.com Address: 198.187.31.96 [notroot@mysystem mydownloads]$ nslookup ftp.drupal.org -truncated output- Non-authoritative answer: ftp.drupal.org canonical name = ftp.osuosl.org. Name: ftp.osuosl.org Address: 140.211.166.134

Kind Regards,
Remmele

Thank you for the replies,

I am able to ping sites and i am able to do manual download install/upgrades. I do not like errors like this hanging around.

I also looked at the resolv.conf and it is generated through the networrk manager. I then checked the ifcfg-ethx file and added two lines which seem to be appropriate, according the rhel documentation. They did not change the resolv.conf generated by network manager.

The reslv.conf file does seem overly simple, it has ...

search mysystemname
nameserver xxx.xxx.x.x

... but it does not seem to be a problem with any other network operations.

It is also strange that I am also able to get updates and update notifications through the RHEL Subscription and Administrator update.

Thanks again. If you have anyother suggestions, I will take a look.

updated again
Hi James,

See the last posts following this one....

No one likes errors like this hanging around.

  • I mentioned that any changes to an automatically generated /etc/resolv.conf would be non-persistent.
    • I brought up editing the /etc/resolv.conf with a 'nameserver 8.8.8.8' just in case you needed an additional dns search for your program to resolve the path since it seems it can not look it up. You can edit the file while the network is active and then --do not-- restart the network or reboot and try it again. Your mileage may vary and there are of course other factors to consider, but incremental troubleshooting is relevant.

When you say you get updates and notifications through RHEL Subscription and Administrator update, are you saying that you actually receive Joomla and Drupal updates via Red Hat's Subscription and Administrator update???? That part was not clear. I would suspect you do not receive Joomla/Drupla updates via Red Hat Inc.

Because your Red Hat updates work, and you can ping those sites, that is of course just an initial test. The fact you can manually download those files is also just an initial test. Now that it is known those initial steps are ruled out, any subsequent troubleshooting can take place.

  • Did you perhaps create a yum repo file in /etc/yum.repos.d/some.repo (replace "some" with an actual name you may have used) for any updates? If you -do- have a repo file for Joomla or Drupal, is it set up properly?

  • What did you invoke in order to attempt an upgrade, was it a yum update command or some command that is part of drupal or joomla? That part is missing in your description.

  • Did you look at the forums and community portals I mentioned in the first post?

    • Since your problem is obviously not with Red Hat updates, check the community portal for Drupal & Joomla as mentioned to see if anyone else is experiencing issues.
    • It would be hard to believe that you are the only who has faced this issue.
    • I would suspect Joomla's and Drupal's forums would be a magnet for people discussing such issues.

The only other immediate thing I could think of is (less likely, worth a try) your firewall. Temporarily shut off your firewall and try the update process.

  • Do you have support with Joomla or Drupal, or are you just using the open-source programs without support?

Also, (a long shot) run the below to see what is going on when you attempt an update, and then take the output and put in wireshark. (you can redirect output too, save the file and open it in wireshark).

tcpdump -i ethx # replacing 'x' with your network device

Kind Regards....
Remmele

James, I think you should have visited Joomla's forums.

I also searched Joomla's forums and found that discussion. Go to the Joomla forum link above I posted where they are currently discussing that consternation you are facing.

Hoping that provides some help or insight.

Kind Regards,
Remmele

James,

Regarding Drupal, check to see if this bit from their website's community documentation (Last updated May 18, 2014.) helps.

Kind Regards,
Remmele

SOLVED

Seems like I have stumbled upon the solution. When checking my virtualhost configuration using the "httpd -S" it said ...

"Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName"

I found a suggestion to put ... "NameServer localhost" ... in my httpd.conf file.

I unblocked the "ServerName" directive in the httpd.conf file and add ...

"ServerName localhost:80"

... this resolved both issues.

No more update problems and no more errors when using the

(Note: I had the ServerName localhost in a virtualhost I had setup for "localhost" but that was not enough. Had to do as suggested and repeated here, above.)

James,

Glad it is working. I had never thought it was your own web server this was tripping over.

What is interesting is in the Joomla Portal, people seemed to be recently experiencing the identical issue based on your previous errors you described.

Glad your update issue is resolved!

Kind Regards...

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.