Support

Admin Tools

#9650 Joomla Upgrade does not work

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Thursday, 04 November 2010 11:47 CDT

user4559
this error message apears:
ERROR:
The archive file is corrupt, truncated or archive parts are missing

What í´m doning wrong?

nicholas
Akeeba Staff
Manager
It seems that your server could not download the Joomla! upgrade package in its entirety. The partial transfer causes this error message to appear. The easiest workaround is to download the file using the direct link presented on the page which gives you the option to upgrade/reinstall Joomla! and place it inside your site's temporary directory. This way Admin Tools will detect that the package is already present and will not attempt to re-download it.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yvesg
Same error for me. The J! upgrade package is not downloaded at all. Your workaround is working, but it would be nice to understand why the package it not written in the tmp directory.

nicholas
Akeeba Staff
Manager
There's a bug with using cURL to download the files in RC2. I have a fix for that in the current developer's release (see Download -> Developer's Releases menu item).

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yvesg
There's a bug with using cURL to download the files in RC2. I have a fix for that in the current developer's release (see Download -> Developer's Releases menu item).


I tried to upgrade from 1.5.20 to 1.5.21 with ATC svn70, but got this error: fopen failed.

PHP 5.2.6 - Apache/2.2.3 (Red Hat)

nicholas
Akeeba Staff
Manager
Your server seems to support neither cURL nor fopen URL wrappers. Can you ask your host if this is the case and if they can enable either of them?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yvesg
Your server seems to support neither cURL nor fopen URL wrappers. Can you ask your host if this is the case and if they can enable either of them?


I contacted my host. fopen is disabled and he recommends to use cURL with FastCGI.

cURL is enabled on my site: libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5

Any chance to make Admin Tools Core work with it ?

Thanks

nicholas
Akeeba Staff
Manager
I uploaded developer's release 74 today. It should address this issue. Can you check it out?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yvesg
I uploaded developer's release 74 today. It should address this issue. Can you check it out?


Still the "fopen failed" message...

nicholas
Akeeba Staff
Manager
I've identified this problem to be caused by certain servers with old and buggy PHP versions (usually in the 5.2.4-5.2.6 range). Unfortunately, I can't work around it. The only solution is to upgrade the PHP version (ideal) or ask your host to enable the URL fopen() wrappers for your account.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yvesg
My host upgraded PHP to version 5.2.14, but I still get the fopen error. For some reason, he doesn't want to enable the URL fopen() wrappers.

nicholas
Akeeba Staff
Manager
I just release 1.0 Stable which should be able to fix this issue. Please try and report back your results. Thank you!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

alexwalker
Nicholas
I get this message when I try and upgrade Joomla via admin tools: "Could not download the Joomla! installation package. You have to update Joomla! manually".
Is there any way of making admintools work? It would make life a lot easier.

nicholas
Akeeba Staff
Manager
Alex, please take a look at the last heading in the documentation page.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yvesg
Nicholas

I get this message when I try and upgrade Joomla via admin tools: "Could not download the Joomla! installation package. You have to update Joomla! manually".

Is there any way of making admintools work? It would make life a lot easier.


Same for me. I will have to continue to update J! manually. =(

[UPDATE] No, I found a better solution: change my host to Rochen ! :D

nicholas
Akeeba Staff
Manager
Yeap, Rochen rocks and I say it out loud every time someone asks me what's the best host to use :) These guys have actually thought out how quality hosting is supposed to be and offer it for a very low price with respect to their service quality :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
[quote=alexwalker]Nicholas

I get this message when I try and upgrade Joomla via admin tools: "Could not download the Joomla! installation package. You have to update Joomla! manually".

Is there any way of making admintools work? It would make life a lot easier.


Same for me. I will have to continue to update J! manually. =(

[UPDATE] No, I found a better solution: change my host to Rochen ! :D[/quote]

Wait, what? I also use Rochen but am getting this same error. Did it work right away on Rochen? After installing admin tools and trying to run the upgrade, I get the "The archive file is corrupt, truncated or archive parts are missing" error.

yvesg
Yes, it worked right away on Rochen for me.

nicholas
Akeeba Staff
Manager
@sypl Are you on a MVS or fully managed server? On these case you get to configure the server environment yourself (as you have full access to the WHM and/or root access to the server). If this is the case, you can file a support ticket with Rochen so that they can check out if your firewall disables communications to joomlacode.org and www.akeebabackup.com over TCP ports 80 or 443.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
Neither, actually. Just plain old shared business hosting package: http://www.rochenhost.com/business-hosting

Does this preclude me from using the auto-upgrade feature? Any workarounds?

user18293
Yes, it worked right away on Rochen for me.


Are you on a shared hosting package like me too? Do you mind if I ask what settings you used?

Did you write directly to file or use the FTP? If FTP, what settings did you use? Writing directly to file didn't work for me so I tried all sorts of FTP configurations.

FTP Host name: tried both ftp://ftp.somerochensite.com and ftp.somerochensite.com
FTP Port: left this as 21
FTP Username: tried both someroch and [email protected]
FTP Password: just used whatever was appropriate pw for that account
FTP Directory to your site's root: tried absolute URLs like /home/someroch/public_html and FTP root paths, like /public_html. Not sure if I need preceding or trailing slashes.

yvesg
[quote=yvesg]Yes, it worked right away on Rochen for me.


Are you on a shared hosting package like me too? Do you mind if I ask what settings you used?

Did you write directly to file or use the FTP? If FTP, what settings did you use? Writing directly to file didn't work for me so I tried all sorts of FTP configurations.

FTP Host name: tried both ftp://ftp.somerochensite.com and ftp.somerochensite.com
FTP Port: left this as 21
FTP Username: tried both someroch and [email protected]
FTP Password: just used whatever was appropriate pw for that account
FTP Directory to your site's root: tried absolute URLs like /home/someroch/public_html and FTP root paths, like /public_html. Not sure if I need preceding or trailing slashes.[/quote]

Hello,

Yes, I'm on a shared hosting package (reseller hosting).

For the FTP Host name, just type somerochensite.com without ftp
FTP Port: 21
FTP Username: someroch
FTP Password: your ftp pw
FTP Directory: I left it blank

Cheers

nicholas
Akeeba Staff
Manager
OK, guys, you are doing something fundamentally wrong. If you are on a Rochen shared hosting plan, your server is using suPHP. This simply means that you are not supposed to use Joomla!'s FTP layer at all. You don't need it, it makes things more complex, will cause timeouts and generally add problems to your life without solving anything. SO, just disable the Joomla! FTP option in the Global Configuration.

FYI, our pre-release testing includes updating sites on Rochen's shared hosting plan. As you guessed, it does work during our tests without as much as a hiccup.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
OK, guys, you are doing something fundamentally wrong. If you are on a Rochen shared hosting plan, your server is using suPHP. This simply means that you are not supposed to use Joomla!'s FTP layer at all. You don't need it, it makes things more complex, will cause timeouts and generally add problems to your life without solving anything. SO, just disable the Joomla! FTP option in the Global Configuration.



FYI, our pre-release testing includes updating sites on Rochen's shared hosting plan. As you guessed, it does work during our tests without as much as a hiccup.


Hmm, odd. Seems like it's just not working then. I disabled the FTP layer and still get the same error.

I tried yvesg's setup too and that didn't work either.

nicholas
Akeeba Staff
Manager
Hm... I can't track it down to the general hosting setup, as I've run my tests on the same host, using the same kind of hosting package as you do. Can you please contact the Rochen guys and have them run an ownsership and permissions check on your site? I think that something is wrong regarding that, but I'd rather have them do the kind of check that you and I can't really do without SSH access to the site.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
I do actually have SSH access to the site. What kind of checks would you like me to run?

nicholas
Akeeba Staff
Manager
You could start by chown'ing all files and directories under public_html to your account's user and group. Then run the following two commands:
find path/ -type d -exec chmod 0755 {} \;
find path/ -type f -exec chmod 0644 {} \;

Alternatively, you can use the newly deployed Joomla! Utilities on Rochen's Control Panel to fix the permissions instead of running those commands (it essentially runs those commands using root access). If you get any error running any of these commands (especially the chown'ing part) you'll have to ask Rochen's support to do this for you.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
Well this is just maddening! I tried with a test install of Joomla and it upgraded fine every single time, no matter how I changed the configuration to reflect my install setup. Some things I tried:
- got rid of htaccess file
- changed database prefix
- moved config file out of web root
- changed directory names of tmp and log folders

... and they all upgraded fine! I suppose this is very good news for Akeeba, but I'm absolutely stumped as to why it won't work on my live site.

I used SSH to make those permission changes, but no luck there either.

nicholas
Akeeba Staff
Manager
Did you do the test installation on the same server as the one with the other site which has issues? If yes, please do contact Rochen's support and have them check the ownership of your account's directories. This is the only possibility we haven't covered and we can't do anything about without root access to the server.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
Figured it out, sort of. It appears to be a problem with the time zone settings in the global configuration. If I set it to +0800 (China time) if fails. Setting it to UTC makes it work fine. Probably an error with the archive extracting tool seeing an archive in the tmp folder that has an impossible date due to the time difference between sending server (Joomla's) and my own? Or perhaps even time difference between Rochen server and configured Joomla time zone. Any way of correcting this? It's not a huge deal to change timezone before updating, but obviously it's not ideal.

nicholas
Akeeba Staff
Manager
I tried creating a site with 1.5.20 on a Rochen server (US datacenter) and set the Joomla! timezone to GMT+8. I installed the latest Admin Tools and proceeded to upgrade the site to 1.5.21. It worked perfectly. I don't know why changing the timezone on your site made a difference. Do you have any other server protection application (e.g. component or plugin) installed on your site which might be filtering files based on their timestamp?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user18293
I just did the same thing and the update worked too. Must be something wrong with my current install of Joomla, but I'll darned if I know what it is now. Can't think of anything that I'm using that would cause changes in timestamps. Maybe it's something to do with my custom template, though I find it hard to see anything in there that would cause this error.

If it's of any use, here's a list of components and plugins I use (not complete, but others are either core of joomfish related):

components:
admin tools, akeeba backup, jce, joomfish, rsform!, xmap

plugins:
jch optimize

nicholas
Akeeba Staff
Manager
No culprit in that list of extensions as far as I can see. Next time you bump into such a site, please contact me. I'd like a first hand experience with such a server, in case I am missing something.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!